Control4 Integration with Sonos 7.0

I've read them. I also read your original lament about not being able to add to your system and keep it at 4.X. You most certainly thought you should be able to add more modern units until you were informed that the newest models weren't even sold when 4.X was out. You then proceeded to backtrack.

But hey, at least there is some amount of technical logic you will accept. Baby steps. Baby steps.

But seriously (and to get this back on topic), you were asked in another thread to supply hard evidence that the Sonos API was lacking the features you accused it of, and you gave nothing. Yet, here you are again with the exact same accusation, and aside from rumors, you again have no facts to back you up. No API specs, no literature, no official statements, nothing. It's time you put up some evidence, or start posting disclaimers. This "I'm going to post assumptions/innuendo/rumors as fact in order to force a statement from Sonos" shtick just isn't cutting it

I haven't yet seen a credible reason why they cannot make old software versions available with the caveat that they are not supported. Most of the other connected home technologies I work with do allow you to downgrade with the understanding that you must upgrade to the current version before you can get support. if you then downgrade back to an older version that is on you. No credible alternative explanation has ever been offered for why Sonos cannot embrace this common practice.


Common practice? Examples? Certainly not offered by companies providing free lifetime support that Sonos is famous for doing so well. Allowing multiple firmware versions would be a support nightmare, increasing costs dramatically, to the point where Sonos would be forced to charge for it, like everyone else. No thanks!

I've read them. I also read your original lament about not being able to add to your system and keep it at 4.X. You most certainly thought you should be able to add more modern units until you were informed that the newest models weren't even sold when 4.X was out. You then proceeded to backtrack.

But hey, at least there is some amount of technical logic you will accept. Baby steps. Baby steps.

But seriously (and to get this back on topic), you were asked in another thread to supply hard evidence that the Sonos API was lacking the features you accused it of, and you gave nothing. Yet, here you are again with the exact same accusation, and aside from rumors, you again have no facts to back you up. No API specs, no literature, no official statements, nothing. It's time you put up some evidence, or start posting disclaimers. This "I'm going to post assumptions/innuendo/rumors as fact in order to force a statement from Sonos" shtick just isn't cutting it

I am not going to falsely present myself as a technically savvy person who can discuss API specs. People on other forums have reported that their customers are unhappy about the new Control4 driver and stated it was because of the Sonos provided API. I have repeated those concerns here so Sonos can explain why they are unfounded both for Control4 and anyone else who depends on the new API for integration. Anything that the user community is unhappy about is considered a "fact" until there is a good explanation they can accept to say otherwise.

As I stated, you are posting speculation, rumor, and innuendo as "fact", in multiple on and off topic threads, in an attempt to "poke" Sonos into making a statement.

How's that working out for you? 😃

Common practice? Examples? Certainly not offered by companies providing free lifetime support that Sonos is famous for doing so well. Allowing multiple firmware versions would be a support nightmare, increasing costs dramatically, to the point where Sonos would be forced to charge for it, like everyone else. No thanks!

Don't even bother chicks. mike has had this explained ad infinitum, and while he relies heavily on the "I am not going to falsely present myself as a technically savvy person" excuse to self-exempt from providing proof of his "facts", he suddenly becomes an IT expert when evaluating the technical aspects of software version control and the ROI therein.

He's got a shtick, and he never wavers from it. Better just to call him on his lies.

I haven't yet seen a credible reason why they cannot make old software versions available with the caveat that they are not supported. Most of the other connected home technologies I work with do allow you to downgrade with the understanding that you must upgrade to the current version before you can get support. if you then downgrade back to an older version that is on you. No credible alternative explanation has ever been offered for why Sonos cannot embrace this common practice.


Common practice? Examples? Certainly not offered by companies providing free lifetime support that Sonos is famous for doing so well. Allowing multiple firmware versions would be a support nightmare, increasing costs dramatically, to the point where Sonos would be forced to charge for it, like everyone else. No thanks!

Support nightmare? Increasing costs dramatically? I clearly stated right here in the paragraph you just quoted that they could offer previous versions with the caveat that they are NOT supported. Cost to Sonos is maintaining some release notes regarding the minimum version needed to use a given player model or feature. Maybe they have some other reason for not wanting to do this but I don't see it creating the support Armageddon you describe.

Support nightmare? Increasing costs dramatically? I clearly stated right here in the paragraph you just quoted that they could offer previous versions with the caveat that they are NOT supported. Cost to Sonos is maintaining some release notes regarding the minimum version needed to use a given player model or feature. Maybe they have some other reason for not wanting to do this but I don't see it creating the support Armageddon you describe.

I hesitate to get into this off-topic nonsense with you, because there is absolutely no amount of logic or technical expertise that will sway your decidedly illogical and non-technical opinion. But hey, in for a penny!

You have repeatedly asked for not just the continued release of old software, but also the ability to "not lose functionality". I define "losing functionality" as . . . well . . . actually losing functionality! As such, if I were to be playing Spotify on my version 4.X Sonos system, and Spotify changes to the web based API instead of the API used by 4.X, rendering my Spotify account useless on Sonos, I define that as "LOSING FUCNTIONALITY!!!"

Also, if I'm happily running my 4.X Sonos system, listening to BBC broadcasts via TuneIn, and all of a sudden the BBC changes to a different streaming format that is not supported by Sonos 4.X, I call that "LOSING FUCNTIONALITY!!!"

How about when Sonos is required to up the security access needed for AWS, such as they did for the Direct Control update, and all of a sudden your 4.X system can't log into the Sonos site, or access any of the AWS servers needed to stream online content? I define that as a big honking example of "LOSING FUCNTIONALITY!!!"

Need more?

As such, to not "lose functionality" Sonos would have to re-release every software version they have ever done, updating it to the new specs for every interface change by the dozens of streaming services they support. This is the support nightmare we speak of, not to mention against the TOS for iOS and thus not even possible.

Now go ahead and define "not losing functionality" to exclude the 92% of Sonos owners who stream from online services. I'm in the mood for a good laugh! 😉

Already explained the concept of release notes. If Spotify or Amazon makes a change that impacts an old release then update the release notes so people know what changed, why, and where they should go to complain about it (Amazon, Spotify, or whoever.) Or the user can decide which "Functionality" is more important to them, a deprecated Sonos feature such as an old hardware controller, or continued access to a streaming service since there is no longer a version that supports both. Point is the user gets to decide, all Sonos has to do is document what is available with each archived version. The 8% who don't care about streaming feel they are accommodated the best way feasible to maintain the functionality they want and the rest move forward as always. No support nightmare required.

Ahhhh, the old "functionality is up to the user to define" dodge. Real big difference from your original definitive statement that there should be "no loss of functionality". Goal posts are moving so fast, they now got wheels on them, folks!

But hey, I'll play along. Given your wishes and definitions, Sonos should open itself up to disclaimer after disclaimer, just to offer old versions of software which are only suitable for the tiny fraction of users who A. Don't use streaming (or are willing to part with this feature) and B. Want to use old software versions.

All the while taking the hit from those folks who never read the disclaimers or release notes who will clog the support lines or review columns with complaints that software willingly and freely offered by Sonos just doesn't work? And they are supposed to simply accept Sonos' disclaimer and lobby Spotify or Amazon to fix it? Seriously? From the guy who never misses an opportunity to shoehorn in a complaint about the Control4 interface not working, and blames it all on Sonos despite no proof; that's a pretty bold statement of hypocrisy.

Yeah . . . as I said, there is absolutely no amount of logic or technical expertise that will sway your decidedly illogical and non-technical opinion. Thanks for the laugh!

Ahhhh, the old "functionality is up to the user to define" dodge. Real big difference from your original definitive statement ...

If by that you mean you raised concerns about the original premise and I advanced some additional thoughts on how those concerns might be addressed then yes the conversation has moved on.

All the while taking the hit from those folks who never read the disclaimers or release notes who will clog the support lines or review columns with complaints that software willingly and freely offered by Sonos just doesn't work?.

Pretty much what already happens each time there is an update that folks don't like and find they cannot go back. If there was a way back it might actually reduce the some of the current support pressure.

Yeah . . . as I said, there is absolutely no amount of logic or technical expertise that will sway your decidedly illogical and non-technical opinion. Thanks for the laugh!

Glad I could brighten your day.