Has anyone got an official answer from SONOS about AMAZON ECHO Integration?

I want to buy a full Sonos system for my house, but won't until there is an official integration with Alexa/Echo. @Sonos - My $ are waiting here for you...

So you think they're going to rush it out the door for you? ROFL.

Well they're obviously working on it, since it is a feature in high demand by consumers. I personally don't like the Echo, it only supports limited music streaming options and I find it does a poor job understanding and responding to commands. But hey they've sold millions of them so what do I know :8.

Why would Amazon want to integrate their wireless streaming speaker with a competing wireless streaming speaker?

Looks like they have at least played with it for fun : http://mattwel.ch/voice-control-for-the-sonos-with-an-echo/

What do you mean by "they"? That link is to a independent programmer's page, not anything to do with Sonos, nor Amazon.

I actually got it to work with this: https://github.com/rgraciano/echo-sonos

Pretty freakin amazing every time!!!

I've been hammering away at this for several days now and can't get past this head scratching point. All commands work via the API (browser) and certain voice commands like favorites, pause, what's playing. Unfortunately volume control and play commands don't work. Then things like next/skip are strange - next doesn't work but skip does. Again, API works great but voice commands is weird.

Really want to get this to work because the wife would use Sonos if it meant telling Alexa what to do, otherwise, forget it (go figure).

boykster: "The key is understanding the connection between the syntax in the intent schema section, the utterances section (both on alexa skills), and the code in the index.js file that gets loaded to Lambda."

And this is where I'm struggling. I found a helpful 38 min video on the AWS website but being new to this, I think I'm going to have to watch it several times before I really grasp the concepts. Since the Echo/Sonos thing seems to be so cutting edge, there isn't a whole lot out there so searching for real world intent schemas, sample utterances, and index.js files is a challenge (reference material).

Thank you for the input and I'll keep grinding away.

Would really like to get this solution working, but I'm totally at a loss when trying to follow the directions. Any chance someone could come up with a tutorial or help a newbie out?

I worked things through and got it working, then dug in and got it to do even more. The key is understanding the connection between the syntax in the intent schema section, the utterances section (both on alexa skills), and the code in the index.js file that gets loaded to Lambda.

If you want to do something new, you will need to define a new intent, new utterances, and make sure the code in the intents.js file does what you need. I've added:

custom slot type for "play " - favorite needs to be all lower case and one word in sonos faves and in the custom slot type value

whats playing (similar to original author)
what's next (same as above, but next song)
play favorite - see above
list favorites - reads off what valid favorites there are
shuffle on/off
repeat on/off

Hi all,

I have read through this and unfortunately if the system does not work flawlessly my wife will despise it. It took me enough just to talk her into getting the system to begin with, I was about to dive into Sonos further and add to the ecosystem but as mentioned above I think the Echo is so good that if Sonos is not planning an elegant solution I will need to look at a new home system....

Sonos, either work with Amazon or develop your own interface that is as strong as Amazon's (but that is a tall order)

Would this eventually be released as an app?

Well you could release desktop app and one for the mobile.

You've answered why you would like it, but that wasn't the question. Amazon wants to sell Echoes. Why would it waste all the intellectual property it has invested in Echo by allowing it to be used to sell Sonos speakers instead of Echoes?

Cross-posting from another thread as I see this one has Sonos staff listening:

I created an account simply to upvote and comment here: this is a huge miss on Sonos' part that a full year after Echo is GA and has dozens of other partnerships that Sonos remains out of the ecosystem. It's great someone has done some creative hackery on github to link the two, but this needs to be officially supported by Sonos.

I own an Echo. I don't own Sonos today, but I'd very much like to own Sonos. It looks like a great system and leaps and bounds ahead of your competition in this space (for now). However, a Sonos that doesn't communicate with my Echo is useless to me. Smartphone apps are nice and all - but I just TALK to my Echo and it plays music I like. Investing in a pricey Sonos system that can't tie into this feature is a step backwards.

Short story: Integrate with Echo, earn an eager customer. Don't integrate with Echo, or come out instead with some standalone lock-in Sonos-only Echo competitor, and my money will go to your first competitor that offers Echo integration.

--
and ps. to rmgraci: nice work! Tempted to buy a Sonos based on your awesome work, but they really need to integrate this into the core product. I'd be fine if they paid you some money and officially supported your work, but I won't invest an an expensive Sonos system where they might make a change that breaks your "user-supported customization" and breaks Echo support. Been burned by that too many times by other companies.

Sonos, here's your chance to partner with Amazon and add the ever-growing Echo customer base as your loyal customers too. If you don't do it, someone else will. Let's see what you can do!