@Fear_na_Boinne 

Green red green red.. That sounds no good. It's more like a "dead"(bricked) device.

Did you upgrade the firmware and disconnect the connection? That'll become bricked. 

Quote LED status:

With the device powered on, press and hold the button for about 5 seconds until the LED is quickly flashing yellow then green, then release the button. The device will restore to factory default settings.

It's getting an IP from the DHCP server? While this makes me think it still works???  Can you use the IP to log into the device and reset it? 

Does it still push WiFi? Can you discover and join? Can you get an IP from the WIFI?

John1234 wrote

@Fear_na_Boinne 

Green red green red.. That sounds no good. It's more like a "dead"(bricked) device.

Did you upgrade the firmware and disconnect the connection? That'll become bricked. 

 

Quote LED status:

With the device powered on, press and hold the button for about 5 seconds until the LED is quickly flashing yellow then green, then release the button. The device will restore to factory default settings.

 

It's getting an IP from the DHCP server? While this makes me think it still works???  Can you use the IP to log into the device and reset it? 

 

Does it still push WiFi? Can you discover and join? Can you get an IP from the WIFI?

@John1234 

I just noticed my previous reply posted empty...

No, there weren't any firmware upgrades in progress. Additionally, the device is still booting and functional! It's SSIDs did correctly reset to the factory defaults, as did the admin user/password combination. It just doesn't seem to start the WebUI!

The AP gets an IP from the DHCP server, and I can strictly speaking log in on SSH, but it fails to execute a shell for me to get in to, and when I try to manually invoke a shell like BASH as part of the SSH command, it tells me it failed to exec that as well. So no way to get in to shell to reset, and no WebUI either!

So it feels like the factory reset that gets invoked on pushing the reset button is incomplete, as if a part of the reset script (the part that removed the OMADA controller settings and reenabled the WebUI) is missing or not getting executed (poor exception catching?)