Welcome to Sonos Week here at Blogography! Each day I will be talking about my leap to the Sonos platform for "smart speakers" and how it integrates with Amazon's Alexa assistant. If you haven't read past entries in Sonos Week, you'll probably want to start at the beginning by clicking here.

And now on with the show...

I'm just going to start this entry off by saying "I love my new Sonos One speakers." Because after you read the problems I've been dealing with, you may begin to wonder.

The whole point of the new "One" model over everything else Sonos has ever released is the Amazon Alexa integration. Without Alexa, the Play One would be just a prettier version of the PLAY:1 that they already have. With that in mind, you'd think that a company with the stellar reputation that Sonos has would make damn sure that the Alexa integration was rock solid and dead simple.

Yeah, you would think.

In reality? Not so much. This comes down to two issues...

1. The Alexa Sonos Skill.
2. Ducking.

In order to get Alexa to do things on top of the basic functionality that's built-in, you have to add app extensions to her "brain in the cloud" which are called "skills." Want to play Jeopardy with Alexa every night? You have to add the Jeopardy Skill. Want to control your Sonos speakers by talking to Alexa? You need the Sonos Skill. There are hundreds of skills to do all kinds of things, and part of the magic of Alexa is using these skills to customize your Alexa experience. Lord only knows I have. Alexa is such a huge part of my life that I find myself asking her to do things even when she's not around. I'm not entirely sure what half of the wall switches in my home do because I haven't used them in years. If I want to turn on a light, I either program it to happen automatically... or ask Alexa to do it.

The issue being that whatever you're wanting Alexa to do is only as good as the skill she uses to do it.

When it comes to Sonos, the skill is really rough.

On the third day of owning my Sonos One speakers, I woke up to an Alexa alarm to feed the cats... my path being lit by lights Alexa turns on. I then get to the kitchen and have Alexa play songs from Depeche Mode's 101 on my Sonos One while I'm dishing up cat food. Then I get myself cleaned up and head to work for the day. When I get home I ask Alexa to play songs by Roxette while I'm unloading my stuff and cleaning up the house. She dutifully complies and The Look starts blasting through my home.

I ask Alexa to turn the volume down and she won't.

I ask Alexa to stop playing music and she ignores me.

I ask Alexa to skip this song and she doesn't know what I'm talking about.

Eventually I'm screaming "ALEXA, STOP!!!" and she cooly asks me what I'd like to listen to while Roxette continues to blare. I yell "OPEN THE POD BAY DOORS, ALEXA!" but the joke is lost on her.

After the song is over, Alexa goes quiet. As a test, I ask her to play songs by Matt & Kim, but she ignores me. Anything else I ask her to do... tell me the time... turn on some lights... read my notifications... she will do. But she categorically refuses to act on commands to control my Sonos speakers. It's as if she has forgotten that my Sonos speakers even exist.

Just to make sure she's hearing me, I look through my request history on the Alexa app. Yep, she heard me alright. Apparently Alexa has gone brain dead when it comes to Sonos, so it's off to the Sonos "Community" forums to find out if other people are having this problem. Turns out they are. This is not an isolated incident or Alexa disobedience... this is the Sonos Skill being wonky as fuck.

What follows is hours of disabling/re-enabling skills... logging-out/logging-in to accounts... deleting/reinstalling apps... forgetting/discovering devices... renaming devices... factory resetting speakers... the list goes on and on and on. Nothing seems to work, so I try everything. Eventually I accidentally get things running again. I say "accidentally" because I have no idea which thing... combination of things... or order I did things... ended up being what got Sonos working with Alexa again. Not a frickin' clue.

And she seems to be working correctly now, though a couple times I've asked her to pause my music and when I ask her to resume, she sends the command to my television instead of my Sonos, at which point I'm back to disabling/re-learning skills.

Obviously, Sonos and/or Amazon has some work to do.

For the sake of anybody coming to this page via Google search because they are having the same problem I was and are ready to smash their Sonos speakers with a hammer, I have three tips (in addition to all the stuff you'll find out there already)...

1. The thing that seemed to make the biggest difference was forgetting all my devices under "Smart Home" in the Alexa app, renaming my speakers to something entirely unused ("Galley" instead of "Kitchen" and "Lounge" instead of "Living Room" in my case) then rediscovering everything.
2. When you connect an Amazon Music Unlimted account to Sonos, you're asked to name it. Sometimes (especially if you use different names) you end up linked to more than one account. If you have the individual plan, you'll get caught in a loop of "Amazon Music Unlimited is already playing on another device. Pause that device to play on this one." This drove me insane because I only have one device using my account, but it ended up that it was being used twice. At this point, delete ALL Amazon Music accounts from the Sonos app and then re-add it.
3. The minute things even start to go wrong, don't keep hammering away at it to try and get it to work through brute force of will. It never works. Start with disabling/re-learning the Sonos skill immediately and you might get lucky that this is all it takes. The longer I spent avoiding disabling/re-learning, the more crazy crap I ended up having to do to get things working again.

This whole ordeal was frustrating to the point of rage for me, and I'm still not quite sure what in the hell is going on. I can only hope that it all gets figured out... soon... so that I don't burst a blood vessel or something.

And now for "ducking"...

Yesterday I mentioned that Alexa on Sonos One has trouble figuring out where you are located so that the correct speaker is talking to you. I ask it a question in the living room and it responds in the kitchen... that kind of thing. But there was something I left out.

"Ducking" is when Alexa will drop the volume of whatever she is playing through her speakers so she can hear your commands. And while it sounds logical, it's actually stupid, stupid, STUPID!

Alexa has a microphone optimized to pick your voice out of other sounds in the room. As an example... when I have the television blaring, I can still talk to the Alexa device sitting next to it. Alexa can't control my television volume, so she does her best to hear around it. And it works... mostly... unless the volume is so loud that she can't make out what I'm saying.

But when your music or your television is plugged into your Sonos system, Alexa can control its volume. And she will lower it each and every time you ask her to do something. And that's not the worst part. If I say "Alexa, next!" to skip a song that's playing, she starts ducking the volume seconds after I'm done speaking... which means she is ducking for nothing!

And it gets better!

Alexa doesn't just duck the volume on the speaker you're talking to... she ducks the volume on ALL Sonos speakers in your whole house.

This is a major bug which I'm told Sonos is working with Amazon to fix.

I sure as hell hope so, because it's a seriously demented flaw that will be especially insane when you have several people living in your home and they are all talking to Alexa in different rooms. Jimmy asks Alexa what time it is in his bedroom on the second floor and the speaker you're listening to in the basement drops in volume? What sense does that even make? Did nobody at Sonos notice this when they were designing the One speaker? NOBODY?!? Good Lord. There's stupid... and then there's... whatever this is. This issue should have been resolved with Amazon long before the product was released to market.

Assuming Sonos makes it so that ducking only happens with the speakers in the room where somebody is talking to Alexa, that will be a big improvement... but I still won't be happy. I want to be able to turn ducking off completely. I never needed it when Alexa didn't have control over my speakers, and I don't need it now that she does. Maybe some people like it or need it, but those of us who don't should have the option of turning it off. Until we do, integrating Alexa with Sonos is kinda stupid.

And so...

The only option for Sonos to work the way it's supposed to and not duck your volume is to disable Alexa from having anything to do with your Sonos speakers. Which is insane for somebody like me who purchased the speakers specifically for their Alexa integration.

Ultimately Sonos One is a very cool speaker with some amazing features which was rushed to market to beat out Apple's HomePod. Unfortunately the thing that makes the Sonos One so compelling... having Alexa integration... is not done very well. Which is a real shame, because this is something which could potentially take Alexa to another level.

I'd say "This is the end of SONOS Week at Blogography... thanks for reading!," but I cannot. Tune in tomorrow to find out why.