Having trouble with Speaker groups? Read this first

[kelanfromgoogle]

Hi everyone, 

Thank you for continuing to notify us of the reliability issues you’re facing with your Speaker groups. I escalated these issues internally and the team is actively investigating a resolution. If you’re able, all feedback is appreciated! Please keep it coming by saying “OK Google, Send Feedback." Providing details, such as mentioning that the issue is with the "speaker group," is especially helpful.  As always, we appreciate your feedback and are working hard to alleviate the issues. 

Thank you for the patience,
Kelan

[kelanfromgoogle · Accepted solution]

Hey folks,

Thank you for your continued patience while our team has been working to address the issues with Speaker group functionality. I want to give you all an update and confirm that a fix was identified which will address a specific problem where some devices, when acting as the group leader, cause an issue with audio not playing on other speakers that are part of the same group. However, you may experience that the main (or leader) device will still play the media as expected.

The following devices will cause this behavior when used as the group leader:

- Chromecast with Google TV (4K)
- Chromecast with Google TV (HD)
- Google Home (Fixed as part of firmware update 3.73)
- Google Home/Nest Hub (first-generation)
- Google Home/Nest Mini (first-generation) (Fixed as part of firmware update 3.73)
- Nest Audio (Fixed as part of firmware update 3.73)
- Nest Hub (second-generation)
- Nest Hub Max
- Nest Mini (second-generation) (Fixed as part of firmware update 3.73)
- Nest Wifi Point
- Pixel Tablet
- A small percentage of third-party speakers were also affected

Note: the issue must be fixed on the device that is the leader of the group in order for the other devices in the group to start playing consistently

The fixes are specific to each device type, and are dependent on upcoming scheduled update rollouts. We will update this post as the fixes begin rolling out for each device so you can test your own speaker groups.

There may be some devices that take longer to receive the update so if you’re still encountering issues, you can try these temporary workarounds:

Cast directly: if you’re trying to play audio in multiple rooms, cast the audio directly to the individual speakers.

Restart your devices: If you’re having trouble with your speaker group and are unsure which device is the group leader, try restarting all devices that are part of the speaker group. This can often resolve the issues.

As always, we deeply appreciate the feedback and your patience. If you are still running into issues with Speaker groups, please leave a comment below with clear descriptions of the behavior you're encountering. This feedback will help the team further investigate and mitigate anything else that might be causing this feature to not work as intended.

Thanks again, we're working diligently to get everything back to how it should be.

Kelan

[morf]

I have just one final question, considering that google assistant and audio spakers are having huge problems for 6-8 months: Is google able to fix it? Is there any roadmap?

I just need yes or no! If no I'm going to sell everything and pass to Alexa...

[fixmy17]

Totally feel the frustration—been dealing with the same issues for months. If Google has a clear fix or roadmap, I’ll stick around. If not, Im seriously considering switching everything over to Alexa too fix my speaker

[RussdaFuss]

Yes, this phenomenon seems to be widespread and also known to Google. In any case, this process has already been described in other posts (... see the numerous threads that I have already referred to here). Yes, your observation seems to be accurate. The connection problem appears to be server-side. This is also the reason why measures such as deleting and re-creating speaker groups are completely pointless. The errors cannot be corrected by the user.

[scragin]

Get used to constant resets and repairing and regrouping and resetting and repairing and regrouping… Google doesn’t care.

[Thor9Stinson]

Been having an issue for a while. I have a hub and mini. Figured this is a good place to describe my issues to help find the root of it

Both work for an amount of time then seemingly stop connecting to my network. The hub shows the WiFi setup QR code and the mini just says "something went wrong" or " there was a glitch. In Google home they show offline.

My phone always works to controly smart devices and all other smart devices seem stable. I have GE Cync Smart bulbs and Samsung TVs. 

I have factory reset both devices a few times and they work for a bit then go back to non functional. If I unplug them for a minute then plug them back in, they reset and work for an amount of time again.

[kelanfromgoogle]

Hey all,

I appreciate the continued reports about Speaker groups not working as intended. We haven't forgotten and the team is still working to address the issues impacting Speaker groups. They've identified some potential root causes but are still working on a fix. In the meantime - please continue to leave comments here with clear descriptions of the behavior you're experiencing with Speaker groups. This feedback will help the team further investigate and mitigate anything else that might be causing this feature to not work as intended.

Thank you,
Kelan

[h20534]

Thank you for the update, Kelan. Can you share what some of the root causes they found were? It might help us in testing for you. Just last night, I went to cast music to a speaker group that included 4 nest minis, 1 Lenovo Smartclock 2, and a Nest Hub 2nd Gen. Everything but the Nest Hub 2nd Gen casted successfully - the Nest Hub 2nd Gen failed to join the group and cast music. If I casted music just to the Nest Hub 2nd Gen directly by itself, it worked fine. 

[kelanfromgoogle]

Hey @h20534, unfortunately I don't have specifics to share. Thank you for sharing more details though. I'll make sure the team is aware, but do you mind also sending feedback via the Nest Hub 2nd Gen? Just say "Hey Google, send feedback."

Thank you,
Kelan

[kq]

Kelan - I'm hoping this information can be of some help to the group working to correct this very old issue.

I've been unsuccessful in getting 'any type' of Speaker Group to work. I'm referring to using the same brand of devices as well as mixing & matching different ones. While Google Home allows me to place in the same group,  the groups simply do not work.

In my case, even when I have 2 of the same brand of speakers in a group, I can't even get those to work longer than a minute or two. When trying again, it's hopeless. One or the other speakers becomes disconnected and require being factory reset and once again, going through the entire setup process. 

Over a year ago, I purchased 2 Nest Audio speakers and to this day, these 2 devices do not work as intended.   I made this purchase because I was so frustrated with all the other devices. I did my research and actually thought just 2 Nest Audio speakers, meant to work together, would do as they were designed. I WAS WRONG!  I can get them to work on the first try for just a few minutes. After that, they cannot be placed in a working speaker group, paired or used via bluetooth

I made this decision after I was unable to get any of my other 28 devices w speakers, which include:

Google Mini,

Nest Mini,

Google Hub,

Nest Audio Hub Max,

Nest Max speaker,

Lenovo displays,

Lenovo displays w clock,

Nest Audio speakers

Google Mesh Wifi Points

Nest Mesh Wifi Points

ecobee Smart Thermostat's

JBL Link View

Google TV's

TVs with Google Assistant

AVRs compatible with Google Assistant

Soundbars w Google Assistant - and whatever I'm forgetting.

With this many devices failing to work as designed and none of them able to use a feature as simple as a Speaker Group, I agree with some of the other posts....this issue belongs to Google.  There is no way possible for all these different manufacturers to all have the exact same problem, pass testing, inspections, Etc.

I am mostly frustrated with Google always relying on paying customers to spend personal time & effort to report these type of major flaws.  How can the highly paid associated working in Quality Control, Quality Assurance and Testing actually be doing to miss these sorts of issues?

Bottom-line - I just care about the problems being corrected  - in a timely and efficient manner. Come on Google, when problem arise and you are notified take action and do it quickly.  Personally, I have so many open tickets (well, they were closed because solution was in the works) dating back over 2 years ago, I can't count them all.

I hope you can commitment to treat customers much better by using this issue as an example.

[rickjforbes]

Hi KQ, I'm afraid this issue will not get resolved, it is borderline disingenuous of the agents here to keep asking for feedback, as others have noted, this is rarely acted on and amounts to a mass abuse of our time.
It was Google who were responsible for breaking that functionality as they are in a patent dispute with SONOS about the control of speaker groups. It's a legal case with twists and turns and obviously large companies with loads of lawyers. However the user is the loser as Goggle still advertise these features despite not having settled the case or finding a way to develop the same feature without breach of a patent. Feel free to use your favourite search engine to get more details..depending up which PR team is briefing the journalist (hint, Google is a much bigger company) you may get a different spin on the story, but be in no doubt, Google know what the issue is (as it all worked before) and your feedback via the app doesn't do sod all other than remind Google how many users are annoyed.

[RussdaFuss]

In my opinion, this is a case for the European Commission for Consumer Protection.

[rickjforbes]

The interesting thing is that Google corporate's attitude to customer service and to some degree, device support can be inferred from consistent behaviour observations. I don't expect you to follow me, but I have had similar experiences of multiple pieces of hardware having a feature stop working, or function differently (and usually less well) following a software release. I have had Google lawyers (yes lawyers) trying to argue with me that the Google Assistant software is not integral to the Google Speakers. I have agents try to go through troubleshooting when an issue is known, well documented and not solved for a large number of users and they will lie about it. This is NOT to claim that a contact centre agent should be expected to know everything that is going on (they are 3rd party contractors anyway) it's the system that supports them when they can't find a solution. I have posted elsewhere about the repetitive to dead-end steps and I have demonstrably proven to myself that these steps are followed across a variety of product ranges, not just speakers.
It's a systemic problem. I have largely stayed off the forums (for posting) keeping my interactions via the direct support channels, but the method is the same.
Acknowledge, Apologise, Troubleshoot, Escalate, Disregard (rinse and repeat)

[Dastud]

EXACTLY! I have been preaching Googles unwillingness to address this and belive that they have no intention to. They know how to fix it but won't. 

[rickjforbes]

I am going to look through your posts @Dastud 
At the risk of crossing threads (but it is relevant) Google are not willing to fix ANYTHING in my experience..it's troubleshooting, then no connection to any kind of developer/bug prioritisation let alone visibility of that for the affected customer(s) I have SO many issues with Google products and I am a diligent, detailed reporter (i.e I have I.T bug solving and product delivery experience) who provides everything you need. As folk often say at work, if my username is on the bug, it's a real problem.
This post shows a good sample of all the issues I am having and I am not exaggerating when I say I have swopped close to a thousand emails with Google Support, I have DONE MY BIT..
how many problems solved? none, zip, zilch, nada, nothing.

List here:
https://www.googlenestcommunity.com/t5/Speakers-and-Displays/Another-Dead-Thread-False-Promises-No-r...

[marcolopes]

I can confirm that.

I debugged the POPPING BUG to all extent

Systematically reported findings

Opened tickets

Made videos

Made tech analysis!

At some point the support STOPPED responding or responded with total garbage or complete NONSENSE!

The last issue i had (the Spotify playlists were NOT played correctly with voice commands) was resolved in a timely manner BECAUSE Spotify was involved in the fix!!! https://www.googlenestcommunity.com/t5/Speakers-and-Displays/Google-Nest-Mini-play-wrong-songs-and-p...

[rickjforbes]

Hilarious..even the Google forum is mixing up data when I click on your profile https://www.googlenestcommunity.com/t5/user/viewprofilepage/user-id/464344 it shows MY subscriptions under the subscription tab, but YOUR replies in the replies tab.
(and yes Google I am using Chrome)

I will leave this one for the admins to direct appropriately

[rickjforbes]

I love the fact that Googlenestcommunity agents just left this one here unresponded

Your website is broken.. not just your speaker groups 🤗

[morf]

There is only 1 explanation...google support doesn t exist..and this is a fact that has to be considered when you are going to buy google products...that s it..

[CornishPaul]

I have a single broadband server (NOT Mesh) home network with seven Google speakers (various types) all connected to a group called "Home Group".  For four years Hey Google. Play <radio station> to the home group has played the channel throughout the house - exactly what I bought the speakers for.  Ideal to keep the dogs stress-free when we go out.

Today, and for the last week, Google says; "I don’t know, but I found these results on search".  This is on every speaker.  I can connect any one speaker to the radio but can no longer play throughout the home.  

I have provided the feedback requested but no hint of a solution.  😪

[RussdaFuss]

It's getting weirder every day.
For a few weeks now I have had to regularly restart my Google Home Speaker so that it can reconnect to the WiFi. My Nest Hub (1st Gen) no longer plays music in the speaker group. It is no longer possible to start music playback on the speaker group via voice command from any speaker because the only speaker group cannot be found. However, music can be played on the speaker group from a tablet or smartphone via TuneIn, Deezer or Spotify. However, playback can no longer be stopped using a voice command. Most of the time, the Google Home app on the smartphone or tablet does not recognize that music is already playing on the speaker group and the music cannot then be controlled via the app. The entire system is just a huge mess and no longer of any use! This is total rubbish!

[marcolopes]

Locking the thread of this ONGOING IMPORTANT UNRESOLVED PROBLEM WITHOUT ANY EXPLANATION is clear message from Google saying: WE JUST DON'T WANT TO, CAN'T, OR WON'T FIX THE ANNOYING POPPING SOUND WHEN STREAMING ALL TYPES OF AUDIO ON THE GOOGLE NEST MINI and a HUGE DISRESPECT for the clients!!! https://www.googlenestcommunity.com/t5/Speakers-and-Displays/Strange-popping-sound-in-my-nest-mini/m...

[RussdaFuss]

I absolutely agree with you. You can't express your contempt for your customers more clearly than that after you've already made money from selling the devices. Shame on you, Google!

[kelanfromgoogle]

Hey @marcolopes,

That thread was closed by mistake, it wasn't intentional and the team is still working on a fix. I've reopened the thread as future updates will be posted over there.

Thank you, and I'm sorry for the inconvenience.
Kelan

[rickjforbes]

I also had a post that is somewhat critical of Google immediately marked as SPAM

[kelanfromgoogle]

Hey @rickjforbes,

It appears the system inadvertently marked the post as spam, this could've happened for a number of reasons as many automated rules are in place to protect users in the community. It appears your post was restored, and a Community Specialist should be reaching out soon.

Thank you,
Kelan

[rickjforbes]

Hi @kelanfromgoogle 

I just wanted you to know that the post that I did get unmarked as SPAM and a colleague reached out to me has now sat unattended for over a week, I got a note, and I responded asking for further clarity and that has just been ignored over and over despite tagging them.
This experience mirrors the ignoring I get through the support channels (email in this case) that brought me here in the first place.
Google has a (hopefully unwritten) policy of simply ignoring customers with many many issues. 

here is the post which you will see is unresponded, as I have written elsewhere, it's as if Google are staying quiet and hoping I will just go away (or shut up) after spending thousands of pounds on your products, I just want them to work as advertised.
https://www.googlenestcommunity.com/t5/Speakers-and-Displays/Your-quot-Higher-Support-quot-quot-Engi...

[kelanfromgoogle]

Hey rickjforbes,

As mentioned previously, the Community Specialist escalated your case IDs with the team and it looks like they've been working with you toward resolution. Here in the Community we are limited in the support we provide, and I’m unable to provide further steps to resolve your cases.

To ensure a consistent support experience, please direct additional follow-ups to the support team members you’ve been working with via email. They’re equipped to give more specific updates regarding your case and answer any questions you might have.

Thank you,
Kelan

[M5DAL]

Over the last week, playing content to a speaker group only gets "I do not understand" . My usual command of Hey Google, stream xyz radio on "Sleep" (speaker group) used to work well, but no longer does. This seems to be a recurring issue. Yes, all resets and new group names tried, but nothing seems to fix. Any ideas, Google?

[Amishruss]

I used to recommend Google products, not anymore.

[Uncle-Googs]

I am so tired of fighting with these speakers and groups.  Just basic functionality.  Like a moron I just recently invested in 4 new nest audio devices.  Setup 2 - and its been complete garbage since.  I spend 45 minutes just trying to get a speaker group or pair just to show up on my cast list.  Then - it may play on a pair - but not a group.  My entire point of buying these was for groups.  And - for a quick 'play some tunes in the garage' and chill.  Instead I am left filled with rage as once again technology fails at the basics.  Speakers playing music - too much to ask these days.  Speaker have no problem reminding me that "by the way - the mic is off".  Right.  What a joke.

[Uncle-Googs]

Wanted to add.  If there is a problem with speaker groups - how about a banner at the top of the home app "Hey - we are experiencing problems...".  Nope.  Let your customers troubleshoot shoot the crap out of their home network.  Pairs.  Groups. Wifi.  Nest Wifi, Apps.  Cache.  Various settings.  Then I find this obscure post.  What a joke.  Own up - let your customers know what is going on... "Hey... We are having problems..." Would earn my respect more that this garbage.

[marcolopes]

LOL, Google doesn't even UPDATE their OWN pages (see: https://www.googlenestcommunity.com/t5/Speakers-and-Displays/Google-Nest-Mini-firmware-384934-NOT-li...), let alone publish a list of LIVE BUGS on the Google Home App! 😄

Currently there are a LOT of SEVERE BUGS on the Google Home ecosystem... SEVERE bugs...

[MittyOZ]

So some Feedback.  For ages now (like, maybe at least a year) our Hub which is part of a speaker group, does not play anything when you ask Google to play something through that group, you need to manually add it in.  Well, finally, this morning, we were sitting there listening to the radio, and randomly it just starts playing.  Running a few tests, it seems like the problem might finally be solved.  Knock me over with a feather.  

[MittyOZ]

Hold the phone:  It's broken AGAIN.  So it WAS working, but then I removed a different device (an original google home) from the speaker group.  The hub then refused to play anything when we asked to play something through the group.  Sorry to give everyone hope.  

[Amishruss]

There is no hope right now with Google getting their act together for speaker groups. Their "high" end support don't do anything. They're useless, so is the forum and Community Managers. They're pointless. Buy any smart speaker ecosystem at all besides Google at this point. Do NOT buy anymore Google/Nest speakers. Make sure you let everyone you know, not to buy their product. Do whatever you can to hit them in the bottom line. They still won't care.

[Uncle-Googs]

Maybe all the VPs at Google while enjoying their long Memorial Day weekend entertaining guests and family - listening to music - will try using their Nest speakers and see how terrible they are.  Oh - wait... They likely all use Sonos.

Its clear to me nobody at Google uses their own products.

Again - if there are problems - give us a heads up.  Do know how many things (hours) I went through trying to find the cause of this.  I bet more than Google Support.

Simple banner in the app "Hey - we are experiencing issues..." Is just common courtesy.

My work around sometimes is casting my audio from youtube app from home.  But that only works with pairs.  Also only about 1 out of 5 attempts works. "Device not compatible with casting... Blah blah blah".  So my Google Pixel, on home Google Wifi, using Google Youtube music paid service, on a Google Nest audio speaker... Is not compatible?  Joke.

[Uncle-Googs]

My problems.

Speaker groups do not show up reliably in the list of devices.  Some groups that actually work - will not show up in the list for 30- 40 minutes... If ever.  After 40 minutes - the moment I had to chill is gone... and I am just left frustrated that I wasted my time trying to play music.  If the group shows up - it has a 25% chance of actually working.  Some never have worked.  I have a few that are consistent that I never touch in fear of them breaking.  No consistent showing up - despite maybe being consistent playing.  Using youtube music whatever is playing on my phone (and then casted) will stop playing.  Play counter goes to zero.  Never moves.  I can adjust volume on the connected group - and see all the led lights move and groups volume adjustments "beep" like the group is indeed connected.  No music plays.

The same can be said for Pairs.  Sometimes they show up... Sometimes they dont.  Pairs however seem to play consistently *if* they show up.

I have noticed Pairs sometimes are VERY slow to load in the UI.  Like it will show the name of only one speaker in the pair.  Even though I know its a pair.  After 15-20 seconds of waiting then the link/button in home will finally show the Pair name.  Sometimes.

While searching for cast devices and pairs - devices come and go,  They show up.. shuffle order.  Go dark.  Disappear.  Come back.  Zero consistency.  I have clicked on a pair or group - only to have it disappear causing me to click on something else in error.

Google Wifi Gen1 - 3 pucks dispersed which should provide plenty of coverage.

Nest audios

Nest mini gen 2s

Various Rokus that support casting

Pixel 6a

Paid youtube music.

I have also noticed that some of my devices are not connecting to the optimal access point.  For example my main TV has a puck right next to it - yet will sitt on an AP/puck on the otherside of the house.  "Weak Signal" reported in the app.

A lot of my devices do this.  Makes me think that it could be related to the problem.

I sometimes think I should eliminate google wifi from the equation... I just dont have the time to gut my entire network.

Also - from home app - picking a pair - and trying to cast playing YouTube music app audio will give me a compatibility error 3 or 4 times in a row.  I vented above that everything at play here is a Google device.  So a compatibility error is infuriating.  Then the 3rd, 4th, or 5th time is will magically work.

I have been hobbling along like this for months.

[HansWSchulze]

I have yet to see consumer mesh work properly, or a mix of devices pretending to be a mesh.  Gave up and bought a clone of a high end router, ax class, reaches everywhere in 3500 sqft house.

Then explain why Nest Display casting audio to Shield 2019 in the same room has been choppy for a year.  Shield is on hub connected directly to wifi router at 1gbps, 2m away. Or casting to Shield and Google devices, the Shield wakes up TV and the music pauses until I restart it.

Sonos casting works fine, everywhere to everywhere.  Sometimes their stuff gets stuck, but not hard to get working again.  No issues with LG or Samsung or TCL devices.

[Vrekasht]

Latest issue with speaker groups I've run into: Very specifically, when switching from Pixel Buds back to the speaker group with Spotify, the speaker group will no longer connect (individual speakers will connect, however) and will show as paused no matter what in the Google Home app.

Deleting/renaming the speaker group does NOT fix it.

Rebooting individual speakers does not fix it either.

To get it working again I have to do the following:

1. Delete the speaker group.

2. Reboot each individual speaker.

3. Not only disconnect but fully unpair the pixel buds.

4. Restart the whole phone (Pixel 7 Pro).

5. Re-create the speaker group.

It'll work again until I want to do something silly like use the earbuds.

Edit to add: If I go into the individual "paused" speakers they all show that they're actively casting audio when they aren't; telling them to stop casting unpauses them but doesn't fix the issue.

[marcolopes]

Exactly what i have to do when i have problems with my STERO PAIRS!!!

It's MASOQUISTIC!!!