Designing Seamless Wi-Fi Roaming Across UniFi Access Points

Have you ever walked from a conference room back to your desk on a video call, only to watch the stream freeze for a beat halfway there while the signal bars never budged? That stall is rarely a coverage problem, and bolting on another access point seldom fixes it by itself.

The uncomfortable reality of Wi-Fi is that your access points do not decide when a client roams to a better one. The device does, and most laptops and phones are stubborn about letting go of a connection they already have.

This is why roaming is a design problem in its own right, separate from picking the right hardware. If you have already worked through choosing the right UniFi access point and mounted a few of them, the next job is tuning how a client moves between them.

The applications that expose roaming failures are the real-time ones, from voice calls to video conferencing to anything holding a persistent session. Email and web browsing survive a rough handoff, but a Teams call or a warehouse scanner session does not.

Get that tuning wrong and you end up with excellent coverage and terrible handoffs. Get it right and a device walks the length of the building without a single dropped packet the user can feel.

Every client tracks the signal strength of its current access point as an RSSI value, measured in negative dBm, where closer to zero is stronger. A reading near -50 dBm is excellent, roughly -67 dBm is the practical floor for smooth voice and video, and past about -75 dBm the connection starts to struggle.

The catch is what the device does with that number. Most clients will hold onto an access point down to -80 dBm or worse, long after a closer AP would serve them better, simply because the current link technically still works.

This is the sticky client problem, and it is the single most common cause of bad roaming on an otherwise healthy network. The client sits at the edge of one cell, retransmitting frames and dragging down its own throughput, while a stronger AP sits idle two rooms away.

You can watch this happen in the UniFi Network client list, where a device shows a weak RSSI and a low negotiated data rate while joined to a distant AP. That is your cue that the roaming design, not the coverage, is what needs work.

Keep in mind that the access point has almost no authority here. Short of a few nudges we will get to shortly, it cannot force a device off, and it can only make staying put unattractive enough that the client chooses to leave.

The design lever you actually control is cell overlap. Neighboring APs should overlap by roughly 15 to 20 percent of their coverage area, enough that a client always has a clearly stronger option nearby before its current signal degrades to the point of pain.

Before you touch any of these numbers, it helps to know your actual coverage rather than guess at it. A quick site survey with a Wi-Fi analyzer app, or the RF environment view in the UniFi Network application, shows you where cells overlap and where dead zones hide.

The instinct when a corner of the building runs weak is to crank every access point to maximum transmit power. That almost always backfires, because a client hears the loud AP from far away and clings to it well past the point where roaming would help.

High TX power also inflates each cell until neighboring APs on the same channel start talking over each other, a condition called co-channel interference. The counterintuitive fix is to lower TX power so cells stay tight and clients are encouraged to roam to whichever AP is genuinely closest.

In the UniFi Network application, set the 2.4 GHz and 5 GHz radios to a fixed medium power rather than auto or high, then walk the space with a signal meter and adjust. The goal is a handoff zone where signal from the old AP falls off just as the new one rises.

The second lever is Minimum RSSI. When enabled on a UniFi AP, it sets a threshold below which the access point disconnects a client, forcing it to reconnect, ideally to a stronger neighbor.

A common starting point is around -75 dBm, then tune based on your floor plan and how devices behave. Set it too aggressive, say -65 dBm, and you will kick clients that had no better option and cause the very drops you were trying to prevent.

Minimum RSSI only works well when there is genuinely a better AP to catch the evicted client, which loops straight back to overlap and placement. It is a scalpel for sticky clients, not a substitute for sound cell design.

None of this holds together without a clean channel plan. On 2.4 GHz, stick to the three non-overlapping channels — 1, 6, and 11 — and keep channel width at 20 MHz; on 5 GHz, spread APs across non-overlapping channels and consider enabling DFS channels for more room.

A single SSID broadcast on every band and every AP is the foundation of roaming, because a client can only roam between radios that share the same network name and security settings. But a shared SSID also means dual-band devices need help choosing the faster radio.

Band steering nudges capable clients off the crowded, long-range 2.4 GHz band and onto 5 GHz, where there is far more spectrum and less interference. UniFi exposes this as a band steering toggle on the WiFi network, and for most modern device fleets it is worth enabling.

The tradeoff is that 5 GHz does not travel as far or punch through walls as well as 2.4 GHz. Steer too hard and a device at the edge clings to a weak 5 GHz signal instead of dropping to a solid 2.4 GHz one, so pair band steering with sane TX power and overlap.

One more radio-side lever is the minimum data rate control in UniFi. Disabling the slowest legacy rates — the old 1, 2, and 5.5 Mbps rates — stops a distant client from clinging at a crawl and nudges edge devices to roam sooner.

If you are running WiFi 6E or WiFi 7 access points, the 6 GHz band adds a third, cleaner lane with even more non-overlapping channels. It is excellent for high-density areas, though its shorter range makes overlap and placement matter even more than on 5 GHz.

Many networks broadcast more than one SSID, with a corporate network, a guest network, and an IoT network being a common trio. Plan those deliberately, because each extra broadcast SSID adds airtime overhead to every AP, and our guide to UniFi VLANs covers segmenting them cleanly.

Three amendments to the Wi-Fi standard exist specifically to make roaming faster and smarter, and UniFi supports all three. They do not force a stubborn client to roam, but they dramatically improve the experience once it decides to.

Here is what each one actually does:

• 802.11k, Neighbor Reports. The AP hands the client a list of nearby access points and the channels they sit on, so the device skips a blind full-spectrum scan when it looks for a better AP. That shortens the time a client spends hunting for a target.
• 802.11v, BSS Transition Management. The network can politely suggest that a client move to a specific, better access point. It is a recommendation rather than an order, but cooperative clients act on it.
• 802.11r, Fast BSS Transition. This caches the security keys from your initial authentication so re-associating to the next AP skips most of the handshake. On a WPA2 or WPA3-Enterprise network running 802.1X, that is the difference between a barely-noticeable blip and a multi-second stall.

In UniFi, these live behind the Fast Roaming and BSS Transition toggles in the WiFi settings. Enable them together, because k and v help the client choose where to go while r makes the actual jump cheap.

There is one caveat worth respecting. A small number of older or poorly-implemented client devices handle 802.11r badly and may fail to connect, so if you support a mixed fleet of legacy hardware, turn fast roaming on and then test your problem devices before rolling it out everywhere.

Even with all three enabled, the client remains the final decision-maker. These standards make roaming cheaper and better-informed, but a truly stubborn device still needs Minimum RSSI or cell design to pry it loose.

For a modern fleet of recent laptops and phones, the trio is close to free performance. For an environment full of aging IoT gear or industrial handhelds, treat it as something to validate rather than assume.

Seamless roaming is the product of several settings working together, not one magic switch. The order matters, because each layer assumes the one beneath it is already sound.

Here is a sane order to work through it:

1. Place and power for overlap first. Position APs so cells overlap 15 to 20 percent, and set TX power to a fixed medium level rather than maximum.
2. Lay down a clean channel plan. Use channels 1, 6, and 11 on 2.4 GHz at 20 MHz width, and spread 5 GHz APs across non-overlapping channels.
3. Unify the SSID and enable band steering. Broadcast one network name across every AP and band, and steer capable clients toward 5 or 6 GHz.
4. Enable the fast-roaming trio. Turn on 802.11k, v, and r together, then test any legacy clients before you rely on it.
5. Tune Minimum RSSI last. Start around -75 dBm and adjust only after overlap and placement give evicted clients somewhere better to land.

Notice that Minimum RSSI comes last, not first. It is the most tempting setting to reach for and the most likely to cause self-inflicted drops when the underlying cell design is not already there.

The hardware underneath still sets the ceiling, of course, since PoE budget, uplink capacity, and the right AP model for the space all bound what tuning can achieve. If you are still sizing that layer, our guide to choosing a UniFi switch for PoE headroom and the full lineup of UniFi access points will get the foundation right.

Finally, roaming is not set-and-forget. After you tune it, watch the client list and event log for repeated disconnects or clients parked on a far AP, and revisit the settings when you add access points or the floor plan changes.

Roaming is one of those problems that stays invisible when it works and dominates every support ticket when it does not. Spend an afternoon walking your floor plan with these five layers in mind, and the frozen-video-on-the-way-to-your-desk problem quietly disappears.