@Arne17 That would be helpful! I'll wait for the DM and then report back. If that doesn't solve the issue, I'll post my config -- it's pretty standard with 2 VLANs (IoT and a trusted networks) and 2 SSIDs. Thanks!

@Hank21  Do we know if the fix found in the firmware version sent by TP-Link Support (EAP650v1_1.0.91) made it into the lastest beta?

EAP650-Wall v1.0 _1.3.0 (Pre-release Version)

This is my configuration.

General Site settings (Site Configuration -> Scroll down for wireless.)

IoT WiFi:

  @Arne17 These match my settings exactly. At this point, turning 6g off, switching to WPA2, and turning PWM = Off seems to have solved the problem.

This is annoying because I'd like to be able to use WPA3. I'm trying to decide if I downgrade my EAPs to the firmware supplied by the TP-Link Supprt Team or I just keep WPA2 until an update is available.

  @Arne17 

I'm further up in this thread and after working through it with support since December, here's what ended up working for me:

-New firmware

-Can not use non-stick roaming in any situation

This solved the issue of things dropping off-line, but we had roaming issues. Interestingly, we found that rebooting APs solved this, too.

After a ton of trial and error we found out that the OC200 controller couldn't manage the mesh. I ended up buying an OC300 and it all seems stable in the short term. I'd like to see it work for longer before I say it's fixed. I totally regret buying into this ecosystem at this point. Having to buy more stuff to make what should have worked, actually work is really unacceptable, but I've now found a bunch of people who said the OC200 is basically a non-functional entry point. 

  @Off-grid By new firmware do you mean the firmware supplied by Support EAP650v1_1.0.91?

  @CoffeeAndTech What's the point in having WPA3 capabilities for IoT? I don't really know of any devices supporting that at this time. WPA3/WPA2 mixed mode is known to cause issues on other vendors, too. I think using WPA2 for IoT devices is an acceptable risk. I think focusing more on securing the subnet itself, restricting internet access for every IoT device etc. will gain more security overall than WPA3 in the long term. Most IoT stuff is built so cheap with bad software and never gets updated. I also don't think this whole issue is TP-Link alone but also IoT devices not following specifications.

Regarding the controller side: I have the Omada software controller running on an Ubuntu VM on a proper server system. No surprise to me that the base model HW controller has no headroom. My Omada VM is using a lot of resources while idling. 

Other systems like Synology, Unify etc. all have their quirks that users are fiddling with. Enterprise grade hardware costs way more money that I don't want to spend for home use. The Omada system definitely has some bugs here and there, but overall nothing that I couldn't fix, except for this one here of course. I hope it'll run for longer now and will probably invest more into this ecosystem in the future.