Direct answer
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.
What this covers
- The observed symptom matches this record
- Customer-accessible settings, connections and external components
- Diagnosis before reset, deletion or component replacement
What it does not cover
- ×A model-specific error code with a different documented meaning
- ×Internal electrical, battery-cell, gas, refrigeration or sealed-component repair
- ×A guarantee that every model exposes the same control label
Capture 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.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Exact questions
Common follow-ups
What should I check before resetting anything?+
Use the mesh app to identify the connected node and compare signal while walking between rooms.
What is the safest isolation test?+
Toggle Wi-Fi on the client for one test, space nodes farther apart and update both client and mesh firmware.
When should I stop troubleshooting?+
Do not split bands or clone networks solely to force one client unless the mesh vendor recommends it.
Answer for the exact device and software version shown above.