A factory-fresh UniFi device won't do anything until it's adopted — pointed at your UniFi console so it can be centrally managed and configured.

Steps

1. Connect the new device to your network (wired for switches/gateways; access points can often be adopted over Wi-Fi too, but a wired connection for initial setup is more reliable).
2. Open the UniFi Network application — a new, unadopted device on the same broadcast domain as the console typically appears automatically under Devices with a "Pending Adoption" status.
3. Click the device and select Adopt. It will download its configuration and reboot to apply it.
4. Once adoption completes, the device shows as Connected, and you can assign it to the correct network/VLAN or configure its specific settings.

Adopting Across a Routed Network

If the device is on a different subnet or VLAN than the console, it won't discover it automatically. Either use Layer 3 Adoption (enter the console's IP directly via the device's local interface or SSH using the set-inform command), or temporarily place the device on the same network as the console for initial adoption, then move it afterward.

Common Questions

Why isn't a new device showing up for adoption?

The most common cause is the device being on a different subnet/VLAN than the console with no route or forwarding rule for the discovery protocol — Layer 3 adoption (above) resolves this without needing to physically relocate the device.

Does adoption erase the device's existing configuration?

On a factory-reset or new device, there's nothing to lose. On a device previously adopted elsewhere, adopt it as a fresh device only after resetting it, or it may hold onto settings from its previous controller.