Google Nest Wifi Pro point needs to be restarted periodically

[hij2001]

This is more a performance issue than connectivity, but the categories in the drop-down menu are limited.

I have two WiFi Pro units Model: G6ZUC
Software version: 3.73.406133 configured as one router and one point using wireless backhaul. They have generally been working fine except for one issue that occurs periodically.  While I normally see 650-750Mb/s downstream near the router and 3-400Mb/s from the point at the farthest distance in my house, it will occasionally only provide 25-30MB/s downstream at that farthest point. 

There are no activities or exceptions reported in the Google Home app activity screen after this occurs, and trying to reset the point from the Home app doesn't work.  The system status shows both units online with a Great connection,  running the mesh test has no effect, and reports a great connection.  The only way to resolve it is to unplug the point for 30 seconds and then plug it in to restart.  This has been an issue with the earlier Software versions as well.

Has anyone else experienced this issue or is there a solution that can be suggested?  

Thanks and regards,

Howard

[LoudT]

@sicsacol Same situation here.  For the last 2 months I've needed to constantly reboot my network.  The product is simply no longer usable.  I've had to install timers to restart my network every night and even then there are days when I still need to reboot the network.  Simply not acceptable.

[fshagsm]

I came up with an amazing solution.  I returned my nest wifi "pro"s and got a system that works.  Had it for 2 weeks and I haven't had to restart my network once

[roblightbody]

I'm right behind you.

[degroof]

An odd thing happened. My spouse changed jobs recently, and the router hasn't acted up since the laptop from the previous job was shut down and returned. Not sure if it was the hardware or some app running on it, or it might just be a bizarre coincidence. 

But now I'm wondering if it has something to do with the router's current software not playing nicely with certain hardware or certain apps or some combination of the two. Wild guess: Zoom running on a Macbook Pro.

I'll try to dig up more info about the now-returned laptop and apps. Might help in reproducing the issue.

Will also reply here if the router starts acting up again.

[degroof]

Correction: Previous job was using Google Meet on a Macbook Pro. Current job uses Zoom on a Macbook Pro.

So, possibly current router software not playing nice with the combination of Google Meet running on a Macbook Pro? There also might've been a Zscaler wildcard thrown into the mix. 

[roblightbody]

Does either job require the use of a work-related VPN?

[degroof]

As far as I know, neither does.

[uber_ray]

I also began having problems about 2 months ago. My Blink WiFi cameras would stop recording video after a few days. The cameras worked fine otherwise and my Blink app still notified me when there was motion detected. Interesting that the same community specialist was responding to me. I understand they have to make sure there's not something being caused by other devices on the WiFi or the ISP, but that person obviously didn't read all of my initial post. Here's the subject of that Nest Community thread and link to it:

Restart WiFi network needed so Blink cameras can record video

https://www.googlenestcommunity.com/t5/Nest-Wifi/Restart-WiFi-network-needed-so-Blink-cameras-can-re...

Mine was working fine for many months until recently. Resets of my Blink Sync module sometimes resolved the issue. A Blink rep said he could see errors in the Blink log indicating problems with the WiFi network. He suggested the next time it happened, to try restarting the WiFi. I was skeptical because no other devices were having problems, but I was growing frustrated so I had nothing to lose. Sure enough, the next time it happened I restarted the Google Nest WiFi Pro network and that resolved the problem. I'm now doing that every few days - when I see the videos stop being recorded to the local USB storage connected to the Blink Sync module. After doing lots of digging online and seeing things like this, I'm convinced the problem is the firmware 3.73.406133. I also just saw this article the other day.

https://9to5google.com/2024/07/02/nest-wifi-pro-update-issues/

Now that I've been monitoring this closely I see my WiFi speeds decreasing when the problem with the camera video recording happens. I'm monitoring the speeds using speed tests from my phone while on the WiFi. Speed gets back up to the 500 Mbps I pay for after restarting the WiFi.

I hope Google releases new firmware soon that fixes this.

[hij2001]

Thanks for posting the article. It’s unfortunate that Google continues to ignore this issue and has failed to provide any update to address users’ significant issues with this product for over 6 months.  

[uber_ray]

That version of firmware was released mid -April, so not quite 6 months yet. Even with a slow rollout it's likely still been a couple months for most users. Hopefully the more this issue is discussed and publicized, it will cause them to act faster to get a new version out.

[hij2001]

Not sure how they rolled it out, but per my original post on 4/2, I had already been running version: 3.73.406133 for a few months. I agree that the more the community raises the issue, I would hope that Google responds and delivers a new functional and reliable release. 

if not, it will be time for me and others to evaluate new mesh systems that deliver reliable performance.      

[Evan_Poe]

I reported the issue to them while also reporting to them the Google Home app doesn’t allow me to reboot the routers any more!  The option is totally gone. Has everyone else experienced that, too?

[hij2001]

You can still do it, but they've moved the settings from the router/point page to the Google Home settings page (gear icon on the bottom right of the home page).  Click on the gear icon and then select the device and the device settings page is there.   Why make it easy or straightforward?  😢

[Evan_Poe]

Thank you. And that is a DUMB spot for it. 

[Naddy]

How are we going with this firmware update.... seems to be taking a while, followed all steps, seems restart is the only things that fixes issues, temporarily, then need to restart again. I have 3 pros, one main, one with wired back haul and one wireless. Nothing but issues since 3.73.406133, wish we could reverse the update.

[guipedroso]

This is awful in these days, internet not working? come on google... the is very shameful. 
Prioritize this thing and fix it! These issues are impacting loads and loads of people! 

[uber_ray]

In another thread - one I created before I found this one, a person mentioned they added DHCP reservations In Google Home for their Blink devices - and that resolved the problem. Here's a link to that thread.

https://www.googlenestcommunity.com/t5/Nest-Wifi/Restart-WiFi-network-needed-so-Blink-cameras-can-re...

I have been resetting my Google Nest WiFi when this happens - every few days - and that resolves it. I am tired of resetting my WiFi so often, I decided to give the DHCP reservations a try. I don't know how long Google Nest DHCP gives an IP address for, but if the lease is only good for a few days, it could indicate the Blink devices aren't getting a new IP address from DHCP when the first lease expires. With DHCP reservations for them, they will always get the same IP addresses, so I'll know if that helps in a few days.

If anyone else tries this, you need to get the MAC address of each device. It is on the back of my Blink Sync module, and next to the battery compartment in each of the cameras. It's a pain to gather them all, but I'm keeping my pics and a list of them for future reference.

[uber_ray]

Unfortunately my cameras stopped recording video to the Blink Sync module either late last night or early this morning. I did an entire network reset of the Nest WiFi through the Home app today and that resolved the problem. It's blatantly obvious there is a problem with the Nest and the Blink devices. It didn't have this problem until the last firmware update from Google. So disappointing. My next WiFi solution will not be Google.

[PaulGautier]

I have 3 Nest Wifi Pro units, and +60 WiFi devices at home connected, some of them controlled by Home Assistant. It's frustrating having to restart the Nest Wifi Pro units network every 7 days... it seems Nest Wifi Pro puts my network into IP isolation mode so my devices will stop talking to each other and Home Assistant will start reporting connection failures to the devices. Restart of network seems to always resolve things but not a practical and workable solution!. Please FIX this!!!   I am thinking of going back to my original Google Wifi units...

[Jacob5]

I can confirm I’ve also had to restart my network so that my speaker group of nest devices works properly and it’s hella annoying. You’d think google routers work seamlessly with other google smart home products (nest speakers and displays) but they don’t. The routers sucks. 

[degroof]

Hey, we just got a software update: 3.73.424613

Fingers crossed.

[Evan_Poe]

Hmm my main hub has :

Software version: 3.73.406133

[cloureiro]

Same here ...

[uber_ray]

Fingers crossed I get it soon. Their page doesn't list it yet. 

https://support.google.com/googlenest/answer/13800967?hl=en

[hij2001]

Interesting - not shown on the Google support page.  I still see 3.73.406133.  Please keep us posted.

https://support.google.com/googlenest/answer/13800967?hl=en

[burroudc]

All of mine are still on Software version: 3.73.406133.

Anyone else have theirs update to 3.73.424613? 

[nrushforth]

My appear to have updated. Showing as 3.73.424613

[hij2001]

Still nothing here or on the Google support page in my post above.  Just curious - for those of you who have received the update, where are you geographically?  They may be rolling out the update based on locations as opposed to simultaneously.  I'm in the Chicago area.

[degroof]

I'm in NC and got the update early morning Aug 7, possibly late night Aug 6.

[Username666]

Mine updated today (Aug. Eighth) 😎Nebraska sometime around when I rebooted my entire network.

[Jacob5]

Mine update but I'm not sure when, hoping for the best.  

[Evan_Poe]

How has it gone for the people who have the new firmware?  

[PaulGautier]

It seems the new firmware has fixed the issue. I haven’t restarted my system since the upgrade (3 weeks) and I no longer have issues with devices not talking to each other.

[burroudc]

Any updates from those that have received the latest update (3.73.424613)?

[LoudT]

I got the update last Thursday.  From what I can tell, this has resolved the issues that have been reported here.  I had reduced my network to one WiFi pro to minimize any issues on the prior build. This was slightly better than having 2 or 3 access points but still required several reboots per week.  After the firmware update, I have restored my mesh network to it's intended configuration and have not seen any performance / connectivity issues or had to reboot the network.  So after 6 days I think that the core issue introduced in 3.73.406133 has been resolved. 

[Evan_Poe]

That’s fantastic. All four of mine are still stuck on Software version: 3.73.406133 even after using the app to restart them. Maybe unplug them to force an update?

[hij2001]

Same here, even after restarting the network.  And  3.73.406133 is still listed as the current version on the Google support page at https://support.google.com/googlenest/answer/13800967?hl=en.

For those who have received the update, please report your location and whether these issues appear to be resolved.  Thanks1

[Naddy]

Still no update here after restarting

[burroudc]

So far 4 of the 6 of mine have updated. Which is introducing its own host of issues currently due to the main router still being on the previous version. But it appears the 4 received the update overnight last night. 

Just as a quick fyi the Google software release notes page will not update until the update has rolled out to everyone. 

[hij2001]

Thanks for the clarification on when the support page updates!  I guess the rest of us will have to just keep waiting. Hopefully it won’t be like Waiting for Godot…