Client devices decide when to roam, so a phone may cling to a usable distant node. Excessively close mesh points, transmit power and stale client state can worsen it. Use the mesh app to see which node the phone uses and compare signal as you walk.
Differential
Likely causes of “Devices stay connected to a far-away mesh node”, and how to tell them apart
- 1
The client decides when to roam and holds on to a distant node
What separates it A phone stays on the first node while you walk to another room and the signal falls, and it roams only when the connection nearly fails.
How to confirm Use the mesh app to see which node the phone uses and compare signal as you walk.
- 2
Nodes are too close together, so signal overlaps everywhere
What separates it Devices see several nodes at high strength and pick one poorly, and the nodes are only a room apart.
How to confirm Space the nodes farther apart and see whether the handoff improves.
- 3
The client's Wi-Fi state is stale
What separates it A device holds an old connection after sleep and only roams after Wi-Fi is switched off and on.
How to confirm Toggle Wi-Fi on the client once and see which node it picks.
- 4
Outdated firmware on the mesh or the client
What separates it Roaming problems appear on one device type and improve after an update.
How to confirm Update the mesh and the client and repeat the test.
Before you touch a setting
Record this first — changing settings destroys the evidence
- Which node a device connects to at several points as you walk the house.
- The distance and materials between nodes.
- The firmware versions of the mesh and the device.
Try in this order
0 of 4 completedCapture the exact symptom
ReversibleUse the mesh app to identify the connected node and compare signal while walking between rooms.
Run the smallest isolation test
ReversibleToggle Wi-Fi on the client for one test, space nodes farther apart and update both client and mesh firmware.
Correct only the proven cause
ReversibleRemove redundant nodes or use supported steering/fast-roaming settings only if problem clients support them.
Verify before changing anything else
ReversibleWalk the route during a call and confirm handoff no longer causes a noticeable stall.
Stop boundary
When this stops being a self-service repair
- !Use supported steering or fast-roaming settings only if the problem devices support them, since some older clients handle them badly.
Evidence ledger
Sources behind this answer
Exact questions
Common questions
Why does my phone stay on the far node?+
Phones decide for themselves when to roam and often hold a usable connection for as long as they can. Spacing nodes and toggling Wi-Fi are the usual fixes.
Why does a device stay on a far node?+
Devices decide when to roam and may cling to the first signal.
Can I tune roaming?+
Some systems have steering options.