Hi  @dahls 

Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240844622, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!

  @Vincent-TP thanks!! I'm home office based hence my network Is my lifeline :-)

  @Vincent-TP 

1: Cables has nothing to do with this issue. The longest cable is 15m, and is a CAT6. 

2: Everything worked BEFORE the FW upgrade. 

3: I cannot do a role back to previus FW version on the OC200 due to that the backup file dosent work with the previous FW version?!

4: ALL the POE adaptors are TP-LINK 

5: ALL network components are TP-LINK OMADA. 

6: TWO EAP-610 are DIRECT connected to the ER706W (via TP-LINK POE adaptors)

I cannot work with this network. 

Please help. 

  @dahls 

For my oc200 v2.0, I found this beta firmware in the forums.

Version:

5.14.20.21

Build:

2.16.1 Build 20240428 Rel.85008\

After installing it, all my Omada WAP client connectivity issues went away.

I've also heard that enabling 802.11r on Omada has issues, so you may try disabling that too.

  @tolcheen im using 1.31.3 Build 20240620 Rel.80383

   @dahls You have a v1 hardware while I have v2 controllers deployed. It took me a while to find it, but go to this post and you can download the equivalent v1 of the software if you would like to try. It's a downgrade, but for me the latest did not work, having the same issues.

https://community.tp-link.com/en/business/forum/topic/663452

  @tolcheen the issue then is that I need to rebuild the whole network. All settings etc. the eap610 are high up... then I need to sync everything again. This is a massive work :( 

don't see why tplink can't fix this ?!