Decide what needs to work
A conference room full of clients and a single workstation beside an AP need different settings. Record the clients, their supported bands, the AP uplink speed and where coverage is required. Keep a wired local test endpoint available so an ISP bottleneck does not look like a Wi-Fi fault.
| Objective | Starting approach | Test before keeping it |
|---|---|---|
| Dense / stable service | 20 MHz at 2.4 GHz; consider 20/40 at 5 GHz | Coverage, retries, channel reuse and roaming |
| Nearby high-throughput client | Consider 80 MHz at 5 GHz; wider 6 GHz where supported | Local goodput, latency under load and interference |
| Older IoT compatibility | Keep a suitable 2.4 GHz SSID with tested security | Association, DHCP and actual device function |
Bands and channel width
2.4 GHz reaches many older clients but shares limited spectrum with neighboring networks and other devices. 5 GHz offers more channel choices; DFS can affect availability. 6 GHz needs compatible clients and permitted local spectrum. Wi-Fi 6E extends the ax generation into 6 GHz; Wi-Fi 7 adds capabilities such as 320 MHz on compatible 6 GHz radios and multi-link operation.
Ubiquiti’s maximum-speed guidance suggests 80 MHz for 5 GHz and 160/320 MHz for appropriate 6 GHz equipment. That is a throughput-oriented scenario, not a universal setting. In a crowded building a narrower channel can deliver more consistent service. Respect country, indoor/outdoor and power restrictions.
Transmit power and client decisions
More AP power can make the SSID visible farther away without improving the client’s return path. Compare client signal, retries and actual coverage while walking the area. Reduce power only when there is an overlapping usable cell, and verify low-power clients can still reach an AP.
Band steering encourages capable clients toward 5 GHz; it does not turn a 2.4-only sensor into a dual-band device. Current UniFi SSID steering uses BSS transition assistance. Roaming also depends on the client. Test a voice call or continuous traffic while moving between APs rather than expecting an AP to force seamless roaming from signal strength alone. No dedicated client/AP lock procedure is provided here because it was not verified in current official help documentation.
Minimum rates and compatibility
Raising the minimum data rate can reduce airtime spent on very slow transmissions but can also exclude older clients and shrink the usable cell edge. Leave the default initially; change only after testing the weakest required client at the intended coverage boundary.
Fast roaming, WPA modes, PMF and advanced multicast behavior depend on client support. Keep modern security on capable devices. If a legacy device fails, diagnose it on a restricted IoT network rather than weakening every SSID. Do not disable isolation, authentication or encryption merely to obtain a successful association.
One change, two measurements
Record channel, width, client PHY rate and local goodput at a fixed position. Make one adjustment, repeat the same test, then check an edge-of-coverage client and a roaming path. Revert if the faster nearby result comes with disconnections elsewhere. A PHY rate is not application throughput, and the sum of AP radio maxima is not an Internet-speed prediction.
Print rate and width assumptions · dBm and mW · Keep IoT traffic separate
These guides use the current UniFi Network concepts. Menu wording and location vary by release; check the policy’s actual scope and result. Kernaali Tools is not affiliated with Ubiquiti.
Technical references
Found an issue? Send a correction with a reproducible example.