02-05-2024 07:17 AM - edited 02-05-2024 12:55 PM
Last week had some internet connectivity issues, and every since,
"Hey Google play music on [speaker group]"
no longer works. It responds affirmatively, so that I expect it should work...then nothing.
The part NOT working is actually saying the command to play music on a speaker group.
I've restarted my router (multiple times). I've restarted all my devices (multiple times). Even tried creating new speaker group names (nope - didn't work either).
This is truly an aggravating experience, and is not the first time something like this has happened, but it seems to be happening more frequently, and in this case, for over a week now (previously it would resolve it magically after a day or two).
02-06-2024 05:25 AM
Hi MrZizzy,
Thanks for reaching out. Thanks for the details you shared. We've passed along your reports to our team, and they are aware of this behavior and investigating. Please keep an eye on this thread for further updates. Sorry for the inconvenience, and thanks for your patience.
Regards,
Juni
02-08-2024 01:36 PM - edited 02-08-2024 01:37 PM
I'm having the same problem...
I don't know if this will help but my smart displays show speaker groups that aren't visible in the Google Home app. there are 2 groups called "shadow" which I didn't create.
a couple times I moved the music to this group via the display and the music started playing on a speaker group that I could see.
these "shadow" groups used to also be visible on the old Google Home app.
02-08-2024 10:09 AM
My friend has the same problem at her house. Spent a few hours trying to fix it.
There's a speaker group called "pineapple" which has 2 Nest mini, a big nest speaker and a nest hub.
All devices have the default audio device set to the pineapple group. Default music provider set to YouTube premium
It was working a few weeks ago. All the following commands would work. On all devices :
Play music on pineapple
Play some music
Play [album /song name/ genre]
Now all devices respond with the same "playing [whatever you requested] on pineapple" and nothing plays.
However if I go to the nest hub, audio, and get it to start playing music on its self, that works. If manually select any other devices to play music to or even the speaker group pineapple, that also works.
It seems like it won't start playing the music on the group, but if you have it playing you can transfer it to the group. Via selecting it on the screen.
I've done all the steps of:
Still no luck...
02-10-2024 04:21 AM - edited 02-10-2024 04:22 AM
02-10-2024 03:17 PM
I have this issue as well. Speaker groups totally broken right now with YouTube Music.
02-11-2024 01:23 PM - edited 02-11-2024 01:24 PM
Also reporting this same problem. Oddly, my automations with music still play on the specified groups. Please work on this, Google! This is a major function of many people's systems!
02-12-2024 01:09 PM
Today "Hey Google, play music on [speaker group]" appears to be working again. Don't know what changed, but I'm glad it's fixed.
02-22-2024 08:28 AM
And this morning, it's back to doing the same thing again.
That this basic feature (using Assistant to cast music to a speaker group) has become so unreliable is extremely annoying, and makes we want to chuck all my Google/Nest speakers.
03-02-2024 07:10 AM
Just adding my name to the list of frustrated users having the same problem
03-03-2024 11:39 AM
About a week ago, I deleted one of my simpler speaker groups (it only had two speakers) and then made a new one with the same speakers. Miraculously I was able to control that group and then all the other groups started working again thereafter. I have still had occasional errors but so far they are still working. I have no clue if that actually did anything or I was just lucky. I really hope Google Home improves their poor service sometimes soon.
03-04-2024 07:57 AM
This seems to have sorted itself out now.
I was going to try the remove/add a group trick mentioned by @bloom.
I did restart all the Google home devices this morning after getting a "hold on while I try to connect to the internet" response so may be that helped.