# Fix Slow Wi-Fi by Forcing Devices onto the Nearest Access Point

**Min-RSSI** (minimum received signal strength) tells an access point to disconnect
any client whose signal drops below a threshold. The client immediately re-scans and
joins a better AP — the same thing toggling Wi-Fi off and on does, automated. On any
multi-AP network it cures the *sticky client*: the laptop that clings to the far-away
AP it joined this morning instead of the strong one ten feet away. The technique is
vendor-neutral — the walkthrough below uses UniFi, with the equivalent setting named
for other platforms. Battle-tested in a real homelab.

---

## The symptom

Pages crawl, video calls stutter — but the Wi-Fi icon still shows bars, so nothing
*looks* wrong. Toggle Wi-Fi off and on and everything is instantly fast. That's a
sticky client. Roaming decisions belong to the phone or laptop, not the network, and
most devices (Apple's especially) hang on to a weak association far longer than they
should.

A real case: a MacBook camped on a distant AP at −70 dBm for **two days** — 130 Mbps
link rate, ~1-second DNS lookups, 58 ms average ping to its own gateway. One Wi-Fi
toggle later it sat on a strong 6 GHz radio at −39 dBm and 1,921 Mbps. Min-RSSI makes
that kick happen automatically.

Two quick ways to confirm it's stickiness and not your internet:

- `ping 192.168.1.1` (your gateway). A healthy Wi-Fi hop averages single-digit
  milliseconds; a sticky link shows 40–150 ms *to a device in your own house*.
- Toggle Wi-Fi off and on. If that fixes it, the problem is roaming, not bandwidth.

## How the numbers read

Signal strength is measured in dBm — negative numbers, closer to zero is stronger.

| Signal | What it feels like |
|---|---|
| −30 to −55 | Great — full speed |
| −55 to −70 | Fine — getting slower toward the bottom |
| −70 to −80 | Painful — low link rates, retries, latency spikes |
| **−75** | **The kick threshold this guide sets** |

## Is this for your network?

**Yes, with two or more access points.** The kick means "go find a better AP" —
multi-AP homes are exactly where sticky clients suffer.

**Probably not with one.** There's nowhere better to roam to; a kick just pushes the
client to 2.4 GHz or straight back to the same radio. Better AP placement is the
single-AP fix.

## Pre-flight checks

Three checks before you enable anything. They're the difference between a clean fix
and a week of mystery disconnects.

1. **Plan to touch only the 5 GHz radio.** 2.4 GHz is where far-flung IoT devices
   live — and your phone from the far end of the yard. A kick threshold there makes
   weak-but-working devices disconnect over and over. 6 GHz doesn't need one; its
   short range self-limits.
2. **Look for 5 GHz-only SSIDs.** In your controller's wireless settings, check
   whether any network broadcasts on *only* 5 GHz — dedicated camera or backhaul SSIDs are the usual
   case. A client there has no 2.4 GHz fallback: if it can't reach any AP above the
   threshold, it loops — kicked, rejoins, kicked again. Confirm those clients have
   comfortable margin (10+ dB above the threshold), or skip Min-RSSI on the APs
   serving them.
3. **Sort your client list by signal.** A *stationary* 5 GHz device already sitting
   near −75 — a far TV, a garage tablet — will churn once the threshold turns on.
   Move it, repoint an AP, or plan a looser threshold before enabling.

## Set it up

The steps below are UniFi, where the setting is called **Minimum RSSI** (per-AP,
per-radio). The same knob exists on most multi-AP platforms — the name to look for:

| Platform | Where |
|---|---|
| UniFi | **Minimum RSSI**, per AP → Radios |
| TP-Link Omada | **RSSI Threshold**, in the AP's advanced wireless settings |
| MikroTik | **signal-range** on a wireless access-list entry |
| OpenWrt | the **usteer** or **DAWN** roaming daemons (signal thresholds) |
| Aruba, Cisco, Ruckus | client-steering is built in (ClientMatch, RSSI Low Check, SmartRoam) — tune rather than add |

On UniFi:

1. Open the UniFi Network application and go to **UniFi Devices**.
2. Select an access point → **Settings → Radios**. (Menu names drift between UniFi
   versions — you're looking for the per-radio settings.)
3. Under the **5 GHz** radio, enable **Minimum RSSI** and set **−75**. Leave 2.4 GHz
   and 6 GHz untouched.
4. Apply. The AP re-provisions — a few seconds of blip on that AP.
5. Repeat for each AP, doing the one *your* device is connected to last so you keep
   your session.

## Verify it

The test is the symptom itself: walk your laptop to the far end of the house and
back. It should hop APs on its own — no toggle. In numbers, `ping 192.168.1.1`
should average single-digit milliseconds wherever you have coverage.

## Tune it

| Threshold | When |
|---|---|
| −70 | Dense coverage, an AP in nearly every room — kick early, stay on strong links |
| **−75** | **The starting point** — conservative, safe for most multi-AP homes |
| −80 | Sparse coverage or a large property — loosen if a far room starts dropping |

Because it's per-AP, an access point covering a far corner can run looser than the
rest of the house.

## What can go wrong

One real failure mode: a device on a **5 GHz-only SSID**, in a spot where no AP beats
the threshold, has no 2.4 GHz fallback and will disconnect-loop. That's what
pre-flight check 2 exists to catch. Dual-band SSIDs degrade gracefully — a kicked
client that can't find good 5 GHz lands on 2.4 GHz: slower, but stable.

If a device starts flapping after you enable this, don't turn the feature off —
loosen that one AP's threshold toward −80, or fix that spot's coverage.