Home Minis and Nest Minis constant "Hmmm there was a glitch, try again in a few seconds"...

[CE92262]

I have a mix of 1st gen Home Minis (two), a Nest Mini (one), an Insignia speaker with Google Assistant, and the Nest Wifi with router and one point (that has Google Assistant).  For the past few weeks, on either the Home Minis or Nest Mini, whenever I issue a command, they respond "Hmmm there was a glitch, try again in a few seconds".  It is very frustrating, as I have to wait for it to time out, issue the "glitch" response, then ask again (which does work).  The Insignia speaker and the Nest Wifi speaker don't have this problem, they work on the first try as they should.  My internet speeds are excellent (as proven by the Nest Wifi).  All of my WiFi devices work as they should without any problems.  My two phones (Pixel 6 Pro, Pixel 6) work great on WiFi.  I've factory reset the Minis over a dozen times, now, with the problem still persisting.  I'm about to throw them all out and getting some Alexas.  Or maybe find some more third-party speakers that actually work like the Insignia.

[kittermant]

Try to restart the device.  
Also make sure the app is up to date.
Lastly, try to restart your wifi network. 

Did that work? 

[CE92262]

I've restarted each device more than two dozen times.  Each device has been factory reset more than a dozen times.  App?  They don't use an app, they are self-contained devices.  My Home app on the phones is always updated automatically.  My WiFi network, provided by the Nest Wifi router and point, has been restarted numerous times already, without solving the issue.  Every other device in the house has excellent WiFi connectivity, all reporting more than 240Mbps/10Mbps speeds.  So, no, that does not work.

[Princesss]

Hi everyone, 

Thanks for visiting the Community.

Sorry to hear about what you're experiencing right now with your Google speakers. Could you please list down the devices that are affected with this "glitch" response? Also, what are the distance of these devices from your router?

Lastly, let's get the cast firmware version of the affected devices so we can check further what's causing this to happen. 

To check the firmware version:

1. Make sure the mobile device is connected to the same Wi-Fi or linked to the same account as the Google Nest or Home device.
2. Open the Google Home app .
3. Tap the device card of the preferred speaker or display.
4. At the top-right, tap Settings Device information.
5. Under Technical information, find Cast firmware:X.XXX.XXXXX.

By the way, thanks for lending a hand @kittermant.

Best,

Princess

[CE92262]

Google Home Mini: Cast firmware: 1.56.282045,  about 20 feet with no obstructions from Google Nest Wifi point.  Tested speed: 74.9 Mbps.

Google Home Mini: Cast firmware: 1.56.282045, about 20 feet, with exterior wall, from Google Nest WiFi point, tested speed: 71.8 Mbps.

Google Nest Mini: Cast firmware: 1.56.299498, about 20 feet through interior wall, from Google Nest Wifi router.  Tested speed: 35.5 Mbps.

WiFi tests 257Mbps/11Mbps.

No other devices, especially the third-party speakers with Google Assistant (like the Insignia speaker or LG TV or Nvidia Shield) have any problem.  These Google speakers have had no problem for over 2 years until the last month, when I suspect some update occurred that messed them up.  I've since read of many, many other people in various forums complaining of the same issue.

EDIT:  I've done as someone else suggested and turned off IPV6 in the settings for my Google Nest Wifi.  Now the Google speakers work as normal.  However, for various other issues, I need IPV6 addressing.  I can have it turned off briefly for testing, but other apps require it.  This is not a viable solution, as the speakers worked for over two years with IPV6 enabled without any problem.  Just in the last month has this become a big, big problem.  

[Princesss]

Hi everyone,

I appreciate everyone who shared some insights regarding this. I'd be happy to take a closer look into this and will update this thread as soon as I have news about it. 

Thanks.

Best,

Princess

[DaithiO]

Thanks princess no settings clog on top right hand corner.   I have the three dots, but nothing there.    Google is loosing me as a customer very soon, after 25 yrs if they don't give a crap enough to fix this issue.

[Princesss]

Hi DaithiO,

I appreciate your honest feedback. I'll make sure to let the team know about this and will chime in to this thread as soon as we have news from our Product Experts. 

Thanks for your patience.

Best,

Princess

[Princesss]

Hi everyone, 

Sorry for the inconvenience that this has caused you. 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,

Princes

[GodsRaven]

No.  This "fixes" it for a short time, as in an hour to maybe a day, then the problems start again 

[jbh54]

 My Nest Hub (1st Gen) has been having the same issue for the past several months after the issue resolved itself for a little while last year.  Factory resetting the Hub did nothing.  The Hub is within five feet of my router.  I'm guessing it's the IPv6 issue, but I remember looking through my router's settings and not finding even an option to disable it.  So essentially my Hub is bricked, and so far this year I've been either using the Echo Dot I bought as a backup due to this problem, or using the Google Home app to control my smart home.  The fact that the issues with IPv6 have been going on for the past year with no fix from Google is disconcerting and really hurting my opinion of this brand.

[CE92262]

I've had the Google Home Minis for over 4 years, the Nest Mini for over 2 years.  All three worked as they should, with the IPV6 setting, for all this time until about a month ago.  First the Home Minis started it, but the Nest Mini still worked.  Then a couple of weeks ago the Nest Mini began doing it.  I think it is an update that Google pushed out.  I wish they would realize their screw up and push out a fix.

[GodsRaven]

Mine stopped working correctly in January or early February of this year.  It's been so long now that I've lost track.  It's gotten slowly worse over the last several months.  Each time I restart, reboot, try anything they suggest to fix the system, it gets better for a day or so, then slowly starts getting much worse than before.  

At this point I have a Google hub (now only a video picture frame which will occasionally play music I want, but only after arguing with it for a couple minutes and for turning on/off lights after conferring with the nests), a bedroom nest (useful only for turning off my lights), and another nest(useful as a music speaker if I can get it to realize I only want the music to play there, not on a different speaker).

My phone also tries to answer instead.  Occasionally my display will ask me if it was supposed to answer instead of the one that did.  I've been in my bedroom, asked to have lights turn off, had my hub say that light doesn't exist on the system, had the light then turn off, then the best say it is turning the light off. 

If I weren't disabled and just had to invest in a "new" car I would have trashed the whole system and gone to Echo by now.  Hopefully I'll do so next year.  This is simply a mess and when you call customer service they are less than helpful.  They're not helpful here either except to repeat the same things in every thread.  They ask you to check certain settings, reset, blah, blah, blah.  I've done all that.  The problems remain.  The issue is Google.  To those who are having these issues as I am, good luck with your expensive paperweights.  They will come in soon and shut down this thread because I'm complaining about Google and blaming them for this.  Lord knows we can't have that.  It must be our fault, right?  If it were Google's fault, they would fix it certainly.  I'm over it.  I'm putting bad reviews everywhere I can until they fix their problem.  To the moderators, YOU are part of the problem as well.  And yes, I call you bots becat you don't really try to fix anything, you just repeat a script.  I'm over you also.  I'm only here to give other customers understanding that yes, it's not just them.  The system needs to be fixed.    

[silverp1]

I have a BT Smart Hub 2 router in the UK and it doesn't allow me to disable IPV6 but under the configuration settings there is an option to change the IPV6 address allocation mode from Stateless to Stateful. After I'd changed that, I powered off the Google Minis for 1 minute and powered them up again. I have not had any glitch messages since.

Hope that helps someone

[LFS]

I am starting to think that not only the backend has software issues, but also the firmware on the minis has bugs. My nest minis have been unable to understand voice commands correctly ever since 1.56.299498 came as a beta. Even my nest wifi point speaker is now acting like it has with hearing issues.

[CE92262]

My Nest Wifi point speaker also did the "Hmm there was a glitch" thing briefly, but I did a factory reset on it and it behaves normally since then.

[Princesss]

Hi everyone,

Chiming in to let you know that our engineering team is investigating the issue and is actively working on a fix. We appreciate your patience!

Best,

Princess

[DaithiO]

Talk is cheap. And this Forum has been talking for a long time about this issue.    A joke that Google is not supporting those who bought they're devices in this competitive space.

[Jake · Accepted solution]

Hey all,

Thanks for your patience while we looked into this! We're happy to share that we've rolled out a fix for this behavior if you use Nest Wi-Fi in your home. To confirm, please ask your Google Nest Mini to perform a command, and you may no longer receive the error message.
 

If you have any questions from here, please feel free to let us know.

Best regards,

Jake

[CE92262]

Mine now works even with IPv6 enabled, so evidently the fix works.  Thank you.

[egmarchand]

So, what is the fix?  What do I need to do to enable the fix? Mine are still telling me that something went wrong.  This is getting very annoying really.

[CE92262]

For me, I had to go into the settings for my WiFi router and turn off IPv6.  After the WiFi rebooted, the speakers work without the glitch.  The speakers should receive an update to fix the issue permanently so you can re-enable IPv6 if you choose.  Mine now work with IPv6 enabled.

[Purple-MG]

My nest mini is still telling me that "there was a glitch" every time I ask it a question, but it will work the second time garunteed, how do I fix this? Do I need to manually update it? This has been going on for months now, to the point where the thing sits dead in the corner of my room for weeks on end before I remember it exists, and switch it back on, only to be re-disappointed all over again by its broken-ness. 

[GL4144]

I also continue to get “something went wrong” from paired nest speakers, which before a couple of months ago worked fine. I have reset everything, disconnect and reconnected to no avail.  Interestingly if I then ask “what’s the temperature?” It will work, and only THEN can I play music or add things to a shopping list. 

[Princesss]

Hi GL4144 and DaithiO,

We've received your form-- thanks for filling that out. I'll consider this post as complete and will lock the thread in 24 hours. Please keep an eye on your email as someone from our team will reach out to you to assist you further.

Best,

Princess

[GodsRaven]

Because they're glitchy.  

[DaithiO]

Hi Princess or other specialists.

Any update on the glitch - It is on the Nest with the screen and also on the original google Home units.   So it is a software issue.    

[GodsRaven]

Exactly.  They'll never admit it though.

[Larcher]

I've been looking for a solution to this for months now, to a point the mini speakers around my home weren't being used and the Google Battery doorbell being a consistent 10 seconds late.

I've always assumed is was on Google's side but after yet another attempt to solve the problem I think I have.

Disabling ipv6 wasn't the solution. 

My router has something called APSD (Wireless Power Saving) which was enabled. It must have been a feature that came via my ISP's overnight updates and sounds great on paper but this energy saving seemed to be the cause of all my "home" problems. 

I've had APSD disabled for a few days now, which is more than enough time for the glitch problems to start and it's been rock solid. Every command to the mini speakers is still quick in response; as is the doorbell chime throughout the home.
I'm just kicking myself I didn't check out the router options months ago.