Nest doorbell reconnecting every 20-60 seconds RT-AC5300

[s814jdh]

My Nest doorbell has been working with my RT-AC5300 router running Merlin firmware for over 3 years. Two weeks ago it started going offline frequently, which I think coincided with updating to Merlin 386.3_2. It took me a few days to have time to look into things and now I see in the logs what looks to me like the doorbell resetting the WiFi connection every 20 to 60 seconds:

Dec 27 20:47:52 syslog: wlceventd_proc_event(508): eth1: Disassoc 18:B4:30:E9:61:BA, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 27 20:47:52 syslog: wlceventd_proc_event(527): eth1: Auth 18:B4:30:E9:61:BA, status: Successful (0), rssi:0
Dec 27 20:47:52 syslog: wlceventd_proc_event(556): eth1: Assoc 18:B4:30:E9:61:BA, status: Successful (0), rssi:0
Dec 27 20:47:52 dnsmasq-dhcp[2173]: DHCPDISCOVER(br0) 18:b4:30:e9:61:ba
Dec 27 20:47:52 dnsmasq-dhcp[2173]: DHCPOFFER(br0) 192.168.1.16 18:b4:30:e9:61:ba
Dec 27 20:47:52 dnsmasq-dhcp[2173]: DHCPREQUEST(br0) 192.168.1.16 18:b4:30:e9:61:ba
Dec 27 20:47:52 dnsmasq-dhcp[2173]: DHCPACK(br0) 192.168.1.16 18:b4:30:e9:61:ba NestDoorbell
Dec 27 20:48:40 syslog: wlceventd_proc_event(508): eth1: Disassoc 18:B4:30:E9:61:BA, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 27 20:48:40 syslog: wlceventd_proc_event(527): eth1: Auth 18:B4:30:E9:61:BA, status: Successful (0), rssi:0
Dec 27 20:48:40 syslog: wlceventd_proc_event(556): eth1: Assoc 18:B4:30:E9:61:BA, status: Successful (0), rssi:0
Dec 27 20:48:41 dnsmasq-dhcp[2173]: DHCPDISCOVER(br0) 18:b4:30:e9:61:ba
Dec 27 20:48:41 dnsmasq-dhcp[2173]: DHCPOFFER(br0) 192.168.1.16 18:b4:30:e9:61:ba
Dec 27 20:48:41 dnsmasq-dhcp[2173]: DHCPREQUEST(br0) 192.168.1.16 18:b4:30:e9:61:ba
Dec 27 20:48:41 dnsmasq-dhcp[2173]: DHCPACK(br0) 192.168.1.16 18:b4:30:e9:61:ba NestDoorbell
Dec 27 20:48:46 syslog: wlceventd_proc_event(491): eth1: Deauth_ind EE:CA:75:C4:C09, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 27 20:48:46 syslog: wlceventd_proc_event(508): eth1: Disassoc EE:CA:75:C4:C09, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 27 20:55:41 syslog: wlceventd_proc_event(527): eth3: Auth AA:A9:8A:5D:B2:85, status: Successful (0), rssi:0
Dec 27 20:55:41 syslog: wlceventd_proc_event(556): eth3: Assoc AA:A9:8A:5D:B2:85, status: Successful (0), rssi:0
Dec 27 20:55:44 dnsmasq-dhcp[2173]: DHCPDISCOVER(br0) aa:a9:8a:5d:b2:85
Dec 27 20:55:44 dnsmasq-dhcp[2173]: DHCPOFFER(br0) 192.168.1.250 aa:a9:8a:5d:b2:85
Dec 27 20:55:44 dnsmasq-dhcp[2173]: DHCPDISCOVER(br0) aa:a9:8a:5d:b2:85
Dec 27 20:55:44 dnsmasq-dhcp[2173]: DHCPOFFER(br0) 192.168.1.250 aa:a9:8a:5d:b2:85
Dec 27 20:55:45 dnsmasq-dhcp[2173]: DHCPREQUEST(br0) 192.168.1.250 aa:a9:8a:5d:b2:85
Dec 27 20:55:45 dnsmasq-dhcp[2173]: DHCPACK(br0) 192.168.1.250 aa:a9:8a:5d:b2:85

I am not convinced it is the firmware of the router just yet. I have two other Nest cameras and 3 Nest thermometers on the same router that are all working perfectly. I have also downgraded the firmware to 386.2_6 with the same result. I saw a thread in the forum of someone trying to get a mesh setup to function correctly with Nest devices but I am not in a mesh configuration, just the one RT-AC5300 that has served me well for quite a few years. I have flashed and reset settings, same issue.

 

[s814jdh]

I have now downgraded to Merlin 386.1_2 and things are looking better. The Nest doorbell has stayed connected for 14 minutes, which is longer than I had seen since I started looking into this issue. Not ready to declare victory just yet, but it is looking very likely that there are issues with the 386.2_x and 386.3_x firmware versions and the Nest wired doorbell.

 

[tck81]

In your firewall settings select "Yes" for "Respond ICMP Echo (ping) Request from WAN."

 

[s814jdh]

@tck81 you think I can update to a current firmware if I have that enabled? It was turned off.

 

[s814jdh]

Updated to Merlin 386.3_2 and changed the firewall to allow ICMP ping from WAN. Doorbell has been online for 8 minutes. Looks like this will work too. Interesting that this setting didn't seem to be an issue with 386.1_2, maybe it was a firewall rule that wasn't actually being enforced.

 

[s814jdh]

40 minutes of uptime on the most current firmware since allowing ICMP ping from WAN. Looks like we have a solution! To me this is a client behaving badly, shouldn't need the ability to ping the WAN (presumably to make sure it is talking to the Nest hub) but this seems to be the thing that I have been searching for.

 

[s814jdh]

Well, bad news. A few hours later in the day I am back to having the Nest doorbell resetting the WiFi connection every 30 seconds. Went back to firmware 386.1_2, disabled firewall entirely. Still resetting every 30 seconds.

 

[CriticJay]

Try a different 2.4ghz channel.

 

[s814jdh]

I have tried multiple 2.4 GHz channels. I have tried auto. I have tried 20MHz only and 20/40. None of it has mattered. The doorbell is resetting the WiFi connection.

 

[RMerlin]

Make sure you disable Airtime Fairness (lots of IoT clients have compatibility issues with that), and implicit beamforming as well.

 

[s814jdh]

I swapped out the Asus router for a Netgear I had in the house. Seemed good at first just like with the Asus though much harder to tell with the lack of detailed device information in the Netgear. End result, about 12 hours later the doorbell is offline again.

I am suspecting the doorbell at this point. Ordered a replacement since it is 3.5 years old and the warranty is only 12 months (which seems ridiculously short for such an expensive device). Going to be a while before I can test things.

 

[Sander_H]

I had similar issues with my Nest Doorbell a while ago. I did a powercycle to the doorbell after it was offline for 2 days and it restored itself. It has issues every month or so but usually for a shorter period 0. The Nest Outdoor Cams are fine - it is just the Nest Hello. Guess it is either a dodgy wifi chip or perhaps overheating.

 

[s814jdh]

Hard to believe it would be overheating in 28 degree Fahrenheit weather we are having in Utah right now. I just bought a new doorbell at the hardware store. Going to see if I have better luck with it. I am restoring to factory settings on the Asus router right now.

 

[s814jdh]

Firmware 386.3_2. Firewall disabled. Airtime Fairness and implicit beamforming disabled. Brand new doorbell. 2.4Ghz with 20 Mhz only (not 40). Channel 11 set, not auto. Connection is -66 dBm. Doorbell resets every 5 or so minutes right now.

 

[s814jdh]

The doorbell has gone 38 minutes without resetting. Maybe it was resetting because I was still configuring the router a bit. I am done for now, so we will see how long it stays like this.

 

[s814jdh]

Doorbell has now been connected for a little over 16 hours! Going to try re-enabling things one at a time to see if it was the doorbell hardware or if there is a specific feature setting that causes problems. First up, enabling the firewall but keeping ICMP ping allowed.

 

[SheikhSheikha]

Maybe good to notice that like Apple Devices and Ring Devices, Nest devices store some hidden "goodies" the first time they connect to a router. With a firmware upgrade these connection "goodies" may not be that good anymore. I have my Nest stuff working without problems but only when I reset the connection to the router after the router update/upgrade. For Nest (and Ring) this means: start from scratch which in the end is not that time consuming (and for Apple devices it means "Reset Network Connections"). Best of luck!

 

[s814jdh]

@SheikhSheikha the interesting thing here is the doorbell and router were both in service for 3.5 years with no issues. All features of the router enabled. Multiple firmware updates to the router. No issues until 2 weeks ago.

 

[SheikhSheikha]

What I wrote in my previous post as possible solutrion(s), is what I, and many others encountered over the past years. It might be that you have been lucky in some way. Anyway, it is annoying but can be overcome. Check if MIMO is switched off on your wireless professional settings

 

[s814jdh]

Firewall enabled good for 24 hours, no disconnects from doorbell. Enabled DoS protection in firewall. Waiting 24 hours...