Lock to AP not working
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Lock to AP not working
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi,
I have been trying to get several devices to stay connected to a set access point, and it seems like the Lock to AP feature is not working at all. I have tried to lock multiple different clients to multiple different APs (EAP225, EAP610-Wall, EAP-650), with no success. The client still jumps to a different access point even though it has a weaker signal than the one I specified the client to connect to with the Lock to AP feature. Any ideas? Thanks!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Same problem with EAP650(US) v1.0 and EAP670(US) v1.0 with firmware 1.0.6
Lock to AP NOT WORKING
HOPE TPLINK WILL FIX IT ON NEXT FIRMWARE.
- Copy Link
- Report Inappropriate Content
I'm hoping the new 5.12 firmware has this fixed. Apparently they fixed devices not showing after locking to an AP, but haven't had a chance to test yet.
- Copy Link
- Report Inappropriate Content
I've not had a problem locking devices to APs. Only exception is my kid's MacBook for some reason won't latch on to the AP I assigned it to??.
I have about 63+ devices (home setup with many IoT items).
All hardware has updated firmware.
So is this issue now resolved, or related to my own APs?
- Copy Link
- Report Inappropriate Content
My devices do not lock to Ap's. Has the issue been fixed yet?
- Copy Link
- Report Inappropriate Content
1 Year after the initial post for this has been made and STILL no firmware update or functionality. Shame on you TP-Link.
- Copy Link
- Report Inappropriate Content
Mine is working ok with recent updates.
- Copy Link
- Report Inappropriate Content
@windows10luke Mine definitely is not!
- Copy Link
- Report Inappropriate Content
@Scott1 Me neither. It seems to be localized to specific AP hardware, though... and in the REVERSE direction. Meaning, I can lock something to an in-wall 615 AP if the client keeps "thinking" it can connect better to a ceiling-mount 660 AP in a different room, but in another location I'm trying, there's two different in-wall APs, one a 216 and one a 615, and a 2.4Ghz client keeps connecting to the 215 IWAP in a different room instead of the 615 IWAP that is literally in the same room with the client.
In the first case, I do get many "Blocked by access control" messages from the client so I "think" that's what's going on - the client tries to connect to an AP on which you don't want it to connect, and it denies it, forcing it to connect to the preferred AP. If the AP does not support this blocking, then the "Lock" function simply doesn't work. At least, that's my theory.
All APs/switches in latest firmware, btw. This feature, alone, may force me to reconsider TP-Link for my new home I'm building. I left Ubiquiti because of flaky software issues, and if Omada can't fix this, I might just go back to Unifi. If I'm stuck with flaky software, I might as well have a better UI (and the ability to change VLANs from the IOS app - how has Omada not done this yet?!?!). :)
- Copy Link
- Report Inappropriate Content
For those of you having issues with "Lock to AP," which Omada Controller are you running? From my personal experience, this feature seems to work just fine (Windows 11-based software Omada controller). Whichever device I bind to a particular AP sticks that AP and functions as expected. Seems to work well with older "dumb" IoT devices as well (such as cameras, smart bulbs, and outlets).
- Copy Link
- Report Inappropriate Content
@Shoresy I'm running an OC-200.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 4607
Replies: 20
Voters 0
No one has voted for it yet.