If it hasn’t been configured before, username and password are ‘ubnt’.
Wireless Networks, configure the SSID(s) and security you are currently using with them.Make sure you configure the following sections on the server: Here are the instructions for setting up the UAPs on the new Unifi Controller software. Same steps as above with initial Unifi Controller settings:
Now you should see the new AP provisioned in the Unifi controller and you can edit the name and update the AP firmware. Send the command again, this should allow the AP to see that it has been adopted. Adopt the new AP and go back to the SSH shell. From either location (alerts or ap device list), you should have a button that says “Adopt”. If you don’t see the alert, check the device list, it should show up there as “Unknown”. In a few minutes, we should see an alert stating a new device has checked in. Next, we go connect to the Unifi command center. Since this is a brand new AP for us, we just need to do this: to do that, use the following command, and then SSH back into the device when it comes back up.
NOTE: If the AP has been provisioned before, you’ll have to reset it to factory defaults. NOTE: If the AP has been provisioned before, you’ll have to use the password for the Unifi controller it was provisioned by. Once you have the IP, we’ll use putty to ssh into the device. In this example, we’ll say the Unifi controller is at 192.168.1.55.ġ) Write down (or take a picture on your phone) the MAC address for the new AP.ģ) Check DHCP to see what IP address was given to the Unifi AP by searching for the MAC address in the DHCP clients table. But, the routers don’t allow the discovery tool to see new APs on other networks, so this is how we add one. In our case, we have a central Unifi controller managing APs on multiple networks.
This is the process to add a new Unifi AP to the Unifi controller when discovery doesn’t work.