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...
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)...
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.
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...
Sonos One speakers are designed to provide great sound in a small package and integrate a microphone so you can talk to Alexa... all while looking good. The speakers, as I mentioned in yesterday's entry, are pretty great for sound. The microphone array for Alexa, on the other hand, could use some improvement. Apparently things were much worse when the One was first released, and they've since improved it with software updates. My hope is that they continue to work on this, because it's irritating how ambient noise can obliterate any Alexa commands you might make. My Sonos One in the living room sits on my media center... exactly where my Echo used to sit. With Echo, I could have the television blasting and Alexa would still respond to commands easily. With One, that's not the case. Both my living room and kitchen speakers will hear me say "Alexa..." (I get that "beep" from both) but, if the television is on, half the time it's the kitchen speaker which is the One to reply. This sucks because I can't hear it with the television on.
Yes, this is a testament to just how good the microphones are at picking up when I ask for Alexa from across the house, but their ability to recognize where I'm at when I'm saying it is really poor. Sure I can disable the microphone on the kitchen One so there's no confusion, but that kind of defeats the purpose of having a One in my kitchen in the first place.
Another issue which may or may not be tied to the design of the Sonos One... there seems to be more lag between when I say an Alexa command and when the speaker will respond and act on that command. It seems faster on Echo and Echo Dot. No idea what that's about, because you'd think Alexa is Alexa no matter where she is. Perhaps Amazon prioritizes commands from the units they sell over third party devices? No clue.
And then there's Alexa not responding to Sonos control commands on the Sonos One speakers, but that's such a complex topic that I'm saving it for my final installment tomorrow.
When it comes to Alexa on Sonos One, the microphone problem and lag are annoying, but it's just the tip of the iceberg. If you listen to Audible audiobooks with Alexa, you can't do it on the Sonos One. At least not yet. If you use Alexa for drop-in (intercom between your Alexa units) or calling, they're not supported on a Sonos One. At least not yet. Some Alexa skills also don't work (like Sleep Sounds). At least not yet. Maybe it's Amazon that's refusing to allow these things, I have no idea. But it's scary to think how the Alexa features people rely on might one day disappear from their Sonos One speakers if Amazon decides to axe them for one reason or another.
As for the physical appearance of the Sonos One speakers, they're very pretty. Also... the design of the touch controls and indicators on the top of the unit are wonderfully unobtrusive. Rendered all in black, it's much better-looking than the multi-toned PLAY:1. Real thought went into making this a gorgeous piece of hardware.
Unless you want to mount it to a wall.
Then you have to add a bunch of shit which destroys the sleek lines of the product.
Because there's no screw mount on the back, all the screw-mount hardware used to hang the very similar Sonos PLAY:1 on a wall won't work. You have to use a specialized mount which has stupid restraining wires to hold on to the unit (something which seems ugly, flawed, and unsafe). I have run this over and over and over in my head trying to figure out why the screw mount was omitted, but keep coming up empty. This is profoundly stupid. Your options for mounting hardware goes from dozens to one or two, and neither are that great (the Midlite cable-conceal mount is not compatible, which is the one I wanted to use, but can't). Perhaps this was a ploy by Sonos to get kickback money? Maybe Sonos hates their customers and wants everybody replacing their PLAY:1 speakers with One speakers to have to buy all new mounts? Maybe they think the Sonos One is too pretty, so they want you to have to ugly it up if you mount it on a wall? I mean, come on... just look at this janky crap hanging off the back...
That stupid wire will never stay straight, as you can see if you look close. Maybe Sonos just hates OCD types like me? And it takes two wires... TOP AND BOTTOM to restrain the damn thing...
This idiotic shit is rage-inducing. Why even bother designing such a pretty speaker if you have to fuck it up to mount it on a wall?
Regardless of how ugly or stupid, I'm sure more mounts are coming. Hopefully somebody can find a more creative way of solving this which doesn't require a big ass wires and massively ugly clips hanging off the back.
Another design decision which may be problematic... you cannot create a stereo pair between a Sonos One and a Sonos PLAY:1, or any other Sonos product other than another Sonos One. While this may be a bummer to some, I don't know that I'd want a stereo pairing between two speakers that aren't identical anyway. I'm OCD like that. What Sonos should do is come out with a Sonos One "Lite" speaker which looks the same as a Sonos One, but doesn't have Alexa in it. That way it would be cheaper (no Amazon licensing fees or additional microphone hardware) and a much better option for those wanting to create a stereo pair. It's not like you need two Alexas in the same space (you'd probably turn one of the microphones off anyway), so this seems like a no-brainer.
But it's hard to give much credit to Sonos for brains when they screwed up the mounting so heinously bad.
And tomorrow we wrap all this up on an even more sour note, so be sure to tune in for that.
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...
There was never any question that I would be giving up some sound quality when I went with Sonos One over Apple HomePod. Apple made sure that having awesome sound was a priority over everything else and, if that was my primary reason for getting a smart speaker, I would have bought one despite it all. But my priority was smart home integration with Alexa, so Sonos it was.
Though I'm hardly an audiophile, I do like having quality audio, and was hoping that Sonos with their years of experience would deliver. This was not guaranteed. Yes, they regularly get good reviews for their equipment, but I'm buying the smallest speakers they offer. And yet... since my home is not that big and I have cats (which means I never blast the stereo at full volume), I was optimistic.
Turns out the Sonos One is plenty enough speaker for me. Despite their diminutive size in comparison to other offerings, the One had no problem filling my home with rich, vibrant sound. I ended up putting one in the living room and one in my kitchen at opposite ends of my home, then grouping them so that they both play the same thing. I can control their volume independently, or control the overall proportional volume for both at the same time, which is handy...
My dining room is closer to the kitchen than the living room, so I have the volume there a bit weaker. When I sit at the dining room table, it's a sweet spot where I am hearing sound equally from both, which is a very cool effect. People can dine and have a conversation while being enveloped in soft music for atmosphere. This... this is the true promise of Sonos. Everywhere sound that can be fine-tuned to whatever effect you want.
Obviously the problem with having only one speaker per room is no stereo sound, because pairing them for stereo in separate rooms is a bit schizophrenic. For my music, I'm not that bothered. If I end up going full-on Sonos with my television and A/V setup, then I'd have to add more speakers to get to Dolby 5:1 anyway (which is as far as Sonos can currently go... no DTS, PCM, DD+, or Dolby Atmos for you!). That being said, there is something which Sonos provides to get the best sound possible from their speakers no matter how many you have or where they're located. They call it "Trueplay" speaker tuning technology, and it's essentially an app on your smartphone that you walk around with to measure your room acoustics so your speaker can alter its output to give the best sound...
In my living room, Trueplay didn't make much different. The speaker seemed to sound the same before and after I applied it. But for my kitchen? Sound quality noticeably improved. Sonos is not blowing smoke here, there was an immediately noticeable improvement. This is a pretty great thing, even though it takes an extra couple minutes of setup to get there (Apple HomePod apparently does this automatically and constantly on its own... no need to walk around with your phone).
In the reviews I poured over before purchasing my pair of One speakers, I heard "lack of bass" mentioned more than once. This is puzzling to me, because I was thrilled to be getting so much bass out of such a small speaker. No, it's not earth-shaking (Sonos sells a subwoofer for that), but it's actually much better than I was lead to believe. Would I like more punch when I fire up All We Need by Odesza? Sure. That thumping bassline is meant to be something you feel. But I'm certainly not feeling deprived by the bass I'm getting, which is very good.
The Sonos One sound lives in the mid-range, which is pretty stellar. And while the highs are nice and bright, they can hit brassy spots that sound harsh to my ear. This is most notable when playing a song like There Must Be An Angel by Eurythmics (my go-to track for testing speakers). It handles the hook beautifully with the angelic backing vocals, but then fumbles a bit with the harmonica solo at the end. Still, it's never so bad that I'm wincing at it, and 98% of the time I'm not noticing anything but beautifully delivered acoustics that surprise me every time I fire up my speakers.
The upshot of all this is that I have no complaints about Sonos One sound quality for what I'm currently wanting to do with it. If I end up wanting to go further, I can absolutely do that buy purchasing more Sonos pieces. And that's the beauty of the system... it's just so darn extensible and configurable.
For a price, of course.
I bought two Sonos One speakers bundled at a $350 limited time price (now since expired), which is $175 each (regular $199). If sound quality is your primary concern, that kind of money can get you a larger speaker with significantly better sound quality. Sure, they won't be wireless, nor will thy have Sonos streaming capabilities or have Alexa built-in... and you'll need an amp to power them... but all that will mean nothing to a true audiophile. So know where your money is going before you plunk down for Sonos, which can get very expensive very quickly for chasing down the best sound the company offers (their largest PLAY:5 speaker, for example, is $500... so $1000 for stereo). Their 5:1 setup would require a PLAYBAR for my TV ($700) and SUB subwoofer ($700) and use my two One's as the back channels ($1750 total investment... $1800 now that the One is no longer on sale). This is a bit absurd when that kind of money can get you a Dolby Atmos-capable amp with some nice speakers for a better home-theater experience. But I'd probably go the Sonos route anyway because I love what it gets me in features and control. Maybe if I had a larger, more acoustic environment... like a custom home theater... my thinking would change. But since I don't, Sonos feels like a better fit, even for the price.
Hefty though it may be.
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...
Yesterday I talked about deciding to bypass Apple's HomePod and leap into Sonos. Now that they've released the "Sonos One" with Amazon Alexa built-in, it was a better fit for me and my Alexa-centric lifestyle.
Alas, since Alexa has no way of accessing my iTunes Match library, my best option for having music she can control is to subscribe to "Amazon Music Unlimited" at $79 a year (that price reflects a $20 discount because I'm an Amazon Prime member). Since I can now discontinue iTunes match at $25 a year, that's a net increase of $54 annually over what I was already paying. I'm not happy about it, but there's nothing else I can do to get what I want. Something tells me that Amazon and Apple are not going to cooperate on getting things integrated, and I'm too enamored with Alexa to contemplate her not having control of my music the way she has control over everything else in my life.
Amazon Music Unlimited is nice, for what it is, but it's hardly perfect...
That being said, there are some things I love about Amazon Music Unlimited too...
So I dunno. If I have to pay for a streaming music service, I'd rather it be Apple because that's where my music purchases and videos come from. But since Apple was way late to the personal assistant game and has nothing to even touch what Alexa can do, that's not going to happen. So long as I am tied to Alexa for everything, Amazon is where I am going to be. Maybe one day Apple will give up on their laughably bad HomeKit crap and buy out INSTEON or something that drags me back into the fold, but right now I'm done. It's all Alexa all the time until something better comes along. And something tells me Amazon ain't going to allow something better to come along. Alexa is getting better and more capable every day.
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. Because there's so much to unpack, I'm breaking it up into five parts.
And now on with the show...
Once Apple announced their HomePod, I started saving for one. "It's like having Alexa for my music!" I thought. And since I'm a Certified Apple Whore, how could I not buy some cool new tech from Apple?
Then at the last minute I changed my mind and went with their competition: the new Sonos One with Alexa. Yes, yes... I know. But I actually put some thought into this...
There's a caveat, of course. Neither Alexa nor Sonos cannot access iTunes Match, which is where the entirety of my music collection resides.
That's a huge deal.
I can download all my music from iTunes and put it on my local NAS drive, which Sonos can access, but Alexa can't control it there. The only thing Alexa can control is Amazon Music Unlimted, Spotify, Pandora, iHeartRadio and TuneIn. The cheapest option is Amazon at $79 a year, but that still won't allow me to access a goodly chunk of my more esoteric songs. I couldn't say "Alexa, play Love on Your Back by Thompson Twins because the B-side to Love on Your Side doesn't exist in Amazon Music Unlimited. It used to be that Amazon allowed you to upload your music to their servers for $25 a year, but they discontinued that which is such a bummer. Music options for Sonos are a somewhat long and complex discussion, so let's save that for tomorrow.
Obviously going the Sonos route has some down-sides when it comes to listening to my music, but the down-sides for HomePod are catastrophic. HomePod isn't even an option unless I have nothing better to do with $350.
And so now I'm here...
And now that I am here, I honestly don't know if it's a place I want to be.
There are plusses and minuses to Sonos that I need to unpack and see if the system makes sense for me. Fortunately, I've got 30 days to decide. I'm not anticipating returning them, mind you, but I do want to live with them for more than a week to see if I can live with the minuses.
So far, however, the plusses are frickin' amazing.
Last night as I was loading my car trunk with some cardboard to recycle, I saw a gallon of milk sitting there. I must have missed it when I was unloading groceries four days ago. Don't ask me how.
I was going to dump it down the drain... but it's been cold out, it's non-fat, and milk is expensive, yo... so I decided to pop it in the refrigerator and give it a shot.
If you never hear from me again, please inform the coroner that it was the milk that did me in.
Now that they've gotten older, I am very fortunate that my cats sleep through the night. They crash downstairs around 7:30-8:00, then follow me up to my room when I retire for the evening. If I turn off the lights to go to sleep, they'll climb on the bed with me. If I leave lights on and work in bed, they'll climb into the kitty beds at the foot of my bed and fall asleep there.
Sounds great, right? Except when I have to get up and pee in the middle of the night. Jake and Jenny think this means I want to play. So when I go back to bed instead of playing with them, they are very, very unhappy I woke them up for nothing.
If you never hear from me again, please notify the police I was eaten by my cats.
Amazon's "Echo" device (called "Alexa") is tied in with my home automation system and controls everything. I can't remember the last time I physically touched a light switch in my home... I just ask Alexa to turn on/off the light I need. At first it was only when I had my hands full. But then... well...
The coolest thing about Alexa is that she can activate "scene" controls and perform numerous functions with a single command. For example... when I say "Alexa, Turn on Night Mode", the following happens:
That kind of thing.
It's absolutely awesome, and I love having Alexa around. She's become so ingrained in my life that when the internet goes down (which Alexa requires to operate) I kind of forget how everything works. When you never use light switches, your head kind of fogs over what to do when you want the lights on. It takes me a minute. In another couple of years, I probably won't even know where my light switches are.
If you never hear from me again, it's either because I'm trapped in the dark in my house... or trapped on the toilet screaming for Alexa to wipe my ass because she does everything else around here and I've forgotten how. Please call 9-1-1.
The mindsets of foreign countries... particularly those in Asia... are radically different from ours. Relations between nations there can be based on cultural differences few Westerners could possibly understand... or on events that happened hundreds of years before the USA even existed. To not understand these circumstances when building foreign policy is to invite disaster. Even the slightest misstep can set events into motion which could have catastrophic consequences. Because of this, it is beyond critical that our leaders be well-advised by people deep into foreign mindsets before making even the smallest decision.
Unless you are President-Elect Trump. Then you just do whatever the fuck you want, no matter how idiotic or dangerous the consequences.
India and Pakistan are nuclear powers. They are also blood enemies. Keeping them from unleashing mass destruction upon each other is a balancing act that has the entire world on edge. So when Trump has a terrifyingly ill-advised phone call with Prime Minister Nawaz Sharif as if he's running Pakistan when, in fact, it's the military that is actually in control of the country... you can see how this could cause a frightening shift in the structure of Pakistan, which could ultimately lead to problems with India. You do not want that.
Then you have Trump accepting a call from the president of Taiwan... which is tantamount to the United States officially recognizing Taiwan's independence from China... which is something that will send China through the fucking roof. This one phone call could set into motion events that have China taking military action against Taiwan in order to make it clear they consider Taiwan to be a part of China. Not to mention making The United States an enemy of China. Which, needless to say, is also a nuclear power. All because Trump wants to build a hotel in Taiwan (or whatever), and he has no fucking clue what in the hell he is doing.
Trump's actions are rushing nuclear powers to conflict in a way he'll never comprehend, and he's not even in office yet.
Can you imagine what happens when he's actually president?
Trump doesn't seem to want to listen to anybody. He acts like a petulant child. He doesn't seem to give a shit what the consequences are for his actions. He is willfully ignorant when it comes to foreign relations and is seriously clueless as to how critical it is not to be making the mistakes he's been making. He is very obviously putting his personal interests ahead of this country. He is inflaming foreign nations with nuclear weapons.
And I'm not saying that to be funny or dramatic.
If you never hear from earth again, it's because President Trump destroyed the planet. Please tell any alien life with time travel capabilities to go back into the past and abort this abomination before he's even born.
Atom Entries Feed Comments Feed
