Kernaali ToolsAn offline AP is not automatically an adoption problem. First establish whether it lost power or merely lost its management connection. Check the exact AP power requirement, the supplying port’s supported PoE mode and the switch’s remaining total budget.
Applies to: UniFi Network application with PoE-powered UniFi APs and their supplying switch or compatible injector. Current public power and event references; no particular AP firmware regression or model is declared fixed. Protect cameras and passive-power conversion recipes are outside this guide.
Validation: documentation-checked on . No device or lab test is claimed. Version references identify the documentation checked, not a firmware upgrade recommendation.
Correlate power, uptime and connectivity
| Observation | Interpretation to verify |
|---|---|
| AP Underpowered or Insufficient PoE Output | Check the AP requirement and actual port/injector capability |
| PoE Availability Exceeded | Review the shared switch power budget and all connected loads |
| Uptime resets and clients disconnect together | Investigate power/cable/reboot evidence at that time |
| Uptime continues and clients work but Network says offline | Follow the management VLAN/application path |
| Link repeatedly renegotiates | Inspect cable, terminations and supplying port; do not assume a firmware cause |
The event names appear in UniFi’s system-log reference. A log label narrows the investigation but does not identify a defective component by itself. You do not need to deploy a SIEM or change logging to compare existing events and uptime.
Check two different power limits
Read the exact AP and switch/injector specifications. A switch can support the required PoE mode on one port while its shared supply is already committed elsewhere. Conversely, a large total budget does not upgrade an individual port to a higher power class. PoE availability and modes distinguishes device requirements from total PoE availability; use the specific model datasheet before selecting a replacement supply.
Do not compare an idle watt reading with the maximum budget and assume every boot or radio-load condition is covered. Also account for whether the switch’s available budget depends on its installed power supply or upstream PoE input. Avoid mixing passive voltage and negotiated PoE based only on the RJ45 connector.
Isolate one variable during a planned interruption
Document the current port configuration and the AP’s client impact. With local access, try a known-good short cable and a verified compatible power port or injector, changing one component at a time. Preserve the AP management/native VLAN and client tagged VLANs when moving a switch port. A port move that fixes power but breaks the management VLAN is not a successful test.
If the AP remains powered, follow offline-device connectivity checks before resetting it. Compare whether another known-good compatible device shows the same problem on the suspect cable/port. Do not repeatedly power-cycle a production AP to generate more events.
Verify under the workload that failed
Confirm stable uptime, link and PoE status while the original client workload runs. Test association, an IP lease and the intended application on the relevant SSIDs; an online management icon is not enough. Record the observation window and avoid claiming a permanent fix from a short idle test.
For rollback, restore the documented port and VLAN assignment or previous known-good power arrangement. Do not restore a supply already verified incompatible just to reproduce the old layout. Remove temporary diagnostic connections and preserve the failing cable/port information for repair. No global AP factory reset or firmware downgrade is part of this workflow.
Powered device cannot reach Network · Check VLANs after moving an AP port
Technical references
Found an issue? Send a correction with a reproducible example.