271–280 of 416 posts
Earlier quoted context omitted.
Everyone here thinks that everyone="all hacking-experienced people", where I mean everyone is the whole world. MOST people are not going to hack their device.
How would you like Bose to solve this issue, If open sourcing the firmware doesn't make cut it?
The hardware on the soundtouch 10/20/30 series was always surprisingly over engineered with heavy magnets, decent power supplies, and good enclosures but let down by a sluggish app and flaky mDNS implementation. With this, they just became the best value proposition on the used market. Flashing these with a minimal distro running snapclient (for multiroom audio) and shairport-sync (AirPlay 2) makes them infinitely be…
Why are these devices connecting to the Internet at all? Aren't they supposed to be connected to phones and TVs via cable or bluetooth? I would never allow any "smart" anything device to speak to the Internet in the first place.
What usually gets missed is that end-of-life is still part of the project, even if it sits years downstream. When software support is withdrawn without a transition path, the hardware doesn’t just lose features — it loses trust. That’s not a technical failure, it’s a lifecycle planning failure.
Open-sourcing at sunset is interesting because it’s one of the few mechanisms that acknowledges this gap. It doesn’t help most users directly, but it at least hands control back instead of silently bricking capability.
I’m curious whether we’ll start seeing project managers and product teams treat “exit conditions” as a first-class deliverable — with explicit decisions about data, firmware, APIs, and ownership once commercial support ends — rather than treating end-of-life as someone else’s problem.
This is not open sourcing any actual software or hardware it is “open-sourcing the API documentation for its SoundTouch smart speakers”. You might be able to point them at an alternative back-end¹ if you want the cloud features, but that will need to be written from scratch rather than being forked from code provided by Sonos. > When cloud support ends, an update to the SoundTouch app will add local controls to retai…
According to this comment[1] by an OSS developer working on reverse engineering the device, the documentation released doesn't allow them to implement an alternative backend. If I understand the purpose of the interfaces correctly from skimming the reverse engineering effort github[2], the API released documents the HTTP interface between the phone app and the speakers, which has been available for years, and covers…
Looking over the API docs seems to confirm what the comment you referenced and the poster I linked here is saying. I'm seeing calls to virtually press buttons on the speaker, set the input source, to query the presets, and some zone-relayed calls, but nothing about actually playing audio from network sources.
For the call re: presets I see:
> Description: Presets are a core part of the SoundTouch ecosystem. A preset is used to set and recall a specific music stream supported by the SoundTouch speaker
There's a GET method that returns information about presets. Presumably you'd use a POST or PUT method to manage the presents. To that end, under POST, it says:
> POST: N/A
It looks like this API basically allows you to control it like an dumb speaker. That's not nothing, but it's not much either.
There doesn't seem to be anything in the API about controlling how the speak communicates with a back end service.
Edit:
Having some time to read over your [2] and the link to [0] it looks like getting root on the speaker w/ physical access is ridiculously easy. Booting the unit w/ a FAT32 USB drive attached with a file named "remote_services" in an otherwise empty root directory opens up an ssh server and the root user has no password.
The comments on [0] have some interesting tidbits in them, too.
These speakers look like they might be fun to play with and once Bose kills the back end people may unload them cheap.
[0] https://flarn2006.blogspot.com/2014/09/hacking-bose-soundtou...
This is how "end of support" should be handled. Instead of turning devices into e-waste, open-source them and let the community extend their life. Kudos to Bose for setting a good example. More companies should follow this approach - especially as right-to-repair becomes a bigger issue.