Adopt / Provision a UniFi Device (AP or Switch)

Category: Networking (UniFi) · Audience: Technicians · Est. time: 10–25 min

Summary

A new or reset UniFi device must be adopted into the UniFi Network controller before it works. This article covers adoption and the common "stuck" states. This is a technician task.

Normal adoption

1. Cable the device to a PoE port (or PoE injector) on the managed network. Wait for the LED to settle (steady white = ready to adopt on newer models).
2. In UniFi Network → Devices, the device appears with status "Pending Adoption."
3. Click it → Adopt. It provisions (LED flashes) and moves to Online. Update firmware if prompted.

Stuck: "Adopting" → "Disconnected" loop

Usually the device can't reach the controller's inform address.

1. Confirm the controller's Inform Host is set correctly: UniFi Network → Settings → System → Advanced → Inform Host (a reachable IP/hostname), and that the device can route to it.
2. Set‑inform manually (Technician). SSH to the device (default ui/ui on new, or the site's SSH creds) and run:

set-inform http://<controller-ip>:8080/inform

Run it, click Adopt in the controller, then run set-inform again to lock it in.

1. Layer‑3 adoption (device on a different subnet/site): set the inform host to a reachable address and ensure UDP/TCP 8080 (inform) and required ports are open between device and controller.

Stuck: won't appear at all

• Confirm PoE power (LED on) and the device is on the same L2 network as the controller (or L3 adoption is configured).
• Factory reset the device (hold reset ~10s until LEDs cycle) and retry.
• Check the switch port isn't disabled or on the wrong VLAN.

Adopt from another controller / previous owner

• A device showing "Managed by Other" must be forgotten on the old controller, or factory reset, before this controller can adopt it.

If that doesn't work

• Confirm firmware compatibility between the device and controller version.
• Escalate to BBN Support with the device model, its LED state, and the controller's inform host.

Prevention

• Document the controller inform host and SSH creds so re‑adoption after a reset is quick.