Constant Updates REALLY ANNOYING



Show first post
This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

127 replies

Stuart, any idea what was the average time between updates in 2012? I could not find it anywhere. Comparing that to the above is more pertinent, I suggest. Or even to any year prior to 2010.
Userlevel 7
Badge +15
Speaking of assertions and 'These are the only releases....' etc.., where is 10.0.2 and 10.0.3? They were separate bug fix releases too from memory. Assuming all 'updates' are being discussed - whether that be player or App.
EDIT: Looks like they were released within days of each other about a month ago
( https://en.community.sonos.com/announcements-228985/sonos-10-0-is-now-available-6820022/index6.html )
Userlevel 7
Badge +22
Speaking of assertions and 'These are the only releases....' etc.., where is 10.0.2 and 10.0.3? They were separate bug fix releases too from memory. Assuming all 'updates' are being discussed - whether that be player or App.
EDIT: Looks like they were released within days of each other about a month ago
( https://en.community.sonos.com/announcements-228985/sonos-10-0-is-now-available-6820022/index6.html )


I was mindful that the site I linked may not be complete which is why I noted for full disclosure.

But just my own feeling based on updates is that it's not every few weeks on average
Memory is notoriously unreliable; with that said, I'd say that I remember this being a once in a quarter exercise back in 2011/12 that is now once in a month.
I have a feeling that the churn started when Sonos started feeling the heat from Echo. They felt that they have to do something even if it often meant churn minus noticeable forward motion. Which led to more bugs needing to fixed as an inevitable consequence, causing more churn.
Userlevel 7
Badge +22
I'd like to think that Sonos are on top of this in terms of they know exactly how the updates have changed over the years and the effect on users. It's clearly a concern.

To me they could perhaps create different levels of updates - minor and major for the want of better explanation. If you select don't update then minor updates will do nothing but majors will notify the user. These should be restricted to, say, twice a year
That is one way of handling this; or major could be defined as where the version number changes - as in from 10 to 11. The problem then is what do you do with the 11.0.1 that usually is the bug fix for 11.0?!
Badge +7
Seems it may be time for a Sonos employee to directly comment on this thread again, and specifically attempt to answer some of the legitimate questions posed. Wade through some of the empty complaints and there's merit among this madness for their representation and clarification.
They clearly have a concern for it since they added the automatic updates feature. It's not something they would add if they were not aware of how some customers feel about updates.

The thing is that automatic updates does not work for those of us that use the desktop controller. I don't know how well it works for androids too, going by my experience - I do not see that my phone app has automatically renewed itself even with the phone set to do this automatically for apps, which it does for others. Maybe there is another thing to toggle just for Sonos that I have missed, but this isn't a big deal for me, stuck as I anyway am with having to manually update the computer controller every time.

And of course, automatic in all cases only works for those that have the network quality and set up to be where Sonos needs it to be. I have no idea what that is as a percent of users.

On the process discipline, let us agree to disagree; I am not seeing it to the extent I would like to, but that may be just me, I agree.

Finally, for some of us, this is just a music system; it is all very well to say that it is software etc etc, but we use it just to play music and are not seeing that use case change in many years, notwithstanding all the jazzing up Sonos may have done to it.

The thing is that automatic updates does not work for those of us that use the desktop controller.


Understood. I wasn't trying to imply that Sonos auto firmware updates made updates carefree across all platforms, just that it's a sign they are aware that upgrades are annoying to some users.


I don't know how well it works for androids too, going by my experience - I do not see that my phone app has automatically renewed itself even with the phone set to do this automatically for apps, which it does for others. Maybe there is another thing to toggle just for Sonos that I have missed, but this isn't a big deal for me, stuck as I anyway am with having to manually update the computer controller every time.


I've had no issues with Sonos automatic updates.


And of course, automatic in all cases only works for those that have the network quality and set up to be where Sonos needs it to be. I have no idea what that is as a percent of users.


Yea, that can be annoying if your phone does updates over a mobile network, but your home has weak or no internet access. Again, I'm not claiming that it's not frustrating to some customers.


On the process discipline, let us agree to disagree; I am not seeing it to the extent I would like to, but that may be just me, I agree.


Eh, I'm not really claiming Sonos does have good process discipline as am that there isn't enough information to claim one way or the other really. It's hard to gauge the consequences of waiting to put in a new feature, security patch, bug fix, etc.


Finally, for some of us, this is just a music system; it is all very well to say that it is software etc etc, but we use it just to play music and are not seeing that use case change in many years, notwithstanding all the jazzing up Sonos may have done to it.


Sure, and I'd happy to see Sonos make changes to make updates easier to delay and/or less painful for you all somehow. I don't know exactly what that looks like.

And FYI, if I could speculate on another reason why updates are coming more frequently, Sonos used to be a much more closed system. With involved in android and iOS systems, and voice control, they are forced to react to changes made to those systems as well as their own. Again, not necessarily a concern of every customer, but something that factors into to the update decisions.
Badge +7
Regardless of what response it might incite, the information provided could at least be stamped official. That has to count for something, no? If nothing else, we can all likely agree on the fact silence from Sonos on the issue could do more potential damage than actually addressing the concern(s) presented. My experience is Sonos does a great job of the latter, but I'm aware that isn't all users' opinion.

Was more an attempt to pull this thread back into a constructive roadmap, as it was taking a hard left turn into... well, nowhere pleasant.

Seems it may be time for a Sonos employee to directly comment on this thread again, and specifically attempt to answer some of the legitimate questions posed. Wade through some of the empty complaints and there's merit among this madness for their representation and clarification.

Honestly, what are they going to say that will alleviate the complaints? Anything they say will just be fuel to the fire.


Vaccines are important for kids. If a child needs 50 shots to be fully vaccinated by the time they're 12, should we give them 1 at a time? Of course not - we group them together to make it easier on the child. If I make the claim that "giving 50 shots one at a time is ridiculous and unnecessary," it is not the same thing as saying that the shots are useless. It's the frequency that matters, not the content that's being administered.


Vaccines are given together, yes, but also as a matter of availability. Yes, you get as many shots at one time as you can, but as new diseases arise, you get the new vaccine irregardless of the last time you had a vaccine. This happens every year with the flu vaccine. People get them in the fall because that's when they become available and that's when they are needed. As new flu strands are considered to be active, the flu vaccine is updated, and you can get the vaccine again if you wish.

It really isn't that great of analogy, as there are plenty of differences between patches and vaccine. I don't think it supports your argument anyway since vaccines aren't spaced out for the convenience of the patient, they are made available as soon as possible.


As I said REPEATEDLY before (but for some reason, people seem to fail to understand), there's nothing wrong with updates, but doling them out more than a few times per year is unnecessary for an app that plays music, and does nothing else.


I understand that you think the frequency of the updates is unnecessary. I understand that they are frustrating and don't have any outward value to you. I just don't agree that the frequency doesn't serve any purpose for all or most of Sonos customers...at least not without looking more closely at what's in the updates and why they are released now as opposed to later.
Badge +7


Got news for you, these types of threads always go nowhere pleasant. Sonos commenting only feeds that. Better to let it run its course until the next update triggers the next dozen or so posters who find fault.


OK, fair enough. Cheers!
Userlevel 3
Badge +1
[quote=melvimbe]
It really isn't that great of analogy, as there are plenty of differences between patches and vaccine. I don't think it supports your argument anyway since vaccines aren't spaced out for the convenience of the patient, they are made available as soon as possible.


Vaccines are not given "as soon as they are available." They are grouped together primarily for the convenience of the patient (or parent).

"Combination vaccines reduce the number of shots your child needs while protecting against several serious diseases." (from www.cdc.gov)

DPT, MMR, etc are good examples. It's done to minimize the number of injections. Newer combos include Pediarix (DTaP, Polio, and Hep 😎, ProQuad (MMR and Chickenpox), Pentacel (DTaP, Polio, Hib,) etc.

Group the updates together so there is more per update, with fewer updates. It's that simple. Fine, if there is some Earth-saving critical patch that will rescue mankind from demise via a glitch in Sonos software, I would welcome that patch and all of the annoyance that comes with it, since humanity is at risk. Since I doubt there are too many potential fatalities from Sonos systems going off the rails, I'm going go ahead with my assertion that Sonos could dial down the volume a bit on their updates and we'd all be just fine.
Userlevel 7
Badge +20
This thread is still going? And now it's somehow about vaccination? Exceptional.
This thread is still going? And now it's somehow about vaccination? Exceptional.
😉 Venom would say: "Outstanding. Now, let's bite all their heads off, and pile them up in the corner."
Eh, I'm not really claiming Sonos does have good process discipline as am that there isn't enough information to claim one way or the other really. It's hard to gauge the consequences of waiting to put in a new feature, security patch, bug fix, etc.

And FYI, if I could speculate on another reason why updates are coming more frequently, Sonos used to be a much more closed system. With involved in android and iOS systems, and voice control, they are forced to react to changes made to those systems as well as their own. Again, not necessarily a concern of every customer, but something that factors into to the update decisions.

Completely agree with this. Sure, you could bundle non-essential updates. But if there are security issues - which are becoming an increasing concern as IoT devices become more of a target, or changes on the side of streaming services/voice assistants that potentially break functionality, I would like to see immediate action from Sonos. I think the stream of complaints we would see if Spotify, Apple Music, TuneIn, or Alexa stopped working would dwarf the complaints about updates. What would be the response if Sonos then said: "just wait until the update in Q3"?

If you're not using any of the functions involved in an update, it might not matter to you, but wait until it does. When your Sonos does not even "just play music" anymore, you would rather have that update sooner than later.

Edit: Didn't see Ryan's post until after I posted. Sonos' thoughts on this seem to be similar:

While we have more regular updates now than before, it gives us more opportunities to release fixes for issues that might have come up. If you're familiar with the community, you've probably seen threads where there's a known bug or issue that we're working to resolve and an update would be needed for it. That update couldn't possibly come fast enough for the people affected.
Userlevel 3
Badge +1
This thread is still going? And now it's somehow about vaccination? Exceptional.

I like to drive off road once in a while. You never know where the path will take you. One thing that's worth mentioning at this point in the thread, is that Sonos updates come out too frequently.

Ok, feel free to talk amongst yourselves.
Badge +7
@Ryan S - thank you.
Userlevel 3
Badge +1

While we have more regular updates now than before, it gives us more opportunities to release fixes for issues that might have come up.


Not to be stirring up dust here, but shouldn't those fixes be resolved before releasing the software on consumers? I understand that some bugs are unavoidable, but if the reason for more frequent updates is to patch holes in the software that cause major system breaks, I think it calls to mind the question of whether the software should be held on to a little longer so more bugs and corner cases can be worked out.

Code that's worked on by multiple engineers who drive their own ship can get ugly, very fast. I'm not saying that's what's happening here, but it does make me wonder if the software is inherently buggy and that's why there are so many "fixes" being released so frequently.
rest assured, software is in testing for a good while before it goes out into the wild.
It seems now to be back in the day that I remember that each update spent a significant time in public beta, and prior to that in private beta testing. I am not sure that this release protocol is compatible with the frequency of releases we now see.
pacificdiver,

Equating reserving IP addresses with being a "mainframe installer" or "engineer" is hyperbole of the highest order. It's akin to equating making a grilled cheese to making coq au vin. Unless one has some type of handicap, one should not be so harsh on one's ability to perform simple tasks.
Userlevel 3
Badge +1
pacificdiver,

Equating reserving IP addresses with being a "mainframe installer" or "engineer" is hyperbole of the highest order. It's akin to equating making a grilled cheese to making coq au vin. Unless one has some type of handicap, one should not be so harsh on one's ability to perform simple tasks.


My father can barely use a screwdriver. Picture a support agent on the phone trying to walk him through the steps given above.

For the record, I have tried many of the fixes listed above. They help, but don't fix the problem completely. What WOULD fix the problem would be to lessen the frequency of the app updates.

And btw, another "An update is available" window literally just popped up on my PC. Oh, the irony.
I'm going to agree with @pacificdiver on the argument that reserving IP addresses and other network troubleshooting can be too much for some people. It's not necessarily because they aren't capable of understanding and learning, it's that they are so afraid of tech that they effectively shut down mentally and can't complete the simplist of tasks.

My mother is a good example of this. She definitely is an intelligent woman, but she was afraid of changing the inputs on the TV for fear she won't be able get cable back on. It took years to get her to be comfortable with the idea. She has a few echos now, and can manage them ok, but I had to setup some Alexa groups for her. There is no way I'd set her up with Sonos as she would not be able to manage it.

(side note: I would get Sonos for mum if she leaved a bit closer to me where providing tech support on a regular basis was a reasonable option)

That's not a knock on Sonos, just that there is a segment of the population that can't handle Sonos, and therefore shouldn't be buying Sonos. But I would say that the frequency of updates really that relevant for the majority of people. If you can't use a screwdriver or change the input on your TV, you're going to struggle with Sonos long before an update happens. And if you can manage to operate Sonos on an every day basis, you should be able to reserve IP addresses and work with Sonos support to troubleshoot networking issues.

As far as the issue of whether the updates need to be happening as frequently as they do, Sonos replied to that and gave reasons why. I'm not sure what the point of further debate on the topic would be.
Badge +7


I'm not always successful at it, but I try and ignore motives in these discussions/debates. That's partially because I don't like it when someone attempts to minimize my own statements/views by claiming I'm just a "Sonos apologist", secretly on staff or something of that nature. A statement is either true or false regardless of why the statement was made. Also, motives are personal, and calling it out can be viewed as a personal attack or lead to personal attacks. I'd rather avoid that.


I understand your point, and respect it just the same. You often underestimate yourself also, but humility is a great quality to have.

Perhaps it wasn't obvious, but my intentions were never to attack. I, not unlike several others, lose patience with empty complaints. This is multiplied exponentially when the complaint isn't followed by acknowledging (and to some degree) following the professional advice given.

Secret Sonos employee claims? Really? Not even going to approach that one. Sorry you have to deal with that.

Cheers!
I too am getting pissed off with the updates, everytime there’s an update I lose most if not all of my zones for a few hours. So just to clarify, are you still running your devices on SonosNet, with the suggested WiFi/SonosNet separation and have you chosen yet to reserve your devices in the routers DHCP Reservation Table, or not bothered, or unsure of how to do those things and finally have you sought support here before, or with Sonos Support? I’m just curious as to what you may have done over the years about your issues?