Post by @jimsalter@fosstodon.org

2026-08-18 17:28 UTC

Each and every one of those is an Apple Mobile device which refused to disassociate from one AP and associate with another, closer AP when its user walked from one room to another. TX is low on all APs. All APs have a very robust minRSSI set. iDevices are the *only* devices I've ever seen refusing to roam like this. Everything else on site, from IoT garbage through Android phones to laptops and more, roams freely and easily as their users do.

Replies (3)

@kmh@hachyderm.io 2026-08-18 18:02

@jimsalter@fosstodon.org is this because most other devices have more strict trigger thresholds? “Know the trigger threshold for Apple devices: The trigger threshold is the signal level (in decibel-milliwatts) at which a client begins scanning for a better connection. Mac computers use –75 dBm and iPhone and iPad devices use –70 dBm as the trigger. Therefore, for example, if you design 5 GHz cells with a –67 dBm overlap, the devices remain connected to the current basic service set identifier (BSSID) longer than you expect. When the threshold is crossed, the devices initiate a scan to find roam candidate BSSIDs for the current wireless network’s identifying name (ESSID).” https://support.apple.com/guide/deployment/optimize-your-wi-fi-networks-dep2af1caf35/web

Open ##5401824
@nowherefast@techhub.social 2026-08-18 18:14

@jimsalter@fosstodon.org I noticed similar behavior at a customers Unifi installation. Of course there were only two dozen devices so I did not want to blame Apple devices prematurely.

Open ##5401826
@feoh@oldbytes.space 2026-08-18 18:56

@jimsalter@fosstodon.org Noticed this too. I feel like Apple is getting more and more blasé about this kind of subtle but important technical detail. I swear they’ve decided they just aren’t going to cater to highly technical people anymore. Sad.

Open ##5401831