Dear @Anjerlaan,

Where do these WPA Authentication Timeout/Failure errors and OC200 online notifications come from and are they related to eachother?

Do you find any wireless clients disconnect from the EAP when it shows WPA Authentication Timeout/Failure? 

Please go to Insight -> Pass connection to check if there is association failure showing there.

As for the OC200 online notification, I don't think it is related to WPA authentication, you may confirm whether the OC200 is still properly connected to the network when the notification comes. Besides, power up the OC200 via a PoE switch instead of via the USB port to ensure sufficient power.

@Anjerlaan 

just jumping in because we have similar setups and similar problems. 

I updated to the new version of the software controller (4.2.8) and started noting a TON of failed connections. 

In the 2 days since the update, there's 16,000 (yes, 16 thousand) failed connections. 

I've got an EAP225 and an EAP225 outdoor. I wonder if my neighbors have devices that are just randomly scanning for wifi and failing to connect, and its happening all day long. I'm going to do a deeper dive into the logs. I found one of my wyze cameras is offline and failing to connect, but there's a bunch of other MAC addresses that aren't mine. 

I'm turning down the power of the radio to medium to see if I can slow down the errors. And going to turn off my outside AP totally as part of the testing. 

Curious what else you might have tried or suggest. 

@Anjerlaan 
 

I'll need to check into that. I have two laptops that simply won't connect to any of my SSIDs. I know Google Home minis (and most Google Home devices) have a terrible time with SSIDs that have both 2.4 and 5gHz, so I don't have any of those. I have a separate 2.4gHz just for my "smart" devices, and they stay connected much much better that way. When they lose their connection, I normally hear them do their cycle, and I see the network drop on my Lenovo Display. 

But the only thing that has changed was the udpate to the new version of the controller. I might take the EAP225outdoor out of the controller and see if any of the devices can connect to that. 

Definitely seems like there's some issues with the newest Omada software. I actually bought an OC200 to move to the hardware controller from running the software on my ubuntu server. Long story short -- the OC200 can't accept VLAN traffic other than its own system VLAN1, which isn't what I wanted. So I'm returning it. Figured I'd upgrade to the newest software, and thats when the issues started. 

Dear @CoKro,

I rolled back to 3.2.14 and everything is fine. My "challenging" laptops suddenly authenticated immediately. The only hiccup right now is that the Omada SDN dashboard is showing 0 clients, when everything is connected and working fine. But right now, that was more important than the software.

Omada Controller v3.2.14 cannot manage the EAP with the Omada SDN firmware since they are incompatible. If you want to manage the EAP properly, please also downgrade the EAPs to non-SDN firmware. Similar problem has been discussed Here.