NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
GuyBrush85
Mar 27, 2017Aspirant
R7800 and Nest Protect
Hello, I have a netgear R7800 on the latest firmware (.28) and I'm having issues with Nest Protect. Before buying and installing the Netgear I had my (now modem), in router mode and Nest Protect wo...
- Apr 05, 2017Well the replacement Nest unit came and I managed to get it all connected up straight away. Couldn't say why the old unit worked perfectly fine before I moved to the Netgear!
Thanks for the help and suggestions everyone.
Mighty_Putty
Mar 31, 2017Apprentice
I've just replaced an Asus RT-AC87R with an X10. My home has 3 Nest Protects, and I have not seen any drops on those devices so far, but I wanted to ask you (based on anecdotal correlations with Asus router owners for the past few years), does the 7800 have a smart connect option or band steering between the 2.4 & 5 GHz bands ? If so, have you turned same option off and tried to validate your Nest devices stability (or lack thereof)? That was a huge issue with a few choice Asus firmware revs until it was fixed.
Have you verified in the Nest app interface that it's actually offline, or are you just going with with device connectivity on the web interface of the 7800? I did notice a couple of devices appearing to fall off intermittently from the router's web interface, (one in particular being a connected Netgear fully populated switch), but none of the attached devices ever lost connectivity. It appears to be a defect, maybe, in the GUI functionality.
I looked up:
https://nest.com/support/article/Troubleshooting-Wi-Fi-and-connection-issues
Not sure if any of those are applicable to you?
My 2.4 GHz is set to channel 7 (not a 1,6,11 guy ), the mode is "up to 800 Mbps" and I'm not enabling 20/40 MHz coexistence.
I changed the preamble mode to short (tried to emulate my Asus settings as much as possible with the limited NetGear choices), did not select HT-160 because of potential Apple connectivity issues, & left IGMP proxy (and multicasting) disabled.
I don't know if this was helpful, but figured at least it might be a starting point...