OK, So this is mostly my fault, and a lesson learned.  But i also feel there should be a built in check to prevent the very thing i did.

I was modifying a switch ACL and accidentally blocked management vlan from itself, killing all omada functionality network wide once it populated to all switches before i could stop it.

I had to disconnect my OC200 from lan, set a static IP on my laptop to connect to management vlan without any switches blocking traffic, correct the ACL mistake.  I hoped that was the end of it, but evidently whatever method Omada uses to provision equipment doesnt bypass ACLs on the management vlan, so my change didnt make it to any of the switches.

I had no choice but to do a hardware reset over putty (they are all L3 switches without a reset pinhole) on each switch, having to unscrew some from some racks to access the power cord.  Once all were factory reset I had to manually connect to my controller again to start the adoption process.

Thankfully, i didnt have to reset my ER8411 gateway with its super slow boot times.

What a pain in the behind.

Anyway, i really feel there should be a simple check in the controller GUI that prevents this from hapenning.