@Shoresy Do you have an estimated release date for the new firmware for the EAP660HD and EAP653 supporting the "Lock to AP" feature (considering 5.9.31 is already the second FW version of the controller that is advertised to have this feature that cannot be used) ?

Thanks for your answer @Shoresy, I thought you were TP-Link staff.

Anyway, how do you know that the "Lock To AP" feature requires new firmware for the EAPs to work?

The release notes do not state that:

(capture taken from the Release Notes of Omada Software Controller_V5.9.9_Linux (Released on Feb 28, 2023))

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

Thanks again for your reply. I hope the general consensus is correct and that the new FWs for the EAPs and switches to support this feature are around the corner. As you wrote in the other topic, it is just what we need for IoT devices that don't need to be roaming.

I can personally vouch for the fact if you enable the feature currently strange things happen and you will have one hell of a job getting things back straight.

Why on earth there are options that can be enabled in software which require further firmware updates baffle me. I would have thought for those options to become enabled the code would have done a dependent hardware check first, only if met does the option wake up.

Usually I am very wary of new features in this system as more often than not they are not fully implemented, cause other issues, buggy or simply don't work. Always worth a check here to see if someone else has tested it.

In my case, I have the controller installed in a Linux LXC (Ubuntu) and after installing v5.9.9 I've enabled "Lock to AP" for several clients (there are about 60 devices connected at all times) and off course the feature was not working, then I migrated to v5.9.31 and the feature still not works, but I haven't noticed any issues other than the clients roaming normally instead of keeping the connection only to the selected AP.

Hopefully the new firmware for the APs supporting this feature arrives soon, but IMHO it is very confusing to have a feature in two consecutives versions of the controller that can not be used by any Omada hardware yet. Specially when it is not menthioned anywhere in the Release Notes of the software.

Thoroughly disappointed to see this still not implemented. I bought a second access point thinking this was supported after seeing it in the controller. Will be returning all of my tplink gear and moving to another manufacturer if we can't count on basic features working.