@FreeBSD 

Here is the command to reset EAP via SSH:

cliclientd reset

Or you can factory reset the EAP via its reset button:

Press and hold the button for around 8 seconds.

Hi  @FreeBSD 

Thanks for the feedback.

Each firmware release undergoes rigorous testing before publication. This issue might be related to your specific usage scenario.

Did you configure VLAN settings for the network?

Would you please share a screenshot of the topology, including the EAP and the controller? 

FreeBSD wrote

Thanks that will be helpful for next time. It seems I have the same problem as [1] below. After upgrading to 5.2.0 neither EAP265 HD v1 US will attach to the controller at all. I had to downgrade to 5.0.5.

 

I tested upgrading to 5.1.0 which broke WiFi with many settings showing no option on my Omada controller, and 5.2.0 wouldn’t even give me the option to adopt it.

 

Worst part of it all is that I was running 5.1.0 without any problems until I tried to upgrade to 5.2.0.

 

All hardware is running the latest firmware including my OC300 Omada controller. [1] https://community.tp-link.com/en/business/forum/topic/765592

Hi  @FreeBSD 

We are very concerned about your feedback. Has the issue been resolved? 

In the meantime,  I had created a support email to follow up on this case more efficiently. The case ID is TKID250758671.

Please check your email inbox. Thanks.