Skip to main content
Trending Lyricist I
Feb 2, 2020 9:27 AM UTC

Obsolescence doesn't have to mean obsolete

My Sonos life began with a Gen 1 Play:1.  I was amazed by the clarity of sound from something so small and was happy for a while.  But … the sound was mono and I wanted more.  This wasn’t because the Play:1 was in any way deficient in design or execution, it just didn’t have enough speakers in it.

So I went out and bought a second Play:1, and was amazed by the clarify of sound from something so small and was happy for a while.  But … I couldn’t plug it into my TV to listen to music or movies. This wasn’t because the Play:1 was in any way deficient in design or execution, it just didn’t have the right connectivity, or the CPU power to deal with Dolby 5.1 audio.

So I went out and bought a Beam, and was amazed by the clarity of sound from something so small.  I was even more amazed that I could re-purpose my Gen 1 Play:1s as surround speakers: even though there weren’t capable in their own right of connecting to my TV, the Sonos system design allowed them to be used alongside a newer box that didn’t exist when they were brought into being, and to augment that experience.  Big kudos to Sonos for that foresightedness.

Recently I’ve acquired a Gen 1 Play:5, and I’m amazed by the clarity and depth of sound from something so small.  It knocks the socks off my Play:1s.  However, as I understand it, I can’t use Gen 1 Play:5s as surround speakers because they lack the 5GHz wifi hardware necessary to perform that feat. Am I dissatisfied with Sonos’s lack of foresight here? No, because I understand that 10-year-old hardware can’t do everything that today’s hardware can.  I also can’t stream Airplay2 audio from my iPhone to the Play:5, again because it lacks appropriate hardware, and maybe doesn’t have the CPU gumption for the job either.  However, if I stream Airplay2 to the Beam then Sonos’ Multiroom feature can get the audio to the Play:5 and keep it in sync.  More kudos to Sonos.

So now we come to the May 2020 End Of Life announcement, and the suggestion that my Gen 1 Play:5 is now only good as a doorstop.  I don’t get it.  I’m already aware that my Play:5 can’t do many thing that newer devices can do, but it’s still a banging good speaker that should be able to act as a Multiroom slave to any future device that supports some yet-to-be-invented streaming service - how about quantum-encoded octophonic immersive audio? It would be nice to think that Sonos could work out how to slave 8 Gen 1 Play:5s to a Shiny New Box to create an audio experience that makes you think you’re sitting in the middle of the orchestra pit at the Last Night of the Proms.  And why not?

So come on, Sonos, allow us the good sense to understand what it and isn’t possible with your hardware. We aren’t upset when our old kit doesn’t do what the new kit can do, instead we’re amazed how you get the old stuff to work so well with the new, within the limits of its capability.  So don’t give up on the Gen 1 Play:5 and tell us to brick it, commit to keeping it as compatible as possible with the new stuff.  That’s how you keep your customers loyal and continue to stand out from the crowd.

    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.

    40 replies

    KomoboAuthor
    Trending Lyricist I
    Feb 3, 2020 11:23 PM UTC

    I guess if you consider the way they work right now as ‘obsolete’...Sonos has just said they can’t add new features to those speakers that are ‘legacy’, not that the speakers will stop working. 

    No, Sonos has said more than “no new features”. They also said that legacy speakers must be split onto a separate network in order to allow supported speakers to be updated, so the legacy speakers will become less capable - for example, I would no longer be able to stream Airplay2 music from my Beam to my Play:5, which I can definitely do today.  This would drastically degrade the usefulness of the Play:5.

    Translate
    Feb 3, 2020 11:35 PM UTC

    So just because I have one legacy product I should keep all the expensive, new devices un-upgraded? Doesn’t sound sensible to me. 

    Why not, if none of the upgrades is something you really want? There are plenty of people on here saying they haven't wanted any of the recent 'enhancements' never mind unknown future ones.  But if it's not for you, OK  I'm not trying to say you should go down any particular route. 

    Translate
    Ken_Griffiths
    Feb 3, 2020 11:37 PM UTC

    No, Sonos has said more than “no new features”. They also said that legacy speakers must be split onto a separate network in order to allow supported speakers to be updated, so the legacy speakers will become less capable - for example, I would no longer be able to stream Airplay2 music from my Beam to my Play:5, which I can definitely do today.  This would drastically degrade the usefulness of the Play:5.

    No..! it’s not a separate network. It’s a separate Sonos household or legacy system. Some users have separate households now, myself included. Not everyone has more than one LAN subnet and so you are still misunderstanding the Sonos announcements yourself. The two will likely run on the same network with a different Household ID.

    You may well be able to AirPlay/Cast or use the Sonos API through Apps to both systems but the detail is yet to be published. 

    Translate
    Stanley_4
    Grand Maestro
    Feb 3, 2020 11:57 PM UTC

    I haven’t noticed a lot of complaints about missing new stuff from the folks that stopped updates to keep their CR-100 or dock working.

    If any of the folks with long frozen systems are following this topic, is there anything you miss or that was working but now doesn’t?

    Translate
    Feb 4, 2020 12:56 AM UTC

    @Stanley_4 : I have been asking just this, so far replies received - a few - have reported nothing missing or gone wrong. More may come to your posted question.

    Translate
    KomoboAuthor
    Trending Lyricist I
    Feb 4, 2020 6:08 AM UTC

    No, Sonos has said more than “no new features”. They also said that legacy speakers must be split onto a separate network in order to allow supported speakers to be updated, so the legacy speakers will become less capable - for example, I would no longer be able to stream Airplay2 music from my Beam to my Play:5, which I can definitely do today.  This would drastically degrade the usefulness of the Play:5.

    No..! it’s not a separate network. It’s a separate Sonos household or legacy system. Some users have separate households now, myself included. Not everyone has more than one LAN subnet and so you are still misunderstanding the Sonos announcements yourself. The two will likely run on the same network with a different Household ID.

    You may well be able to AirPlay/Cast or use the Sonos API through Apps to both systems but the detail is yet to be published. 

    I think you’re splitting hairs into Sonos-specific nomenclature now. “Households” exist on separate IP subnets so, okay, I should have said “separate IP SUBNET” rather than “separate network”, but the effect is the same: today my Play:5 is in one “Room” (another word with special meaning in Sonos-speek) and my Beem is in another but a single Controller (Sonos-speek) lists both Rooms and can Group (Sonos-speek) them together so that audio only discernible by the Beem can be played on the Play:5. Sonos’ “legacy” announcement says this will no longer be possible - the Room-to-Room link that exists today will be broken.  Sonos will brick up the doorway.  I don’t see why that should be necessary.  And, having spent over 30 years working in computer software with a heavy slant on IP networking, routing, bridging, firewalls, you name it, I’ve got a reasonable idea of what’s possible if you just put your mind to it.

    Translate
    KomoboAuthor
    Trending Lyricist I
    Feb 4, 2020 6:18 AM UTC

    I haven’t noticed a lot of complaints about missing new stuff from the folks that stopped updates to keep their CR-100 or dock working.

    If any of the folks with long frozen systems are following this topic, is there anything you miss or that was working but now doesn’t?

    My Beam didn’t support Airplay2 when I bought it.  If it had been part of a “frozen” CR-100 Household (let’s not say “network”, others are touchy about that word) then I would have been unable to update and so would be “missing new stuff”. Does that give you a significant enough counter-example?

    Translate
    Feb 4, 2020 6:56 AM UTC

    It is possible to run two Sonos households (systems) on the same IP subnet. I repeat that we do not know what a split system will look like after May. Maybe Sonos don't know every detail yet. I have no idea.  What's the hurry?

    We all have option to enjoy our systems until May, see the details,  then decide. Then a few months later decide something different if we haven't upgraded.

    Translate
    KomoboAuthor
    Trending Lyricist I
    Feb 4, 2020 10:29 AM UTC

    It is possible to run two Sonos households (systems) on the same IP subnet. I repeat that we do not know what a split system will look like after May. Maybe Sonos don't know every detail yet. I have no idea.  What's the hurry?

    We do know that the split system is split: two separate islands with an insurmountable void between them. Sonos may not know the detail, but they do know the outline. Why hurry? Because if we complain now then there’s time for them to change the outline and come up with different details, to invent a way that two pools of devices on different software releases can co-exist AND COMMUNICATE with each other. That’s why this debate matters now. By May it will be too late.

    Translate
    Feb 4, 2020 10:39 AM UTC

    We do know that the split system is split: two separate islands with an insurmountable void between them. Sonos may not know the detail, but they do know the outline. Why hurry? Because if we complain now then there’s time for them to change the outline and come up with different details, to invent a way that two pools of devices on different software releases can co-exist AND COMMUNICATE with each other. That’s why this debate matters now. By May it will be too late.

    There is also a selfish reason for Sonos to do this. For example: if the above referred split system has line in jacks on the modern side ( on the legacy side today it will for sure have these), the insurmountable void is substantially bridged by setting these jacks to autoplay and wiring two Echo Show 5 like devices to both. The void then gets bridged by the Echo multi room grouping feature. It also provides album art on both devices - and if this isn't needed, one can do this even more cheaply by two Echo Dots. 

    If Sonos allows such solutions to get discovered and publicised because of its silence till May, it lets the competition get a toe hold into its installations and exposes itself to the subsequent risk of that toehold displacing Sonos kit over a period of time.

    Translate