05-25-2022 01:27 PM
Google assistant at 11 am this morning refuses to execute verbal commands to turn on/off all smart bulbs, switches, and power strips. The response is always: sorry looks like there was a problem. This happens on every Google device I own that runs Google assistant. I own multiple minis, nest minis, home maxes, homes, pixels, nest audio, etc.
I can control these devices using the Google home app and the 3rd party software so the devices themselves function perfectly well.
Additionally, Google assistant properly executes verbal commands for other stuff on all the Google home products I own. Examples:
1 - It can tell me the current time. This shows internet connectivity.
2 - it can control my chromecast devices. Hey Google, pause kitchen chromecast works perfectly.
3 - I can cast audio to all the devices, play radio, play podcasts, and video using assistant commands.
Hey Google turn on the kitchen light.... Sorry there was a problem.
Seriously, what's up with this? Extremely frustrating! There is obviously a BUGi n Google assistant so don't ask me to do stupid stuff. Please help.
05-25-2022 01:35 PM
Also, this is completely unacceptable. It just shows that the Google assistant is not consumer ready.
05-25-2022 01:40 PM - edited 05-25-2022 01:46 PM
Yep, exact same problem. All my routines just failed "something went wrong" for every command in the routine no matter which device it's executed from, or from schedules. And spoken/typed commands as well, just like you.
Nothing has changed, hundreds of commands get executed in my house every day with no issue, this was the morning wake up routine, the evening goodnight routine executed flawlessly about 7 hours ago, so it's happen in that window.
Experience tells us this is nothing to do with a "bug" on your devices, it's always on the Google server side where the problem is, it happens far too regularly, it's just poor testing and governance by Google, letting idiot engineers tinker with things without testing properly first.
There's literally nothing you can do about it, you just have to wait until someone at Google notices these posts and starts looking into it.
The last time was with nest wifi about 3 weeks ago, and it took them 2 weeks to fix it. There's been many such instances with Google Home, similar symptoms, and it either gets fixed within a couple hours when someone goes "whoops" or will take several days for them to work it out.
05-25-2022 01:43 PM
First time it has happened to me. I saw a similar issue pop up on 2/16. Yes, definitely server side because it happens on every single device that runs Google assistant.
05-25-2022 02:16 PM
Hello, I have the same problem. I'm really starting to have serious doubt about smart homes and domotics if any problems or updates at Google can have disable many users houses. Maybe I'll have to look into something that can be self-hosted.
05-25-2022 03:02 PM
Is there a self hosted assistant?
05-25-2022 03:07 PM
I did reach out to Google. Very frustrating experience. I have a support ticket.
Hey Google, Please look into Google Assistant. You have a big BUG! I can't turn on/off the smart lights, power strips, bulbs or fans using verbal commands via Google assistant. Otherwise assistant functions normally.
Do you need to test your beta software before breaking the system? Please contact me. I will be happy to test it for you!!
05-25-2022 03:40 PM
As of 330 pm seems to work again for me.
05-25-2022 04:24 PM
Yep, fixed here too
06-08-2022 11:58 AM
Hi, everyone.
We did have a bug we identified with Google Assistant. By now things should be working well again, but if you're still having any issues, please let me know and we can look closer at your situation.
Thanks.
06-15-2022 01:19 PM
Hey, all.
Just a quick follow up to see if anyone here still needed some help on this or to see if it cleared up for you.
Thanks,
- Jeff
06-20-2022 11:09 AM
Hey, everyone.
It looks like we've slowed down here again. We'll be closing up the thread unless anyone else has any input or needs anything else. If so, just let me know and we can keep this open a bit longer.
Thanks,
- Jeff