Solution Solution to Repeating Notification of "[Gateway] was connected" Issue on ER605 V2 [Case Closed]
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
Been a few days since I looked at my system... 187 alerts about disconnecting....
It seems to happen every 20 minutes....
Haven't tried updating to the beta again, since that process didn't go well
Was out of town for a few weeks... back now.. guess I have this to still deal with.
Any ballpark for an official release on the er605 v2 ??
Rebooted the controller, and Rebooted the router..connected again
- Copy Link
- Report Inappropriate Content
Hello @JS_racer,
As mentioned in my last reply, since your controller is installed on Synology NAS using Docker, it's possible that there are some firewalls or something blocking the communication between the device and controller's HTTPS management port. For example, you may check firewall settings like Access Control, try remove the firewall settings for checking.
If you have an doubt, you can try to upload the firmware of your switch or the access point for a test, it should be failed with the same reason like the router upgrade failure if the current firmware of your switch or access point is also adapted to controller v5.
If you still cannot figure out the issue of your linux controller, or you still think it's the Beta firmware issue, perhaps you may choose to forget the Router from the controller and upgrade the firmware from the standalone page, then re-adopt it for management.
- Copy Link
- Report Inappropriate Content
TL-SG2008 V3 was updated online with no issue the end of march... i didn't manually push the firmware, it was the online process... red dot, update... (hope that makes sense)
not sure if that process is different than a manual update
controller software remains the same... waiting to swap to the 200, but the firmware needs to be the same as my lunix version to transfer settings ??
if i forget the er605, then update, then apopt again, am i able to backup settings, and restore them if needed ??
thanks so much for your time..
(sorry, after 3 weeks riding motorcycles in the mountains, i'm slow to catch up to what i was doing before, lol)
- Copy Link
- Report Inappropriate Content
Hello @JS_racer
Yes, both controllers will need to have same controller version if you do the controller migration.
The settings related to the router are configured on the controller. If you only forget the ER605 (not re-install the controller), the controller will provision the settings related to the router once it's adopted again.
- Copy Link
- Report Inappropriate Content
ok, swapped to the oc200, instead of my docker omada setup.
was quiet for the first day or 2, seeing just a couple er605 connected messages.. i have not tried to update the router firmware to beta yet..
say is thee a way to reboot the oc200 ?? i have it poe from a TL-SG2008P
thanks much
- Copy Link
- Report Inappropriate Content
Yesterday evening I upgraded my ER605 V2 to the latest available firmware version advertised in my Omada controller for the ER605:
Firmware Version: 2.2.0 Build 20230629 Rel.64012
Before the upgrade I was running on firmware 2.1.2 Build 20230210 and experienced alot of "Gateway was connected" notifications throughout the day. Since the release notes of 2.2.0 mention that this issue should be solved, I expected the notifications to disappear.
Unfortunately, today, I already have 12 notifications (and counting..) "Gateway was connected".
Is the fix for this issue really included in 2.2.0?
- Copy Link
- Report Inappropriate Content
Hello @MrBowser,
Thank you for your valuable feedback.
Yes, the fix for the repeating notification of "[Gateway] was connected" issue has been included in the 2.2.0 official firmware. If you still encounter the issue, you case might be a different issue. To figure out the issue, please allow me to confirm the following information.
Have the notifications "Gateway was connected" decreased after you upgrade from 2.1.2 Build 20230210 to 2.2.0 Build 20230629?
What's the current version of your Omada Controller? Are you using OC200/OC300 or Software Controller (Windows/Linux)?
Does the "Gateway was connected" notifications affect your actual network connection?
- Copy Link
- Report Inappropriate Content
See my answers to your questions below:
Have the notifications "Gateway was connected" decreased after you upgrade from 2.1.2 Build 20230210 to 2.2.0 Build 20230629?
That depends on the day. Last 3 days was less, but monday was more. See some days below:
2.1.2:
- July 4 : 10 notifications
- July 5 : 20 notifications
- July 6 : 11 notifications
- July 7 : 18 notifications
2.2.0:
- July 10 : 24 notifications.
- July 11 : 2 notifications
- July 12 : 3 notifications
- July 13 : 3 notifications (up to 13:00h).
What's the current version of your Omada Controller?
5.9.31
Are you using OC200/OC300 or Software Controller (Windows/Linux)?
Software controller running in a Docker container on a dedicated virtual machine for my network.
Does the "Gateway was connected" notifications affect your actual network connection?
No, I don't experience any other issues in my network, it is just the notification.
- Copy Link
- Report Inappropriate Content
I stil lget repetitive notifications for the same device over and over
Tried every version of firmware and never able to resolve
this is todays (every second):-
1 | 2023-07-13 14:41:51 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64] |
2 | 2023-07-13 14:41:50 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
3 | 2023-07-13 14:41:49 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
4 | 2023-07-13 14:41:48 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
5 | 2023-07-13 14:41:47 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
6 | 2023-07-13 14:41:46 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
7 | 2023-07-13 14:41:45 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
8 | 2023-07-13 14:41:44 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
9 | 2023-07-13 14:41:43 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
10 | 2023-07-13 14:41:42 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
11 | 2023-07-13 14:41:41 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
12 | 2023-07-13 14:41:40 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
13 | 2023-07-13 14:41:39 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
14 | 2023-07-13 14:41:38 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
15 | 2023-07-13 14:41:37 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
16 | 2023-07-13 14:41:36 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
17 | 2023-07-13 14:41:35 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
18 | 2023-07-13 14:41:34 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
19 | 2023-07-13 14:41:33 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
20 | 2023-07-13 14:41:32 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
21 | 2023-07-13 14:41:31 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
22 | 2023-07-13 14:41:30 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
23 | 2023-07-13 14:41:29 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
24 | 2023-07-13 14:41:28 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
25 | 2023-07-13 14:41:27 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
26 | 2023-07-13 14:41:26 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
27 | 2023-07-13 14:41:25 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
28 | 2023-07-13 14:41:24 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
29 | 2023-07-13 14:41:23 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
30 | 2023-07-13 14:41:22 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
31 | 2023-07-13 14:41:21 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
32 | 2023-07-13 14:41:20 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
33 | 2023-07-13 14:41:19 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
34 | 2023-07-13 14:41:18 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
35 | 2023-07-13 14:41:17 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
36 | 2023-07-13 14:41:16 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
37 | 2023-07-13 14:41:15 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
38 | 2023-07-13 14:41:14 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
39 | 2023-07-13 14:41:13 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
40 | 2023-07-13 14:41:12 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
41 | 2023-07-13 14:41:11 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
42 | 2023-07-13 14:41:10 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
43 | 2023-07-13 14:41:09 | DHCP Server | NOTICE | DHCP Server allocated IP address 192.168.1.4 for the client[MAC: 00:eb:d8:28:df:64]. |
I've given up now. THis is just the Router, I do not use a controller
- Copy Link
- Report Inappropriate Content
What device is it with that Mac Id ?? May need to reboot it or something
- Copy Link
- Report Inappropriate Content
Information
Helpful: 5
Views: 10774
Replies: 50