Too many UniFi APs at too high power

Over-deployment doesn't fail loudly. Connectivity holds. Speed tests run fine when you're sitting in the right room. The pattern is more diffuse:

• A video call holds while sitting next to one AP and starts dropping packets the moment the phone walks past the boundary between two APs.
• A laptop shows full bars but a speed test runs at 30 Mbps on a 1 Gbps WAN.
• A device stays connected to a distant AP at -75 dBm even though a much closer AP is available at -50 dBm — the classic “sticky client” pattern.
• AirPlay, Chromecast, or a hand-off-friendly business app (Zoom Rooms, Teams, a VoIP softphone) works on one side of the building and disappears on the other, then comes back when the device reconnects.
• Doorbell cameras, IoT devices, or wall-mounted scanners intermittently show as “offline,” usually at the same times of day.
• In the UniFi controller's WiFi Insights view, the 2.4 GHz channel utilization sits above 60 percent for hours at a time, and several APs are showing the same client at signal levels within a few dB of each other.⁶

These look like five different problems. They are usually one problem.

Wired networks scale by adding capacity. Plug in another switch port, get another full-rate link. Wi-Fi does not. Every Wi-Fi radio on the same channel — yours and your neighbours' — shares the same airtime. Adding another AP on an overlapping channel is more like adding another loud voice to the same conversation than like adding another lane to a road.

The 2.4 GHz band makes this brutal in residential deployments. The band has 11 channels in the U.S., but only three non-overlapping ones — 1, 6, and 11. Setting any 2.4 GHz channel width above 20 MHz eliminates that separation entirely. A three-AP home that “just turned on” without explicit channel planning will, by default, have all three radios contending. The 5 GHz band is more forgiving — many more channels, smaller cells — but the same mechanism applies: more radios on the same channel set means each radio gets less airtime.

There is now a published measurement number for what this looks like in real homes. The Sharma and Feamster IMC 2024 study tracked dual-segment latency and throughput on 50+ home networks over two years with more than 22,000 joint measurements, and reported directly that for users with WAN links above 800 Mbps, “the user's wireless network was the performance bottleneck 100 percent of the time.”¹ The wire stopped being the limit. The RF environment inside the home is now what determines whether a gigabit WAN delivers a gigabit experience.

That changes the audit question. On a 100 Mbps cable connection, modest Wi-Fi was good enough — the WAN was the choke. On a multi-gig fiber connection, Wi-Fi configuration is the experience. Over-deployed, over-powered APs are how that experience gets thrown away.

Wi-Fi is bidirectional. The AP transmits to the client and the client transmits back. Quality depends on the weaker direction. This is where high-power AP settings cause the most damage, because the AP's transmit power has no symmetry with the client's.

A typical UniFi access point can transmit at up to roughly 26 dBm on 5 GHz, depending on model and regulatory domain. A modern smartphone, by FCC limit and battery design, transmits at roughly 14 to 17 dBm. That is a 10 dB asymmetry, which is a factor of ten in power. The practical consequence is that a phone might still heara distant AP loudly enough to stay associated with it, while being completely unable to make itself heard at acceptable rates in reply. Throughput collapses; the phone client doesn't disconnect; the user assumes the network is broken.

Lowering AP transmit power restores the symmetry. If the AP and the client can hear each other at roughly the same effective range, the cell where the AP is useful shrinks to match the cell where the client is useful. The client roams sooner because the AP it's on actually does become unusable when the client walks out of range, instead of being just weak-enough-to-stay-on.

Ubiquiti's own documentation states the consequence directly. The help-center article Optimizing WiFi Connectivity and Reducing Latency describes the “sticky client” pattern and recommends explicit per-AP transmit-power and minimum RSSI tuning as the remediation.⁴ The separate article on minimum RSSI walks through the feature's purpose — a hard threshold below which the AP forcibly disassociates a client to encourage it to roam — and the side effects to be aware of.³

A foundational fact about Wi-Fi that surprises people: the roaming decision is made by the client, not the access point. An AP can hint, kick, or disassociate, but it cannot pick the client's next AP. Different operating systems and even different firmware revisions of the same phone behave differently. iOS, Android, Windows, macOS, and the various smart-home and IoT stacks all have their own preferences for when to start scanning for a better AP and which AP to land on.

The IEEE 802.11 standard, in its 2020 revision, defines the three roaming-assistance mechanisms used by modern APs:²

• 802.11k — Radio Resource Measurement. The AP can advertise a Neighbor Report that tells the client which other APs are nearby, on which channels. The client doesn't have to off-channel scan to discover them.
• 802.11r — Fast BSS Transition. Pre-authenticates roaming targets so the handover from one AP to another doesn't require a full EAPOL or PSK key exchange — invisible to a voice or video call instead of a 200 ms pause.
• 802.11v — BSS Transition Management. The AP can send a polite suggestion (a BSS Transition Management Request) telling the client “you should move to that AP over there.” The client is free to ignore it, but modern clients usually comply.

UniFi exposes these as Fast Roaming (which bundles 802.11k and 802.11r when supported) and Roaming Assistant(which uses 802.11v BSS Transition Requests to nudge clients off below a configurable signal threshold, typically -70 to -75 dBm). Both are off by default on most SSIDs. The community consensus is that Roaming Assistant is the gentler option to enable first — clients can ignore the request if they have a reason to — and Minimum RSSI, the hard-disassociation hammer, is a last resort because some older clients respond to it badly.³

None of these features substitutes for getting the physical layer right. If the AP cells are designed so that the client always has at least one signal-and-noise-margin-acceptable AP available, roaming becomes a non-event. If the cells are badly-overlapping at high power, no amount of 802.11v hinting will fix it — the client is making a rational decision to stay on what looks like a perfectly good connection.

The UniFi Network application exposes everything you need to see whether a residential network is over-deployed. Three views in particular:

1. Channel Utilization (WiFi Insights or Site Magic Insights)

The single most diagnostic number. If 2.4 GHz utilization sits above 60 percent for sustained periods, or 5 GHz utilization above 40 percent, the radios are saturated. Ubiquiti's own troubleshooting guidance on high airtime utilization names this directly as a primary cause of Wi-Fi performance complaints.⁶

2. Client signal by AP

In the Clients view, find a single device and look at what signal it's seeing from each AP. If multiple APs report the same client at -55 to -45 dBm, those cells are overlapping more than they should. If the client is at -65 to -70 dBm on every AP, the cells are too small and there's a coverage gap. The healthy pattern is a clear primary AP at -55 to -65 dBm with one neighbour at -70 to -75 dBm as a roam candidate.

3. The per-AP radio settings page

The audit-worth-doing-five-times view. For each AP: check whether 2.4 GHz is enabled, what channel width is set, and what transmit power level (Low, Medium, High, or custom dBm) is configured. The overwhelmingly common misconfiguration is every AP at Highwith 2.4 GHz on at 40 MHz width. The desired-state pattern is most APs at Medium or Low, with 2.4 GHz on for at most one central AP at 20 MHz width.

These are listed in the order we'd make them on a real audit. Each one is reversible. If a household has Wi-Fi-driven IoT that misbehaves after any individual change, undo that one — the rest still help.

1. Lower 5 GHz transmit power. Start at Medium on every AP. In a small single-story home with two APs, or an office floor with APs spaced closer than roughly 25 feet, drop to Low. The Ubiquiti Maximizing Wireless Speeds article and the high-density WLAN scenario guide both name reducing cell overlap as the primary tuning lever.⁵⁷
2. Disable 2.4 GHz on every AP except one.Pick the most central, most-elevated AP to be the 2.4 GHz radio for the whole home. Set its channel explicitly to 1, 6, or 11. Width 20 MHz. That single radio handles the IoT devices that need 2.4 GHz (smart plugs, older doorbells, older Sonos units); every other AP is 5 GHz only.
3. Disable wireless meshing on wired APs. Wireless Uplink is enabled by default on UniFi APs as a safety net for non-wired deployments. On a home where every AP has an Ethernet drop, it should be off. Ubiquiti's own guidance on optimal wireless mesh networks recommends keeping mesh hops to a maximum of two, and only when wiring isn't an option.⁸
4. Set explicit 5 GHz channel width to 80 MHz.160 MHz is the intuitive answer for fastest speeds, but in residential 5 GHz it shrinks the usable non-overlapping channel set dramatically, especially on the U-NII-2 DFS channels. 80 MHz is the pragmatic ceiling for most homes. 6 GHz on Wi-Fi 6E and Wi-Fi 7 APs can use wider widths without the same penalty.
5. Enable Roaming Assistant.Threshold around -70 dBm on 5 GHz, -75 dBm on 2.4 GHz. This sends 802.11v BSS Transition Management Requests — polite hints, not kicks. Most modern clients respect them.
6. Enable Fast Roaming if all clients support it.This adds 802.11k and 802.11r and is usually transparent. Watch for any device that fails to associate afterwards — older smart-home hubs occasionally don't understand it. Most modern WPA3 setups already imply Fast Roaming via the SAE-based association flow.²

After all six, the audit follow-up is the same Channel Utilization view. If 5 GHz utilization dropped from 40 percent to 15 percent and 2.4 GHz dropped from 70 percent to 20 percent on the single remaining 2.4 GHz radio, the network is now doing the work it should be doing.

“Fewer APs at lower power” is the default answer, not the only answer. The exceptions are specific and worth naming:

• Heavy structural walls — brick, plaster-lath, concrete, stone, or commercial firewalls.A pre-war townhouse with three-foot masonry walls, or an office building with rated firewalls between suites, loses 15-25 dB per wall. Each room may genuinely need its own AP. The fix-by-tuning still applies (lower power, disable 2.4 GHz on most APs), but the count can be high.
• Multi-story buildings with concrete decks between floors.Vertical penetration is generally worse than horizontal at 5 GHz. Per-floor APs are usually correct — in both homes and office buildings.
• Detached structures. Pool houses, detached garages, outdoor kitchens, ADUs, warehouse yards, parking decks. These almost always need their own outdoor-rated AP, not a stretched signal from inside.
• High client-density rooms.A home theater with a streaming projector plus an Apple TV plus several family phones plus speakers can saturate a single AP's airtime even when the rest of the building is idle. The same is true of a conference room with twelve laptops plus a video bar plus everybody's phones. A dedicated AP for those rooms is sometimes correct.
• Outdoor coverage. Lawn, pool, courtyard, loading dock, parking lot — outdoor radio behaves differently from indoor and belongs on dedicated outdoor-rated hardware.

The diagnostic rule across all of these is the same: deploy based on what a physical site survey shows you, not on a square-footage rule of thumb. A real on-site walk-through with a phone-based survey app is the only way to know.

The finding holds up under independent verification. Three categories of evidence:

r/Ubiquiti, 2024-2026

The single highest-vote post in the “is-this-too-much” genre on r/Ubiquiti at writing is “This seems like waaaay too many APs, right?” — 555 score, 233 comments. The top reply on the original thread, paraphrased accurately: some of your APs are close enough to kiss, your signal strength will be awesome but the interference will not be, two APs would be plenty.The companion thread on the underlying mechanism, “What does Roaming Assistant actually do?” (407 score, 97 comments), explains the 802.11v soft-kick that lets clients hand off cleanly. The subreddit's residential lean is partly an artifact of who posts in public — but the underlying physics is the same in any multi-AP deployment, and the office-network version of this complaint shows up in private channels and integrator communities just as regularly.

Installer write-ups

Nine independent installer-or-consultant articles flag this as the single most common configuration error: Crosstalk Solutions, Willie Howe, The Hookup, LazyAdmin, HostiFi, Evan McCann, UniFi Nerds, Hostbor, and HowToGeek all rank it first or second. Most of these authors work across home and small-business deployments, and several explicitly note that the issue gets worse, not better, when AP counts rise. The HowToGeek summary, written by Patrick Campanale in 2026, names “access point broadcast power being too high” as one of the four things its author wishes they had known before building their own UniFi network.⁹

Academic measurement

The IMC 2024 longitudinal study of WiFi bottlenecks in home access networks, by Sharma and Feamster, is the cleanest published number. On home WAN links above 800 Mbps, “the user's wireless network was the performance bottleneck 100 percent of the time.”¹ That study is residential by design — there isn't an equivalent multi-year office-network dataset published yet — but the same airtime-contention mechanism it documents is what shapes every multi-AP business deployment on gigabit-class internal links. On multi-gig connections, getting the radio side right is no longer an optimization — it is the difference between the WAN line speed and the actual experienced speed.

• Single-AP sites are out of scope. Many apartments, small homes, and one-suite offices are correctly served by a single access point. The over-deployment finding is structurally about buildings with three or more APs.
• “Most common audit finding” is not “most networks have this.” Plenty of UniFi networks are tuned well and don't trip this finding at all. The data we and the cited community sources are looking at is biased toward networks that already have a complaint or are being audited for a reason. The honest claim is narrower: when there is a problem, this is the most common one. It is not a claim about the population of all UniFi networks.
• Client behavior is the largest source of variance. A network can be perfectly tuned and still have one phone model that roams badly because of a specific OS firmware version. Treat per-device complaints as worth investigating separately from the overall RF design.
• 6 GHz changes the math.Wi-Fi 6E and Wi-Fi 7 add a clean band with much less neighbour-AP interference and steeper signal falloff. Cells designed around 6 GHz can be smaller and tighter than the same architecture on 5 GHz. The principles here still apply; the numerical thresholds may shift.
• Minimum RSSI is not a default. Using Minimum RSSIat, say, -75 dBm — the hard-kick feature, separate from Roaming Assistant's soft hint — does help some networks, but it disassociates clients that some older IoT firmware never recovers from gracefully. Treat it as a tuning option after the first six steps, not as part of them.
• We do not publish per-home survey numbers here. The audit produces a written report for a specific home, not a public dataset. The pattern described above is what we and the cited community sources observe in residential UniFi installations — not a claim that it is true in every home in some statistical sense.
• Wireless mesh is not always wrong. Some homes have an AP placement that genuinely needs to be reached wirelessly (a detached structure with no buried fiber, an attic AP that pre-dates a retrofit). The recommendation is to disable wireless meshing where APs have wire, not to disable it globally.

None of these caveats changes the headline pattern: across community evidence, installer consensus, and academic measurement, the single most common reason a residential UniFi network underperforms is that it has too many access points running at too high a transmit power.