error "hm. something went wrong try again and hm there was a glitch trya again

[CrystalB]

We have 5 gen 2 Nest Mini's in our home connected to a Max. The minis all stopped working at the same time we have rebooted them, factory reset and reinstalled them and we can get thru the set up but when we go to use them they all will have a delay and come back with either "Hum, something went wrong try again in a few seconds or Hum there was a glitch and to try again. It never works and we get the same messages each time from all 5 of them. Our Max works great no issues. All of our other wireless/streaming devices in the house work. Anyone run into this and know how to fix it? I even purchased new ones and the same thing from the start. Any help is greatly appriciated.

TIA

Crystal

[SpareKid]

Same problem here... I couldn't find any fixes yet

[CrystalB]

I haven't either I read to see if my router has IPv6 turned to 'on' to turn it off. I double checked and my is set to IPv4 so that fix wasn't a help either. Hoping someone on here has an idea.

[SpareKid]

I called some friends that have google devices. Everything is down. I suppose is a server problem, related to the lastest incidents that took place inside google warehouses... *Fingers crossed* that this situation will be fixed soon. 

[Muddi]

Hey folks,

Thanks for sharing details about the issue here. My apologies for the late response.

I know how challenging it is when you're having issues with your Google Nest Mini. Let's dig deeper into this. A few questions: when did the issue start? How far are the devices from your router? Are you using a dual-band router? Do you have a network extender or repeater? Have you changed any settings on your router lately?

To eliminate network issues, please try setting up one of your devices using a mobile hotspot. Please note that you will need two mobile devices for this setup (one will serve as a router and the other to be used to set up your Google Nest Mini). 

Cheers,

Muddi

[SpareKid]

On my end:

I haven't changed any settings. My devices were working just fine for about one year, two different google devices (nest mini and display hub). I'm using a performance router (single and dual band, tried both connections, tried changing wifi channels). First is 1m from the router and the other one at about 6m, no walls in between. 

I'll try setting them up with a mobile hotspot and come back with an answer. 

[CrystalB]

This issue has been going on for a few months we even purchased 5 new gen 2 mini's and the 3 we set up are doing the same. The original 5 worked for 2 years before this started. We have them in multiple rooms and one in our basement (directly under the router) the distance on the 4 up stairs range from approx. 20' to 100' (I'm guessing). We are using a dual band router and this is on the 2.4 channel. We do not have an extender or repeater set up and we haven't changed any settings. Our Google Hub works great and its on the same network.

I'll try the hotspot and see if that works. 

Thanks,

Crystal

[Princesss]

Hi everyone,

I appreciate all the details you've shared. Can anyone here confirm if the Google Nests speakers responds to the second query? Let's go ahead and try these commands: "OK Google, what time is it?" After its response, ask "OK Google, what's the weather outside?"

Lastly, kindly provide the following info:

• What type of Google Nest speakers are affected
• Distance of the Google Nest speaker from the router
• Cast firmware version

To check which firmware version you're on, follow these steps:

1. Make sure your mobile device or tablet is linked to the same account as your speaker or display.
2. Open the Google Home app .
3. Touch and hold your device's tile.
4. At the top right, tap Settings Device information.
5. Under "Technical information," find Cast firmware: X.XXX.XXXXX.

Keep me posted.

Best,

Princess

[Princesss]

Hi everyone,

We just want to check if you have seen our response posted above. Let us know if you have additional questions, otherwise we'll be locking the thread.
 

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

[CrystalB]

Ok. I’ve not been in town to try the hotspot to see if that will narrow it down. I’ll start a new thread after I try it. Thanks for the help

[Muddi]

Hey SDeemer,

Just bumping in to make sure that you've seen our responses. Feel free to update this thread if you need help with your Nest Hub.

Cheers,

Muddi

[Princesss]

Hi CrystalB,

Thanks for responding. I'll go ahead and lock this thread in 24 hours. 

Safe travels!

Best,

Princess

[SDeemer]

As of 10:00 AM EDT, this thread appears to be unlocked. I have tried everything on Google's help page https://support.google.com/assistant/thread/120543967/something-went-wrong-please-try-again

I have been running a routine to start playing a radio station at 7:00 EDT on an Insignia speaker since 2018. Recently, it stopped working. I repeatedly edited, deleted, and recreated the routine without solving the problem. I have unplugged, rebooted, and reset the speaker to factory specs without solving the problem. The speaker is less than 20 feet from a router that covers the farthest reaches of my house.

My latest experiment is to create another routine to set the volume on the speaker, then a minute later to start the actual radio routine. I won't know if it actually fixes the problem until 7:00 AM on August 20. I ask that you do NOT lock this thread until I can report back.

[Muddi]

Hey SDeemer,

Sorry to hear about your experience with your Insignia speaker. Please note that we have very limited support on third party speakers with built-in Google Assistant like Insignia. Since you've exhausted all the troubleshooting steps, it is best to reach out to them for better assistance.
 

Feel free to update this thread if you need help with the Google Home/Nest devices.

Cheers,

Muddi

[SDeemer]

Muddi : I realize that. However, it's clear from other reports that this is also an ongoing problem with Google Home/Nest devices, which Google has never resolved. 

As a Platinum Product Expert for Chromebooks, so I'm very familiar with problem reporting, as well as step-wise diagnosis of problems.

[SDeemer]

Two scheduled routines were supposed to go off this morning:

• 0655 :  Adjust speaker volume to 45
• 0700 :  Play radio

The first worked, the second did nothing. I subsequently unplugged the speaker for 10 minutes, and power-cycled my router. Both routines worked at temporarily scheduled times. I have reset them to the original times, and will see what happens Saturday morning.

 

[SDeemer]

Misery loves company, I suppose. I'm glad that I didn't try to replace my Insignia speaker with a Google device. As you report, this started recently, after working fine for several years.

[NancyE]

I have a google home and 4 nest minis.  For a week, I can say, Hey, Google, play but when I ask to play on Home Group I get the "something went wrong" message.  If I use my phone to cast Sirius on Home Group, it works fine.  Sometimes the speakers will remember Home Group if I change radio apps.  But, most of the time, I get the "Sorry" message.  Now my speaker groups will only work from my Android phone, but they don't show up on my Iphone SE.  

[SDeemer]

I have been dealing with this issue on an Insignia speaker off and on for months, after working reliably for several years I have a routine that is supposed to start at 0700 every morning, and turn on the radio to a specific station. As soon as the routine starts on schedule, I get the "Something went wrong..." message. If I start the routine manually, it always works. 

I have gone through all the suggestions to unplug and restart the device, to reboot it, to return it to factory specs, etc. and none has worked. I am beginning to wonder if during the night the speaker forgets its Wi-Fi connection, and when the routine wakes it, the error message is returned.

I just tried a new experiment, setting a routine to change the volume of the speaker 1 minute before the daily radio routine kicks off. This worked: at 0944 the volume routine went off, and at 0945 the speaker started playing without the "Something went wrong..." message. I will not consider this solved until 0700 tomorrow.

[SDeemer]

I'm not 100% convinced this solved my "Something went wrong...." problem, but the set volume routine went off at 0655 this morning, followed by the radio routine at 0700. Both worked as expected.

Normally, I try to change only one variable at a time, but I also power cycling my router yesterday may also have been a factor. If Something went wrong...." occurs again, power-cycling the router will be my first step — even though everything else in my house was working fine yesterday.

Fingers crossed.

[Muddi]

Hey SDeemer,

Thanks for the update, and we appreciate you for sharing the steps that you've been trying. Moving forward, please note that we haven't received similar reported issues like this on Google Home and Nest speakers. Also, our team doesn't have access to crash reports from a third-party speakers - that's why it is best to report this issue directly to the manufacturer so they can help you properly with your concerns.

Thank you for understanding.

Cheers,

Muddi

[SDeemer]

Muddi : Quoting from the opening post in this topic, the "Something went wrong..." error clearly applies to Google Home and Nest speakers :

We have 5 gen 2 Nest Mini's in our home connected to a Max. The minis all stopped working at the same time we have rebooted them, factory reset and reinstalled them and we can get thru the set up but when we go to use them they all will have a delay and come back with either "Hum, something went wrong ...

If you search for google speaker something went wrong, you will see page after page of problem reports. The problem is widespread, has been going on for some time, and affects all manufacturers.

Unfortunately for me, the Insignia speaker is a discontinued model, so no firmware updates and no meaningful support are available from the manufacturer.  After working fine for 4 years, the "Something went wrong..." error started about 3 months ago, which suggests a change at Google's end. 

[Muddi]

Hey SDeemer,

Sorry to hear that Insignia was not able to help you with this. We can forward this to the team but will not be able to provide you a timeline for updates as this is an issue with third-party speakers. 

By the way, do you still have issues with your Google Home and Nest speakers and display? If yes, let's discuss it further and troubleshoot the issue.

Cheers,

Muddi

[Muddi]

Hey SDeemer,

Just wanted to confirm if you have the same issues with your Google Home and Nest speakers?

Cheers,

Muddi

[SDeemer]

I am not using any Home or Nest speakers as alarm clocks. I have had occasional "Something went wrong" on a Nest Hub, 2nd generation, using voice commands.

[SDeemer]

Also, the "Something went wrong..." error occurred on the Insignia this morning, after working yesterday. I have basically given up. In my experience, Home routines operating on a schedule have become too unreliable to be useful.

[Muddi]

Hey SDeemer,

Understood! I know this is not the answer that you are looking for. The best thing to do now with your Insignia issue is to send feedback, so their team will be able to check what's going on with your device. As for your Nest Hub (2nd gen), could you tell us how often do you experience the issue in a day?

Cheers,

Muddi

[SDeemer]

I'm continuing to experiment. "Something went wrong..." again this morning. A minute later, when I triggered the same routine by tapping the start routine arrow, it worked. 

My next experiment will be to set a copy of the same routine to run 1 minute later.

[Muddi]

Hey SDeemer,

How was your Nest Hub (2nd gen) now? Have you tried creating another routine to see if you will have the same issue?

Cheers,

Muddi

[SDeemer]

Thanks. I have been on the road. The "Something went wrong..." error only occurs on scheduled routines. 

[Muddi]

Hey SDeemer,

Would you know the specific action where it normally happens?

Cheers,

Muddi

[SDeemer]

[Princesss]

Hi SDeemer,

Thanks for the additional info. 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.

Best,

Princess

[Azarco]

Hey SDeemer,

It's us again. Have you had the chance to fill out the form? 

Thanks,

Alex

[Princesss]

Hi SDeemer,

We just want to follow up-- have you filled out the form we sent?

Best,

Princess

[SDeemer]

I have been on the road for the past two weeks, and unable to comment. I should be home again next week.

[Princesss]

Hi SDeemer,

Thanks for letting us know about this. We'll keep this thread open and wait for your response. Safe travels!

Best,

Princess

[TS0]

I am also having this problem continuously. Sometimes commands work on the 2nd or 3rd time of asking but most of the time I get "something went wrong" or "there was a glitch". 

Note: this is happening across multiple devices. I have two Nest home speakers and two Nest minis. I have not changed any settings on these devices recently.

It has just started happening in the last couple of weeks and it's driving me crazy.

I would really appreciate a solution to this. I am very close to getting rid of all my Google devices.

[SDeemer]

@TSO : Misery loves company. It's gratifying to see a report like this from someone who has nothing but Google devices, not those from a third party. The wakeup routine for my Insignia speaker (which does nothing more than turn on a streaming radio broadcast at a scheduled time) worked this morning for the first time in months. Good luck.