Sonos Voice versus Google Assistant Era 100

Google set the rules that keep Google Assistant from being used on Era, and other third party speakers. Perhaps you may want to send your concerns to Google?
 

Sonos isn’t a big enough company to fight Google, they just don’t have the money or clout, in my opinion. 

You could try Alexa, but unfortunately you won’t be able to create speaker groups, cause unfortunately  that feature doesn’t work on the Eras yet

My understanding is that Google have changed the way Assistant has to be implemented on the Eras, which requires different coding, and Sonos are saying they want Google to go back to their old coding method. It’s rather bizarre that I have a Beam (Gen 2) that has Google Assistant and the two Eras which are designed to work with it have Sonos Voice. Trust me when I say it really is that bad, and it is within Sonos’ gift to code a better voice assistant or go to Google. They’d save a lot of time if they did the latter.

Additionally, Spotify does not support Sonos Voice. Spotify have no plans to work with Sonos Voice as they see it as niche. It’s crazy - all would be resolved by coding Google Assistant. FYI I think Google are an awful company, but their voice assistant, unfortunately, is the best on the market in my view. I’ve just got rid of my HomePods because Siri was so unreliable.

Yes it does, the only aspect missing (at the moment) for Era’s, is the ‘enabling’/‘controlling’ of an Alexa Group. It does not stop Alexa grouping/ungrouping Era speakers with other Sonos Rooms. Just set any other Alexa product as the group ‘enabling’ device and set the Era’s/other rooms in the 3rd speaker section of the Alexa group and set the ‘playback option’ to ‘Always’.

 I believe there’s more to it that this.  My understanding that Google changed the API that makes it more difficult to use, more resource intensive and taking more developer time to maintain.  The reason existing GA interfaces still work is probably because Google allows the old interface on existing products, but not on any new products.  It’s a way to allow for transitioning to the new API that causes less pain.  I would not be surprised if Google turns off the old API at some point in the future.

I have Sonos Voice, and I don’t find it to be bad.  To be fair though, I rarely make requests to play specific artists or tracks.  That’s partially because I found it not to be too reliable on Alexa and developed the habit.  The other reason is that I just don’t really think of artist/tracks off the top of my head like that, and browsing through a screen helps me ‘zero in’ on what I want to hear.  I mostly use voice control to initiate station playback or to control grouping.

Where are you coming up with this information about Spotify?  Have you seen any articles saying that Spotify doesn’t like SVC, or you just making an assumption?  

Sonos Voice I’m afraid isn’t good. It cannot play ambient sounds at night, it cannot take requests where I’d like to play music on all speakers, it cannot request music stations that GA can - it’s not doing what the competitors are doing.

I appreciate the API is different, and might need to be maintained more, but as a consumer is that my issue or Sonos’?

The thread about Spotify currently not supporting Sonos Voice is here: https://community.spotify.com/t5/Live-Ideas/Sonos-Partnership-Spotify-and-Sonos-Voice-Control-native/idi-p/5520363

You cannot use Sonos Voice at this time to request a song in Spotify, and considering the Beam Gen 2 can with GA, it’s not on is it? Why defend it? I’ve spent a lot of money on the Beam and Eras!

“Ambient sounds” is that a radio station or some sort of GA skill.  SVC can play music on all your Sonos speakers.  It can also change groups on the fly without restarting a stream.  There are something GA can do better for sure, but SVC is also locally processed only and designed just for the Sonos system.

Odd way of looking at it.  Sonos made the decision not to support and you have the choose to buy Sonos or buy a different product that does support GA, if that’s important to you.  It’s not anyone’s ‘issue’ per se.

I’m aware that Spotify isn’t supported currently, but you additionally made the claim that Spotify chooses not to support the integration and sees it as niche.  I’m asking you to back up the claim.  Asking for you to support claims is not defending Sonos.  I genuinely want to know if it’s reall info or your just blowing smoke. Pretty sure it’s the latter, but trying to give you the benefit of the doubt.

As far as why Beam Gen 2 has GA and the Era speakers do not, that’s already been answered.  Take it or leave it.

I have no idea why you feel so passionate about defending a substandard product, but each to their own. Ultimately I’m writing feedback to improve the product, your stance is take it or leave it. Don’t change it. Really odd position, you don’t have to love a product unconditionally, you can constructively criticise it. Have I said anything unfair or untrue about Sonos Voice? How do you expect a product to improve if you don’t give feedback?

I’m not sure what your point is about Spotify - I have read online their support agents write there isn’t enough users to invest money on supporting it = niche. It’s hardly a controversial statement, just the truth. The fact is Spotify have not wrote coding for the Sonos Voice API 6 months after release.

As I had a Beam 2 I had no idea GA wasn’t supported on Eras. I can assure you after looking online I wasn’t the only one who found this out. The review sites criticise this too and mark it down on this basis.

If I were as unhappy as you, the last thing I would be doing is posting on a support forum wishing they change.  I’d sell them on the Bay or donate them and be done with it.  Life is too short to wait for the makers of “substandard products” to bring them up to my standards, and certainly too short to launch a silly support forum campaign.