To strengthen overall security and meet evolving regulatory expectations (including those in the EU), we’ve introduced enhanced user authentication controls. These new features are optional and are detailed below. This update is focused on improving system security and includes some features many of you have been asking for.
To access the new settings, go to your Account Settings and open Privacy & Security. You’ll find a new section called Connection Security, where you can configure the following three options:
The new settings you have are:
Authentication: This setting applies to third-party integrations that use Sonos cloud services and Local Area Network (LAN) APIs. When enabled, it requires those integrations to authenticate before connecting. This may also affect services like Direct Control (e.g., music apps with direct playback to Sonos devices) and some features using AirPlay.
UPnP (Universal Plug and Play): This setting controls support for the older UPnP protocol, which is no longer actively maintained. Disabling it may prevent older apps and devices - such as the original desktop controller or some third-party apps - from connecting, especially if they rely on UPnP instead of newer protocols like MUSE.
Guest access: This option controls whether devices to the same WiFi network as your Sonos system can control playback, volume, and group configuration without needing admin-level access. When disabled, only authenticated or authorized users can control the system.
The default setting of these settings are:
Authentication is off by default
UPNP is on by default
Guest Access is on by default
Enabling/Disabling them may affect how certain third-party apps or legacy components interact with your system. We’re making you aware of them so you can choose to enable them if you’re looking to apply additional security controls and are not relying on features such as UPnP.
Also, we are discontinuing support for the legacy WEP (Wired Equivalent Privacy) standard, which is recognized as outdated and insecure. If your network is still using WEP, we recommend updating your router settings or upgrading to a modern router. While this change may require a one-time adjustment, it aligns with current security best practices and helps maintain a more secure wireless environment.
After the update, Sonos speakers won’t connect to WEP-secured networks anymore. To avoid any connection issues, make sure your WiFi uses a modern encryption standard like WPA2 and/or WPA3.
As usual, the new features will be rolled out gradually over the coming weeks to help ensure stability and performance. We’ll post another update once the release has been completed.
Page 2 / 3
I hadn't really thought about this until now, maybe I have always associated players with system.
Reading the sonos.com website there are also some inconsistencies:
Refers to ‘System’, but when you click ‘manually check for updates’ link it refers to ‘speakers’ in the title, but ‘system’ in the content. And when you click ‘release notes’ on the ‘update your Sonos speakers’ it links to the ‘release notes’ for ‘Sonos app updates’, the people that write the web content know what they mean, but from a consistency point of view, it could be confusing if unfamiliar with the terminology.
The only ones debating this on semantics are the ones that should know better. Nobody else appears confused in any way.
I am also a little confused why others maybe confused. 😀
I’m confused as well as to why there’s still a conversation about a question raised 1 day ago and was satisfactorily answered by @Rhonny 18 hours ago (CST)?
I’m confused as well as to why there’s still a conversation about a question raised 1 day ago and was satisfactorily answered 18 hours ago (CST)?
More questions have been asked, just like your post above, that has lead to a discussion about the semantics of Sonos terminology, possibly with a delay due to time zone difference(s).
I’m confused as well as to why there’s still a conversation about a question raised 1 day ago and was satisfactorily answered 18 hours ago (CST)?
More questions have been asked, just like your post above, that has lead to a discussion about the semantics of Sonos terminology, possibly with a delay due to time zone difference(s).
Actually, my last post (question ) was rhetorical 😂
As a third party developer who is directly affected by these changes, I have a couple of questions:
What is the “LAN API” (evidently different to UPnP)? I see no mention of it on the developer site. I am guessing its the Cloud API but sent to local devices, is that right?
What has MUSE got to do with Sonos, exactly?
Thanks
My iOS app is version 80.23.9. The new release is 85.0-66270. When I try and update the system I’m told my system is up to date. I’m confused.
My iOS app is version 80.23.9. The new release is 85.0-66270. When I try and update the system I’m told my system is up to date. I’m confused.
Your system most likely updated automatically if you have that option enabled in the app.
It is set to update automatically. But of the new release was available on July 8 why wasn’t it updated?
It is set to update automatically. But of the new release was available on July 8 why wasn’t it updated?
Your app and system are on the latest versions.
Your Sonos account needs to be flagged for the new features mentioned in this thread.
Once that is the case, you will be able to see the new features in the app you have.
So more clearcut software from SONOS? Why was I sent an email announcing the new release, without any mention of automatic update settings?
PS I worked in software development for years. Either something is ready for release or it’s not. This is nothing more than a glorified beta test.
So more clearcut software from SONOS? Why was I sent an email announcing the new release, without any mention of automatic update settings?
The automatic update settings have been there for years. I guess it would be helpful to mention this every type updates are released, but it does not seem like it’s something Sonos should be faulted for.
PS I worked in software development for years. Either something is ready for release or it’s not. This is nothing more than a glorified beta test.
My understanding is that Sonos is releasing the feature in waves like this partially because the app stores aren’t built to release a new app to the whole world all at one time, and so that Sonos support can better handle any questions and issues that may come up when users start using a new feature. My company doesn’t release software in waves like this either, but there certainly is a spike in support questions when there are new features. I can’t say that letting customers wait on hold longer, or hiring temporary workers who know little about the product, are better options.
Then why send an email blast like this? SONOS is clearly better at audio hardware development than software management. After all of their recent troubles you would think they would have a better understanding of release, and user, management.
Not mentioning the way these new features are released is indeed strange - this can lead to disappointment with customers who think the features are released with the update and then find out they do not.
In my opinion an update is not “ready for release or (…) not”. You can’t test for everything, so a measured roll out can make a company halt the process if something unexpected goes wrong. To me this means Sonos has at least learned something form the debacle that was the (roll out of) the new app.
Then why send an email blast like this? SONOS is clearly better at audio hardware development than software management. After all of their recent troubles you would think they would have a better understanding of release, and user, management.
I don’t get your issue here. All the things Sonos highlighted in this email are live in your app and on your system. If your system has updated automatically, great. You’re good to go.
If you’re yet to see the security settings highlighted in this forum thread, so are a lot of people. It’s not exactly a feature to get excited about and will be activated in due course.
The announcement concludes
As usual, the new features will be rolled out gradually over the coming weeks to help ensure stability and performance. We’ll post another update once the release has been completed.
I’ve not seen a second notification so I conclude that not everyone has the features added to their system yet. But they did try to set expectations.
Then why send an email blast like this? SONOS is clearly better at audio hardware development than software management. After all of their recent troubles you would think they would have a better understanding of release, and user, management.
I completely understand your point here. The new features mentioned in that email were introduced in the software update from June 10th, not the latest software update from July 8th. I was surprised to receive that email given the stated features had been available for over a month. Email would have been accurate if it had been sent in a timely manner, but clearly that wasn’t the case.
Edit: The Arc Ultra speech enhancement by AI was from May, so even older.
The release notes link at the bottom of the email brings you to this page. The version name is clearly different from the release name that my system says is current. This is not how application management works.
Further, the reference to automatic updates on the release notes page suggests that, if my app is set to auto update, my app will in fact be automatically updated to the new release. It does not say that if I want the new release I should turn auto update off.
Beneath the “Current System Version” is a list of 10 previous versions. All of these versions post date the version my system says is current. There is no mention for any of these releases that they apply to specific products only. Why is my “current” version 11 versions behind?
This is not how application management is done.
@kwarendorf - I think you are confusing app version (80.23.9) and system version (85.0-66270). They are two different things.
Why are the 2 different? The email clearly references software updates. This implies changes to the way the user interacts with SONOS. For 10 years I worked on systems that supported thousands of users in more than 500 locations at a major investment firm. I spent 15 years working on a system that managed a multi trillion dollar loan portfolio. In neither case was there a divergence between system and application.
Part of my responsibilities in both jobs was the writing of myriad technical documents. Writing related to systems needs to be precise. Communications from SONOS is not. It is vague, incomplete and confusing. Following the recent fiasco SONOS declared that they were going to fix things. In my opinion, from a communication perspective, they have not.
Kyle
PS Don’t get me wrong. I love SONOS. I have various speakers throughout my home. Their software management is another matter.
For 10 years I worked on systems that supported thousands of users in more than 500 locations at a major investment firm. I spent 15 years working on a system that managed a multi trillion dollar loan portfolio. In neither case was there a divergence between system and application.
500 locations is 0.003% of the 16+ million locations that Sonos is currently installed, so I would guess software ‘releases’ and ‘rollout’ of features has to be managed in a different way. I doubt the vast majority of consumers read T&C, privacy statements, release notes before upgrading/installing Apps on their personal devices.
Looking at your CV it looks like you don't have any embedded systems experience.
Sonos devices are considered "embedded systems" and the programs they run called firmware.
Sonos Controllers are conventional software or Apps, and now a web page too.
While the two (software/firmware) must interact for the Sonos devices to function they are separate components of the system. While they must be compatible there is no reason they updates must be in sync.
Why are the 2 different?
Because it’s common that a new feature or bug fix only requires an update to the app. or the device firmware. Because updates are burdensome to users, Sonos does not want to push customers to update the app or firmware if the only thing changing is the version number. That said, I would personally want an update that does require app and firmware update to take the opportunity to get app and firmware on the same version, or have a version system that intuitively tells you what app and firmware versions are compatible, but without knowing more details of the development process, I can’t say how feasible that is.
As others pointed out, I don’t know that many pay attention to versioning systems anyway, and only care that the system is up to date. I really only care about software versions when I am trying to determine if a new software or system I want to acquire is compatible with something I already have.
