Adopting Matter?

@Bliz I had to look this up: The Connectivity Standards Alliance Unveils Matter, Formerly Known as Project CHIP - Zigbee Alliance

I'd be interested in what you think Matter would bring to Sonos. 

I would like to see some integration with this as well. The only thing I don’t understand though is why does it have to be a HomePod Mini? I mean if you have an Apple TV, it’s effective a home hub with Siri integration already but it requires push to talk on the remote. Why not update it so that it can process Siri requests for any third party device? Be way better than having to buy a Apple speaker to play your non-Apple speaker…which makes no sense at all (so I agree with Sonos being upset about this). 

After sonos changed and forced Me to buy new devices. Which happen to work left efficient than the former ones I lost My  faith in sonos. The main victims are us. 

 @OlivR What would matter bring to you?

I’ve done some looking and yet to see how Matter would impact smart speakers in any way.  At least for now, it seems to be focused on setup and control of lights, plugs, cameras and more generic smart devices.  It’s not surprising, considering speakers tend to be a a bit more complex in functionality and control capabilities.  But the point being, I have no idea what anyone would expect Sonos to do about Matter at this point.

As stated, it’s not the idea that was patented, but the method. Google had the option of paying a license fee to Sonos, or developing a different method of volume control.  The chose to just take the feature away from their customers.  I think you could make a strong argument that if Sonos didn’t defend their IP, then the tech giants would just steal the tech and outprice any competition, using the funds they have from their other lines of business.  There’s not way Sonos or any other smaller business could survive in that sort of environment.

As far as playing with others, an streaming service is welcome to connect with Sonos.  Is that the case with Google’s smart speakers?  Sonos would love to allow Google and Amazon voice to work on the same smart speaker, but Google doesn’t allow it. 

You were never forced to buy new speakers.  Sonos reached a point where they could no longer keep their older products that had limited capabilities compatible with their new modern speakers, while still offering competitive products and features that customers are looking for. It’s strange how Google and the other tech giants are always in the news about how they are leveraging their massive size to control smaller companies and give themselves competitive advantage, yet some seem to think Sonos is the bully.

As for Matter: it’s brand new, so obviosuly there isn’t much using it now. But most major vendors have announced they’d join. As for what I’d like to be able to do, maybe direct my doorbell to Sonos speakers. Or my bed alarm. Automatically shift my phone’s music to my Sonos when I arrive home. Blast alarm noise when my camera detect a burglar. Or tell my dog to get off the couch remotely, etc, etc, etc. The list is so long.

Thanks so much for sharing this! It’s really good to see that Sonos has joined the CSA Alliance which will likely bring Matter support to their products. Hopefully, it can be done via an update rather than new products. 

I’m not so sure that I agree with you here.  The issue of Sonos not integrating with other multi room speakers is more to do with the propriety buffering/audio sync approach, rather than simple connectivity.  Thread and Matter is about connectivity between Smart Home devices, I have seen nothing to indicate Audio Synchronisation would be included in this framework.

That’s not to say that Sonos couldn’t use this framework to standardise the connection with local Audio Sources or perhaps to make SonosNet Thread compliant.  However, if I was a product manager within Sonos, this wouldn’t be at the top of my priority list and definitely not above local voice control (Snips)

Smart Home integration is already available via the Sonos API.  I successfully use Home Assistant and Hubitat to connect to my Sonos system, either as a single or grouped devices now.  Thread should make this integration easier and at a local, rather cloud level.  The advantage that Thread has over existing connectivity approaches (e.g. Zigbee & Z-Wave) is auto repairing and no single point of failure and that devices can change their role if a specific device fails.  e.g. in the diagram below, if the leader fails another device can change itself to fullfill that role.  From a Sonos perspective, the Roam and Zoom would take on the properties of ‘Sleepy end devices’ when using their battery as a power source, whilst using the properties of ‘End Devices’ when mains powered - as the other Sonos devices would do.  The question of using a Sonos mains device as a ‘Router’ or ‘Leader’ device, could be an option and could be a useful approach for reducing wi-fi interference in congested environments.

Sonos has continued it’s stated aim of releasing 2-3 new products or major functionality improvements per year - can you point out any reduction in new technology as a result of the litigation around patents? 

The reason for Sonos enforcing their patents isn’t about stopping others from using their technology per se, it’s about enforcing a licensing model that stops big tech players from offering to integrate to their technology and then stealing that USP for their own benefit and at no cost. There are lots of factual cases of bullying from Apple, Amazon and Google and using their market dominance to keep smaller companies from competing on a level playing field.  Sonos have invested a lot of time and money to get to a position where they are profitable and their shares listed.  Can you point to one factual case of Sonos bullying? I for one think it only just that if partners become aware of their technology by collaboratory projects, that they license rather than steal that technology.

All achievable now and set-up in my home - well apart from the dog part, my cat just ignores me, remotely or at home!

I think the difference here is that for instance the Hue hub will be Thread compliant rather than all Hue devices and that will adopt the role of a Thread Router and so extend the mesh network for other Matter/Thread devices to connect to.  Perhaps I should have stated the difference of a Thread Router  and a Network router in the diagram above - my mistake.

And…. its delayed, again. https://www.digitaltrends.com/home/matter-delayed-fall-2022/

I agree in theory, but a couple concerns about Sonos and Matter.   Yes, Sonos could adopt the Matter API for speakers, but they would still need to maintain their existing API.  So more space on the speakers...probably not a big deal.  But also their existing API, being Sonos specific, would have more control over Sonos features, not the subset of features that Amazon/Google/Apple want to support. It could actually result in 3rd party devices having less control over Sonos then they do now, if the drop support of Sonos API in favor of Matter API for speakers.

The other concern is that, people will assume that if two speaker brands have the matter certification, then they will play in sync together.  And this confusion will be blamed as Sonos misleading the public for a lot of consumers.  We know that’s going to happen because it already does with Alexa and Google Assistant integrations.  People assume that echos play with Sonos, or Google Nest (and whatever else) play with Sonos….and shame on Sonos for not making that easy code change happen!

It’s interesting that Sonos has dropped off the website listed earlier in this thread. Wonder what that means?