R605 v2 - disconnected in Omada software controller
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.R605 v2 - disconnected in Omada software controller
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
My R605 v2 is regularly shown as disconnected but internet and VPN is still working. Usually I get notification it is connected few minutes later.
It was also happening with firmware 2.1.1, don't know if it was happening with versions before that.
EDIT: image was to big, so I made it smaller...
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Have a look in the 'Events' and see if there are other logged things happening around the same time as the ER605 disconnects. Could be something as simple as an intermittent ethernet connection.
- Copy Link
- Report Inappropriate Content
There is nothing logged around the same time (+- few minutes) as those "was disconnected" or "was connected" events, no pattern. Few examples - no event logged 10 minutes before disconnected message, 5 message that R605 was connected but no other event in between, after that 5 messages one was disconnected message, etc.
- Copy Link
- Report Inappropriate Content
@NeoCZ I'm seeing the very same thing, started this morning GMT, my ER605 v2 (firmware 2.1.1) keeps cycling its connection to the Omada controller (5.7.4 in a Docker container), but is otherwise doign its job as a router. Restarting both the router and the controller made no difference. I'm thinking of upgrading from 5.7.4 to 5.8.4, but I'm not presently willing to go to the trouble without any reason to think it might help.
UPDATE: I have upgraded the ER605 v2.0 to firmware 2.1.2, and perhaps unrelatedly, the connection/disconnection has stopped and all seems normal again.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hank21 wrote
The Disconnected issue has been reported to the R&D team who has located the issue and will fix it with high priority.I'll update this post as soon as possible once we get the new developments.
I'd like to update the post with a solution here.
TP-Link has provide a Beta firmware to fix the issue urgently, please check the following post for details.
Solution to Repeating Notification of "[Gateway] was connected" Issue on ER605 V2
You may take your time to upgrade the beta firmware and confirm the issue you encountered has been resolved.
- Copy Link
- Report Inappropriate Content
@Hank21 after cycling power and upgrading to the existing 2.1.2 firmware (not any beta), I have had a quiet Omada dashboard for nearly 5 days now. It's possible that my specific setup was able to sidestep the issue your engineers have fixed. I won't install the beta in that I won't be able to tell you if it fixes my earlier issue. Thank you in any case!
- Copy Link
- Report Inappropriate Content
@Hank21 The looping disconnects returned last night, and I've just now cycled power in order to have control long enough to apply the beta firmware update. I will report if this has not fixed the issue. The firmware version in the Omada controller continues to report "2.1.2" even though the official 2.1.2 had been previously applied.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Hank21 So far so good, no new connected / disconnected logs after upgrade to beta firmware.
- Copy Link
- Report Inappropriate Content
@NeoCZ @Hank21 My router has once again entered the disconnection looping situation, but with the beta firmware having been previously provided. I would say the beta firmware has not fixed this issue. Thanks for any further advice or firmware updates that might put this right.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1428
Replies: 15
Voters 0
No one has voted for it yet.