I had something weird happen to a UniFi network I manage that upgraded to a new ISP. I set this network up initially and never had issues with the WiFi portion of this UniFi network.
They upgraded to a fiber ISP after being on Cellular for the longest time because it was the only thing offered in the area. They wanted to keep the Cellular as a backup, so we added the wired WAN (Fiber) to the Pepwave Modem/Router and made it priority. All of that is fine.
However, only our WIRED devices have Internet. I have two PC's there (one for IP cameras and one so I can remote into to troubleshoot issues). A few TV's are wired but every other PC, laptop, phone all rely on WiFi and there is NO internet and as a result, they get a 169 address.
On the UniFi network, the Wi-Fi network is connected to the network I named LAN and it points to the DHCP provided by the Pepwave Modem/Router:
The "Wireless" network uses LAN and the AP groups called Access Points which all pull a 50.1:
And here is a vew of all of the devices in the UniFi network...
What is interesting is the dependency on the AP called STORAGE ROOM.
(side note, ignore the BEACON Adoption FAILED for now...I am currently upgrading them to those but this issue has pulled me away from it).
I've done a lot of searching and I cannot for the life of me figure this out. The challenge...this is for or CEO and he is already upset (unfairly) at how long it has taken me on some projects for him personally (being the SOLO IT person for company too)...he is out of town until Monday afternoon but I only have remote access to his house until Monday morning. I can troubleshoot remotely...like I said, I have internet on the wired devices and he can see his port forwarded IP cameras but no internet for the Wi-Fi. Since he can see his cameras where he is now, he is happy and he doesn't know the internet to the Wi-Fi is down.
Any other suggestions?