@Gilles2516 

I've got 2 653 AP in my network. 1 is getting disconnected every day since upgrading to 1.3.4. The other one is constantly dropping connections. Tried everything to revert to version 1.1.3 but nothing works. I also noticed that 1.3.4 is no longer available as a firmware version.

  @Gilles2516 I'm using the OC200 2.0 (2.21.7 Build 20250707 Rel.72486) hardware controller.

  @Gilles2516 

yes it seems like something is wrong, found an access point to do a test against the Essentials controller, you can see the result below, haven't tested on any other controllers.

the access point also has Version 6 redy firmware.

but in the short test I haven't lost wifi signal and haven't been logged out of the access point, so everything seems to be working.

  @MR.S 

First of all thanks for looking into this. There is a bit more to it, at least in my situation. I get these logs too:

When this happens I see clients disconnected and moving to other AP's. Network speeds are also affected. 

None of this has happened before the firmware update. My network has been rock solid before.

  @Vincent-TP 

This weekend new firmware for the OC200 was released (2.22.9 Build 20251027 Rel.76714) With this release, so far, it seems that all my previous disconnection errors are over and the netwerk performs much more stable.

  @Vincent-TP 

The update of the controller software seemed to help the problem a bit. I still noticed memory problems on the EAP653. They were high after a boot (62%) with no clients connected. After a few days this slowly increased to 93-95% with only a few clients. Dropping connections with clients and again disconnecting from the controller.

To me it looks like the amount of memory in these AP is not sufficient. For example: my old EAP245 has only a memory usage hovering around 42%

For now I've found a temporary solution in disabling fast-roaming and bandsteering. I also disabled 2 of my 5 vlans for these AP's. I also created a daily reboot schedule for these AP's. It's a bit of a workaround until there's new firmware that properly adresses the memory leak.

@Vincent-TP  
@OlivierNijs 

I have two eap653v1 with firmware 1.3.4. controlled by an omada software controller. Problems started by upgrading the eap to firmware 1.3.2: Massive memory leaks making it necessary to reboot the eap653 twice a day. Upgrading the omada software controller from v5 to v6 did NOT resolve the issues. Today I was in touch with tp-link phone support and was told that all eap653v1 firmware version 1.3.x are NOT stable and one must downgrade to firmware version 1.1.3. According to tp-link support a direct manual downgrade from 1.3.4 to 1.1.3 is NOT possible. So I was to told to first install firmware version 1.3.90 before a downgrade is possible. A provided download link via email is inaccessible for me, since it needs a login. So I'm waiting for them to upload the required firmware to my selfhosted cloud storage.