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
Already tried. Actually I tried for months now, having the APs running standalone in between tests. There is no chance for me to get them running stable on 1.3.5 or 1.3.7 so I need a rollback.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 6427
Replies: 51
Voters 0
No one has voted for it yet.