Google Nest and Mini (gen 1) Speakers reply with "there was a glitch/sorry something went wrong".

[rrkrueck]

This is the third time I've set these same 5 speakers up in a home (2x gen1 mini and 3x nest speakers). EVERY TIME at first the speakers all seem to work fine. Over time the assistant responsiveness just deteriorates. I'm talking over the course of ~4 months. Right now I'm at a point where when I "hey google" one of them, it performs the task but EVERY OTHER speaker does the "sorry something went wrong/there was a glitch". Its absurd and obnoxious and honestly terrifying in the middle of the night when I'm tryna turn on a light. Its to the point where I have just turned off voice commands on the speakers and just use my phone now to issue commands. My "smart speakers" have become music players only. Ive invested lots of time and money in this setup for it to be continuously just a pain. On the verge of just switching to another brand if I cant get this to work. Any help is appreciated. 

[Rinic27 · Accepted solution]

I've been having the same problem. But I discovered that connecting my speakers to my Google Wifi guest network does solve it. The only difference I can see between the networks is the primary one has the gateway address 192.168.86.1 while the guest network is 192.168.84.1. So the issue might lay there somehow.

[areyoukiddingme]

Well it's going on at my house. Started 4-5 days ago. No changes to my home system. 500mb download, Linksys Mesh for past 4 years. Every other device (50+) in my home that connects to WiFI works perfectly, Only the Google devices are not working.

All of my nest devices will frequently say 'sorry there was a glitch'. Google sucks. 

[Jake]

Hey all,

Sorry for the late reply. I wanted to follow up and see I could be of any help? Please let me know if you are still having any trouble from here, as I would be happy to take a closer look and assist you further. 

Best regards,

Jake

[rrkrueck]

Issue is still very much a problem. 

[Jake]

Hey Keso, 

Thank you so much for providing more details, and what helped fix the issue for you. I will leave the post open for a couple of days in case other people are looking for a fix to the issue. Please let me know if you have any questions from here.

Best regards,

Jake

[rrkrueck]

Jake, I'm the OP here and still having this issue. Have you red my issue and Keso's response? Ive disconnected and reconnected to a different network each time. I've moved physical addresses with different routers each time and if you read my post you can see that the issue is recurring. I have no idea why you would close my post because someone else posted what fixed theirs. The support on these devices that I paid Google for has been MISERABLE. 

[Princesss]

Hi everyone,

Thanks for posting.

I appreciate everyone who shared some steps that worked on their end. Upon further checking, it looks like this discussion is similar to what we have on this thread. Let's go ahead and continue our discussion on that so you can also try the steps others have tried.

By the way, thank you for your help on assisting the others, @Jake.

Best,

Princess

[rrkrueck]

The service is absurd that I can't get in touch with someone to specifically help me. Instead I have to rely on postings on a message board from other people having the issues. Where is GOOGLE in fixing this? Or are they simply not willing to help? At this point I have unplugged all my Google smart devices and just going back to a day before I had any. Its much more convenient than the alternative. WHERE IS THE CUSTOMER SERVICE?

[Princesss]

Hi rrkrueck,

Sorry about this. We'd be happy to take a look into this for you. Please fill up this form with all the needed information then let me know once done.

Best,

Princess

[Keso]

I have had the same issue with 2 nest mini devices. I tried many suggested fixes with no success.

This is the fix that worked for me:

1. Remove device from network through Home app.

2. Connect to a different network. (I set up a guest network to do this)

3. Remove device from this new network.

4. Reconnect to original network.

Just removing and reconnecting to the same network did not work.

Good Luck

[Rinic27 · Accepted solution]

I've been having the same problem. But I discovered that connecting my speakers to my Google Wifi guest network does solve it. The only difference I can see between the networks is the primary one has the gateway address 192.168.86.1 while the guest network is 192.168.84.1. So the issue might lay there somehow.

[Rinic27 · Accepted solution]

I seem to have fixed my issue by disabling WPA3 Security in my router settings and power cycling the router and every speaker.

[Princesss]

Hi Rinic27,

Thanks for updating us.

It's good to know that your speakers are already working. We appreciate the info you've shared as this would be very helpful to others who is also experiencing the same thing. 

Meanwhile, if there's anything else that you want to add up and share, feel free to update this thread so others can also join the discussion.

Best,

Princess

[Princesss]

Hi everyone,

Due to inactivity, I'll go ahead and lock this thread in 24 hours. Feel free to start a new thread if you need assistance with your Google speakers and we'd be glad to assist you further.
 

Best,

Princess