UniFi - Device Adoption

1. Ensure that your application is set up and running on a UniFi Console.

UniFi Network must be set up and running before adopting a new device. Make sure you have already gone through the setup process of your UniFi Console*. Alternatively, see Standalone Access Points (without UniFi) to learn about AP management without a UniFi Console. Please keep in mind that APs set up in Standalone mode will lack various benefits only obtained with a UniFi Console, such as remote management, global configuration, and more.

*Advanced users self-hosting the UniFi Network Server should make sure it is already installed on the appropriate machine. This should only be running on one machine for the lifetime of your network.

2. Update to the latest versions.

Ensure that UniFi Network and UniFi OS are using the most up-to-date versions, found here.

3. Check your device’s power supply.

UniFi devices may require PoE, PoE+, or PoE++ power. Check your product’s datasheet to verify that you are using the correct power source. Compatible PoE adapters can be purchased here.

If your device is connected to a PoE switch, ensure the switch isn’t exceeding its PoE availability. All switches have a maximum power output, and it is possible to hit that maximum before using all available ports. See PoE Availability and Modes for more information.

4. Check your device’s physical connection.

A damaged cable or port may prevent your device from adopting. We recommend testing a new cable and port (if using a switch) to rule out any damage. 

If you are unsure about your cabling, we recommend an Official UI Cable.

5. Verify that your device is ready for adoption.

A solid white LED indicates that the device is powered on and awaiting adoption. If your device has a blue LED, this indicates that it has already been set up. If this is the case, it is likely that you mistakenly set the device up in Standalone Mode on your mobile app. For more information, see Understanding Device LED Indicators.

If your device isn't ready for adoption, but you expect it to be, factory restore it.

6. Make sure your device is receiving an IP address.

You can verify if your device is receiving an IP address by using the WiFiman Mobile App’s Discovery feature (iOS / Android). See below for further information, based on your IP result:

Device does not appear, or appears with an IP address of 192.168.1.20 (our 'fallback address'):
Your device is plugged in, but lacks connectivity, and is unable to receive an IP address. Make sure it is correctly plugged into a local network port (LAN), and traffic is not being restricted by a switch port, gateway, or firewall rule. See Virtual Network Connectivity and Isolation to learn more.

Device appears with an IP address other than 192.168.1.20
Your device has general network connectivity, but something is preventing it from being detected by your UniFi Console. Disable any local firewalls and make sure traffic is unrestricted for ports required for adoption (TCP Port 8080 and UDP Port 10001). If your device is not on the same network as your UniFi Console, you will need to use Layer 3 adoption. See Required Ports Reference, UniFi Adoption Guide, and Layer 3 Adoption to learn more.

We recommend using a UniFi Gateway Console, which has a built-in gateway capable of providing IP addresses without intervention. For users with a non-UniFi gateway or router, contact your vendor or ISP for more information.

7. Ensure there are no third-party applications blocking connectivity.

We recommend our UniFi OS Consoles because they are preconfigured to allow communication with our devices. They also minimize the impact of third-party environmental factors. Non-UniFi gateways and ISP modems are known to block certain ports necessary for running UniFi. TCP Port 8080 and UDP Port 10001 must be open for device adoption. Contact your third-party vendor or ISP for assistance with opening these ports.

For a comprehensive list, see our Required Ports Reference.

For users with a self-hosted UniFi Network Server, please also be aware that software-based firewalls (particularly Windows) and antivirus software are known to block communication. We recommend disabling these for testing purposes.

1. Ensure that your application is set up and running on a UniFi Console.

UniFi Protect must be set up and running before adopting a new device. Make sure you have already gone through the setup process of your UniFi Console.

2. Update to the latest versions.

Ensure that UniFi Protect and UniFi OS are using the most up-to-date versions, found here.

3. Check your device’s power supply.

UniFi devices may require PoE, PoE+, or PoE++ power. Check your product’s datasheet to verify that you are using the correct power source. Compatible PoE adapters can be purchased here.

If your device is connected to a PoE switch, ensure the switch isn’t exceeding its PoE availability. All switches have a maximum power output, and it is possible to hit that maximum before using all available ports. See PoE Availability and Modes for more information.

4. Check your device’s physical connection.

A damaged cable or port may prevent your device from adopting. We recommend testing a new cable and port (if using a switch) to rule out any damage.

If you are unsure about your cabling, we recommend an Official UI Cable.

5. Verify that your device is ready for adoption.

A solid white LED indicates that the device is powered on and awaiting adoption. If your device has a blue LED, this indicates that it has already been set up. If this is the case, it is likely that the camera is already 'Managed by Other.' For more information, see Understanding Device LED Indicators.

If your device isn't ready for adoption, but you expect it to be, Factory restore it. 

6. Make sure your device is receiving an IP address.

You can verify if your device is receiving an IP address by using the WiFiman Mobile App’s Discovery feature (iOS / Android). See below for further information, based on your IP result:

Device does not appear, or appears with an IP address of 192.168.1.20 (our 'fallback address):
Your device is plugged in, but lacks connectivity, and is unable to receive an IP address. Make sure it is correctly plugged into a local network port (LAN), and traffic is not being restricted by a switch port, gateway, or firewall rule. See Virtual Network Connectivity and Isolation to learn more.

Device appears with an IP address other than 192.168.1.20
Your device has general network connectivity, but something is preventing it from being detected by your UniFi Console. Disable any local firewalls and make sure traffic is unrestricted for ports required for adoption (TCP Port 8080 and UDP Port 10001). 

We recommend using a UniFi Gateway Console, which has a built-in gateway capable of providing IP addresses without intervention. For users with a non-UniFi gateway or router, contact your vendor or ISP for more information.

7. Ensure there are no third-party applications blocking connectivity.

We recommend our dedicated UniFi Consoles as compared to self-hosting a UniFi Network Server because they are preconfigured to allow communication with our devices. They also minimize the impact of third-party environmental factors. Non-UniFi gateways and ISP modems are known to block certain ports necessary for running UniFi. TCP Port 8080 and UDP Port 10001 must be open for device adoption. Contact your third-party vendor or ISP for assistance with opening these ports.

For a comprehensive list, see our Required Ports Reference.

1. Ensure that your application is set up and running on a UniFi Console.

UniFi Protect application must be set up and running before adopting a new device. Make sure you have already gone through the setup process of your UniFi Console.

2. Update to the latest versions.

Ensure that UniFi Protect and UniFi OS are using the most up-to-date versions, found here. If applicable, you should also update UniFi Network and your UniFi APs since this facilitates the wireless adoption process.

3. Confirm the device is receiving sufficient power.

The device's LED should be on. A damaged cable or power supply may prevent your device from adopting. We recommend inspecting your device's power cable and port (if using a switch) to rule out any damage.

4. Verify that your device is ready for adoption.

A solid white LED indicates that the device is powered on and awaiting adoption. If your device has a blue LED, this indicates that it has already been set up. If this is the case, it is likely that the camera is already 'Managed by Other.' For more information, see Understanding Device LED Indicators.

If your device isn't ready for adoption, but you expect it to be, Factory restore it. 

5. Ensure New WiFi Device Auto-Link is enabled if you have UniFi APs.

If you are adopting your wireless cameras to a network that has UniFi APs, the New WiFi Device Auto-Link feature will automate the adoption process and optimize the wireless connection.

6. Use the Protect Mobile App to adopt your camera

Move close to the wireless device and open the UniFi Protect Mobile App (iOS / Android). If you have UniFi APs, you should be able to instantly adopt the device. If not, you may need to choose which WiFi SSID you want the camera to connect to. Ensure the WiFi SSID is associated with the same local network as your UniFi Console.

Note: You must sign in using the UI Account associated with your UniFi Console and ensure Bluetooth, Local Network, and Location permissions have been enable for the UniFi Protect app.

7. Attempt adoption closer to an Access Point.

If you still have issues with adoption, move your wireless camera closer to the nearest AP to improve WiFi connectivity.

8. Check for any firewalls blocking connectivity.

Ensure that firewalls, especially third-party ones, are not blocking network (VLAN) connectivity between your camera and UniFi Protect Console.

If you purchased an Early Access device, make sure you are running the appropriate Early Access software version. See our Releases for more information.

This indicates a device was set up and adopted by another console. You can resolve this by factory resetting the device and readopting it, or restoring a backup from the original device console.

There are three potential reasons for this status:

1. You factory reset your UniFi Console, but did not reset your device.
2. You downloaded and installed the UniFi Network Server by accident, and adopted your device to that.
   • Note: The Server is not a 'viewer.' Only one instance of UniFi Network should be installed
3. You set up your device in Standalone Mode on the mobile app.

This requires Wireless Meshing, which is enabled by default.

This setting is located under UniFi Network > Settings > WiFi. This requires at least one wired AP present and within range of the wireless AP you wish to adopt.

This requires New Device Auto-Link, which is enabled by default. 

This setting is located under UniFi Network > Settings > WiFi. This requires at least one wired AP present and within range of the wireless device you wish to adopt.

Devices that suddenly go offline or switch between online and offline may indicate a network overlap. Make sure your ISP modem is in Bridge Mode. Contact your ISP to request assistance. 

Devices connect to the UniFi application using the hostname http://unifi:8080/inform; check your router/gateway DNS settings if devices are unable to connect suddenly.