Google Speaker Groups not working

[MsLevis]

I'm also having similar problems-  Have mix of Google audio cast and google enabled speakers across the house- most of the time casting doesn't work - If I go into the home app the groups are disappearing and re-appearing alot- I'll select a group that worked the day before and only one speaker plays - it still shows all devices playing-  I can try it a few times- go in and out of the google home app and try to force it that way- sometimes it works, sometimes it doesn't - all the firmware is up to date and it's just SOOOOO frustrating -  I even went and got a new google home speaker thinking maybe gen1 was causing an issue- nope still same problem-  COME ON GOOGLE!!!  

[StevieStevie]

Over a year later, and the exact same thing is still happening to us out here. Something is very very wrong.!!

[Houndquake]

Try removing your Chromecast that's connected to your TV. A user named Hardy did this and I did it and it works until I connect the Chromecast device

[OmaCoder]

No Chromecast device here. My TV has Google TV built in. 

[Houndquake]

So thats it if I remove the google tv and start it works every time.  I can add the tv once it starts and it works until I restart it

[jonathan1980]

This is really infuriating me. I managed to solve the problem and then the next time I connected, the issue returned. Spent an hour on the phone to Google trying to solve it, they couldnt do it and so they said they would get back to me within 2 days. After that they emailed me and said I need to speak to my Soundbar manufacturer. Basically they dont know and are washing their hands of it...

[DLSS]

I have a JBL link 10 and a JBL 9.1 soundbar. They used to work fine in a group set up. Now the soundbar does not cast. Removed all devices, uninstalled Google Home, unplugged Link10, reset soundbar, reinstalled Google Home. Soundbar will cast, put the Link10 into devices, put them in a group and only the Link10 will play when cast. Looking at the comments here it looks like a failed product with no resolution leaving so many with unfulfilled expectations, Google's integrity collapsed around the issue.

[ClausBP]

Hi DLSS,

I had similar issues with my JBL Soundbar.

I tried to assign a static IP address to on the router to the Soundbar - and that resolved the issue.
Good luck!
Claus

[kfer95]

I thought I was going crazy for awhile and thought it was just me figuring this crap out. I have spent 4 hours on the phone with google this week trying to get this to work. Every time they just blamed by Internet provider…. I just bought 5 Nest Minis to get my house covered for music playing… sale price was too good to be true it seems. What a waste of time and money for something that Amazon (and other smart home tech companies) seems to have no problem doing.  

[Phlynn]

Did SONOS tie up EVERY programming method to master the speaker groups and volume control?  It's nearly a year since mine have worked correctly.  One of the problems that is NOT a SONOS issue is the Google Home app can delete the speaker group but does not FORGET the speaker group.  Is this one of the problems? I have reset all of my speaker and chromecast enabled speakers and the old speaker groups still show up in parts of the app (although not in the speaker group area?!?) If any of you have been able to clear the history from your Home App, let me know so I can try that before we call the class action lawyers...  My theory is there is some programing priority/addressing situation interfering with the speaker groups after a change.  Mine worked great until I moved a mini and changed the speaker group.

[DiannaWorks]

I found the app remembered a deleted speaker group name-even though it wasn't showing up in the app-so I created a new group with a different name and it's working so far.

[TacoThunder]

How did you go about determining the app remembered a group, if it wasn't showing up in the app?

[DiannaWorks]

My first group name was Rock On. I deleted it and restarted the app. The group was gone. The new group I created was  RockOn, changed slightly by removing the space, because I didn't want to take a chance that there would be an issue with a duplicate name (my ESP, or logic after years of dealing with tech, etc.) When I told Google to play music on the new name RockOn, it came back with "Would you like me to use Rock On or RockOn?" both pronounced the same way.  Obviously it was using voice data instead of text data to remember the first entry Rock On, even though I had deleted it and it was no showing in the app. I then just deleted the new RockOn so that there were no groups listed in the app again. I created Rock Me instead and has been working since yesterday.

Were ya'll able to wrap your heads around all that rockin'?  Lol

Rock on! 

[MarceloL]

Hello,

Sharing my experience here and hopefully I will help people too. I was also deeply affected by the quality since the lawsuit. I had a mesh network (Google Wifi with 1 router and 3 points) and 78 devices connected.. including 18 nest mini, 4 next audio and 3 JBL  Linkview, 3 Cameras and smart lights. I noticed that after the lawsuit the network became overwhelming slow, even to load the app. I then realized that probably Sonos had a really smart way to reduce the traffic within the network and Google could not do it anymore. The only way I could fix it would be more a better mesh system. I was already too deep invested in google products to give up.. I decided to give my last try before starting to sell everything: I got the Nest Wifi Pro. Problem solved! I can finally play my groups without issues. I still cant run the whole house at the same time, but at least I can do the whole downstairs. Here and there it gets stuck, but all I do is stop, and stream again. So, all the network communication is being "bottle necked" by your router more likely. Sonos probably had a "light" way of doing it, and google is forced to do the "heavy" way. I hope this helps! and no.. I am not an infiltrated google marketing agent. Trust me, I do still have a love and hate relationship with Google. I also have a background in computer science.. so I know a little bit what I am talking about.  

[DiannaWorks]

Update on Speaker Group Fixes:

After 3 months of working now, it appears that just deleting the group, reserving IP addresses for each speaker in the router configuration, then setting them up with a brand new group name worked.  It also is working with band steering (both wifi names the same) or with just the 2.4GHz radio.

In order to set up the IP reservation in the router, I used the device information in the Home app to get the MAC ID and the current IP address of each speaker, both used to reserve the IP address for each speaker in the router configuration. If you are using a hamstringed ISP router and their app doesn't allow you to set static IP addresses (reservations) for your devices, you can try calling their tech support to see if they can do it, or you would need a separate router to accomplish this.

I hope this helps someone out there!

Previous post:

I tried setting up a speaker group for the first time this morning and ran into the same issues many folks faced- with none, just one, or some speakers working.  I tackled it to the ground and did get all the speakers working. 

Here's how- Put in layperson's terms as much as possible. 😉

1. I deleted the group.

2. I connected my phone to the 2.4 GHz wifi name. (See note at the end regarding 2.4 or 5 GHz.)

3. In the app I went to the setting for each speaker to made sure they all were on the same 2.4 Ghz wifi name as my phone (they were not.)

4. In the settings for those speakers that were not on the same wifi name, I deleted (forgot) the incorrect wifi name, unplugged the speaker, and then re-added the speaker using the correct wifi name.

5. Once all the speakers were on the same wifi name, I closed the Home app completely on my phone.  (Make sure it's closed and not just in the background.  Reboot phone if you're not sure.)

6. I reopened the app, then set up the group again with all the speakers, using a different group name--as it seems the old name was still existing in the Home app, even though I did not see it.  Trust me, it's whacky.

It was working fine after that. 

NOTE: I did not try connecting the speakers to the 5 GHz wifi.  These speakers do not require faster speeds, and there are still several devices out there that cannot connect or stay connected successfully to a 5GHz band.  Also, if you are using band steering (where both 2.4 and 5 GHz radios have the same name) that may also be the issue. I have mine split out for other IoT devices so not sure if this is your problem, but I've seen it many times in the past. The bands will probably need to be split out where one of the radios has a different name.  If you are using a cable modem/router combo from your cable company or your own router equipment you should have the app to be able to rename them.

GOOD LUCK! 🎵🎶

[OmaCoder]

Update us in 1 day on this. I bet it breaks. 

I use the wifi router provided by my ISP, Verizon, and their hardware does not give the option of splitting the networks into dual bands 👎

[DiannaWorks]

I would get a dual band router of my own and connect it to the modem in that case. If the modem has the router built in, put it in bridge mode so it doesn't interfere with your personal router.

[OmaCoder]

If I have to buy new hardware to fix this issue that Google caused, then I'm buying Sonos One and these are all going in the trash! 

[DiannaWorks]

So far so good after two days.

[NikolaiM]

Probably the first solution that makes sense to me. Keep us posted as many of these solutions only seem to work temporarily

[Mellamo]

FINALLY! Thank you!

After months of trying, I finally got my Soundbar (Harman Kardon) to work. I'm not sure which change did the trick, but it's possible that the combination of the following three steps solved the issue:

1. Reserved the Soundbar's IP address.
2. Updated the Soundbar's name in the router settings.
3. Created a new speaker group with a new name.

I had previously tried creating a new speaker group and name without success. It's worth noting that I'm using the speakers on a 5 GHz network with the same name as the 2.4 GHz network, but this didn't seem to be the issue in my case. 

I´m guessing the reservation made the trick,

Hopefully, this solution will continue to work without issues moving forward.

[DiannaWorks]

So glad that worked for you! I suspect the IP reservation was the trick. Even after a couple network outages and router reboots it is still working after 3 months. Yay!

[ChanceBacca]

My speaker group worked for the first time in a few months today.... But constantly played commercials telling me to upgrade to Premium... Which I have had since Day 1 of Google Music.

This is so infuriating. The first time it worked, and it still didn't work. Ffs

[Erik8]

Here’s my problem and how I fixed it:

When playing music on my speaker group, only one or two speakers would work at the same time. Sometimes you could hear the other speakers trying to connect or crackling. 
I tried resetting EVERYTHING multiple times with no success. 

Now that only one or two speakers are playing in a speaker group session, I unplug the speakers that aren’t playing and plug them back in while the speaker group is active. It has worked everytime so far. 

Still. Google Home speakers gets a 2/10 because of these issues. 

[DiannaWorks]

The only way I've been able to get my speaker group to work consistently was to delete the group, then assign a static IP address for each speaker device in my router, so that no matter what happens with the network they get their assigned IP every time. I then set up a new group with a different name. I have to issue the command to play as, "OK Google, play classic rock on Pandora on [group name]."  This has been consistently working as long as I give the command in that order and am succinct with it. 

[Jimmymacc]

Thanks for sharing this. Unfortunately, I have no idea how to assign a static IP address for each speaker device in my router. 

[DiannaWorks]

Go to the Google Home app to get the MAC ID and the current IP address of each speaker, this info is used to reserve the IP address for each speaker in the router static (aka Reserved) IP configuration. If you are using a router from your internet service provider I would call their tech support to help you through setting the static/reserved IPs. If you own your own router, there is probably a management app for it or google search for the user manual.  Hope that helps some anyway.

[BamaBillyP]

I have the latest chrome version too. My JBL (with Chromecast) is added to the "Home Speaker" group however it will not play while the others will. Any thoughts?

[BamaBillyP]

I have the latest chrome version too. My JBL (with Chromecast) is added to the "Home Speaker" group however it will not play while the others will. Any thoughts? 

[Phlynn]

Wish I did. Same with the chromcast enabled sony str dn1080. Plays when cast to it,  but will not play when part of a group. Google software issue???  

[Splash]

My Groups have not worked since -19 to my best recollection, and yes I have done plenty of talking with support and reseting/testing to no avail.

I´m just wondering if you are still ”working on the issue”?

[Brian_B]

I have 5 Google home devices in my home.  I reset 2 of them to attempt to get Groups working again.  Both units I reset now fail setup at the very last step.  I'm down to 3 working units and Groups is still non-functional.  Google's latest software update cost me almost $200 in now non-functional Google Home devices...  I no longer recommend Google Home to friends and family.

[Splash]

I hear you, the support was nice until the problem could not be solved and another support person wanted me to redo every reebot and report back the ”numbers on the back” for the fift time and so on untill the ticket got killed.

[Muddi]

Hey folks,

Sorry to hear about your experience when playing music in a speaker group. I'd like to dig deeper into this. How many speakers do you have in a group? What is the make and model of your router? How far are the devices from the router? Have you tried connecting some of your devices on a different network to check if your devices will have the same behavior?

Looking forward to your response.

Cheers,

Muddi

[Splash]

2 home Minis, one minin nest and one Google home.

I allso have 2 JBL playlist speakers that have previously worked with the system.

I have had 2 different wifi systems, one provided by the local provider it is made by ”Sagemcom” aparently it works for most users in Sweden for their Home systems.

Distance does not seem to help even when all units are in the same room.

It plays on a random speaker and at times a crackel can be heard on another speaker but not realy playing anything.

I did try a Covr Mesh system from D-link that was suposedly google home compatible but ther was no improvment and it realy got confused wit the nest trying to run it on the 5ghz at the same time as running the others on 2,4ghz(you can not turn of a chanel on this mesh system aparently).

Even whitout the nest and the JBL speakers this did not help the situation so I got rid of the Mesh system.

I have tried to reset both speakers and the network in all versions of the tests, with and whitout some speakers and in the same room and different rooms.

I have reset my app and removed other devices that may disturb the wifi such as lamps and similar.

The best result thus far has been two minis playing at the same time.

[Muddi]

Hi there,

Sorry for the delays. I appreciate everyone for sharing helpful steps. I agree that the network plays a significant role in experiencing issues while playing music on speaker groups. It is common for routers to be dual or tri-band without the option to restrict them to a single network. This can be the reason why some of your devices or speakers in the group may have disappeared or why the sound quality is poor.

Also, the strength of the network signal can also be a crucial factor. Please ensure that your device is positioned within 15-20 feet of your router, taking into account factors such as wall thickness and potential interference from other devices.

If rebooting your speakers and router did not resolve the issue, you may want to consider setting up a new speaker group with fewer speakers and ensuring they are positioned closer to your router. Another troubleshooting step you can try is setting up your devices on a different network to see if the issue persists.

Cheers,

Muddi

[MadPotter]

Muddi. I only have 2 speakers. Both are within 15-20 feet of my router. One is in the same room and one has a hollow core, internal wall between it and the router. I only have access to one network but that network is very strong. I have a smart TV as my only other device. Both nest minis were working well on a group for several months - until they stopped being a group. I have tried numerous times to delete the group and make a new group, and have done factory rests on both devices which has not fixed the issue. I have turned off and unplugged every device in the house, including the tv, minis and router. That made no difference. How many people are going to have access to more than one network?

It is so frustrsting as the reason I bought the minis was for them to act as a group. I'm treating them as separate speakers from now on and leaving  this discussion as it's quite obvious you guys have no idea as how to fix this.

[DeeSaR]

Over and over the same standard advicees that have no use at all, while other streaming systems like Sonos or Heos have no problems in the exact same wifi networks. Google has to fix their **bleep**ty firmware to fix this! But since almost a year no update for chromecast or nest devices. (except the recent models perhaps) 

[Muddi]

Hey MadPotter,

Have you tried setting up your speakers on a different router to check if you will have the same issue? Also, what is the make and model of your router?

@DeeSaR: Could you tell us more about your concern? How many speakers do you have?

Cheers,

Muddi

[Muddi]

Hi there,

It's been some time since this thread was updated. Does anyone here need assistance?

Cheers,

Muddi

[Hanky]

Do you enjoy feeding us lies Muddi? Just tell us the truth.. Google has disabled the functionality. Simples. 
Open the door for class actions.