Видео

Thanks for this information. I was able to get things working using this method. Why this isn't documented or shared by Ubiquiti is a surprise to me.

Can you clarify? Are you saying you didnt have LAN or WAN plugged in and it only had Mesh to existing APs to try and use to find your controller and then adopt?

@@tobyport5873 Yes with nothing plugged in. If you have other wireless mesh devices it should detect it.

I also cant get mine adopted. So, are you saying you set it up, added a user ubnt/ubnt and then adopted it? when i tried to ssh into it, using the set-inform method, the default login was ui/ui, not ubnt ubnt. the blasted thing is driving me nuts. Can you please elaborate?

@tobyport5873 ok so I use a self hosted network application (in theory, should work the same as a cloud key once you log into the web portal). When you’re logged in via the web, you have a username/password. For my network application, I changed the user to “ubnt” password was the same. Hooked up my unifi express and went through the adoption process to add it to my existing stuff. And it found it right away and adopted. NOTHING else I tried worked like this has worked. After it was adopted, went back to my unifi network application dashboard, adjusted my user login back to what it was before and all is good

@@tobyport5873 Somehow I thought I replied to this. I use a self hosted unifi network application. In theory, it should work exactly like a cloud key once it's setup. In the web interface, I changed the main user to be ubnt and the password to be ubnt. I then connected the unifi express to my network and searched for it via the Network Application web interface. Went through the adoption process and it adopted right away. After the adoption was complete, I changed my login username/password for the network application web interface back to my defaults. I didn't have to SSH or do any set-inform procedures. Simply changing the default username in the web interface of the network application (or maybe the cloud key in your case) was enough to make the device adopt. I have also done the mesh adoption process that the OP listed in their description. But that method is a pain in the butt and it really should not be this hard to get a piece of equipment adopted. Especially in a way that it's described to be able to function. Hope this helped you out!

@@tobyport5873 I keep replying to you but the comment keeps vanishing! If you can see the reply, let me know if that helped you and you got everything adopted

I am still trying to get an RMA return and refund on my order with Oukitel directly. So far I have neither a working/charging tablet nor my money back.

​@@MicahStroud I tried all cables and charger but it doesn't work in OFF Mode and I only see blinking red LED light, I try to boot it ON via pressing the ON button for 5 to 10 seconds to fully ON the tablet, I tried to research it on Google but I couldn't see any answers .... I will return this tomorrow via J&T services and the seller will pay for the return shipping of the unit not me that's why he is begging for compensation...lol

​@@MicahStroudanother system update just arrived

​​@@MicahStroudI returned my Oukitel ot5 after newer system update is still the same, the worst part is the system update its only 13mb but it took 30 minutes of installation and still no progress I still can't charge my OT5 in OFF Mode and I have to press the power for 5 to 10 seconds to boot it ON that's why I returned it to shopee... I'll get Redmi Pad SE or Blackview Tab18 if my money is refunded...