Add me to the list of affected customers, bought two sonos one gen2s three days ago contacted google yesterday they said to talk to sonos come here and see this... and of course I threw the boxes away so returning them will probably be a pain.
I am in the same boat. Google Assistant works flawlessly with my new Sonos Beam with the exception of Google Play Music playback. I have tried what others have suggested, starting again from scratch with an all account removal and unlinking of services but without success.
What a frustration. I am tempted to switch to Amazon Alexa and give it a try but I have been a Google Play Music user since it launched in beta. I am reluctant to make the change.
I don’t get it. How can a bug be tagged to specific google accounts? So now I have to keep creating new google accounts whenever something like that happens again?
Email just received from Sonos, cancelling my service call tomorrow because they know they can't fix it:
Hi Jack,
I was reviewing your case prior to our call tomorrow and it looks like you are one of a handful of customers suffering from a bug that is affecting specific accounts with Google Voice Assistant and Sonos.
The unfortunate news it that currently the only work around is to use a different gmail account to get Google Voice working on the system but we have opened up the bug with Google and are providing them information around the affected customers as we encounter them. I'm unsure of an ETA of the fix yet, but we will keep on top of this with them to ensure we obtain one because we know that using another Google account is not an ideal solution.
This means that there isn't anything we can really do for this with our call tomorrow, but I've added information from your ticket to our bug report and will keep your ticket in my court as we keep on this issue. Soon as I hear an update from the Google team, and if there is anything they want us to have our users try I'll reach back out to you.
Thank you,
Brandon G
Sonos Escalations Team
Brandon, i think you really need to have a list of people with this problem and see how big of an issue it is. I’m holding off buying more sonos products until this is resolved.
Having the same problem. Looking fwd to a fix.
Suddenly started working for me today. Guess they fixed it? Or did I just get lucky?
Suddenly started working for me as well today.
Yep, started working for me as well. Only problem now is both my phone and the Sonos try to respond at the same time, but I’m about to upgrade my phone which I’m hoping will resolve that.
Glad to see forward progress!
I just discovered this is now working for me as well. Very happy...but it would have been nice to have a heads up.
I was also experiencing this same issue and through a lot of trial and error discovered the fix.
This issue is caused by Google Home assigning your Sonos items to individual rooms within the Home app and as such if any of these items ever get re-added it creates an internal assignment error. In order to correct this problem do the following:
- Open the Sonos app > go to Settings and select Services > click on Google Assistant > select the Sonos device that isn't working > click on remove the Google Assistant.
- Download the Google Home app from the app store > follow the instructions to add your Sonos speaker to your home group > once added assign a room name and location > after the Sonos speaker is added close the app.
- Open the Sonos app again > add Google Assistant under the speaker with the issue and link your Sonos account to Google again.
This fix worked for me after about two hours of frustration. I hope it helps.
How did everyone get this to work? Ive tried all the workarounds and got nowhere ?
I’m also experiencing this issue. Can work around it by removing all connections between google home and Sonos, and then re-configuring it. It will then work for about a day, before entering broken state again.
Any permanent solution to this problem??
Thanks! 
(SOLVED) Update from my end: After contacting Sonos support they told me that my system had "no access to cloud services”, based on my supplie diagnostics. Unfortunately they couldnt tell me anything else, nor help me troubleshoot further as a reslt of this.
After digging around in my router settings, and contacthing my ISP (recently moved, and got a new fiber agreement), I found that I was not assigned any public IPv4 address. I only had an internnal IPv4 due to address shortage. I made them remedy this, and got one assigned.
After this was fixed, all my issues were fixed. Google assistant now working flawlessly on Sonos One, and all GA can play Spotify / TuneIn on all sonos speakers. '
What I find strange is that the GA service on Sonos One and getting GA to play on sonos worked “sometimes” witouth a public address. If this is indeed a requirement (apparently is, when Google services tries to access my local sonos network from the cloud) I would expect it to NEVER work when no public address is available.. But somehow it worked for a few minutes every time I set it up, and sometimes once or twice the day after..
TLDR: Apparently you need a public IPv4 address for GA to communicate with Sonos, even though Sonos itself and GA itself does not require such.
Specifying the service name also does not solve this for me. Same behavior on Google Play, Spotify, Pandora, TuneIn and regardless of what the default music service is set to.
Did anyone figure out what the problem was?
Sonos support on Twitter DM have asked for all my hardware details and apparently someone will be in touch tomorrow to schedule a call.
I am experiencing the same issue. Super frustrating. Has anyone fixed this yet?
I am having the exact same problem for two(ish) weeks now, since the first Google Assistant outage some time ago...
I went through everything with $support_person, and the problem is, that they can't even see me calling for music playback in any logs they might have. There's definitely a bigger problem here somewhere, and I really hope for a fix, like, soon! 😮
Hi everyone, there were some playback issues over the long weekend, but I believe for now they should be resolved.
If you're still having trouble, I'd suggest that you contact the team live to troubleshoot, after you've already done the basics.
This issue is not fixed... It hasn't been working for many people for many weeks.
From the troubleshooting I did with tier-2 support, this problem seems to be related to specific Google accounts, and there is an ongoing open issue with Google about this.
Also posted about here:
https://en.community.sonos.com/google-assistant-and-sonos-229109/sonos-not-working-on-google-assistant-6829259
Any updates here? Emailing with support, but I am not expecting much here... JoeYan, do you have any more details?
Im having the same issues with the GA and music play back. I either get the error that the speaker isn't available right now or the content cannot be found. Sonos want to schedule a phonecall with me at some point. If we figure out a fix I will post it here.
I've been having the same issue for months. Sonos support has not told me that this is an issue that they are aware of, quite the opposite actually. They have referred me to Google support....and then Google says I need to talk to Sonos. Bahhhh!
If I configure everything with a new google account it all works fine. This isn't a solution naturally but it does point to an issue with the Google account itself.
Damn. That's not a great fix for me at all. I have a phonecall booked with the Sonos team tomorrow evening. The main fault I have at the mo is the GA telling me that the speaker isn't available right now if I voice command music or radio playback. But when that fault isn't happening then every other song I request I get the error this content isn't available. If I have to use a different Google account then to be honest the speaker will be returned as that's not a fix for me.
