Heartbeat missed and stability issues for EAP653 after firmware / Cloud controller update
Hi all,
In my home setup I have 3 EAP653's that often show heartbeat missed. When this happens, it appears the clients connected to these AP's loose network connection and try to connect to other AP's. Local ping to these AP's keeps stable during these events, and uptime for the affected AP's in the Omada portal is not reset.
I also have a EAP610 and a EAP225 that work just fine. I have no other Omada gear yet, my PoE switch and router are from other brands. For management of the AP's I'm using Omada Central Essentials (in the EU), so no on-prem controller.
The issues started with either a firmware update of the EAP653's, or the update of Omada Central Essentials to v6, I can't be sure. Before that everything was running smoothly.
I already have tried:
- Power cycling AP's and PoE switch
- Factory reset of EAP653
- Manually trying to downgrade firmware to the latest online version (1.1.3). Strangely enough the AP rejects that firmware.
Has anyone come across something similar?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @OlivierNijs
I just checked on my side and everything works as expected. Please try again.
If the same situation, could you please share some screenshots of a short video showing the error? Thanks.
OlivierNijs wrote
Thanks for the 1.3.92 firmware. Unfortunately the files seems to be corrupted. I get an error when I unzip the file. Also the firmware is not accepted by the controller software
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Downloaded the file a third time. The unzip error comes from the buildin unzip softeware of MacOS. Used a different package and that seemed to fix that part of the problem. Still the controller software comes back with an error message that upgrading the firmware was unsuccessful. (1.3.90 -> 1.3.92)
- Copy Link
- Report Inappropriate Content
I have tried in stand alone and controller, both fail, stand alone gives no error message but the upgrade cancels after 1-2 seconds
- Copy Link
- Report Inappropriate Content
Just to jump on this bandwagon
During testing an unrelated issue with support i was sent 1.3.51 beta for my EAP650 v1 (which is essentially the same unit as EAP653 v1) which exhibited the exact same issues as the OP it immediately disconnected not just the EAP but everything on the site - it took the controller about 20 minutes to reconnect to everything, it was very strange. i immeditely reverted the firmware.
I havent had any issues reverting my EAP650 from 1.3.50 beta to 1.1.3, it just took the file happily
On freshly reboot EAP650 units
FW 1.3.50 - cpu 2% memory 62%
FW 1.1.3 - cpu 2% memory 60%
on 4-day uptime unit on 1.3.50 memory is still at 62%
I have 7 SSIds, EAP ACLs, mix of 2.4 and 5g bands. All performing well on the 1.3.50 beta
I will keep one unit on 1.1.3 to compare over time
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
To clarify, that firmware is for upgrade directly from 1.3.4.
Now that you are using the 1.3.90, you can downgrade to the official firmware 1.1.3 directly,.
I would suggest you keep this firmware and wait for the next official release. It won't be long. Thanks.
OlivierNijs wrote
Downloaded the file a third time. The unzip error comes from the buildin unzip softeware of MacOS. Used a different package and that seemed to fix that part of the problem. Still the controller software comes back with an error message that upgrading the firmware was unsuccessful. (1.3.90 -> 1.3.92)
- Copy Link
- Report Inappropriate Content
I have tried to upgrade from 1.1.3 and 1.3.50, but it failed on both, I have never heard of version 1.3.4, where can I find it?
- Copy Link
- Report Inappropriate Content
Vincent-TP wrote
I finally got upgraded to 1.3.92, tried to upgrade from several different versions but all failed, the only one that worked was upgrading from 1.3.1 to 1.3.92.
so everything is ok now :-)
- Copy Link
- Report Inappropriate Content
I upgraded to 1.3.90 and kept it there for half a day. The issues I had remained. Then I downgraded to 1.1.3 and my wifi network is a lot more stable now.
For those of you who had issues, the Zip downloads I got from support worked fine. I unzipped using the Windows 11 builtin Extract function. For one AP I got the failed error when upgrading to 1.3.90, but after a refresh it appeared the upgrade did succeed.
This is of course anecdotal, but I have an Iot device connected to my network that reports back some measurements every 30 seconds over wifi. With the instable firmware there would be disconnects every minute or so. After downgrading the connection is very stable, back to what is was before. This is a screen shot of the Iot management tool (so nothing TP-Link related):
The grey striping illustrates the disconnects that have disappeared after 20:00 when I downgraded the firmware.
Perhaps this helps in solving this issue.
Giel
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 988
Replies: 37
Voters 0
No one has voted for it yet.