issues with firmware for EAP230-Wall "3.2.3 Build 20240815 Rel. 33684"

Dear TP-Link Support Team,
I recently upgraded my EAP230 AP's to the newest Firmware (3.2.3 Build 20240815 Rel. 33684).
After the upgrade i have massive troubles connecting to hidden SSIDS.
All my Smartphones does not Connect to the hidden SSID at all. If i leave the Smartphones for a few hours, there is a chance (50%) that the devices are connecting to the ssid.
I downgraded to v 3.1.1. -> absolutely no problem with this version.
how can i resolve that issue?
is this a known bug?
best regards
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @WahlFisch
Do you have a controller?
Apart from the hidden SSID, is there any other change on this SSID?
Is this issue happening on all of your wireless clients?
- Copy Link
- Report Inappropriate Content
@Vincent-TP Yes, the AP's are adopted to a (software) controller (ubuntu server) - installed the newest version of omada controller
There are no other changes on the ssid.....
it looks like all devices are affected, which are moving around in the area - devices which have to roam (tablets, smartphones,..)
If i leave the device (for example my smartphone) at one place for about 30 Minutes - it connects to the ssid again....
i went back to firmware 3.1.1 -> now everything is working fine again...
- Copy Link
- Report Inappropriate Content
Hi @WahlFisch
Do you mean this only happens when devices are trying to roam between different EAPs?
How many EAP units do you have? Are they all EAP230-wall? Are they all having this issue?
In the meantime, I created a support ticket for you, the case ID is TKID250148765. Please check your inbox and reply it.
- Copy Link
- Report Inappropriate Content
@Vincent-TP Yes, it looks like that is has something to do with roaming. in general the whole wifi network was feeling unstable and slow...
i have 5 EAP-230 Wall AP's in use -> All had that issue with FW 3.2.3.
As i already described, i rolled back to FW 3.1.1 -> everything is working fine with that
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 227
Replies: 4
Voters 0
No one has voted for it yet.