If an access point or switch will not adopt, first identify whether it lacks connectivity, belongs to another console or is failing during the adoption process. Repeated factory resets can erase useful information without fixing the path to the UniFi Network application.
Need help adopting or migrating a device?
We can review an existing UniFi Network deployment remotely when the required access is available. Tell us the device model and the exact status shown.
Identify the device and the application that should manage it
This guide focuses on UniFi Network access points and switches. Protect cameras and Access devices have their own application and adoption requirements. For a camera problem, use our Protect troubleshooting guide.
Record the intended console or self-hosted Network application, the device model and whether the device is new, previously adopted or being moved between sites. Check compatibility before assuming a software update or reset is the answer.
Check power, link and addressing
- Confirm the device is powered by a compatible source and has a stable connection.
- Find its current IP address and compare it with the intended management network.
- Review recent cable, switch-port or VLAN changes if it was working before.
- If it lacks the expected address, investigate that path before retrying adoption.
Ubiquiti’s device-connectivity guide provides an addressing and reachability workflow. An entry in the device list is useful evidence, but it does not by itself prove the application can maintain management connectivity.
Use the displayed status to choose the next check
- Not discovered: verify the device’s network and the path to the intended application.
- Pending adoption: confirm you are in the right site and have the required administrator permissions.
- Managed by another console: establish ownership and access to the previous deployment before planning removal or migration.
- Adoption fails or repeatedly returns offline: compare addressing, application reachability, compatibility and the timing of connection events.
Status wording can vary by application version. Keep the exact message for a support request rather than treating every failure as the same problem.
Different subnets need a deliberate management path
When a device and Network application are separated by routing or located at different sites, discovery and management need additional planning. Check the intended host address, routing and narrowly scoped firewall requirements for your deployment.
Use Ubiquiti’s Layer 3 adoption documentation for that scenario. Do not copy a command containing another site’s host address or expose management services publicly without understanding the design. If the device lost connectivity after a network change, review our VLAN troubleshooting guide.
Plan a reset or migration before starting it
A reset may be appropriate for equipment you own and can safely reprovision, but it removes configuration from the device. A switch or gateway change can also cut off the remote session used to repair it.
Preserve the relevant configuration, confirm authorized ownership, agree on downtime and establish a recovery route. A reset should be a planned step after the connectivity and ownership checks, not an automatic first action.
What to include in an adoption support request
Send the model, intended console/application type, exact status, when the problem began and whether the device was previously managed elsewhere. Include a simple topology and whether someone can access the equipment. Do not send passwords, recovery codes or private keys through the initial form.
Send Your Adoption Support Request
We review suitability and agree scope, fees and availability before a session. Learn more about nationwide remote support or on-site installation in Virginia and North Carolina.