Unifi UAP LR not being detected, solid amber light

[spiceuser-u4tkb]

Hi Guys,

So I’ve deployed a crap ton of these in the past. Never had one single issue… until today.

So I have an old UAP LR that I got off a client site. It’s old and was replaced with a newer model, but was working fine with no problems. Client just liked the blue light on the newer model. When we left the site, he told me to take them off site and do ‘what ever i want’ with them. So…

I kept one of the devices and did a factory reset on it. (Hold down the reset button for 10 sec etc). It restarted and came up solid amber (ready for adoption I believe, but definitely on factory defaults per the website).

I installed the controller on my PC (5.12.22) and it started up fine. I launched it and created an account for home use… but for the life of me, I cannot find this damn device on my home network.

Firewall is disabled, the device is powered etc. I’ve used different POE’s, cables, routers etc… but nothing. I’ve tried directly connecting it to a laptop and using the default IP that is assigned to many Ubiquity devices (192.168.1.20) but that didn’t work either. Really want to deploy this device as an extender in my house. Any help would be greatly appreciated.

[byronhynes (bphynes)]

What I would do first is see if the AP is pulling a DHCP address by checking the DHCP server.

Then make sure that your UniFi controller software is on the same broadcast domain (or “subnet”). You can use DHCP to tell the AP where to register, but in most installations it’s just going to broadcast for the controller. It doesn’t need the controller to operate, but it does to get set up.

If you know it’s getting an address and don’t see it in the controller, download the UniFi discovery tool and see if discovery sees it.

We have 75 UniFi APs across our largest site and they do fail, especially the older models. (We’ve stopped mounting them in places that we need a lift to reach. Lol.) However, we find they still represent good value.

[Rod-IT]

You said you took them all off site - where are the others to try another one?

If you scan your LAN - do you see it at all?

Put Wi-Fi on your mobile, can you see the AP that way - this might confirm if it reset or not

[markwilliams3]

Use the phone app to block it in. Even if you just use it to point the AP to the controller.

Is the controller named ‘unifi’ in your local DNS? That alone can stop the AP from finding the controller.

[stephenwilkins]

scan your network using a net scanner and see if it has a dhcp address, then use putty and log into it and set the adoption manually to the controller pc.

https://help.ubnt.com/hc/en-us/articles/204909754-UniFi-Device-Adoption-Methods-for-Remote-UniFi-Controllers#8 -step 3 under ssh i usually add sudo to it as well and send the command twice.

[john31182877 (john.chuma)]

I would attempt doing a factory reset on the AP and then see if it will come up.

[milerky2]

I had this issue…

I went to the DHCP in my router, put the MAC in my ip reservations, then restarted the AP. It discovered it then.

(I was adding them to my consumer Netgear router at the time.)

[evantuohy1019 (Evan8697)]

try new POE injector or connect to POE port on switch.

make sure it is plugged directly into the device doing DHCP

Do manual firmware updates once an IP is seen and SSH access is up

[gregghill (greggmh123)]

@markwilliams3

Use the phone app to block it in. Even if you just use it to point the AP to the controller.

Is the controller named ‘unifi’ in your local DNS? That alone can stop the AP from finding the controller.

It’s an old UAP-LR; the phone app doesn’t work with those models.

Gregg