EAP615-Wall(US) v1.0 has issues with 1.2.3 Firmware
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I saw the upgrade prompt in the controller, and upgraded my 3 EAP-615WALL APs. Immediately upon upgrading, some devices would not reconnect under any circumstances, all failing with errors pointing to the password being incorrect. However, none of these devices had passwords changed, and other devices using the same password could connect with no issues.
Additionally, 2 of the 3 EAP-615WALL devices had problems re-adopting to the network. They are all are connected via Ethernet (POE) to a TL-SG2210P v3.20 switch. no issues with POE were noted by the switch. After unplugging/replugging to Ethernet, eventually those two would connect, but be meshed, and not connected via Ethernet.
Upon manually downloading the 1.1.6 firmware and installing that back on the APs, immediately everything worked correctly, and previously non-connecting devices connected with no issues.
It seems there are still some issues with the 1.2.3 firmware, at least in respect to the EAP-615WALL 1.0 devices.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
:) I'd intended that message for the iPad poster...
Glad to hear you've narrowed it down to a hardware device+firmware combo. I'm guessing TPlink will want to know the serial number of the device that is not taking the upgrade happily (and maybe the serial of one that does). Maybe your serial number will correlate with the others who have been having issues with this device/upgrade combo.
- Copy Link
- Report Inappropriate Content
Hi @chrisfromthelc，
Thanks for such detailed information you provided!
Please try the last troubleshooting to precisely locate this issue, could you try upgrading the firmware of this specific EAP615-Wall to 1.2.3 in Standalone mode, and after upgrading done, please use the controller to adopt it, check whether there is still an issue.
- Copy Link
- Report Inappropriate Content
Hi @Icare2000,
Thanks for reporting this issue to TP-Link community!
Would you be able to provide some more information on what you are experiencing (EAP/Controller types, Topology, firmware versions etc)?
Any screenshots would also help.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hello
i have a quite simple setup. I just downgraded yesterday.
my controller is OC200
I was not able to connect my Ipad. ( Ipad Air 2, ios 15.8)
Best regards
- Copy Link
- Report Inappropriate Content
Hank21 wrote
Hi @chrisfromthelc，
Thanks for such detailed information you provided!
Please try the last troubleshooting to precisely locate this issue, could you try upgrading the firmware of this specific EAP615-Wall to 1.2.3 in Standalone mode, and after upgrading done, please use the controller to adopt it, check whether there is still an issue.
@Hank21
This seems to have been the key.
I had the device still on 1.1.6, but not in the original location (removed for troubleshooting). I hooked it back up, and logged into it directly before adopting, upgraded it with the 1.2.3 firmware that I had downloaded. Once it completed that upgrade, I put it back in the original location, adopted it, and it's been running for 10+ hours without issue. Previously it would have started having problems within minutes of upgrading if I'd upgraded from the controller. I can also confirm that devices have no issues connecting, and the connection is stable. The connection previously would not outright drop/disconnect, but be extremely slow to the point of being unusable.
So, the issue appears to originate from the controller handling the upgrade. I'm curious if the other folks try this, if they see the same results.
- Copy Link
- Report Inappropriate Content
I am having the same exact issues described in this thread realted to 1.2.3. I am manually downgrading to 1.1.6 and will try the standalone upgrade.
There seems to be a definite issue with this device and firmware that should be addressed by TP Link, pulling the firmware in the meantime.
- Copy Link
- Report Inappropriate Content
I think the problem is bigger than that. The issue appears to be with the 5.13 controller (@Hank_21 to confirm), as the 1.2.3 firmware is fine if loaded manually. So 5.13 needs to get pulled, or the 'current firmware version file' needs to be edited to remove 1.2.3 as a valid upgrade for 5.13)
- Copy Link
- Report Inappropriate Content
Hi @chrisfromthelc,
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240113963, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Hi @nRayAffair，
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID240113977, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 3045
Replies: 30
Voters 1
