When I try to reconfigure my primary Nest WiFi router in the Google Home app on my Android device (Pixel 5), it cannot connect due to the Nest WiFi being offline. This is not a surprise, because it is configured with a static IP that is no longer routable on my home network.
The Home app SAYS that in order to change this, I should:
It says when I do this I should be able to save the settings change to DHCP. It took many times trying this before it actually recognized that I had completed the requested steps and made the WAN settings editable.
The big problem is that even though I can *change* it, when I hit the save (floppy disk) icon, it shows a spinner forever.
It never *actually* saves the setting to my primary Nest WiFi router.
I spent something like an hour on the phone with Nest WiFi support, doing what they said even though the rep wasn't understanding that the Nest WiFi coming up, getting on ethernet, and assuming it could communicate using its statically configured IP address doesn't help when it cannot *actually* use that IP address. I had to go around in circles with them about this, and when I got cut off, they didn't call me back.
I'm pretty sure it would be difficult to get through to a rep who is senior enough to understand the problem, and it's possible this is simply something that is just broken in the Nest WiFi router OS. 😞
Also extremely frustrating:
Neither with my phone connected to the Internet via other means (mobile data or a different WiFi network) ... nor connected to my Nest WiFi network (offline, disconnected from ethernet) can I retrieve wireless passwords. Presumably the same flaky, not properly tested system of connecting to a Nest WiFi without a functioning uplink that causes me to be unable to reconfigure it for DHCP ... also stopped me from retrieving the WiFi password for the guest network.
If I had the guest network password, I could factory reset the Nest WiFi router and reconfigure it, but without that I would be stuck, because there is a device which I cannot reconfigure (someone from the US Geological Survey would have to schedule a visit to my house to reconfigure the device) which needs access to my guest network.
Apple cloud keychain to the rescue. Even though I do not normally connect to my guest network, I apparently at some point *had* done so, and Keychain had the password. Phew. So now I can factory reset my Nest WiFi router to fix its configuration.
I don't *want* to have to factory reset. This is a seriously broken Nest WiFi router OS problem. But I don't see there as being any other solution for me at this point. I hope someone from Nest WiFi sees this and is able to fix the problem for other people.
Thanks for sharing the case ID. Upon checking, the Nest Wi-fi or Google Wi-fi must be online before we try editing the WAN settings. I'm afraid we need to reset the network back to factory defaults in your case. We're always looking for ways to improve and we'll take this as feedback. Let us know if you have any questions — we'd be happy to help.
That is indeed what I found. That's an invalid assumption that you can always be successfully online to edit network settings, as network settings changes may be needed to get you back online.
In this case, if I had thought of it in advance I could have undone the static IP configuration, but I would never have guessed that a networking device would be incapable of being reconfigured unless it had a working connection to the Internet.
I would suggest treating this as a high priority to fix. One needs to be able to recover without the thermonuclear option.
Things you really MUST be able to do without a functioning upstream connection:
1. Retrieve the WiFi password for main network and guest network (especially guess WiFi).
2. Fix the network configuration on the device (WAN settings).