11-24-2022 04:54 PM
Among other things, I have a 1st gen Google Home Mini and a 2nd gen Nest Hub. Both of them worked fine until a few days ago. I noticed they were having problems when I wanted to cast some music to one of those speakers. My other speaker (Lenovo Smart Clock) and a couple Chromecasts showed up on the list of devices to cast to, but none of the first two. Both were connected to my network, they responded to voice commands. But when I went to their respective settings in the Google Home app, they gave a message that they were not connected to the same home network, despite showing in the same settings that they were.
I then decided to factory reset both. I turned off mobile data on my phone and tried to set them up. It got to almost the end of setup where I got a message stating I needed to be on the same network (I was). Both devices failed to completely set up. I even tried doing this on my iPad, same problem.
I don't know what to do with these two things. I like using them but I can't have two paperweights sitting in my home.
11-26-2022 09:13 AM - edited 11-26-2022 09:13 AM
Try these steps:
If none of the steps above help, try setup using a different phone or tablet if you have one, just to test.
11-27-2022 01:25 PM
I've tried all of that, it gets to the point in setup where it says I'm not connected to the same network. Now my Chromecast with Google TV is doing the same thing. This must be some kind of Google bug.
11-27-2022 01:42 PM
Try these alternative steps:
11-28-2022 05:38 AM
Make sure there is access to Google's DNS servers.
My experience is that the Nest Home 2nd gen(only Nest produck I own) has to use Google's DNS(8.8.8.8. and 8.8.4.4) for Internet access.
11-28-2022 06:57 PM
I've been using a Pihole on my network for the past few years with zero issues. All my Google (but oddly none of my 3rd party stuff) stuff always disconnects from wifi, and the only thing that can bring them back on is a factory reset. That's a huge problem on Google's end.
11-29-2022 05:39 AM
I don't know anything about Pihole, but it can assign which DNS servers to use? Maybe you can assign the Google devices to use the Google DNS?
When I got my Nest Home 2nd gen, it initially had internet access, because it updated firmware. But when it restarted after firmware update, it said that it couldn't access internet. I tried resetting it several times, but it didn't help. In my router I could see that it was connected, and shown as having internet access.
Then I tried using my phone as HotSpot, which worked. So I knew the Nest Hub wasn't bricked.
Suddenly I remembered that I at some point had blocked the Google DNS IP addresses in the router, and after unblocking them, the Nest Hub worked. I have since tried enabling the block again, and that caused it to loose connection again. So I know that Google DNS servers are mandatory.
I have written support and asked them to remove the google only for DNS in future firmware.
11-30-2022 06:02 PM
Hi folks,
@David_K, @Jens_G, I really appreciate the help and the information you've provided. It helps a lot.
@CheapCChair, @toby1401, have you had the chance to try the suggestions above? I know this must have been done already but would you mind doing the sequential reboot one more time? Unplug the power cord of your router/modem followed by all your Nest speakers. Re-plug all in the same sequence. Restarting your phone might also help. Don't forget that all devices must be on the same network to communicate.
Also, about AP isolation, you need to contact your ISP or routers manufacturer for them to disable it if you cannot access the settings.
Tell me how it goes.
Best,
Dan
12-01-2022 01:55 AM
Hi Dan, thanks for your post. I have done all that and still getting the same outcome which is that the Nest device connects to the router, it's there in the router UI as a connected device when I log in but the Home app can't see it. Ask the Nest device to do something and it tells me to log in to Home. This is pretty basic connectivity - it shouldn't be this hard. I am shipping both devices back to Google today - I bought direct from Google Shop - as I am well within the return period. Very disappointed. And now after all that, Home can't see my original Nest Audio so I've gone backwards. it's pathetic really and I'm reasonably comfortable with tech, for someone who isn't this would be a nightmare. I'm using Google mobile device as well so to not be able to make their own devices talk to each other is really poor. This should be plug and play with simple set up through the app. Sorry for rant and thanks for trying to help but I've lost hours trying and failing to make something work that should be a cakewalk....Dave
12-11-2022 01:28 PM
Hi folks,
Apologies for the delayed response and we thank you for your patience and doing all the steps provided. Are you still experiencing the same behavior with your Nest devices? Are your devices still not able to reconnect to your Wi-Fi? May I know what the exact message is when you're doing the set up? We also wanted to confirm if your Nest devices still work on another hotspot?
Keep me posted.
Best,
Dan
12-14-2022 01:33 PM
Hey there,
I wanted to follow up and see if you still need help. Please let me know if you are still having any concerns or questions from here, as I would be happy to take a closer look and assist you further.
Regards,
Dan
12-14-2022 01:51 PM
Hi Dan, thanks for following up. Unfortunately, as I said in an earlier post, I have returned the two new Nest devices to Google and had a refund. I spent too much time trying to get something that should be simple connectivity to work - very disappointed but appreciate you checking in.
Dave
12-17-2022 12:58 PM
Hi folks,
@toby1401, we're sad to see you go. We hope we can make it up to you in the future. Send us a message if you change your mind.
@CheapCChair, how are your Nest devices? Are they now connected to your Wi-Fi? Are they responding to your commands?
Thanks,
Dan
12-17-2022 01:01 PM
Sorry for the late responses. Yes, they are working now, it took a few hours of tinkering to troubleshoot, I had to downgrade the firmware on my mesh router to get them to work. Not sure why that was the problem since they worked on that firmware for a couple weeks before I started having that problem. Fingers crossed it stays that way.
12-18-2022 12:48 PM
Hi CheapCChair,
You're awesome! I'm glad that you're able to work this out. As we got our resolution here, I'm going to mark this one as resolved and will be closing this thread after 24 hours. Please feel free to open up a new thread if you have other questions or concerns.
Cheers,
Dan
11-29-2022 05:01 AM
I am having the identical issue. I have an existing Nest Audio working fine on my home wifi network. Just bought another Nest Audio and Nest Mini - arrived today. I can't get either to set up completely. Early stages work fine - I hear the connected sound and confirm, identify the selected room and then wifi netwrok and at this point it falls over when the Connecting to Wi-Fi screen appears - same message as CheapCChair - make sure your device is on the same network - it was, then the setup fails with a message saying disable AP setting in router. The device is set up but can't be seen by the App at all. Factory reset, router settings check and reboot - same outcome for both new devices. At least I'm in the return window for my paperweights, This will come up as anonymous sorry - first post and need to add screen name.