09-28-2021 12:28 PM
I have 5 google home minis, a google home max, and 2 regular google homes in my home. When they work they are great. Last year it seemed like at least once a week the speakers needed reset in order to get them working again because google assistant would not respond. It eventually fixed itself and we hadn't had issues in a while. Around the start of the month all speakers began to act up. You ask a request or question or anything and the first time the speaker will respond "Hmmm there was a glitch, try again in a few seconds" then you try after it stops talking and works perfectly. Whats really weird is I can ask a question to one google home and if its the first question sometimes 3 or 4 google homes will respond with "there was a glitch" even ones 2-3 rooms over from where I am.
I've tried factory resetting all speakers and that didn't work. I tried rebooting my router and that worked for about a half hour but then every speaker responds "there was a glitch" It is maddening when I'm trying to just turn off the lights in my house and all of a sudden google hears me, waits like 2 minutes, responds "there was a glitch" , and I have to say the command again. A simple task that should take roughly 10 seconds ends up taking like 3 minutes.
I would understand a device could be defective but when all 8 speakers in my house are doing this it doesn't seem like all of them can be defective. Is it because they're technically old now? Is this google pushing me to buy the new speakers?
I just want them to work. Anyone know a fix for this?
Answered! Go to the Recommended Answer.
10-01-2021 07:44 AM - edited 10-11-2021 01:15 PM
Found a fix that seems to be working!
I read around the internet looking for an answer to this and a few people over on reddit at the google home subreddit said that disabling IPv6 on your router could be a fix for this. I also read that if you have a mesh network enabling fast roaming could work. Or another one I read was switching the channel of your WiFi bands could do the trick too. I ended up trying all three.
Just changing the channel of the WiFi bands didn't seem to work, it did at first but quickly reverted back to the "there was a glitch"/"there was a problem". I then enabled fast roaming on my mesh network, again seemed to fix the problem for like 20 minutes but then reverted back. I then tried disabling IPv6 and it worked like a charm. I did this last night around 5pm and this morning it is still working which is the longest its gone without problems in a few months.
Edit: This has now been working for 2 weeks without issue
To disable IPv6 on your router you should be able to navigate to your router settings via browser by entering the default gateway into your address bar (should look something like 192.168.1.1) Sign into your router's setting pages. From here it differs for each manufacturer but essentially you want to look for some sort of advanced settings and see if there is a setting for IPv6 there. Toggle it off and everything should work. If you have a netgear orbi router I can provide a little more detail of the process because that is what I have. Steps to diable IPv6 for orbi routers:
09-28-2021 12:29 PM
Also labels aren't entirely accurate, its more than just the google home mini 1st gen, its also the regular google home, and the google home max. We use both iOS and Android in our house so setting up with either shouldn't be an issue.
10-01-2021 07:44 AM - edited 10-11-2021 01:15 PM
Found a fix that seems to be working!
I read around the internet looking for an answer to this and a few people over on reddit at the google home subreddit said that disabling IPv6 on your router could be a fix for this. I also read that if you have a mesh network enabling fast roaming could work. Or another one I read was switching the channel of your WiFi bands could do the trick too. I ended up trying all three.
Just changing the channel of the WiFi bands didn't seem to work, it did at first but quickly reverted back to the "there was a glitch"/"there was a problem". I then enabled fast roaming on my mesh network, again seemed to fix the problem for like 20 minutes but then reverted back. I then tried disabling IPv6 and it worked like a charm. I did this last night around 5pm and this morning it is still working which is the longest its gone without problems in a few months.
Edit: This has now been working for 2 weeks without issue
To disable IPv6 on your router you should be able to navigate to your router settings via browser by entering the default gateway into your address bar (should look something like 192.168.1.1) Sign into your router's setting pages. From here it differs for each manufacturer but essentially you want to look for some sort of advanced settings and see if there is a setting for IPv6 there. Toggle it off and everything should work. If you have a netgear orbi router I can provide a little more detail of the process because that is what I have. Steps to diable IPv6 for orbi routers:
10-15-2021 12:12 PM
Hi All,
First, thank you AlexM for your update and finding a solution! That is great to hear.
For everyone else, thank you for taking the time to try and troubleshoot this issue. I appreciate your time and will try to help all of you.
10-16-2021 08:23 PM
Thanks so much for your insights! After months of having this issue, reading and trying everything, marking ipv6 as “pass through” FINALLY resolved the issue!
I must say that I also marked IP as fixed once I notice one device had two IPs in router although in Home App showed only one.
Hope everybody else can also fix it, I really know how annoying a childish and slow assistant can be!
10-06-2021 06:32 AM
Is there a fix forthcoming that doesn't require disabling IPv6? I'm not an expert on the mechanics of WiFi, but it sounds like disabling that could have a detrimental effect of the performance of other devices on the network, and even still, I've been having trouble remembering the password to my router's admin website.
10-06-2021 10:12 AM
I have not heard anything about a fix coming. It seems about 1-2 time a year some sort of update is pushed that causes these issues. Last October I was hit with these issues but they ended up resolving themselves eventually. I was just tired of it happening this time because it was happening for about a month. Since I have disabled IPv6 I saw no loss of functionality in any of my other devices whatsoever. I have around 30 devices on my home network and not a single one has had issues since I turned of IPv6.
10-11-2021 11:27 AM
So I dug through my router's configuration page and there doesn't seem to be an option there to disable IPv6, though by digging through a forum post from 2016 it looks like (At least then) that my ISP doesn't even support IPv6 to begin with? I suppose I'll just have to wait until Google pushes a fix for the Nest Hub.
10-11-2021 12:43 PM - edited 10-11-2021 12:43 PM
What router do you have and who is your ISP if you don't mind sharing?
10-11-2021 12:56 PM
It's a Netgear C6300 running on Xfinity.
10-11-2021 01:11 PM
While Xfinity does support IPv6 networks you may be correct in stating that IPv6 may not be offered by Xfinity in your area. You should still at least find an IPv6 setting in your router's settings page. Straight from Netgear's website it looks like you might be able to find it by following these steps:
Like you said though it is possible that you currently are not running an IPv6 network in which this fix will not work for you. Hopefully this doesn't send you right back into a circle a steps that you've already tried. I've noticed for quite a few people this fix has worked but it is possible that this issue exists due to multiple reasons and IPv6 is not the reason this issue persists for you.
10-11-2021 01:23 PM
I checked in IPv6 settings, there's no checkbox to turn it off, only settings for IP address assignment, (Giving me the option to switch to using a DCHP server manually) disabling the IPv6 firewall, and the option to either automatically or manually assign DNS servers.
10-15-2021 12:14 PM
Hello @jbh54
I have made a case for you so that you can receive more help from the support team. This will be sent to the email address associated with your community profile. Your Case ID is: 6-5770000032074.
10-12-2021 01:12 PM
This seems to be a regression on functionality. All 3 Google home devices "glitch". No changes on wireless setup.
I do use IPv6 in my setup, is there any other workaround? We control lights and smart devices with Google Home, and the glitch makes them effectively useless. I am literally in the process of ordering Alexas
Are there any known workarounds that do not require disabling IPv6?
10-12-2021 01:16 PM - edited 10-12-2021 01:20 PM
I have not found any other fixes myself and I haven't found anything substantial of Google even acknowledging this problem. I would say if you need to use IPv6 and Google isn't fixing this yet give the competition a try. Aside from connectivity issues, I really do prefer google homes over Alexa but if something isn't working and the only fix is to break something else then you sorta have your hands tied and are left with one option.
Edit: I also assume you have already tried resetting your google homes. If you call google that is really the only help they offer for this issue but outside of talking to someone on the phone I have not seen on statement from google about this problem. I also feel like most of the people that end up here have already tried resetting their devices and are still left with problems afterwards.
10-12-2021 06:57 PM
Thanks for the follow up. Yes I've tried but the issue still reproes.
10-14-2021 08:42 PM
I have the same result.i turned off Ip6 and the 2 out of 4 that were glitchen Google devices started to work again..Then I found out I could not VPN back to work again on my work PC. I had to to enable IP6 again...Now I am back to glitches. Resets do not work. Very disappointed in glitchen Google re: this.
10-15-2021 12:34 PM
Hello @Charliechaplin
Thanks for reaching out. I have made a case for you so that you can receive more help from the support team. This will be sent to the email address associated with your community profile. Your Case ID is: 1-7204000031898.
10-19-2021 09:00 AM
Hi @lina
Thanks for your update! I am glad to hear that you were able to find a solution.
If anyone else has any other questions or concerns, please let me know. Thanks!
10-22-2021 11:36 AM
Hi All,
We haven't heard any updates from you. I'll go ahead and lock this thread. If you have any questions regarding your case or this issue, please reach out to the support team. As always, if you have any new questions, feel free to make a new post. Thank you and have a great day!
10-15-2021 12:23 PM
Hello @AnnoyedGoogUser
Thanks for your message. I have made a case for you so that you can receive more help from the support team. This will be sent to the email address associated with your community profile. Your Case ID is: 7-1341000031956.
08-23-2022 11:24 AM
I recently moved into a house with 1gb ATT fiber and currently use eero pro 2nd gen (2 total). I have 8 google speakers (minis, speakers, hubs) and when I initially say "hey google..." I will get one of two responses: "hmm something went wrong try again in a few seconds" or "There was a glitch..." THEN I can immediately follow up with a question/action and it will respond like there was no issue.
I have searched for days and have:
- modified the ATT modem/router to only act as a modem
- reset each google device multiple times
- turned off IPv6 on my router (worked for like 5 mins)
- moved devices from 5ghz to 2.4 and back
Searched the forums and this was the closest thing that worked. HELP PLEASE! https://www.googlenestcommunity.com/t5/Speakers-and-Displays/quot-There-was-a-glitch-quot-on-first-t...
08-23-2022 07:18 PM
Hey goophi206,
We’ve duplicated your thread to the main one here. You’ll receive all updates on this issue on the main thread and we recommend updating and checking this thread when needed.
Cheers,
JT