Question about the CR100 and legacy mode

The CR100 used such an old version of embedded-flash that it is unable to communicate with most of today’s https servers, ruling out most music services. It has other problems too, but this is the biggest by far. Also: it was a truly ugly codebase. I miss the hardware though.

Despite the old version of the software (V 7.3 in my case), my 2 CR100s continue to work fine with Qobuz and Amazon (Prime) Music.  And the controllers remain my first choice to play TuneIn content.  It would be good if the possible branch in the software in May (something we were told all those years ago could never happen) could restore the CR100 to normal use  - but I presume that could never happen...  Too much water under the bridge development-wise.

How good would it look, however, if proper legacy support was introduced so saving not only CR100s but older but extremely useful tablets an PCs / laptops.

Which ones. We still have 3 in daily use for TuneIn and amazon Prime Music. Operate with no issues. 
if you add up the stuff added since their withdrawal it adds up to very little. I suspect it could be won’t be added to the legacy version due to loss of face. But refusing to do a legacy version, then doing one, already makes the decision process look a mess. 
 

Dave

I can’t remember, its been a long time. Certainly not TuneIn as it is the simplest service there is as there is no authentication. I would guess Google is broken as they always use the latest TLS version (likely the CR100 can’t do that) and certificate pinning. The SMAPI docs warn that older versions of TLS may not be supported in the future, and when they throw that switch then the CR100 would be even less useful.

My CR100 still works fine to access Spotify with system software 8.4.  The CR100 itself is on software version: 4.3.2.  Fancy that,. a system that functions with hardware on different firmware versions.

Too bad they didn’t fork the 8.4 software as S1, people could have moved forward for a while longer with pretty much all there Legacy Equipment.

I agree that would have been the better option. 
 

but if you block Sonos.com and all it’s subdomains to help keep your system at FW8.4 keep in mind that one subdomain has to remain unblocked or your radio will fail at some point: 

sslvalidator.sonos.com

if that’s blocked, your Tunein radio will lock up And stop playing at some point.  Took mine almost 2 years but here we are. Everything else @ sonos can be blocked, per my experience.   

 to make room for other more important things

More important to whom?  My CR100 is important to me, and I bet anyone who has one (and most of those who had one) would say it’s important to them.  Why is your important primary to my important???  This is plain ridiculous, I can’t believe this was selected as a “solution” to the “problem.”  

I doubt many folks have any CR-100 still available.

This “doubt” is because you don’t have one.  Not because of anything like truth.  I have one and it is important to me.  Your “doubt” is not a reason that my hardware should be disabled remotely, without permission, never to function again.

 ruling out most music services

I bought my system so it could play my files.  I’m not interested in paying for services, and that is not what the system was intended for.  Just because they changed their minds is not a good reason that I should lose my working system.

It has other problems too

I’m waiting to know what these other problems are.  If they are being hidden from me, then that is yet another reason I am done with Sonos.

If Sonos were to add my CR100 back into my system, I would reconsider my position, but until then not only will I never buy another piece of Sonos, but anyone that sees & hears mine gets an “Eh, it’s an expensive piece of crap controlled by overlords who remotely destroy hardware without permission, you can do better with X setup.”  And they’ll tell two friends, and so on and so on.

FWIW, I still have multiple CR100 as well, fully functional.  My system is frozen at FW8.4 and everything I need just works.  I use pi-holes and  my gateway to keep the Sonos components here from contacting anything at Sonos.com other than sslvalidator.sonos.com.  Belts and suspenders.  
 

Because the metrics subdomain at Sonos.com cannot be contacted by my components, Sonos likely thinks my components have gone the way of the dodo. Likely anyone who uses pi-holes or who also wants to keep their Sonos systems at 8.4 or less will have similar safeguards leading to an undercount.

My radio services still work fine.  The local radio stations always worked and once I re-enabled sslvalidator.sonos.com, so did the tunein stations and podcasts.  Last.fm also likely falls into that category.  
 

As for day to day, the CR100 works great for playlists, radio shows and so on. On my iPhone, SonoPhone does a great job, esp. if I have to search for something. Unlike the official Sonos iOS app, SonoPhone and SonoPad allows the control of systems even older than FW6.4. So it can be done, it’s just that Sonos doesn’t want to do it.  

I’m still using three CR100s on my system, which is locked down on OS 8.4. The controllers work and look great and I’ll never get rid of them.

But I want to be absolutely clear about this: Is OS 8.4 the absolute latest I can run? In other words, if I upgrade to S1, it will brick my CR100s?