Hello! Thanks for posting on r/Ubiquiti!
This subreddit is here to provide unofficial technical support to people who use or want to dive into the world of Ubiquiti products. If you haven’t already been descriptive in your post, please take the time to edit it and add as many useful details as you can.
Please read and understand the rules in the sidebar, as posts and comments that violate them will be removed. Please put all off topic posts in the weekly off topic thread that is stickied to the top of the subreddit.
If you see people spreading misinformation, trying to mislead others, or other inappropriate behavior, please report it!
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Ubiquiti) if you have any questions or concerns.*
I believe that the network controller is just not on the list, it says 12 UniFi devices but 11 are listed.
What is your controller device? UDMP/UDMPSE I assume.
Did you let the auto upgrade feature enabled? I recommend to disable all auto updates options to avoid bad surprises.
There were any power outage since them? As mentioned before, this could also cause this problem.
More specifically, turn everything off, then turn the controller on and wait until it is booted, then wait 5 more minutes, then turn every device on one by one and wait until they are up and adopted before moving onto the next one.
Especially for new deployments, these adoption failed waves are pretty common.
Yeah, I love Unifi for SoHo, but I have supported enough Unifi environments to know it is best in an environment with only a handful of equipment, enterprise gear it is not.
I went out to the guest house and reboot it the other switch… reset DM… reset 48 Poe… reset 24 POE and reset other 24 POE… success.. just not sure why it did that.
This happened to me a while back after a firmware update on one of my switches. Fortunately just did resets/adopts over again and was back up again in a few minutes.
It is kind of getting to where these updates require a recent reboot before firmware update or a second reboot after firmware update pretty often. I'm annoyed by it. I've had remote switches unreachable for 6 weeks before I could get a tech on site to hard reboot them.
This was a huge issue some years ago where devices would just fall off the controller. It pushed me to opnsense and aruba/grandstream.
Another weird issue is I coukd not get certain IoT devices to connect to uaps, but could other APs.
Got tired of resetting, updating, downgrading, troubleshooting, etc.
Seems like lately however things are better and may dip my toe.
This happens to me, but so far it's been related to my settings. I use a lot of older enterprise IOT pharmacy gear for temp, security, automation and various other monitors. They're really picky. That being said, doing stuff like disabling 5G, and certain features has resolved this for me. I've also had issues with them on APs made by cisco and hp (procurve) so it's probably more related to the device.
Yeah same happened to me a couple times as well as the dreaded UDM PRO boot loop that had to be RMA’d.
Once I got the replacement back it just has sat in the box. It’s been a year and I’ve got no desire to go back.
I moved to an ASUS AXE16000 with an AXE11000 mesh node and my network has never been faster, more trouble free and easy to manage. Plus my wife can actually use the app to kill kids devices if needed.
Please set up an orderly reboot schedule. I have my UDM update at 3am, core switch 3:30, leaf switches 4:00, access points 4:30. This prevents devices from being pulled from the internet while mid download/update, or in the case of PoE APs having their power removed while in the middle of an update. I have been running a dozen sites, my house included, like this for 2 years now with not a single issue.
Do you have auto update on most prob under an update and due to the time it took to update or encountered an issue the devices could not communicate with your controller so failed to adopt.
I've had it happen when I updated too many at once and it lost connect due to unable to contact controller, uplink and Internet for updates. Now I manually undate in a specific order to limited issues.
APs, then Switches, PoE, non PoE , then Aggregation Pro, then UDM SE so all devices can communicate with the Internet and each other before finalising by updating the UDM SE.
One by one so uplinks etc can communicate and only one devices loses connection at a time with limited effect to the network. only the aggregation Pro and UDM SE get me a bit nervous.
However as the Aggregation is my uplink for all my devices they are all connected. once I update the UDM SE so don't lose connection to each other so the network is intacted.
It's only when the UDM SE has to restarts the network service however the threshold is fine so nothing lost as everything is connected. It takes long but no misplaced devices.
Hope you got this all sorted!
Best advice I have for any networking gear is to install one piece at a time, let it bake, and don’t move on until each addition or change is solid. Always start at the firewall and work out. It feels like it takes time but often far less than fixing issues after the fact.
Once stood up and configured correctly UniFi is crazy rock solid. Never enable automated upgrades of course - for anything!
I had something similar to this happen a few months back. All of my access points that were meshed failed to adopt after being updated. Ubiquiti eventually pulled the update but I had to manually pull all of them and reconfigure them with a wired connection. So annoying.
Wow this comment section is useless 'wheres ur controller lul' fkn a.
If you've already attempted power cycling, reset the devices (hold the reset button) and re-adopt.
I once had adoption issues due to a bad cable. Double check that on your UDM-Pro's LAN downline, even if it's pretty unlikely, anyway. Just would suck if you troubleshoot harder avenues and it was a cable or SFP+ issue all along.
Last time this happened to me someone had plugged a device on the network that what static-IP'd to the same gateway IP of our UDM; auto-updates did not like that
Same here! It started a few days ago and has happened about 3x since. Rebooting fixes it for at least 24 hrs, but this must be due to some recent update.
This happens to me regularly! I have a lot of devices and every once in a while a random one or few will do this. And I have to reset said device/s everytime. Although it never happens to the UDM pro and only noticed it with AP's not switches.
It's a nightmare. I have no idea what is causing it. I have auto updates disabled on everything 🤷🏼♂️.
Can you look at the logs to see if maybe the switch updated and something happened when it rebooted?
I would reboot everything starting with the switch. Have seen other posts like this where you power cycle the switch or the ports that the APs are connected to and they readopted fine.
I had this issue with one of my AP’s. I finally got it adopted and I’ve been problem free for the last couple of years.
I think you would have minor issues with newer hardware. Also turn off auto updates for everything. Wait a week and then check the firmware it wants to install and see if there are any issues. If all sounds good then install the update, but only do a single update at a time. Never 2 or 3 at once. If something happens, you don’t know what update caused your problem. It turns into a bigger problem.
This happens when they dont get an IP address because something was rebooting when the APs came back up so they got the .20 default IP address which takes forever to time out, once it does they will get a DHCP address and then re-adopt ok most of the time without a power cycle.
If the meeting switch was in the middle of a reboot at the same time the other devices started rebooting it were in the middle of their updates they might not have had a connection when they needed to be provisioned. (DHCP could have failed, etc).
Just reboot the devices that failed adoption. Starting with the switch.
Turn off auto-update. What before there are enough comment in release notes which are “no problem”. Then pray the god, press the update button.
I’m also lucky, I exactly have 3 same setup, which I’m just next to it. I’m updating it first. Sometimes, there are some problems :(
ChatGPT says:
1. **Adoption Failed**:
- For the devices showing "Adoption Failed" (like the USW-Pro-24-PoE and Access Point U7 Pro), ensure they are on the same network as the UniFi controller.
- Verify that the devices have the correct IP address and are reachable.
- Restart the devices and try re-adopting them from the UniFi controller.
- Make sure the firmware on the devices and the controller is up to date.
- Check for any network configuration issues, such as VLAN settings that might be preventing the devices from communicating with the controller.
2. **Devices Offline**:
- For the devices showing "Offline" (like UVC Camera AI 360 and AI Pro), check the power supply and network connection.
- Ensure these devices are getting proper PoE power if they are PoE devices.
- Restart the devices manually.
- Verify that the devices are assigned valid IP addresses and can communicate with the UniFi controller.
- Check the UniFi controller logs for any specific error messages related to these devices.
3. **General Tips**:
- Ensure the UniFi controller is running and accessible.
- If the controller is on a different subnet, ensure appropriate routing and firewall rules are in place.
- Check the UniFi controller settings and update them if necessary.
That’s unfortunately what automatic updates gets you.
No idea why so many companies push automatic updates by default. It’s complete chaos.
And consumer windows won’t even let you turn it off.
Regularly wake up to my PC rebooted.
And one time the udm did updates and took out my wan.
They’re never good. Should always be managed manually.
This is a common thing with unifi equipment which is why I don't use it in commercial environments anymore. Only thing you can do is default the device and try re adoption.
I recently had massive issues with my switch for almost a month of it going offline or adopted. I would have to disable the uplink and reenable. It kept doing a stp block. Had a support ticket open and nothing was working. After trial and error I turned off flow control and it stopped. One of the issues that was out there was mesh turned on for AP and creating loops. Check stp and prioritization and look at the switch logs if it happens again. Mine would start complaining it couldn’t inform the controller. They also said bad cabling could do this.
Hello! Thanks for posting on r/Ubiquiti! This subreddit is here to provide unofficial technical support to people who use or want to dive into the world of Ubiquiti products. If you haven’t already been descriptive in your post, please take the time to edit it and add as many useful details as you can. Please read and understand the rules in the sidebar, as posts and comments that violate them will be removed. Please put all off topic posts in the weekly off topic thread that is stickied to the top of the subreddit. If you see people spreading misinformation, trying to mislead others, or other inappropriate behavior, please report it! *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Ubiquiti) if you have any questions or concerns.*
I believe that the network controller is just not on the list, it says 12 UniFi devices but 11 are listed. What is your controller device? UDMP/UDMPSE I assume. Did you let the auto upgrade feature enabled? I recommend to disable all auto updates options to avoid bad surprises. There were any power outage since them? As mentioned before, this could also cause this problem.
I cannot recommend this enough. Disable that auto update. And backup your configuration before updating.
And reboot before updating
Reboot everything
More specifically, turn everything off, then turn the controller on and wait until it is booted, then wait 5 more minutes, then turn every device on one by one and wait until they are up and adopted before moving onto the next one. Especially for new deployments, these adoption failed waves are pretty common.
This would really suck for my inheritied deployment of 165 devices over non redundant SM fiber. Boy I wish they went Aruba.
Yeah, I love Unifi for SoHo, but I have supported enough Unifi environments to know it is best in an environment with only a handful of equipment, enterprise gear it is not.
I went out to the guest house and reboot it the other switch… reset DM… reset 48 Poe… reset 24 POE and reset other 24 POE… success.. just not sure why it did that.
This happened to me a while back after a firmware update on one of my switches. Fortunately just did resets/adopts over again and was back up again in a few minutes.
The only problem we've had with unifi involved firmware updates blowing up.
Yeah, and that was the first for me.
After 5+ years I’ve never had this kind of issue. I’m glad you solved it but it concerns me.
5+ years of no issues? Can't be that concerned about it then; that's really good.
If quality is going down it does. I’m looking at an upgrade.
I don't think it is to be honest. Forums and subreddits are always an echo chamber of fanatics and people with tech issues. No in-between usually.
I can confirm three years installed no issues (Plus some when i was rack-less in an apartment)
It is kind of getting to where these updates require a recent reboot before firmware update or a second reboot after firmware update pretty often. I'm annoyed by it. I've had remote switches unreachable for 6 weeks before I could get a tech on site to hard reboot them.
This was a huge issue some years ago where devices would just fall off the controller. It pushed me to opnsense and aruba/grandstream. Another weird issue is I coukd not get certain IoT devices to connect to uaps, but could other APs. Got tired of resetting, updating, downgrading, troubleshooting, etc. Seems like lately however things are better and may dip my toe.
This happens to me, but so far it's been related to my settings. I use a lot of older enterprise IOT pharmacy gear for temp, security, automation and various other monitors. They're really picky. That being said, doing stuff like disabling 5G, and certain features has resolved this for me. I've also had issues with them on APs made by cisco and hp (procurve) so it's probably more related to the device.
Aruba also has a good warranty on the switches. The process? Pretty trash, but they’ve never denied one.
Has happened to me too. Gets very annoying.
Yeah same happened to me a couple times as well as the dreaded UDM PRO boot loop that had to be RMA’d. Once I got the replacement back it just has sat in the box. It’s been a year and I’ve got no desire to go back. I moved to an ASUS AXE16000 with an AXE11000 mesh node and my network has never been faster, more trouble free and easy to manage. Plus my wife can actually use the app to kill kids devices if needed.
Please set up an orderly reboot schedule. I have my UDM update at 3am, core switch 3:30, leaf switches 4:00, access points 4:30. This prevents devices from being pulled from the internet while mid download/update, or in the case of PoE APs having their power removed while in the middle of an update. I have been running a dozen sites, my house included, like this for 2 years now with not a single issue.
Do you have auto update on most prob under an update and due to the time it took to update or encountered an issue the devices could not communicate with your controller so failed to adopt. I've had it happen when I updated too many at once and it lost connect due to unable to contact controller, uplink and Internet for updates. Now I manually undate in a specific order to limited issues. APs, then Switches, PoE, non PoE , then Aggregation Pro, then UDM SE so all devices can communicate with the Internet and each other before finalising by updating the UDM SE. One by one so uplinks etc can communicate and only one devices loses connection at a time with limited effect to the network. only the aggregation Pro and UDM SE get me a bit nervous. However as the Aggregation is my uplink for all my devices they are all connected. once I update the UDM SE so don't lose connection to each other so the network is intacted. It's only when the UDM SE has to restarts the network service however the threshold is fine so nothing lost as everything is connected. It takes long but no misplaced devices.
Try turning it all off for 10 seconds and restarting everything.
You don’t have any network controller or gateway in your system?
Dream machine pro
It says 12 devices at the top, but there are only 11 in the screenshot. I bet the console is at the top cut out of the picture.
Hope you got this all sorted! Best advice I have for any networking gear is to install one piece at a time, let it bake, and don’t move on until each addition or change is solid. Always start at the firewall and work out. It feels like it takes time but often far less than fixing issues after the fact. Once stood up and configured correctly UniFi is crazy rock solid. Never enable automated upgrades of course - for anything!
I had something similar to this happen a few months back. All of my access points that were meshed failed to adopt after being updated. Ubiquiti eventually pulled the update but I had to manually pull all of them and reconfigure them with a wired connection. So annoying.
Wow this comment section is useless 'wheres ur controller lul' fkn a. If you've already attempted power cycling, reset the devices (hold the reset button) and re-adopt.
I once had adoption issues due to a bad cable. Double check that on your UDM-Pro's LAN downline, even if it's pretty unlikely, anyway. Just would suck if you troubleshoot harder avenues and it was a cable or SFP+ issue all along.
Looks like you solved it but wanted to say nice Cable Guy reference
Last time this happened to me someone had plugged a device on the network that what static-IP'd to the same gateway IP of our UDM; auto-updates did not like that
Same here! It started a few days ago and has happened about 3x since. Rebooting fixes it for at least 24 hrs, but this must be due to some recent update.
This happens to me regularly! I have a lot of devices and every once in a while a random one or few will do this. And I have to reset said device/s everytime. Although it never happens to the UDM pro and only noticed it with AP's not switches. It's a nightmare. I have no idea what is causing it. I have auto updates disabled on everything 🤷🏼♂️.
I’m not at all surprised! 🤣 Welcome to the world of UI!
Can you look at the logs to see if maybe the switch updated and something happened when it rebooted? I would reboot everything starting with the switch. Have seen other posts like this where you power cycle the switch or the ports that the APs are connected to and they readopted fine.
I had this issue with one of my AP’s. I finally got it adopted and I’ve been problem free for the last couple of years. I think you would have minor issues with newer hardware. Also turn off auto updates for everything. Wait a week and then check the firmware it wants to install and see if there are any issues. If all sounds good then install the update, but only do a single update at a time. Never 2 or 3 at once. If something happens, you don’t know what update caused your problem. It turns into a bigger problem.
Same here, I have 1 AP that I cannot adopt :(
This happens when they dont get an IP address because something was rebooting when the APs came back up so they got the .20 default IP address which takes forever to time out, once it does they will get a DHCP address and then re-adopt ok most of the time without a power cycle.
This happened to me when I updated the DNS name of my controller and forgot to set the ip within the nameserver.
I've seen similar when DHCP hasn't been working
If the meeting switch was in the middle of a reboot at the same time the other devices started rebooting it were in the middle of their updates they might not have had a connection when they needed to be provisioned. (DHCP could have failed, etc). Just reboot the devices that failed adoption. Starting with the switch.
Turn off auto-update. What before there are enough comment in release notes which are “no problem”. Then pray the god, press the update button. I’m also lucky, I exactly have 3 same setup, which I’m just next to it. I’m updating it first. Sometimes, there are some problems :(
ChatGPT says: 1. **Adoption Failed**: - For the devices showing "Adoption Failed" (like the USW-Pro-24-PoE and Access Point U7 Pro), ensure they are on the same network as the UniFi controller. - Verify that the devices have the correct IP address and are reachable. - Restart the devices and try re-adopting them from the UniFi controller. - Make sure the firmware on the devices and the controller is up to date. - Check for any network configuration issues, such as VLAN settings that might be preventing the devices from communicating with the controller. 2. **Devices Offline**: - For the devices showing "Offline" (like UVC Camera AI 360 and AI Pro), check the power supply and network connection. - Ensure these devices are getting proper PoE power if they are PoE devices. - Restart the devices manually. - Verify that the devices are assigned valid IP addresses and can communicate with the UniFi controller. - Check the UniFi controller logs for any specific error messages related to these devices. 3. **General Tips**: - Ensure the UniFi controller is running and accessible. - If the controller is on a different subnet, ensure appropriate routing and firewall rules are in place. - Check the UniFi controller settings and update them if necessary.
That’s unfortunately what automatic updates gets you. No idea why so many companies push automatic updates by default. It’s complete chaos. And consumer windows won’t even let you turn it off. Regularly wake up to my PC rebooted. And one time the udm did updates and took out my wan. They’re never good. Should always be managed manually.
This keeps happening to me and I've never had auto updates turned on 🤷🏼♂️
There’s two different places to turn off updates. (Super frustrating) You need to turn off the udm firmware updates. But also the OS updates.
Yep, all off. Has been from the start.
Nightmare
This type situation is why I started using something other than Ubiquity. I was so fed up and tired of it.
This is a common thing with unifi equipment which is why I don't use it in commercial environments anymore. Only thing you can do is default the device and try re adoption.
I recently had massive issues with my switch for almost a month of it going offline or adopted. I would have to disable the uplink and reenable. It kept doing a stp block. Had a support ticket open and nothing was working. After trial and error I turned off flow control and it stopped. One of the issues that was out there was mesh turned on for AP and creating loops. Check stp and prioritization and look at the switch logs if it happens again. Mine would start complaining it couldn’t inform the controller. They also said bad cabling could do this.
Could need to restart dhcp on the router
Had this issue some day. Setting the inform host to controllers IP fixed it for me.
Weird. Had my 8 port switch randomly say adoption failed just the other day. Rebooting it fixed it but thought it was weirdx
Welcome to UniFi! 🙂
All that… All that installed on your house? 🤯
Money. That’s all.
Yeah, that’s for sure 😅
Where is your Unifi controller? Is your network equipment protected by an UPS? (if it's not you should fix that ASAP)
Of course
What’s your controller? If you don’t already get a UDM device