NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Google Home
2 TopicsChromecast (Google Home) on Orbi -- not able to see all speakers
My wifi devices cannot see all of my Google Home devices in order to Chromecast. Depending on whether I'm connected to 5/2.4 GHz or the base station/satellite, I see a different collection of Chromecast speakers and groups, but never all of them at the same time. Casting only works most of the time. Re-setting up the speakers often leads to "your phone is unable to communicate with the Google Home" errors and a link to help article on AP isolation, though they can all connect to the wifi just fine. Repeating the setup multiple times eventually succeeds but the problem of not being able to see all the speakers persists. I've tried getting them all on the 5 GHz band by disabling Fast Roaming, I've tried disabling daisy chain / MIMO / beamforming, all with no success. Everyone seems to indicate that Google Wifi works great, so I'm assuming it's a bridge setting or something buried in Netgear that's causing the problem, rather than an inherent problem with mesh networks. Extensive Googling hasn't really turned much up. Does anyone have any tips? I'm on firmware 2.1.4.10.Google Home and Chromecast
So I got the super orbi crashing and rebooting on the router and satellites. I seemed to have narrowed it down to when working with Google Home. When ever I try to stream something it would prompt an orbi reboot and I would loose wifi for 1-2 min while it boots back up. Sometimes, after the reboot, google home will work fine other times I'll get the message "hmm.. something is wrong try again in a few seconds" which usually prompts me to restart the home itself via unplugging. Just recently (after upgrade to 2.0.0.74) I also noticed that my dropcams have been randomly dissconnecting. That prompted me to check [ipaddress]/debug.htm and I noticed that all my routers and satellites have been randomly restarting (via the uptime counter). Upgrading to 2.1.1.12 still results in crashs and I also notice that I also have the CPU utilization 70%+ as well. Halp?