Nest has stopped responding to commands, I only get 'Sorry something went wrong' message

[Tim71]

Hi

Everyday I use the voice command 'show me the news' on my nest (there are 4 Nests in the house) and my selected news plays without issues. Approximately 1 week ago whenever I say this (or any other command) I get 'sure here's the news, sorry something went wrong, when your ready give it another try'. It's still doing the same on all devices.

I've reset all devices, makes no difference, I found a few 'similar' posts where one fix was to disable IPv6 on the Google wifi - mine was already set to disable. I enabled it, disabled it again and reset all devices - still the same issue.

For clarity, when I ask Google Nest a question it answers fine, but when I ask it to do something ('show me the news', 'play 96fm radio', 'play led zeppelin radio on spotify' etc. - all of which worked fine for years) I get the sorry something went wrong etc. message.

It's bizarre as everything has worked fine for years and nothing has been changed in the last 12 months (no new devices, no internet or wifi changes etc.). Any advice would be very appreciated as now I can't use these devices the way I want to. 

Thanks.

[mejiacruz · Accepted solution]

Hi @Tim71 

That definitely sounds frustrating! It seems like something has changed with how your Google Nest devices are interacting with Google Assistant. Here are some troubleshooting steps you can try to get your voice commands for actions working again:

1. Update Google Home App and Nest Firmware:

• Ensure you have the latest version of the Google Home app installed on your phone or device. Updates often include bug fixes and performance improvements.
• Check if there are any firmware updates available for your Nest devices themselves. Google sometimes releases updates that can address Assistant-related issues.

2. Re-train Voice Match:

• While unlikely, re-training Google Assistant to recognize your voice might be helpful. This can sometimes fix issues with Assistant understanding your commands. Access this option through the Google Home app under your Nest device settings.

3. Check Google Assistant Settings:

• Verify that Google Assistant is still enabled on all your Nest devices. You can check and adjust these settings through the Google Home app under each device's settings.

4. Temporarily Disable Routines:

• If you have any routines set up that involve voice commands, try temporarily disabling them to see if they are conflicting with your manual commands. You can re-enable them after troubleshooting.

5. Factory Reset a Nest Device (Last Resort):

• As a last resort, consider factory resetting one of your Nest devices. This will erase all settings and data on the device. Be sure to back up any important information before proceeding. This step can sometimes clear up unexpected glitches. However, make sure to only reset one device at a time and see if the issue persists before resetting others.

Here's an additional thought:

• While you mentioned disabling IPv6 on your Google Wifi didn't work, some users have reported success with temporarily switching to a different DNS server (like OpenDNS or Google Public DNS) and then switching back. This might be worth investigating as a potential solution.

Hopefully, by following these steps, you'll be able to get your Google Nest devices and Google Assistant working seamlessly again. If it doesn't, please let me know so we can look into this further.

All the best,

Josh

[ozzie1p]

Same....

[mejiacruz · Accepted solution]

Hi @Tim71 

That definitely sounds frustrating! It seems like something has changed with how your Google Nest devices are interacting with Google Assistant. Here are some troubleshooting steps you can try to get your voice commands for actions working again:

1. Update Google Home App and Nest Firmware:

• Ensure you have the latest version of the Google Home app installed on your phone or device. Updates often include bug fixes and performance improvements.
• Check if there are any firmware updates available for your Nest devices themselves. Google sometimes releases updates that can address Assistant-related issues.

2. Re-train Voice Match:

• While unlikely, re-training Google Assistant to recognize your voice might be helpful. This can sometimes fix issues with Assistant understanding your commands. Access this option through the Google Home app under your Nest device settings.

3. Check Google Assistant Settings:

• Verify that Google Assistant is still enabled on all your Nest devices. You can check and adjust these settings through the Google Home app under each device's settings.

4. Temporarily Disable Routines:

• If you have any routines set up that involve voice commands, try temporarily disabling them to see if they are conflicting with your manual commands. You can re-enable them after troubleshooting.

5. Factory Reset a Nest Device (Last Resort):

• As a last resort, consider factory resetting one of your Nest devices. This will erase all settings and data on the device. Be sure to back up any important information before proceeding. This step can sometimes clear up unexpected glitches. However, make sure to only reset one device at a time and see if the issue persists before resetting others.

Here's an additional thought:

• While you mentioned disabling IPv6 on your Google Wifi didn't work, some users have reported success with temporarily switching to a different DNS server (like OpenDNS or Google Public DNS) and then switching back. This might be worth investigating as a potential solution.

Hopefully, by following these steps, you'll be able to get your Google Nest devices and Google Assistant working seamlessly again. If it doesn't, please let me know so we can look into this further.

All the best,

Josh

[Tim71]

Okay thanks very much, I'll give these a try and will let you know.

[pippip]

Hi Tim

I have a similar issue. Try this and let me know: Say one of your usual commands eg 'play 96fm radio' and after you get the 'sorry something went wrong etc' reply, say the same command again. Do this for four cycles of command/response.

When I do this it always works on the fourth attempt. This is clearly not a long term solution, but it is kinda curious

[Tim71]

Hi pippip- I tried for a total of 10 cycles and nothing 😞

I'm glad it works for you though!

[pippip]

Sorry that didn't work Tim. Maybe some good news though - after a week or so of this problem, my Home Mini seems to be working fine this morning responding to all commands first time, so maybe a fix is rolling out? Though I have had this on and off for a while so could be a false dawn.

In the meantime there was one other work around I used. My Mini Home is named 'bedroom speaker' and I have a Pixel phone. To my phone I could say "Hey Google stream Radio 4 on bedroom speaker" and, despite the mini home saying "there was a glitch.." , nonetheless it would actually start playing

[Tim71]

I'm glad for you that it seems to be working now. My issue has been around for just over a week.....fingers crossed.....soon....

[Tim71 · Accepted solution]

Okay resolved! While starting to look at suggestions from @mejiacruz I noticed that for some reason a whole bunch of my devices had been 'unassigned' from rooms and were sitting under a LOCAL DEVICES section, with each device status showing as LOADING and that would never change / update. I assigned each of the devices back to a room and now everything is working as normal. How bizarre!

[mejiacruz]

Hi @Tim71 

That's a great solution! Hopefully, it helps others facing the same situation. Thanks for letting us know. Feel free to post any future issues, and we'll be happy to assist.

Best regards,

Josh