topic Re: "There was a glitch" and "Hmm, something went wrong" in Speakers and Displays

"There was a glitch" and "Hmm, something went wrong"

connorhale96 — Fri, 16 Jun 2023 18:55:08 GMT

Extremely frustrated with my Google Home experience as of late. All displays and speakers were working completely fine up until a few weeks ago. Almost every single time I have a command Google will either respond with "There was a glitch" and "Hmm, something went wrong" and I'm so close to switching to Amazon products. The last time I had this issue I switched from Xfinity to RCN/Astound and that fixed it for about a year.

I've seen so many suggestions from hard reboots, to turning off IVP6 on your router, but I'm hoping to create the latest thread for troubleshooting this issue since everything I've found seems to be from a few years ago. PLEASE SOMEONE HELP.

Google Products I have in home:

2 Mini Speakers

2 Nest Hubs (2nd Gen)

1 Nest Hub Max

ISP: Astound/RCN

Arris Model: DG3450

Re: "There was a glitch" and "Hmm, something went wrong"

Review4You — Sat, 17 Jun 2023 02:43:42 GMT

This has been an ongoing issue for me as well for approximately six weeks. I've reset the mini, tried different wifi connections, and still the same thing happens. I'm pretty tired of it, to be honest.

Re: "There was a glitch" and "Hmm, something went wrong"

digittante — Sat, 17 Jun 2023 07:46:54 GMT

Same here. We have 2 Nest Hubs (Gen2):
- Fuschia 10.20221207.2.100042 / Software 51.0.27.523530146

- Motion, Sleep, Gesture sensing are all off

- IPV6 off at the router level

Starting a few weeks ago, these fail to perform all core features like:

- respond to voice / questions like "what time is it?" -voice recognition times out, resolves nothing, then the Hub says, "Hmmm, something went wrong, try again in a few seconds"

- display Home devices / info - most widgets just show "Loading..."

- play media

- control home - toggle a button for some lights, but they don't actually turn on/off and the toggle reset itself after a few seconds-

- make calls - calls time out without connecting

What works:

- the wake phrase 'OK, Google' causes the 4 dots to wiggle that indicate its awaiting voice input

- display of current time

- swiping the touchscreen

- occasionally, after a few minutes of swiping around, it regains its ability to perform but that lasts only a minute or two and is unpredictable

I've tried multiple times to remove/add via the Home app, rebooted, reset, change networks, reboot router, etc. No change in behavior. Of note: there's never any onscreen indication of an explicit disconnect from the network. It just unable to respond, load info, or complete commands.

In contrast, we have 2 Lenovo Smart Clocks (which Google has announced are no longer supported). They work just fine and often respond from the next room when I'm speaking directly to a Nest Hub.

Personally, I'll share this is very frustrating. Our home has been a Google ecosystem for +decade going back to the beginning of Google Play Music. Chromecast Audios, Minis, Hubs, 3rd Party devices. Then GPM was abandoned, YTM, even at the Premium level, is a lesser service. All our Gen1 Minis got 'end of life'. Hub usability has decayed in the last ~6 months. 3rd party devices were abandoned. The latest Home app update erased our library of Routines that ran fine for years. I feel like I'm now in a race to rebuild everything on another platform like Home Assistant before Google just turns everything off.

So I'll cut to the chase: @Google: Would you like to fix your Hubs or take them back?

Re: "There was a glitch" and "Hmm, something went wrong"

digittante — Sat, 17 Jun 2023 20:09:26 GMT

Adding 2 more things to the list of "What works":
- casting to both Nest Hubs, solo or as part of a speaker group, from other devices/services works

- speaker group stay-alive - Since the Sonos settlement and the depracation of speaker group features, individual members in a speaker would sometimes drop out. Now all members, including these hubs, persist all day.

Re: "There was a glitch" and "Hmm, something went wrong"

connorhale96 — Mon, 19 Jun 2023 17:00:04 GMT

SOLUTION that may come as a disappointment...I called my ISP (RCN/Astound) and they noticed there was extreme lag. They sent a representative to me and called in for a hard reset of my router. Completely reset everything to default, so I had to rename the network. Luckily since I renamed it to the exact same thing, all devices were able to reconnect. Have not had any issues since. Happy for now, but concerned I will have to do that regularly assuming the issues will continue to arise.

Re: "There was a glitch" and "Hmm, something went wrong"

Review4You — Mon, 19 Jun 2023 20:14:15 GMT

Yeah, I've tried that about 15 times over a two month period, and am completely done dealing with it for now. Thanks for the heads up!

Re: "There was a glitch" and "Hmm, something went wrong"

digittante — Wed, 21 Jun 2023 00:27:58 GMT

Thanks for chiming in. Any info about what the actual problem / condition was in your scenario? "Reset the router" doesn't sound like a durable solution. Thanks.

Re: "There was a glitch" and "Hmm, something went wrong"

connorhale96 — Thu, 22 Jun 2023 19:27:22 GMT

This was all the info my ISP gave me. It wasn't just a simple restart, they completely reset my router to its default settings. This seemed to fix all issues I was experiencing with the Google Home and has worked for some time now. Sorry I don't have a more durable solution, would be helpful to know exactly what was fixed so I know for next time.

Re: "There was a glitch" and "Hmm, something went wrong"

Mezza — Fri, 14 Jul 2023 22:07:36 GMT

I too are having this problem. Could someone please tell us another way of fixing the problem.

Re: "There was a glitch" and "Hmm, something went wrong"

Muddi — Mon, 17 Jul 2023 18:12:29 GMT

Hey everyone,

My apologies for the late response. I know how it feels to not have a working device when needed. I'd love to dig deeper into this. To confirm, are you still having the same issues when your device is connected to a different network? What is the make and model of your router? Also, please list all the Google Home or Nest speakers that you have.

Looking forward to your response.

Cheers,

Muddi

Re: "There was a glitch" and "Hmm, something went wrong"

digittante — Tue, 18 Jul 2023 22:41:38 GMT

HI @Muddi.

The problems persist for me, even after the recent FUSCHIA update from 10.20221207.2.100042 to 11.20230306.3.112014.

Per my previous posts on this and related threads: our base network and Google Home setup remain the same (although I have tested on alternate network and Home setups). Our ISP is a 1gig fiber connection, and the router/AP is an OrbiPro SRR60 w/ 2 OrbiPro SRS60 satellites with IPv6 disabled. Our Google Home devices include 2 Google Nest Hubs, 2 Chromecast Audios, and 2 Lenovo Clocks (gen 2), and 5 generic "works with Google" switches for lights & fireplace.

What works: ad-hoc voice commands directed at the Lenovo Clocks can control music playback on Hubs and Chromecasts, and control all switches. Automations in the Google Home app can do the same.

What (still) doesn't work: voice recognition, media control, home control, and duo calling via voice commands or touchscreen on the Hubs. Per suggestions from @Princesss I have also tried (1) retrain the voice model, and (2) setup alternate Home. No luck.

Re: "There was a glitch" and "Hmm, something went wrong"

digittante — Tue, 18 Jul 2023 23:15:50 GMT

Also, router traffic suggests devices on my network are reaching out to the following URLs. I've indicated what's currently allowed -v- blocked:

allowed:

play.googleapis.com
youtubei.googleapis.com
clients3.google.com
clients4.google.com
www.google.com

blocked:

www.googletagmanager.com
www.google-analytics.com
ssl.google-analytics.com
pagead2.googlesyndication.com
firebaselogging.googleapis.com
analytics.google.com

LMK if Google Home devices require different/other URL access than shown.

Re: "There was a glitch" and "Hmm, something went wrong"

Muddi — Wed, 19 Jul 2023 21:47:25 GMT

Hi digittante,

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

Cheers,

Muddi

Re: "There was a glitch" and "Hmm, something went wrong"

digittante — Wed, 19 Jul 2023 23:14:49 GMT

Um, how is filling out that form different than the form I filled out by your request weeks ago on this same thread/issue?

Re: "There was a glitch" and "Hmm, something went wrong"

Muddi — Thu, 20 Jul 2023 13:36:15 GMT

Hey digittante,

My apologies, as I was not able to pull up the case yesterday, but as I double checked it, I found the case ID:4-5602000033890. I'll let the team know that you've tried the suggested steps but still have the same issue. We'll get back to you by email or post an update on this thread.

By the way, what type of account are you using (Business or personal email)?

Cheers,

Muddi

Re: "There was a glitch" and "Hmm, something went wrong"

Mezza — Thu, 20 Jul 2023 21:26:19 GMT

My nest is now working. Thankyou

Re: "There was a glitch" and "Hmm, something went wrong"

Muddi — Sun, 23 Jul 2023 17:07:07 GMT

Hi Mezza,

Perfect! We're happy to know that your issue is now fixed. Could you share the steps that help you fix the issue?

Cheers,

Muddi

Re: "There was a glitch" and "Hmm, something went wrong"

Mezza — Sun, 23 Jul 2023 21:03:48 GMT

Unfortunately it is back to the problem. It worked for a day. I didn’t do anything it just worked.

Re: "There was a glitch" and "Hmm, something went wrong"

Muddi — Mon, 24 Jul 2023 16:58:22 GMT

Hey Mezza,

Sorry to hear that. How far is your Nest speaker from your router? Also, what is the make and model of your router?Please try performing a sequential reboot. This will help refresh the connection of your Google speaker to your network. To do this, disconnect both your speaker and router from the power source and leave them unplugged for 1 minute. Once the minute is up, plug them back in one at a time with intervals.

Cheers,

Muddi

Re: "There was a glitch" and "Hmm, something went wrong"

Muddi — Thu, 27 Jul 2023 21:55:36 GMT

Hi Mezza,

I'm just checking in to see if you still need help with your device.

Cheers,

Muddi