After upgrading my Controller to v5.0.30 everything appeared to be working normally, until a brief power failure at one of my EAP245s caused it to reboot. At this point it appeared in the Devices list as "ADOPTING", and remained like this for 5 solid days.

I checked the Forum here and saw the "Adopting and provisioning loop" thread. The device never says "Provisioning" and I am on x.30 so I don't think this is relevant, but I made sure AI Roaming was off anyway. This didn't help, so I rebooted my controller VM, and now oth my EAP 245s and single EAP 225 are stuck at "ADOPTING" and have been for over 24 hours. My lonely EAP235 Wall mount is the only WAP that is connected.

Devices can still connect to the EAPs just fine and from a user point of view there is no apparent issue, but of course none of these clients show up in the controller, and I cannot make any adjustments to my SSIDs or VLANs.

What further steps can I take to resolve this?

Omada is running on a dedicated Ubuntu 20.04 server instance, on the same subnet as the Management VLan that was set on my EAPs and Switches. Incidentally, all three of my switches are connected just fine. Three different models.