Solution Solution to Repeating Notification of "[Gateway] was connected" Issue on ER605 V2 [Case Closed]
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
This Article Applies to:
ER605(UN)_V2_2.1.1 Build 20230115
ER605(UN)_V2_2.1.2 Build 20230210
Issue Description/Phenomenon:
Recently we received feedback that using ER605 V2 2.1.x firmware would cause repeating event notifications of "[Gateway] was connected" as below, and there might be a disconnected notification occasionally.
On Omada Controller:
On Omada App:
Related Posts:
Very lot messages to connect devices (Gateway)
ER605 Repeating Event Notifications On Omada App
Available Solutions:
Here is the current available solution to resolve the issue described in this thread.
Beta Firmware Download:
ER605(UN)_V2_2.1.2 Build 20230221 (Beta)
Please be sure you have read the Beta Test Agreement before proceeding!
Beta Release Note:
Fixed the repeating notification of "[Gateway] was connected" issue based on the official firmware 2.1.2_Build 20230210.
Feedback:
If this was helpful, welcome to give us Kudos by clicking the upward triangle below.
If there is anything unclear in this solution post, please feel free to comment below.
To submit a new different issue, please Start a New Thread for better assistance.
Thank you for your support and contribution in TP-Link Community!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello @Brandon181062
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 TKID230314699, please check your email box and ensure the support email is well received. Thanks!
- Copy Link
- Report Inappropriate Content
@Brandon181062 Exactly the same for me still getting repetitive messages every few seconds
- Copy Link
- Report Inappropriate Content
Hello @SeanieP
Do you mean that you get repetitive notification of "disconnected" after installing the Beta firmware provided in this original post?
Was your ER605 V2 disconnected and then connected automatically every few seconds on a loop?
Would only the ER605 get disconnected without affecting other devices or services?
When did the issue start to happen, from the first day you install the ER605, or from a recent firmware update or config change?
- Copy Link
- Report Inappropriate Content
I get repeated DHCP Notifications :-
EG:-
| 2023-03-16 11:50:41 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.54 for the client[MAC: XX:XX:XX:XX:XX:XX]. |
| 2023-03-16 11:50:05 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.54 for the client[MAC: XX:XX:XX:XX:XX:XX]. |
| 2023-03-16 11:49:55 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.54 for the client[MAC: XX:XX:XX:XX:XX:XX]. |
I haven't witnessed any disconnections, just the repeated message in the syslog file
I have only had this router a few days, I updated to the latest released version when installing the router and the issue was apparent then
I then installed the ER605(UN)_V2_2.1.2 Build 20230221 (Beta) and the issue still exists
- Copy Link
- Report Inappropriate Content
I'm having the same DHCP messages :
| 12 | 2023-03-18 11:39:05 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.8.165 for the client[MAC: |
| 13 | 2023-03-18 11:38:25 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.8.165 for the client[MAC |
| 14 | 2023-03-18 11:36:07 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.8.165 for the client[MAC: |
| 15 | 2023-03-18 11:34:08 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.8.165 for the client[MAC: |
| 16 | 2023-03-18 11:33:51 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.8.165 for the client[MAC: |
| 17 | 2023-03-18 11:32:39 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.8.165 for the client[MAC: |
There are many through the syslog. I use the router standalone.
- Copy Link
- Report Inappropriate Content
Seeing the er605 disconnected, connected messages not as well. it started just in the last few days.
i added a SG2008 about 5 days ago, close to when this started. not sure if its a coincidence. the switch seems to be working well.
i am running omada in docker, version 5.9.9
updating the er605 to the beta posted in this thread now . wish me luck, lol
uploaded, got a failed message, now showing disconnected under status ........ sigh (it does try to provision from time to time, but says disconnected after)
Master Administrator XX failed to upgrade ER605 manually. Please check your network configuration and make sure the device can access the Controller's HTTPS management port.
not sure my next step, do i power down the er605 to reboot ??
or reboot the controller ?? internet is working, and my wife works from home
i can ping the er605 on the old listed ip and it responds just fine.
- Copy Link
- Report Inappropriate Content
@JS_racer I actually had 5.9.9 software on my software controller as well on a docker container. I had used the tag latest when upgrading the container. I was running into the same issue, but ended up reverting the vm to the snapshot I had taken and pushed the upgrade to 5.8.4 and everything started working great. If your out of options that might be worth a try.
- Copy Link
- Report Inappropriate Content
so you rolled back the omada software, to 5.8.4 and updated the er605 ?? or it was able to provision again ??
would have to see what backups i have available... 2/1 might be the last with 5.8.4 but looking...
i do have the 584 image to reinstall possibly, thinking settings would transfer over ?? haven't changed much recently,
i see 2 images in portainer, 12/8/22 and one from 2/4/23 not seeing version info though... hmm downloaded the last few versions from tp-link controller page on website
i do see from time to time, the er605 connected, adopting, provisioning, then disconnected again...
- Copy Link
- Report Inappropriate Content
Well, restarted the controller, no change.
Rebooted the er605 and it is connected again. And the webpage shows login again, and it's working in the controller.... I forgot how long it takes to reboot... like crazy long.. lol... like was past the ummmmm point.. but all is good
Still haven't fixed the connected disconnected issue...
Not sure what I did wrong trying to load the firmware to it.. used chrome
Any eta on the router firmware that will include the fix that's not beta ??
Thanks
Should I update to the latest Linux 5.9.35 or so .. on 5.9.9
- Copy Link
- Report Inappropriate Content
Hello @JS_racer
JS_racer wrote
i am running omada in docker, version 5.9.9
updating the er605 to the beta posted in this thread now . wish me luck, lol
uploaded, got a failed message, now showing disconnected under status ........ sigh (it does try to provision from time to time, but says disconnected after)
Master Administrator XX failed to upgrade ER605 manually. Please check your network configuration and make sure the device can access the Controller's HTTPS management port.
What's the current firmware version of your ER605?
It seems that there is NAT or Firewall existed between your ER605 and Controller. As the log indicated, please check your network setup and ensure the ER605 can access the Controller's HTTPS management port. Check out the solution post below for details.
Solution - Failed to update Omada devices by Omada Controller Online
- Copy Link
- Report Inappropriate Content
Information
Helpful: 5
Views: 10888
Replies: 50
Voters 1
