Hi  @Hank21 

I've tried the latest Beta for the EAP653 after I've encountered the same problem mentioned here https://community.tp-link.com/en/business/forum/topic/628596 and https://community.tp-link.com/en/business/forum/topic/641576

I've got three EAP653 in total and flashed them all with the same version 1.0.90 Build 20231012 Rel. 31553. Since I've installed the update I've got no problems with unresponsive Accesspoints. However, a few other side effects occurred now way more often:

Last time I've checked my Omada Controller Log I've seen a huge number of association failures:

I've read that I should reduce the transmitter power, so its now to medium. I've got two APs quite close together, but separated with a big concrete wall of a staircase, but this doesn't seem to affect these failures.

Additionally I've had download problems that only occurred when connected via Wifi, but not via LAN. So I could rule out my internet connectivity. Wifi connection was quite good at around 800mbps during that time so it shouldn't be the issue. It happened on two separate Macs connecting to the same AP. Once they connected via LAN the download was fast again.

 Hi @Hank21,

I cannot move the EAPs, since they are already in their place for over an year without seeing this authentication error issue.

During that time no devices were added to my network, so that shouldn't be an issue of wrong passwords. I've tried the AI Wifi Optimization in the past but it did not help much, so I've put each AP on separate channels with enough space to the next one to avoid overlaps in the frequency bands.

In the meantime, I did not check Omada again. But when I wanted to check the log as you suggested, I've seen 20221 new authentication failures. I've noticed this morning, that my iPhone was unable to use the Wifi and asked me, if I'm really connected to the internet. What place should I check the logs? I've selected the organization with the affected failures and clicked on logs. I don't see any error messages, except the ones where one of my EAP653 started to disconnect regularly and I flashed the beta firmware to solve this. I don't have any messages on warning and on Info I only got messages of devices connecting/disconnecting, which looks quite normal I assume.

However, what's interesting is that these 20221 new authentication failures came all from the same EAP653 which started to misbehave and caused my journey of flashing beta firmware in the first place. Do you need anything specific from this AP only? I've pulled the Device Info for this AP and could send it to you.

Hi @Hank21,

The client logs where on the default levels and I've set them as you requested. In the meantime it showed today 19615 failures for the affected AP.

All three EAP 653 run 1.0.90 Build 20231012 Rel. 31553 and are powered via PoE on a TL-SG2008P v2.0 with Firmware 2.0.7 Build 20230602 Rel.73473.

The iPhone recovered itself after a while, at least when I've taken a look the next time I've checked it. Its currently working.

 Hi @Hank21,

I've got a new problem today. One of my EAP653 decided to be unresponsive to the health requests and stopped serving data. Devices connected to it had a dropped connection until I've unplugged that AP and restarted it. Its the only AP that was unresponsive. The other two APs are using the same beta firmware and are now online for 34 days withour reboots.

@Hank21 

i have the same issue with the new firmware for eap 650 v1 that was released 

a lot of devices won't connect to ssd or don't receive an IP