Fix slow WiFi, sticky clients, adoption drops, and channel interference using UniFi OS tools.
UniFi AP Troubleshooting
Structured steps before replacing hardware or opening a ticket.
1. Is the AP online in UniFi OS?
| Status | Action |
|---|---|
| Offline | Check PoE, cable, switch port, power budget |
| Adopting stuck | See Adopting UniFi Devices |
| Online, clients slow | Continue below |
2. Client-level checks
- Open Clients → select affected device → check signal (RSSI), AP, channel, tx/rx rates.
- Weak RSSI (below -70 dBm): client too far — add AP or adjust min RSSI.
- Client on 2.4 GHz only: enable band steering or separate SSIDs temporarily to test 5 GHz.
3. RF / channel issues
- Insights → WiFi / RF environment — look for co-channel interference.
- Reduce 2.4 GHz power if cells overlap heavily.
- Avoid non-standard 2.4 GHz channels.
4. Roaming problems
- Disable 802.11r temporarily if only certain clients drop on roam.
- Adjust minimum RSSI so weak clients disconnect and re-associate closer APs.
- Verify all APs advertise the same SSID on intended bands.
5. Throughput lower than ISP speed
- WiFi is half-duplex and shared — 300 Mbps WiFi ≠ 300 Mbps internet.
- Test wired PC at gateway first to isolate ISP vs WiFi.
- Check for mesh hops — wire APs if possible.
6. Multicast / streaming issues
- Enable IGMP snooping / multicast enhancements per UniFi guidance for your version.
- Isolate heavy multicast (cameras) on dedicated VLAN.
7. Firmware
- Match AP firmware to a stable release — see Firmware Updates: Best Practices.
- Upgrade one AP first in multi-AP sites.
When to open an i2unifi ticket
- Controller reachable but many APs offline after no on-site changes
- Suspected platform issue affecting inform path to hosted controller
Include: AP model, firmware, RSSI screenshots, and whether wired clients work.