RSSI Threshold Ignored
I've been experiencing issues with smart devices connecting to VERY FAR away APs and getting signal levels in the -85+ range. I have set an RSSI threshold on the AP's to -75, and confirmed that there is good signal (usually -60ish) available for the device to connect to a different AP, but for some reason they keep insisting on connecting to the AP's with really low signal. Fast roaming and AI roaming are both enabled. Forcing a re-connect rarely solves the issue (even doing it dozens of times!). I've tried locking to AP's, but then the device just doesn't connect at all. Sometimes a reboot of a specific AP that has higher signal at the device resolves the issue, but not always. I do NOT want to have to set up 12+ SSID's for the network just because this is an issue. Are there other options/things I can try to resolve this?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I had the same problem but I use rate control, it works pretty well. Even if the signal is bad the speed should be at least 24 Mbps and that is good enough for most IoT devices.
if the speed is not 24Mbps, the device roams to another access point
- Copy Link
- Report Inappropriate Content
@MR.S Quite a number of my IoT devices negotiate 1-6Mbps speeds when they're idle and have good signal (~-60's).... Wouldn't forcing them to connect/roam at a higher speed like that just create a bunch more chatter on the network?
- Copy Link
- Report Inappropriate Content
In general, I know most vendors mini rssi isnt pin point. It's usually off by a bit.
I also know it matters on your AP and if the controller version / AP firmware support its. I know my 615-IW just recently supported it, like this year.
I usually set my a tad lower -73 and by the time it hit -75 it drops.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@dononeil What does your LOG show you for the client device? Does it roam and change AP's often? Is it trying to connect at 5 GHz at -80 dBm, while 2.4 GHz is available at -70 dBm? Some devices like TV streaming sticks seem to prefer a weaker 5GHz signal before they downgrade to 2.4 GHz. You can also see logs of failed connection attempts. The client device plays the largest role deciding how it connects or roams. Locking to an AP doesn't solve, as the device attempts a connection, gets rejected, goes somewhere else, tries to come back... watch the logs how that works out.
Get really good with the logs. They are not comprehensive. There are search features to help cull the problem device and understand what is going on with it. Share what you find into this thread. I've found that some devices have poor roaming implementations. See how a different device/manufacturer associates from that same location. Use WiFiMan or similar to see what your phone does from that same location. Analyzing RSSI and device associations would become more of an AP category, than under controller.
Good luck!
RF Dude
- Copy Link
- Report Inappropriate Content
@RF_Dude All of the devices that are having this problem are 2.4 GHz IOT only devices. They don't roam, they just connect to the first AP and stay there, no matter how many times you try to reconnect them. I never see a roaming message in the logs. The only way to get them to not connect to the distant AP is to physically shut that AP off so they are forced to connect to another one. It's obviously a problem with the roaming function, whether on the AP or on the device I can't say.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 182
Replies: 6
Voters 0
No one has voted for it yet.