1 of 3 nodes not upgrading SW version

[GooglyMoogly]

I’ve been successfully running a home network with one router and 3 nodes for several years. Today I noticed one of the three nodes has a lower software version than the other two. It has a great connection. Any reason it might be “behind schedule” in auto-updating it’s firmware?

Network setup:

• Router, model H2D, SW version 14150.376.32
• Node A, model H2E, SW version 1.56.315675
• Node B, model H2E, SW version 1.56.315675
• Node C, model H2E, SW version 1.54.294928

[olavrb]

Strange. Tro to factory reset it ( https://support.google.com/googlenest/answer/6246619?hl=en ) , not the whole network, and add it to the network again?

[GooglyMoogly]

Tried that today. Factory reset, then re-added the device. Message in the Google Home app at the end of the process indicated 'Network is Up-To-Date', but it still shows the older software version that don't match the other two nodes. Still shows 'Great connection' after a mesh test. Any other ideas / suggestions?

[olavrb]

Whats the output regarding firmware if you go to "http://<its' local IP address>/api/v1/status" in a web browser while connected to the network by Wi-Fi?

For the main Nest Wifi puck, unless you've changed the default adress of the LAN, it would be "http://192.168.86.1/api/v1/status".

Mine says:

   "software": {
      "blockingUpdate": 1,
      "softwareVersion": "14150.376.32",
      "updateChannel": "stable-channel",
      "updateNewVersion": "0.0.0.0",
      "updateProgress": 0.0,
      "updateRequired": false,
      "updateStatus": "idle"
   },

[Jeff]

Hi GooglyMoogly,

I just wanted to jump in real fast to see if you saw olavrb's reply and to see if you still needed some help on this or if you were able to get it sorted out. If you are still needing some help, just let us know and we'll be happy to continue helping.

Thanks,
Jeff

[GooglyMoogly]

Thanks. Saw olavrb's reply and posted my follow-up on 16-Oct. Upon just checking my system now, however, I see that my Node C which was showing outdated software version info has now "caught up" with the other nodes. I did perform a full system restart earlier today, so maybe that's when the upgrade was triggered. Thanks for your message, but I think I'm all set now. Cheers.

[Jeff]

Sounds great, GooglyMoogly. I appreciate the update as well.

I'll go ahead and mark this as resolved in the next day or so. If anyone has anything else to add, feel free. Thanks to olavrb for all the help here.

Regards,

Jeff

[GooglyMoogly]

Mine says:

"software": {
      "blockingUpdate": 1,
      "softwareVersion": "14150.376.32",
      "updateChannel": "stable-channel",
      "updateNewVersion": "0.0.0.0",
      "updateProgress": 0.0,
      "updateRequired": false,
      "updateStatus": "idle"

Looks like a match to what you've posted above, and doesn't indicate there's a required update or an update in progress (or stalled).  As a point of further clarification, there is no known difference between my three nodes; all were purchased together as part of a kit at the same time, installed together within a few hours of each other, and all have operated on the same network for two plus years. 

Perhaps there is a method to "force" an upgrade or manually initiate an upgrade check & validation?