How to use Set-Inform to adopt Unifi Access Point

34 Comments

Unifi Access points are great devices, most of the time when you connect a new Access Point they will find the controller within a minute. But what if your new access point isn’t showing up in your controller?

When the status led of your new access point is steady white (or steady amber for older access points) then it’s waiting for adoption. But sometimes the device won’t show up in the controller.

In this article, I will explain how you can use the Set-Inform command on an Unifi Access Point.

Use Set-Inform on Unifi Access Point

The Set-Inform URL tells the Unifi Access Point where the controller is located. By default, the access point will search the network for the controller, using the default DNS name unifi. This doesn’t always work, so we need to tell the access point the correct address of the Unifi Controller.

To set the inform URL we need to connect over SSH to the Unifi access point. You don’t need an SSH client for this, we can simply use PowerShell for this, which is installed by default on all Windows 10 and 11 computers.

The default SSH username and password are ubnt. If you have changed it, then you can look it up in the controller under System > Application Configuration > Device SSH Authentication.

Note

The default inform url is http://unifi:8080/inform. Unifi is the internal DNS name of your Unifi Controller. This doesn’t always work, better is to use the IP Address of the controller, for example: http://192.168.1.1:8080/inform

We also need to know the IP Address of the access point. You can use the Ubiquiti Discovery Tool for this or Advanced Ip Scanner.

  1. Open PowerShell


    We first need to connect the access point over SSH. To do this we are going to use PowerShell.

    1. Press Windows key + X (or right-click your start menu)
    2. Choose Windows PowerShell

  2. Connect SSH


    Type ssh [email protected] (replace 192.168.1.142 with the IP Address of your access point)

    Enter the default password ubnt (or lookup the SSH details in your controller)

    SSH Unifi Access Point

  3. Set-Inform URL


    The inform URL is the IP Address of your controller followed by the port number: 8080/inform.

    So if the IP Address of your controller is 192.168.1.1, then the inform URL is :
    http://192.168.1.1:8080/inform

    Type the following command and press enter:
    set-inform http://192.168.1.1:8080/inform

    unifi set-inform

  4. Complete the adoption in the controller


    You should now see the access point in the controller, ready for adoption.

    Adopt unifi access point

If the access point still doesn’t show up in the controller, then check if the settings are applied correctly. Type info and press enter to see the status of the access point:

UAP-AC-Lite-BZ.5.43.36# info

Model:       UAP-AC-Lite
Version:     5.43.36.12724
MAC Address: f0:9f:c2:f6:d1:fd
IP Address:  192.168.1.142
Hostname:    UAP-AC-Lite
Uptime:      633 seconds

Status:      Not Adopted (http://192.168.1.1:8080/inform)
UAP-AC-Lite-BZ.5.43.36#

As you can see in the results above, the inform URL is set correctly, but the device is still waiting for adoption.

Wrapping Up

If you are still unable the adopt the Access Point, then follow this article where we are going to solve the adoption failed error.

If you have any questions, just drop a comment below.

Tweet
Pin
Share
Share
0 Shares

Related Posts

Get more stuff like this

IT, Office365, Smart Home, PowerShell and Blogging Tips

I hate spam to, so you can unsubscribe at any time.

34 thoughts on “How to use Set-Inform to adopt Unifi Access Point”

  1. Hi, I have a small unify network (5 UAPs, USG, Cloud key Gen1, and US-8-60W, running fine for 5 years.
    Yesterday I swapped out the US-8-60W for a new USW-24-POE 24 switch, and when accessing the Cloud key config from my PC, it does not find the USW-24-POE 24??
    I can ping it and they are on same subnet (cloudkey 192.168.0.146, UWS 192.168.0.250). I can see the USW as a Unifi client.
    My iphone Unifi app sees the USW-24-POE 24, however adoption fails.
    Cloud Key is running version 6.5.55-16678-1, and fails to upgrade to 7.2.97-18705-1.
    My admin passwords do not work when I try and SSH into Cloud key from powershell. Would this be related?
    Do I need to backup the Cloudkey, and factory reset, upgrade to 7.2.97-18705-1, when restore from backup?

      • Yeah, after a factory reset of the cloud key & upgrade the software, then restored config from backup and all working perfectly … and able to adopt the new USW-24-POE.
        Thank you

  2. I’m not very knowledgable but I got through all this and the status is Timeout. It doesn’t show up in the controller.

  3. Hello,
    Its looks like there is no data transfer between
    my controller (network application for windows 7.2.95) and UAP-nanoHD 6.2.49 (the latest)
    The UAP address is correct (starts with 10.0) the status is always “adopting”,
    and I can’t see the WIFI clients that connected to the AP.
    In the Wi-Fi settings when I un-pause a paused WLAN its not turned on that WLAN.

    In Unifi for Android, I can see that there are connected clients.
    What the red “Restart” doing in the Unifi for Android ?
    Is there a way in Android to add/remove and/or pause/un-pause WLAN

    Thanks,
    Giora

  4. Hi,

    Tried to install a new U6-pro AP but can’t get i to work. AP shows in the controller but adoption is failed. Tried everything (reset, new cables……). Als i cannot ping the AP so i can;t ssh into it. Do you have a suggestion?

  5. Hey Rudy

    I have factory reset the UAP, SSH into it and set-inform to console address. it says server reject.
    I tried adopting it from the Unifi Console and it fails, i tried advanced adoption with device username and password and it fails. Tried the mobile app and couldn’t adopt it.
    I can ping my console from ssh into the UAP!!!
    not sure why it isn’t working.
    Please help!

  6. Hi
    All my APs are stuck in looping between ‘adopting’ and ‘Getting Ready’ after reset. Check:

    UAP-AC-Mesh-Pro-BZ.6.2.35# info

    Model: UAP-AC-Mesh-Pro
    Version: 6.2.35.14043
    MAC Address: f0:9f:c2:d0:d8:c7
    IP Address: 41.x.x.x
    Hostname: UAP-AC-Mesh-Pro
    Uptime: 465 seconds

    Status: Unknown[12] (http://41.x.x.x:8080/inform)
    UAP-AC-Mesh-Pro-BZ.6.2.35#

    • Can you ping the controller from the AC? Ip address 41.xx seems like a public IP, both devices are in the same range? In the case of an online controller, have you checked the firewall settings?

      Also, the firmware on the access point is behind, you can try to update it over SSH.

      • Hi Rudy,
        1. Yes I can ping the controller from the AP.
        2. We’re on public IP (hence censoring IP) and yes devices are in the same subnet (range)

        3. Firewall settings on my PC? I have both my PC (Controller) and the AP connected to the same cisco switch.

        4. I have updated to the recent firmware via SSH.

        THANKS

        • Firewall on your computer won’t be an issue if think (you can test it by simply turning it off it’s running). When access points don’t want to adopt, then often it’s a version mismatch between the controller and access point. You have updated the firmware on the access point, is the controller also running the latest version?

  7. We have an old unifi controller running on a non accessable vmware machine.
    We wish to setup a new unifi controller but when we startup new AP’s we can’t see them in the new (test) unifi controller.
    Even when we set-inform in this case to my ip adres that is running the unifi controller software it won’t show up. (Status: Timeout (https://10.74.0.143:8443/inform))
    From the AP I can ping the adres.

    What am I doing wrong?

  8. My problem is my USG-16-150W won’t adopt. I tried to SSH into it’s IP address but the connection is refused. Can I use the console connection on the back to accomplish this task?

    • yes, that should work. You will need an RJ45-to-DB9, serial console cable, and use the following settings for the connection:


      • Baud rate 115200
      • Data bits 8
      • Parity NONE
      • Stop bits 1
      • Flow control NONE

  10. With your DCHP servers, tell the Unifi equipment where the controller is.
    Use DHCP Option 43. You identify your Unify server in hex. It *MUST* be prefixed with 01 04, then the hex value of your unify server’s IP address. (This is what Unify does when you use their equipment and declare where your UniFi server/console is.)

    https://community.ui.com/questions/pfSense-DHCP-provision-option/b42003ce-7560-4680-8731-805e59459bfc

    Also: https://community.ui.com/questions/DHCP-Option-43/59fb8337-bfa1-4b7d-8e95-3780d10c3603

    For my pfSense, I have to do it like this:
    DHCP Option 43, Select String, and for an IP address of 10.0.0.10, your string value would be: 01:04:0A:00:00:0A

    Read the documentation on your specific format for your DHCP server.

    This fixed many problems across my test lab when playing with subnets.

  11. Thank you. My controller is on a different subnet. I have been wasing my time with this. Your information worked perfectly. Thank you

  12. Pretty neat – started to think my u6LR is a piece of brick. They should add another button, next to reset or something 😉

  13. Thanks a lot! Worked like a charm here.
    One observation though: Windows 10 ssh implementation failed connecting to the AP whereas Putty worked fine, same copy – pasted password (with shift-insert). Did not try with Powershell, but I do remember having earlier used the Powershell ssh just fine.

  14. Hey, sorry but i think i found out what the problem is!

    My Unifi Controller is a Docker Container. If i lost power supply, the container gets a new internal IP Adresse. That is confusing for the set inform adresse. I think i have to set the IP of the Container Static.. but i dont actually know how to do this.. Maybe i’ll find it out and tell it here.

    Regards
    Malte

    • Which docker container are you using? With the jacobalberty/unifi container you could try to use the –net=host option in the docker run. Then it will take the IP of the host. But you will need to check the port number and make sure that you don’t get any conflicts.

  15. No, i think you dont understand me…
    if i change the inform adresse and my power supply is broken – the inform adress resets everytime from a specific IP to 172.17.0.9…

    i dont want to login every time in with ssh so i change in the dns the route of 172.17.0.9 to the valid ip… cause my AP’s dont remember!

  16. Hi, sry but it cant! i repeat it very often. I have to set the inform adresse every time again. Yes the AP’s get connection to my controller (hosted with a docker container)…

    My Workaround: Change the DNS of the given IP in my case 172.17.0.9 to the right IP of the controller… But thats not the solution with the set inform adresse from this guide here. I just want to understand why it doesnt work.

    Regards
    Malte

  17. Hi,

    if i set the new inform adress and the AP lost his Power Supply the inform address disappear. What i have to do to fix that?

    • The access point will remember the last set-inform as well, in case the newly set one doesn’t work. Are you sure that the AP can access the controller?

  18. we are using 3 dhcp servers in a radius server, when i fix new AP it shows different ip range in controller , so the adoption was failed, what was the issue

Leave a Comment

0 Shares
Tweet
Pin
Share
Share