USELESS UPDATES!!!

There are some potential issues if Sonos were to have some sort of rollback feature. Users will have the potential of messing up speakers and functions they use that are not supported in the version they wish to rollback to. Sonos would have to deal with that. Then there are security updates and one-off features that people on older versions will insist are easy and should be added to the version of their choose. Many will not accept that the version they chose is unsupported.

And although I know people don't want to hear it, but Sonos does exist to make money. They cannot pay employees, support existing products, or develop new products and features without revenue. Currently the only source of revenue is product sales. And customers who aren't on the current version can't buy new products, pretty much by definition. Although Sonos does want and need to make customers happy, making it easier for customers to stay on old versions and never provide any revenue isn't exactly in Sonos best interest. Those customers could eventually upgrade when there is a product or feature they want, sure. or Sonos could develop some other revenue model (like support fees), but it's hard to say that that is really much of an improvement, for Sonos or it's customers...IMO anyway.

I see this as a catch-22 situation. There isn't exactly a solution that has no drawbacks.

.

I see this as a catch-22 situation. There isn't exactly a solution that has no drawbacks.

Sure there's all kinds of straw men one can envision if you look at this issue through a Sonos centric lens. Current situation means that all drawbacks are borne by the customer. People are waking up to this. The next round of devices bricked will be interesting if this continues.

Sonos has our money. We Shouldn't risk bricking or losing features or to set surrounds because the desktop controller knows an update exists. By the way did you catch that from that other thread: everything on 9.1, desktop control on 9.1 but knows there's an update. Can't adjust 5.1 set up.

If you tell phone not to auto update apps there will be no forcing. Problem of forced is if phone updates it’s app.

I don't have auto-updating.
That still doesn't fix forced updates of apps and the desktop controller by disabling features until you've updated. Sonos also tells you functionality will be reduced if you don't update. I don't need updates for services and hardware I don't use or own.

.

I see this as a catch-22 situation. There isn't exactly a solution that has no drawbacks.

Sure there's all kinds of straw men one can envision if you look at this issue through a Sonos centric lens.


I don't see how companies needing to make a profit is a straw man.


Current situation means that all drawbacks are borne by the customer. People are waking up to this. The next round of devices bricked will be interesting if this continues.


Sonos has been supporting these seldom products and functions for years. The burden has been on Sonos to do so up till now. Whether customers are due support for whatever number of years after purchase is debatable, regardless of how many users use the product/feature is debatable. But you're right that these things don't matter to the customers effected, and when that group of disgruntled customers get large, it does get interesting. I do think the negative PR events becomes cumulative, and tends to overshadow positive news, at least on these forums.

[quote=melvimbe][quote=Peagle].
Sonos has been supporting these seldom products and functions for years. The burden has been on Sonos to do so up till now. Whether customers are due support for whatever number of years after purchase is debatable, regardless of how many users use the product/feature is debatable.

Sonos just needs to create a mechanism for a support-market to exist. I don't need to go to the manufacturer of an expensive TV or car to keep it going after the warranty is expired. Sonos have expensive kit that is totally dependent on their continued investment.

I don't see how companies needing to make a profit is a straw man.
M.
Dude ^case in point, give your head a shake no one is arguing they shouldn't make a profit.

Also this nonsense:

.

"Then there are security updates and one-off features that people on older versions will insist are easy and should be added to the version of their choose. Many will not accept that the version they chose is unsupported..

Updates … some people love them … some people hate them …. rarely any bugs in updates. If you are having troubles you most likely are getting IP address issues with other devices in your house. Set permanent IP addresses for your Sonos and most used network devices and you will most likely never have update troubles. It really is your network with the problems.

How do I set permanent up addresses? #Sonosupdatescrewedupmysystemagain

How do I set permanent up addresses? #Sonosupdatescrewedupmysystemagain

https://www.howtogeek.com/184310/ask-htg-should-i-be-setting-static-ip-addresses-on-my-router/

[
Ok. So it does seem that if you want to add new components you need to update but you are still 100% in control of whether or not or when to update.

Yet another update yesterday that crippled my controller, forcing me to do an update. Due to all the disabled menu items I was unable to modify my library until the update was done.

100% control is more like 10% control.

Setting static/reserved/permanent IP addresses is done from your router's DHCP page, just how varies by router but it is usually explained in the router manual.