I've added a second satellite to my Orbi network and had it in situ for a month or so but I notice that the system seems a bit dimwitted when moving around the house, very often leaving devices on the farthest satellite from where you are.
As an example, moving from the office to the garden at extremes of the house, leaves my phone on the satellite closest to the office, but the connection speed in the garden is virtually non-existent, though the phone is still able to connect to the satellite (albeit with what looks like a lower number of bars showing on the Orbi app)), hence I added a satellite in the kitchen, which is closest to the garden.
When connected to the kitchen satellite, u/l and d/l speeds are as expected, it just seems really slow swapping the device between satellites - I often have to flip the wifi off/on on my phone to get it to jump over.
Anyone else having similar issues? It doesn't seem to be fw related as have updated to the latest since adding the 2nd satellite.
Running V2.5.1.16 on RBR50 (in router mode in the grnd floor front room), RBS50 x2 (one upstiars on 1st floor landing, second in kitchen on grnd floor at the rear)
Daisy Chain is off, Beamforming on, MU.MIMU off, Fast Roaming off (could this be issue - though I think it relates more to enterprise WPA?). Or, could I fiddle with the transmit power, would this help, I'm guessing we have too much overlap between the three devices?
Any thoughts, even if just, 'that's the way it is mate', appreciated.
Re: Orbi slow switching devices between satellites
Fast Roaming must be enabled. In general, the 802.11 Working Group standards k, r, and v let clients roam more seamlessly from access point (AP) to AP within the same network. 802.11r is indeed for the business networking with WPA2 Enterprise - correct designation is "Fast BSS Transition (FT)" so not available on most consumer, SOHO and SMB wireless systems.
If you disable Fast Roaming here, the clients will stick with the BSSID (the named radio connection from one AP/radio) until the connection does fall under the typically very low signal level and quality. This behaviour is named sticky client.
