Wi-Fi Drops When You Walk Between Rooms: Roaming Explained

You start a call at your desk, walk to the kitchen, and three sentences disappear. The podcast stops halfway down the hallway and resumes ten seconds later in the bedroom. Nothing is broken — you are watching a handoff, and your device is making it badly.

Here is why phones cling to a radio that has stopped being useful, what 802.11k, v and r change, and how to arrange coverage so the switch lands in a corridor instead of mid-sentence.

One radio at a time, and the switch is not free#

Your device is associated with exactly one radio at any moment — one BSSID — even when the router, the extender and every mesh node broadcast the same network name. Moving between them is not a fade. It is a sequence: notice the link is bad, scan for alternatives, pick one, authenticate, re-associate, get an address, resume.

That sequence has four speeds, and you can feel which one you got.

The last two rows are what sent you searching, and neither is a hardware fault. The decision to leave a radio belongs to the client, not to your network.

Why your phone hangs on to a dying radio#

Scanning is expensive. To look for something better, a client keeps leaving its current channel for tens of milliseconds at a time, across dozens of channels — costing throughput on the link you are using and draining the battery. So devices are lazy on purpose:

• A trigger level. Most clients do not start looking until the current radio degrades to roughly -70 to -75 dBm. Plenty hold on past -80 dBm.
• Hysteresis. Having found a candidate, many want it 8 to 12 dB stronger before committing, because the switch itself costs an interruption.
• Idle wins. A phone that has not sent a packet in ten minutes has had no reason to reconsider anything.

Two quirks make this worse in a real house. Direction matters: walking toward the router while still attached to a far node gives you a relayed link while you stand next to the source. And 2.4 GHz typically reads 4 to 8 dB stronger than 5 GHz at the same spot, so a phone that fell back to it sees a comfortable number, feels no pressure, and quietly gives up most of its speed — how the three bands compare on range is a decision of its own.

802.11k, v and r, in plain terms#

Three standards attack three parts of the delay. Current mesh kits usually implement all three; a router with a separate extender often implements none, because the two boxes never talk about your phone.

Four caveats. Both ends must support them, so an older laptop or a budget smart display behaves as before. 802.11v suggests rather than compels, and stubborn clients ignore it. 802.11r has a history of upsetting older gear — if a printer stops joining after you turn on fast transition, that is why. And none of the three create coverage: steering your phone from one weak radio to another fixes nothing.

Design the overlap so the handoff lands in a hallway#

The most useful figure in this article: neighboring coverage should meet at around -67 dBm.

Work through why. Your phone will not consider leaving until its link falls to about -70 to -75 dBm, and it wants the alternative 8 to 12 dB better. If two radios only meet at -80 dBm, then at the moment your phone becomes willing to move, everything it can see is also at -80 dBm. There is no better option, so it rides the bad link down. That valley is the whole problem, and placement creates it.

Set the boundary at -67 dBm and the arithmetic flips: by the time the old link reaches the trigger level, the neighbor is comfortably stronger than the margin your device demands.

The consequence surprises people: nodes belong closer together than feels necessary. As a rule of thumb, one access point per 1,000-1,500 sq ft in open, timber-framed construction, and one per 700-1,000 sq ft in brick, block or plaster and lath. Node counts and the chain-not-star layout belong to the mesh node placement guide.

Every pair of radios has a boundary somewhere. You do not get to delete it — only to choose which room it lands in.

• Aim for hallways, landings, stairwells and doorways. A gap you walk through in three seconds is a gap you never notice.
• Never leave the boundary across a desk, a sofa or a bed. Signal wanders 3 to 5 dB while you sit perfectly still, so a laptop parked on the boundary flips back and forth all afternoon — the classic cause of calls breaking while you are not moving.
• Know your resolution. Doubling the distance in open air costs about 6 dB; an ordinary interior wall costs 3 to 8 dB at 5 GHz. Moving a node one room shifts the boundary by roughly one of those steps, which is why position beats settings.

Fix it in your own house#

1. Name the route, not the room. "Desk to kitchen, always at the doorway" is data. "Wi-Fi is bad" is not.
2. Find out which radio you are on at each end of that route. Android shows the BSSID in the network details, and most router or mesh apps list which node each client is attached to. The crude version: unplug the far unit for thirty seconds and see whether the device drops.
3. Walk the route with a continuous ping running to your router's own address. One to three seconds of loss is an ordinary re-association; five to twenty is a full re-authentication; a gap that never recovers until you toggle Wi-Fi is a client that gave up.
4. Measure the valley. Stand where the gap happened and compare both radios. If the near one reads about -70 dBm and the far one is no better, that is the hole. Move the far unit one step toward the router — counterintuitive, and usually the fix.
5. Turn on the network-side helpers. Look for "802.11k/v/r", "fast roaming", "AP steering" or "smart connect". If your gear also offers a minimum RSSI setting, keep it near -75 dBm; set it closer to zero and devices at the edge of the house loop endlessly.
6. Stop trying to make stationary devices roam. A TV, desktop or console has no reason to move, so pin it to one radio instead — the same-name-or-separate decision covers how.
7. Retest with the thing that failed, walking the route on a real call rather than running a speed test.

When roaming is not the problem#

Four faults get misfiled as bad roaming, and each one costs money to get wrong.

• It drops while you stand still. That is interference or congestion, not a handoff. A DFS radar event on 5 GHz also boots every client off the channel for a minute or so. Start with what interferes with Wi-Fi at home.
• You only have one router. Then there is nothing to roam to and you are walking out of range — a coverage problem, described in why one room has no signal.
• You were about to add a third radio. An extender in a house that already roams badly gives your phone one more mediocre option, not fewer bad ones, and a single-radio unit roughly halves throughput for everything behind it.
• The route crosses concrete or a masonry core. Reinforced concrete costs 15-25 dB one way, and no roaming setting survives that. The answer is carrying the link over coax or Ethernet, which turns the far radio into a real access point instead of a relay.

Decide where the boundary lands before you move anything#

Walking a unit from outlet to outlet and repeating the ping test is a slow way to search a house. Range Up does the searching on a drawing. Sketch the layout, set the material preset to the way the house is built — wood frame, brick or concrete — put the router where it truly stands, and it paints the coverage that geometry produces, room by room. Add a second radio at a spot you could actually use, then step between the before and after maps: the strip dividing the rooms that improve from the rest is the handoff zone your call keeps dying in. Nudge the candidate, watch that strip travel with it, and stop when it lands where nobody sits.

What this settles is geometry — whether a second radio has any position that produces a clean boundary, and which one. It works from the building rather than from your live network, so the walk test stays yours to run and the 802.11k/v/r switches stay in your router's app. Download Range Up to try the layout half, or read how placement is planned on a floor plan first.