Google Assistant Support

Thanks Ryan S.!!

As for the default speaker function, good to know that it is just not available yet. I saw how to do it under the google device "Default Music Speaker" setting but did not see my sonos speakers so I thought I did something wrong.

Off and running!!

Still love my Sonos ecosystem and while I'm still rather disappointed that it was a solid year and a half (more than that if from the time of my pre-order) until my SonosONE could do what I purchased it to do at the onset. Though, to be fair (and I must be) I initially was simply in the market for an additional Play:1 speaker at the time and the Sonos:ONE was the same price so I bought it instead.

At the end of the day I'm simply overjoyed to finally have Alexa out of my kitchen. Native Googe devices have their strengths, and Sonos devices have theirs. I'm just happy they can finally communicate at all. I'll continue using the app for most tasks anyhow. Thanks, Sonos, for finally following through on your promise. The wait was long.

As of today, we've officially rolled out support for Google Assistant on Sonos players, and control of Sonos devices using Google Home devices. For more details, check out our announcement post here, and some of our getting started and tips and tricks posts.Thats great Ryan!

Not be the guy at the party who shits all over the good news but I am curious why all the missing features? No calling.. no routines.. No voice match.. We were told the reason for the lengthy delays was that it was supposed to be perfect.. Is there an ETA for full support?

Not sure where you heard it was going to be perfect. I think the idea was that the features that were supported were as bug free as possible. And Ryan may say different, but Sonos is pretty consistent with avoiding given ETAs...to avoid the bad PR from missing dates and such. Sonos has not even officially said it's a feature they will eventually support.

@palpatine242 At the risk of over complicating the answer @Ryan S provided, the rules he's providing only apply to the Google/Sonos integration. With Alexa/Sonos integration you can utilize Alexa groups to better control where the music plays when you make a request to Alexa.

You can group a Sonos room with an echo in that room so that commands automatically play to that Sonos room. For example, you can say "Alexa, play X" to the echo in your kitchen and your kitchen Sonos speakers will play the music.



Coming from Alexa, I would agree with @melvimbe on this if you have not started down the google assistant path yet and that is important for you. The 2 main things I am missing are the "play x" command and it plays in the room local to the voice device and sonos device and playing my own music through google play to a sonos speaker.

Like anything else in this evolving world though, you start to get used to it and naturally work around until the feature gets released. Hopefully one or more of the 2 above is going to be released soon. Default room speaker with sonos and grouping in google home should probably come together if Google home recognizes sonos as a smart speaker within the app like other google home devices.

Now that the integration itself is out, does anyone know what the next features of this integration being looked at are? Or, confirmation that it has not stopped at this.

Same product, different country. So what?

We watch Game of Thrones at the same time...

Settings Sonos players as default speakers isn't available with Google Assistant at this time. This is just the beginning of our work with Google. You'll see new features and improvements as we continue to develop with them.

Well, it's encouraging this most important feature just maybe, possibly, might be available at some point. I'm not holding my breath, though.

Same product, different country. So what?

We watch Game of Thrones at the same time...


Apples and oranges really. I would imagine there are language issues, slight difference in the tech framework and legal requirements in each country.

I'm sure that doesn't do anything for your disappointment though, I'd hate to wait as well.

Great news. I eagerly await the service coming to Canada.

Ryan, could you please explain?
I thought you could make groups and play the same thing in multiple rooms at the same time.
For example, during a party, couldn't I say "OK Google, play "Playlist A" "Downstairs", where Downstairs is a collection of Sonos Amps that are linked?
Is this just an issue with using Google Assistant to do it, or is Sonos not able to do this at all?
Thanks!

At this time, Google Assistant needs to use a Google Play Music Premium account to play music on Sonos. I'll make sure to let the team know you're looking for this, but for now, the only free services supported are TuneIn and Pandora when using Google Assistant.This is just painful. Such a long wait for such an arbitrarily limited delivery.

I have a large library of music sitting in my computer, which has the Sonos Desktop Controller installed. This same collection is in the Google Cloud and available through Google Play Music. I also have an Amazon Music subscription. All those work well with the Sonos app, but I can't touch any of them with the Google Assistant-Sonos bridge. What a let-down. It's the kind of thing that makes you just want to give up. Had a bought a Google Home Max none of this would be happening.

I would bet that it's Google that is requiring a paid premium subscription, not Sonos. Sonos has nothing to gain by such a restriction. The same goes for your Amazon music subscription. You certainly can't access Amazon music through a Google Home Max.

I am a software engineer and I have written silly apps integrated with Google Assistant. All you need is an OAuth server, a server to handle the GA requests, and the will to do it. Two years and all we get is this. Man...

I don't think this is a technical reason, but business. I also don't know that it's accurate to compare your apps to the development and testing required for this integration.

None of that is to say that your frustration is invalid. I just don't know that blaming this on Sonos, or inferring that this is a failure on Sonos development part, is going to be very productive in getting the services and features that you want.

I live in Scotland. Thanks, anyway!

I don't think it was even "Early 2018"... I think it was just stated as being in 2018. Sonos' press release regarding Alexa and Google Assistant availability is here: Sonos unveils smart speaker with support for multiple voice services.

I agree that the decision is probably a business one, but I doubt Google has the blame here. Google is in a mad competition with Amazon, and wants as much hardware as possible integrated with the Google Assistant. Also, having the ability to integrate with users' music library works in favor of Google too, as it shows the potential of having equivalent access to an much larger library via the paid service. Besides, Sonos already has access to music libraries via the app, and that includes libraries shared from home computers via the desktop version of the Connector.

Regarding who has something to gain with the restriction, it probably has to do with who gets the data being collected. It would not surprise me if this is at the heart of the artificial limitation. All I can say is that, as a consumer, I am standing at the losing end. As much as I love the sound quality of my Play 5, it is no longer the only kid in the block. It hasn't been for some time. I would not consider purchasing another Sonos product until this is addressed appropriately.