WiFi Roaming Threshold Explained: How to Tune Your Router’s RSSI Kick Level So Devices Switch Access Points Faster in Multi-AP Homes

If your phone shows a strong WiFi signal but speeds are sluggish, or your laptop drops a video call the moment you walk from one room to another, you are almost certainly dealing with a sticky client. The device has latched onto a distant access point and refuses to hand off to the closer one — even though the closer AP would deliver 3× the throughput. The fix is tuning your router’s roaming threshold, also called the RSSI kick level. This guide explains exactly what that setting does, what values to use, and how to configure it on the most common home and prosumer hardware.

What Is a Roaming Threshold?

In a multi-AP home — whether you have a mesh system like eero or Deco, a set of wired access points, or an ASUS AiMesh setup — each access point independently broadcasts the same network name (SSID). The decision about which AP a client connects to, and when it switches, is controlled almost entirely by the client device, not the router. This is the core of the sticky client problem: a phone that associated with your living-room AP at full signal will often keep that association even after you walk into the bedroom next to a different AP, because switching costs battery power and brief disruption, so client firmware tends to prefer stability over optimization.

The roaming threshold (or minimum RSSI setting) is the tool APs use to override client stubbornness. When a connected device’s signal drops below the configured threshold, the AP takes action — either politely suggesting the client move, or forcibly deauthenticating it so it has no choice but to reconnect, ideally to a stronger AP. Our guide on WiFi client roaming aggressiveness settings covers the client-side half of this equation on Windows, Android, and Mac.

RSSI Values: What the Numbers Mean

RSSI is measured in dBm (decibels relative to one milliwatt), always expressed as a negative number. A signal closer to zero is stronger; a signal further from zero is weaker:

• −30 to −60 dBm: Excellent — you are in the same room as the AP.
• −60 to −70 dBm: Good — solid throughput, two or three rooms away.
• −70 to −80 dBm: Fair — speeds begin to drop; modulation rate steps down.
• −80 to −90 dBm: Poor — frequent retransmissions, noticeable lag.
• Below −90 dBm: Unusable — connection is unreliable.

Default client roaming thresholds vary by manufacturer. Android devices typically begin scanning for a better AP around −65 dBm by default. iPhones and iPads tend to hold connections until around −70 to −75 dBm. Windows laptops with Intel adapters default to medium roaming aggressiveness, which corresponds roughly to a −70 dBm trigger. These defaults are conservative — which is why sticky clients are such a common complaint in multi-AP homes.

Hard Kick vs. Soft Kick

APs can push clients to roam in two fundamentally different ways:

Hard Kick (Minimum RSSI Disassociation)

The AP forcibly deauthenticates the client when its RSSI drops below the threshold. The client receives a deauth frame and has no choice but to disconnect and scan for a new AP. This is blunt but effective — the client will reconnect to the strongest available AP in most cases. The downside: the reconnection takes 50–300ms, which is perceptible in a video call or active game session. If the threshold is set too aggressively, a device that legitimately moves back and forth between zones will disconnect repeatedly.

Soft Kick (BSS Transition Management — 802.11v)

The AP sends an 802.11v BSS Transition Management frame — essentially a polite request for the client to move, accompanied by a list of neighbor APs ranked by signal strength. The client receives this and, if it supports 802.11v, initiates its own roam to the recommended AP. This produces a faster, cleaner handoff than a hard kick because the client can pre-authenticate to the new AP before disconnecting from the old one. The downside: not all clients honor the request, and a stubborn device may ignore the suggestion entirely. Our guide to 802.11r/k/v roaming protocols covers how these work together.

Recommended Threshold Values

The right threshold depends on your home layout and device behavior. Start with these values and adjust:

• −65 dBm: Aggressive. Clients are kicked while still at decent signal. Use this if your devices are notoriously sticky and your APs are densely placed (every 20–30 feet). Risk of oscillation if a device sits exactly on the threshold boundary.
• −70 dBm: The recommended starting point for most homes. ASUS uses this as its default Roaming Assistant value. Clients get kicked when signal is fair-to-poor, with enough signal remaining that the reconnect completes cleanly before the connection degrades further.
• −75 dBm: Conservative. Good for IoT devices like smart displays, cameras, and thermostats that rarely move and handle reconnects poorly. Reduces disruption but still prevents clients from clinging at truly weak signal levels.
• −80 dBm: Too lenient for most multi-AP setups. Only useful as a safety net to disconnect clients that have completely lost signal rather than as a proactive roaming trigger.

How to Configure the Roaming Threshold by Brand

ASUS Routers and AiMesh

ASUS calls this feature Roaming Assistant. To enable it: log into the router at router.asus.com, go to Advanced Settings › Wireless › Professional. Scroll to Roaming Assistant and set the threshold (default: −70 dBm). Enable it on every band (2.4 GHz and 5 GHz tabs separately) and on every AiMesh node through the same interface. ASUS’s implementation uses a hard kick by default. For most homes, start at −70 and tighten to −65 if stickiness persists.

TP-Link Omada Business APs

In the Omada Controller, navigate to Settings › Wireless Networks › [SSID] › Advanced. Enable Minimum RSSI and set the threshold. Optionally enable Force Disassociation to hard-kick clients rather than just sending a BSS Transition suggestion. TP-Link recommends starting at −75 dBm for mixed environments and tightening to −70 dBm if clients remain sticky. TP-Link Deco home mesh systems handle roaming automatically via AI steering and do not expose a manual RSSI threshold in the consumer app.

Netgear Orbi and Nighthawk

Consumer Orbi mesh systems manage roaming automatically and do not expose a configurable RSSI threshold. Netgear Insight-managed business APs offer a Client Threshold setting under wireless profile advanced options. If you are on a consumer Orbi and experiencing sticky clients, the most effective workaround is ensuring Band Steering is enabled in the Orbi app under WiFi settings, and that 802.11k/v is active (it is by default on Orbi 700 series and newer).

UniFi (Ubiquiti)

UniFi uses a feature called Roaming Assistant (not to be confused with ASUS’s same-named feature). In the UniFi Network application, go to Settings › WiFi › [Network] › Advanced and enable Minimum RSSI. Set the threshold in dBm. UniFi distinguishes between a soft kick (BSS Transition frame only) and a hard kick (deauthentication). For dense deployments, −70 dBm with hard kick is the common recommendation from the UniFi community. Also ensure that Fast Roaming (802.11r) is enabled, which cuts handoff time from ~300ms to under 50ms for supported clients.

Avoiding the Threshold Oscillation Problem

The biggest mistake when tuning roaming thresholds is setting them too aggressively in a home where AP coverage zones overlap significantly. If your living-room AP and bedroom AP both cover the hallway at −68 dBm, and your threshold is −65 dBm, a device standing in the hallway will be kicked back and forth between the two APs in a loop — reconnecting every few seconds. To prevent this:

• Use a hysteresis margin. Some implementations (UniFi, Omada) let you specify that a client must see the target AP at least 5–10 dBm stronger than the current AP before the kick is issued. This prevents oscillation in overlapping zones.
• Set the threshold 5–10 dBm weaker than your overlap zone. If your APs overlap at −60 dBm in the middle zone, set the threshold at −70 dBm so kicks only fire in the transition zone where one AP is clearly stronger.
• Reduce transmit power. Overlapping coverage zones are a root cause of oscillation. Reducing AP transmit power tightens each cell and makes roaming boundaries cleaner. Our transmit power guide explains how to dial this in.

Pairing Roaming Thresholds With 802.11k/r/v

A roaming threshold alone tells the client to leave. The 802.11k/r/v protocols tell it where to go and how to get there fast:

• 802.11k (Neighbor Reports): APs share information about neighboring APs so a client can build a roaming candidate list without scanning every channel. Cuts roam initiation time significantly.
• 802.11r (Fast BSS Transition): Pre-authenticates the client to the target AP before it deauthenticates from the current one. Reduces the handoff gap from 200–300ms down to 20–50ms. Essential for voice calls and online gaming.
• 802.11v (BSS Transition Management): Enables the soft kick mechanism described above. The AP advises the client on where to roam rather than just booting it.

Enable all three on every AP in your system. They are supported on every major mesh platform released after 2020 and are enabled by default on most. If your system exposes them as separate toggles, turn all three on. See our full 802.11r/k/v protocol guide for a deeper look at each.

Verifying Your Changes

After adjusting the threshold, verify the change is working with a simple walk test: connect your phone to the network, open a continuous ping to a server (or use a WiFi analyzer app that shows RSSI in real time), and walk slowly from one AP toward another. Your device should disconnect and reconnect cleanly as you move through the transition zone, without bouncing back and forth. If you see repeated disconnects in the middle zone, raise the threshold value (e.g., from −70 to −75 dBm). If devices still cling to the far AP, lower it (e.g., from −70 to −65 dBm). Use a WiFi analyzer app to watch RSSI in real time while walking — it will show you exactly where the transition is happening and whether the kick is firing at the right level. Once sticky client behavior is resolved, run a speed test from the rooms that previously showed poor performance to confirm the throughput improvement.