How to Fix Sticky Client WiFi Roaming: Stop Devices From Clinging to a Weak Access Point

If your phone shows two bars on a router downstairs while you’re standing right next to the router upstairs, you have a sticky client problem. Your device is clinging to a distant, weak access point instead of roaming to the stronger one a few feet away. This is one of the most common WiFi complaints in multi-AP homes and mesh networks — and it’s almost always fixable.

What Is a Sticky Client?

WiFi roaming is client-controlled. When you move through your home, your device decides when to disconnect from one access point (AP) and associate with another — the APs themselves have no authority to forcibly disconnect a client under the basic 802.11 standard. The problem: most devices are conservative. They stay connected as long as the signal is technically functional, even if a nearby AP would deliver far better performance.

The result is a device sitting at −75 dBm on a distant AP when a unit 10 feet away is broadcasting at −45 dBm. Speeds tank, video calls stutter, and gaming latency spikes — all because the device won’t let go.

Why Devices Get Sticky

Roaming decisions are made by the device’s WiFi driver and firmware. Manufacturers tune these algorithms differently. iOS devices typically roam when signal drops below roughly −70 dBm. Android devices vary wildly by vendor. Windows laptops, smart TVs, and IoT devices can be the worst offenders — some won’t roam until the signal is nearly unusable.

The core issue is the roaming threshold: the signal level at which a device decides to search for a better AP. If that threshold is set too low (or the device ignores it entirely), the device stays stuck.

Fix 1: Enable 802.11k, 802.11v, and 802.11r on Your Router

These three protocols — collectively called Fast BSS Transition or fast roaming — are the most important tools for solving sticky clients. Most modern routers and mesh systems support them, but they are sometimes disabled by default.

802.11k — Neighbor Reports

802.11k allows an AP to respond to a device’s scan with a curated list of nearby APs: their BSSIDs, operating channels, and signal data. Instead of scanning all possible channels to find a better AP (which takes seconds), the device can jump directly to the right channel in milliseconds. This dramatically speeds up roaming discovery.

802.11v — BSS Transition Management

802.11v gives the network a voice in roaming decisions. An AP can send a BSS Transition Management Request to a sticky client, essentially saying: “You should move to this other AP; it has a much better signal for you.” Compliant clients honor the request and roam immediately. This is the most direct fix for sticky clients in prosumer and mesh setups.

802.11r — Fast BSS Transition

802.11r speeds up the authentication handshake during a roam. Without it, every time a device moves to a new AP it must complete a full WPA2/WPA3 four-way handshake (50–100 ms), causing a brief audio or video glitch. With 802.11r, the device pre-authenticates with the target AP before disconnecting, cutting the transition to under 50 ms and making roams seamless.

To enable these: on ASUS routers, look under Wireless → Professional → 802.11k/v Roaming Assistant. On TP-Link Deco, enable Fast Roaming in the Deco app. On UniFi, toggle all three under Settings → WiFi → Advanced Options. Most modern mesh systems (Eero, Google Nest WiFi Pro, Orbi) enable 802.11r/k/v automatically and without user configuration.

Fix 2: Set a Minimum RSSI Threshold

Some routers and access points support a Minimum RSSI (or “Minimum Signal Strength”) feature. When a connected client’s signal drops below this threshold, the AP forcibly disconnects it, prompting the device to re-scan and associate with the nearest AP. This is the most aggressive — and most effective — fix for stubborn sticky clients.

Recommended starting values:

• −72 to −75 dBm: Good balance. Devices disconnect before signal degrades badly, but not so aggressively that they disconnect when briefly passing through a weak transition zone.
• −70 dBm: More aggressive. Use in homes with many APs and dense coverage overlap.
• −80 dBm: Conservative starting point. Helps with very sticky IoT devices that otherwise never roam.

On UniFi Access Points, this appears as Minimum RSSI under the AP’s wireless settings. On ASUS AiMesh, look for the Roaming Assistant threshold in Wireless → Professional. Note: setting the threshold too high (−65 dBm or above) can cause devices to disconnect unnecessarily in transition zones between APs.

Fix 3: Optimize Access Point Placement

Sticky clients are worse when AP coverage zones overlap too much or too little. If two APs have nearly identical signal strength across a large area, devices have no clear reason to roam — both look equally mediocre from the device’s perspective. Ideally, each AP should have a strong core zone with a clear fade at the edges:

• Place APs so their −67 dBm contour (the edge of “good” signal) just overlaps with the neighboring AP’s strong coverage zone.
• Avoid placing two APs in the same room or with clear line-of-sight to each other — this creates a large overlap zone where neither AP is clearly better.
• For a two-story home around 2,000 sq ft, one AP per floor is typically sufficient.

See our guide on WiFi roaming and access point handoffs for more detail on coverage planning and AP placement strategy.

Fix 4: Adjust Band Steering Settings

If your router broadcasts a unified SSID for both 2.4 GHz and 5 GHz, band steering tries to push capable devices to the faster 5 GHz band. However, aggressive band steering can interfere with roaming — a device that the system keeps pushing to 5 GHz may fight to stay on 2.4 GHz, causing re-associations that look like sticky client behavior.

If you’re experiencing roaming issues alongside band steering:

• Set band steering to “Prefer 5 GHz” (soft steering) rather than “Force 5 GHz.”
• Or disable band steering entirely and create separate 2.4 GHz and 5 GHz SSIDs to manually assign devices where needed.

Fix 5: Adjust Windows Roaming Aggressiveness

On Windows, roaming aggressiveness is often configurable at the driver level. Open Device Manager, expand Network Adapters, right-click your WiFi adapter, and select Properties → Advanced. Look for Roaming Aggressiveness and set it to Medium or High. For Intel WiFi adapters specifically, this setting has a direct and measurable effect on how quickly the device scans for a better AP.

On macOS, roaming behavior is controlled by the OS and cannot be tuned directly. Keeping macOS updated ensures you have Apple’s latest roaming algorithms. For iPhones and iPads, iOS uses a fixed threshold near −70 dBm — enabling 802.11k/v on your router is the most effective way to help Apple devices roam faster and more reliably.

Checking Whether Your Fixes Worked

After making changes, walk around your home while running our speed test tool on your device. Check which AP your device is connected to using your router’s client list — you should see the association shift as you move between coverage zones. Speeds should remain consistent without the sharp drop-offs that indicate a sticky association persisting past its useful range.

For deeper diagnostics, a WiFi analyzer app like the one described in our WiFi analyzer guide will show you the exact RSSI and which BSSID your device is connected to in real time, making it straightforward to confirm that roaming is happening at the right moment.