Weather data on 2 Nest Hub fullscreen clocks disappears overnight on Firmware Version 1.60.305621

[MplsCustomer]

This started with one of our Nest Hubs a few weeks ago and now is occurring on two of them. Each night, around 3:00 -3:30 am I think, the weather data that is displayed on the fullscreen clock on two of our Nest Hubs disappears. When this first started occurring, I was able to restore it by selecting a different clock face and then returning to the Weather clock face. Now, it will occasionally restore by just opening the Google Home app, or by visiting the Photo Frame setting. Usually, however, I have to reboot the Nest Hub in the Google Home app.

This does not affect any of the other functionality of either Nest Hub.  They still always have Internet connectivity and you can get Google results at any time.  They can be accessed from the Google Home app.  In fact, you can ask it for the weather and it immediately returns results, but the weather data on the fullscreen weather clock face still shows no temperature, clear, and sunny regardless of the actual weather.

If I had to guess, I'd say that some sort of function gets performed on Google Nest Hubs around 3:00-3:30 am each night, and this function has a bug in it.  I have noticed a couple of times that our Nest Hub Max sometimes reboots on its own around this time.

[Princesss · Accepted solution]

Hi everyone,

Thanks for responding. We apologize for this. Our team is still investigating the issue. I'll make sure to get back to this thread as soon as we have some updates about this.

Thanks for keeping in touch.

Best,

Princess

[Princesss · Accepted solution]

Hi everyone, 

We appreciate your patience on waiting for a fix. We're coordinating with the team and still waiting for an update. 

By the way, thanks for sharing some steps @AMiesem.

Best,

Princess

[Muddi · Accepted solution]

Hey folks,

The team is still investigating this issue and we haven't received any updates as yet. We'll continue checking in with the team and share any updates we receive.

We understand this issue has been happening for quite some time and has been a rather frustrating experience. Thank you for your patience while our team works through this. 

Cheers,

Muddi

[bougij]

Yes, it is the same issue.

[Princesss]

Hi bougij,

Thanks for clarifying. Since this is a similar discussion, we'll move this conversation to this thread so we can update each and everyone once we have some news to share.

Best,

Princess

[AMiesem]

So, I'm not sure if anything changed, but it seems like all of my devices are now functioning correctly without me having to do anything else. Maybe I just got lucky or maybe it's an anomaly, but it's been a couple of days and everything is functioning correctly.

[lalex]

If you check Device information in Home, you'll probably see that your firmware number is different from the one listed here with the issue. That's what fixed it for me.

[backspace]

My 1st gen device was updated sometime during the last week and the problem now appears to be fixed.

As of Oct 7, 2022

• Fuschia version: 7.20220419.2.166
• Software version: 48.41.32.466204089
• Cast firmware version: 1.62.312297

[MplsCustomer]

All of our Nest Hubs except one is now on Cast Firmware Version 1.62.312297 and the problem has not occurred for 3 nights now. Oddly, one of our Nest Hubs is still on 1.56.309385.

[bougij]

I now also have the same Firmware Version.  I haven't had the problem for 3 days now as well.  Sure hope it has been fixed.

[gren45]

glad I found this thread. now I know I am not crazy. both my android phones show the weather widget but my 2019 Nest doesn't.  Except for 1 mobile android phone every other device uses the same single WiFi here at the house.     Only way to get the Nest widget is to de-install Google Home on my android phone, then re-install the app...but that only lasts a day.   Relied on my Nest weather widget for years but now I have to always ask "Hey Google whats the weather like today"

[WillyOne]

To gren45, you now "seem" to be an outlier.  The problem has been resolved on both of my Nest Hub (Gen. 1) devices for many weeks.  I also haven't seen any new complainants on this post for some time.  Some people had resolved the issue by joining a beta test group, however I was not one of them.  I did nothing other than continue to install software updates and, as I said, mine's been fine now for quite a while.  I assume one of those updates resolved my issue but others will have to speak up and give their experiences because I haven't seen any declaration from Google stating the issue has been resolved.  Just as an aside, unlike yourself, when I was having the issue I found the display would temporarily correct itself merely by opening and then immed. closing the Home app on either my phone or my tablet.  I never had to uninstall/reinstall the app.  

[lalex]

As WillyOne stated, the problem has been repaired for some time now. Just make sure you're not still on version 1.60.305621. If so, I forced an update by unplugging and replugging in my hub. Or you can go here for more info.

[steveindanville]

As of today the weather widget shows "--" degrees for no reason.  Nothing I've done will bring it back, including all the hints mentioned in the existing thread.  So, this problem is back.  This is on my Nest Hub 2nd Gen.

[Conmore]

Hi there

i checked mine this morning and displaying correctly, so not sure why yours is blank. Just check you have the latest firmware update as suggested. 
Cheers. 

[steveindanville]

It's back working again but of course the Photo Frame is, and continues to be frozen.

[curiousmike]

The "- -" for weather had been plaguing me for weeks - super annoying.  I had tried tons of suggestions all over - to no effect.

Finally, the one suggestion that worked for *me* was changing my home address one house over ( just changing my address ).

That evidently kicked the system in the butt and got me working again.

Settings -> Tap on your address -> Tap on Home Address -> Edit -> Set it to one house over.

[lalex]

It looks like this old problem from a year ago and solved, has reared its ugly head again.

Must be in some bad code in an upgrade. Perhaps everyone with the issue should share what version they're on?

Your solution is brilliant, by the way. Bravo!