Most people blame the router when mesh Wi-Fi feels slow. Often the real culprit is the device in your hand. Phones, laptops, and tablets decide which node to connect to, and they often refuse to switch even when a closer node is sitting right there. The industry calls this the sticky client problem.
It exists on cheap Wi-Fi extenders and on expensive mesh systems alike. Once you understand why it happens, the speed complaints start to make sense, and so does what to do about them.
What happened
- Sticky client behaviour happens when a device clings to a distant or weak Wi-Fi node instead of switching.
- Your device, not the router, decides which node to connect to and when to switch.
- Apple publishes guidance: iPhones wait until the signal hits -70dBm before scanning for a new node.
- Mac is even more patient, waiting until -75dBm before looking for something better.
- Apple's rule says a new node must be 8dB to 12dB stronger than the current one before the device switches.
Why devices refuse to switch
Phone and laptop makers engineer devices to keep connections stable rather than chase a stronger signal. Every switch means disconnecting and reconnecting, which can cause a hiccup in a video call or a stutter in a stream. The trade-off leans toward stability, even when stability means staying connected to a weak node.
Eero's own support page acknowledges this directly, stating that client steering offers no promise your handset will hop to the faster band or the nearest satellite. That's not a flaw specific to eero. It's an industry-wide pattern.
The signal math, with Apple's own numbers
Wi-Fi signal strength is measured in negative dBm. Closer to zero is stronger. A reading between -50dBm and -60dBm is good; between -60dBm and -67dBm is decent for video calls and streaming.
Apple has put its roaming rules on paper, and they explain a lot. Per those pages, an iPhone or iPad will not start hunting for a stronger satellite until the existing signal falls to -70dBm. A Mac holds out longer, staying put until the reading hits -75dBm. On top of that threshold, the replacement node must outdo the current one by between 8dB and 12dB.
Work through the idle case. Your iPhone's reading drifts to -72dBm, past the trigger, so it begins scanning for a stronger satellite. Under the strict 12dB rule, a candidate has to come in at -60dBm or stronger to qualify. If the node sitting ten feet away is delivering -65dBm, your phone ignores it and keeps the old link. On an active video call the bar eases to 8dB, which still demands -64dBm or better from the next satellite. A node 7dB cleaner than your current connection is close enough to see, and the device still won't bite.
The takeaway is that devices are conservative by design, sometimes to a fault.
Our analysis
Sticky client behaviour is built into how consumer devices prioritise stability over performance. It's not a bug in any one mesh system. It's a side effect of Apple, Samsung, and every other device maker deciding that dropped calls are worse than slow Wi-Fi.
The practical implication is that mesh Wi-Fi marketing often overstates real-world performance. A three-node system can blanket a home on paper and still leave a sticky device clutching a hallway node from two rooms away. Once you accept that, the workarounds make sense: turn off band steering on the router, give the sticky device its own SSID, force a manual disconnect when needed, and accept that some devices just won't roam well.
The wider question is whether mesh vendors will finally ship aggressive client steering that overrides the device's tendency to stay put. Some enterprise gear already does this. Consumer gear like eero is moving in that direction but hasn't arrived.
What it means for you
Say you're on a video call in the living room and your mesh system has a node in the kitchen and one upstairs. Your phone latched onto the upstairs node when you were upstairs, and now it won't drop it. Try toggling Wi-Fi off and back on to force a re-scan, or forget the network and reconnect. If that's a daily annoyance, give that device its own SSID on the closer node and don't expect the mesh to handle roaming for you. Run a quick signal check with a Wi-Fi analyser app to see whether the closer node is actually delivering a better number.
What to watch next
Two things to watch. First, whether mesh vendors ship more aggressive client steering that overrides device preferences the way enterprise gear does. Second, whether Apple and Google loosen their dBm thresholds in future OS updates. Bottom line: sticky clients aren't a flaw in any one mesh system; they're a feature of every phone in your house. Plan around them and your Wi-Fi will feel faster tomorrow.
Key takeaways
- Phones, laptops, and tablets choose their Wi-Fi node, not the router, and they often refuse to switch.
- Apple's published roaming rules say devices wait until -70dBm (iPhone) or -75dBm (Mac) before looking for a stronger node.
- A new node must beat the current signal by 8dB to 12dB before the device switches, per Apple's documentation.
Frequently asked questions
What is the sticky client problem?
It's when a device clings to a weak or distant Wi-Fi node instead of switching to a closer, stronger one, as described by How-To Geek.
How low does my iPhone signal need to drop before it looks for a better node?
-70dBm, according to Apple's Wi-Fi roaming documentation cited by How-To Geek.
Does the router or the device decide which mesh node to use?
The device decides. Your phone, tablet, or laptop picks the node and chooses when to roam.
Can I force my phone to switch mesh nodes?
Yes. Toggling Wi-Fi off and on, or forgetting the network and reconnecting, will force a fresh scan.