EAP610 Random Reboots & Clients all on one AP
EAP610 Random Reboots & Clients all on one AP

I have 2 EAP610s managed by an Omada Controller v5.15.6.7. However this issue also happened with the previous 5.14.x controller.
Essentially, these two APs will randomly stop accepting clients and all clients move to one or the other. I then also have issues where both APs will randomly reboot. Sometimes, they both get so hungup that neither will accept clients and I have to power cycle them manually.
Anyone else experiencing this? This is in a 2100sqft 2-story home. Each AP is on their own channel for 5 and 2.4 bands. I have a combination of SSIDs with dedicated VLANS using PSK and a couple SSIDs using DPSK for VLAN assignments.
When I upgraded to 5.15.6.7 of the controller I did from a fresh install of Ubuntu 22.04 and just re-imported my backup config to the new controller. I am thinking this is something in the firmware on these APs and just not been reported as an issue as it might be related to DPSK which I think many don't use.
I also have not seen any beta release of the firmware for the EAP610 that I could try.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Vincent-TP
Looks like the issue is still not resolved. Here is what I see.
Both access points have rebooted in the past 24 hours on their own for some reason (no loss of power, connected to a PoE switch which shows 65 days of uptime and is on a UPS). One is possibly not accepting clients correctly even now as it only has 7 vs 30 on the other (and the one that has 7 usually has the most clients).
Who can I contact to work on this and provide diagnostic data to? This is clearly some issue with these EAP610 devices and I'm seeing others posting about similair issues.
- Copy Link
- Report Inappropriate Content
A quick update for those interested.
I do have an open support ticket on this as the issue has me close to throwing out these APs and going to a competitor but I want to give TP-Link a chance to resolve.
However, the current request from them has been to remove the use of PPSK. This would unfortunatly result in me having to establish seperate SSIDs for each VLAN (I have 4 that use PPSK today). That process would take quite a bit of effort to reconfigured 30+ devices on the network. Many of those required a factory reset and re-setup. And, if this did work, that would mean a feature of the EAP610 is simply not working.
At this point, I'm waiting to hear back from tech support on my request for them to simply escalate to their engineering teams as a possible firmware bug.
Over the past 30 days, each AP has locked up or randomly rebooted at least 15 times each.
If you have EAP610 devices and use PPSK, report back if you are experiencing issues.
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 668
Replies: 12
Voters 0
No one has voted for it yet.