![]() 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? This is to the point that today, if I was to spend 10 grand in a sound system for the house, I wouldn’t pick Sonos. But I feel the company is loosing it’s edge, and ramping up lawyer rather than engineers and designers, which is sad to see. I never said Google was better, but that doesn’t excuse Sonos from doing it. It’s unfortunate because I like Sonos, and have for years. I stick to what I said about Sonos participating to the patent wars and playing the bully. 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. 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. in the diagram below, if the leader fails another device can change itself to fullfill that role. Zigbee & Z-Wave) is auto repairing and no single point of failure and that devices can change their role if a specific device fails. The advantage that Thread has over existing connectivity approaches (e.g. ![]() Thread should make this integration easier and at a local, rather cloud level. I successfully use Home Assistant and Hubitat to connect to my Sonos system, either as a single or grouped devices now. Smart Home integration is already available via the Sonos API. 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) 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. Thread and Matter is about connectivity between Smart Home devices, I have seen nothing to indicate Audio Synchronisation would be included in this framework. ![]() 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. I’m not so sure that I agree with you here. I’m really happy to see Sonos on the CSA member list. Google joining the CSA/Matter/Thread standard means that this current stipulation/limitation that Google artificially forces (where you can’t have Alexa and GA on the same device) will be a thing of the past for any Matter devices. It’s designed for multiple controls, as the consumer sees fit. This means, specifically, that you can control things from the SmartThings app, use Alexa or GAssistant interchangeably for voice control, use HomeKit integrations or Siri Shortcuts at will. Apple/HomeKit, Samsung/SmartThings, IKEA/Tradfri, etc are all members and ALL devices that work with Matter will automatically work with each and every other Matter member company. I think this is the whole point of why we’re hoping Sonos adopts Matter - because Google/GAssistant, Amazon/Alexa. 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. . ![]() As far as playing with others, an streaming service is welcome to connect with Sonos.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |