Five UniFi defaults that are costing you performance

UniFi's defaults are chosen so that somebody adopting their first access point gets a working network without reading anything. That is a good product decision. It is also, once you have four access points, the wrong configuration — and nothing in the interface tells you so.

These are the five changes that make the most difference, roughly in order.

1. Transmit power is too high

The default is High or Auto, which in a multi-AP deployment produces overlapping cells, sticky clients and co-channel contention.

Set 2.4 GHz to Low and 5 GHz to Medium as a starting point, then measure. The instinct that more power means better coverage is wrong in both directions: the access point can shout further, but the phone in someone's pocket still cannot shout back.

2. Minimum data rates are left at the floor

Buried in the advanced SSID settings, and the single highest-value change available in UniFi.

Setting the minimum rate to 12 Mbps or 24 Mbps disables 802.11b compatibility overhead, shrinks effective cell sizes and forces clients to roam rather than clinging to a distant access point at 1 Mbps. Set it per band, on every SSID.

3. Every 2.4 GHz radio is on

UniFi will happily run 2.4 GHz on all twelve of your access points, sharing three channels. That is not a channel plan, it is a queue.

Turn the 2.4 GHz radio off on at least half your access points. There is no global switch — you do it per device, so record which ones you turned off before the next engineer wonders why.

4. Channel selection is unconstrained

Auto-optimise is fine as a mechanism. Left unconstrained, it will choose 80 MHz channels in a dense office and DFS channels you may have decided against.

Set the constraints deliberately: allowed channel list, fixed channel width, minimum and maximum power. Then let the automation work inside them.

5. Automatic firmware updates are on

Convenient for a house. Wrong for a business.

Ubiquiti iterates quickly, which is why the software is as good as it is, and occasionally ships a client-compatibility regression. Stay one minor release behind the newest stable build, read the release notes, and update deliberately.

The bonus one: IoT is on your LAN

UniFi's default inter-VLAN behaviour surprises people. Create a network for IoT, assign it an SSID, and then actually write the firewall rule blocking it from reaching your LAN. Creating the VLAN is not the same as isolating it.

While you are there: UniFi supports multiple pre-shared keys per SSID with per-key VLAN assignment. That is the right way to handle a mixed IoT estate, it survives MAC randomisation, and it costs nothing extra.

None of this is a criticism of the platform. It is what happens when one product has to serve both a first-time home user and a fifty-access-point business. The defaults serve the first group; the second group has to do this pass, and most never do.

Our full UniFi settings walkthrough goes through the rest.