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 retain as much functionality as possible without cloud services

This is a far bigger move than releasing API information, IMO bigger than if they had actually open sourced the software & hardware, from the point of view of most end users - they can keep using the local features without needing anyone else to maintain a version.

--------

[1] TFA doesn't state that this will be possible, but opening the API makes no sense if it isn't.

▲ pavon a day ago | parent | next [-]

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 functionality that isn't going away. The interface between the speaker and the cloud services that are shutting down is still undocumented.

[1]https://arstechnica.com/gadgets/2026/01/bose-open-sources-it...

[2]https://github.com/deborahgu/soundcork

	▲	EvanAnderson a day ago \| parent \| next [-]
		A comment here also says this is the case: https://news.ycombinator.com/item?id=46544001 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...
	▲	dspillett 18 hours ago \| parent \| prev [-]
		Ah, that makes sense as well. Not sure why I fixated on what the speaker might call out to, and didn't think of what might want/need to control the speaker.

▲ 0xbadcafebee a day ago | parent | prev | next [-]

One thing nobody is touching on: since it's not actually open source, when this thing is found to have dozens of security holes (or any bugs), they are not going to be patched.

( Their announcement: https://www.bose.com/soundtouch-end-of-life The API doc: https://assets.bosecreative.com/m/496577402d128874/original/... )

▲

fgeiger a day ago | parent | next [-]

Also, when the likes of Spotify change their APIs, the integration will likely stop working too.

	▲	nsteel 7 hours ago \| parent [-]
		Has that not already happened? Spotify recently broke streaming on a load of AVRs following the Anna's Archive release, I'd have thought this hardware would have suffered the same fate.

▲

Thaxll a day ago | parent | prev [-]

Ho no, XML.

▲ rcbdev a day ago | parent | prev | next [-]

IBM's opening of desktop PC standards also contributed a lot to computing.

Sometimes, an open API is all you need.

▲

LetsGetTechnicl a day ago | parent [-]

It was reverse engineered, not opened by IBM

▲

aeyes a day ago | parent [-]

No, they published schematics and full BIOS source code.

But it was not libre, they held the copyright to the source code. So to get around this, competing companies wrote a spec from the source code and then had another team which never saw the code implement a new BIOS from the spec.

	▲	cromka a day ago \| parent [-]
		That's exactly what blackbox reverse engineering is.

▲ samrus a day ago | parent | prev | next [-]

Yeah but writing that backend app will be much much easier now

▲

ahepp a day ago | parent [-]

It’s a very nice thing to do, but from what I have read it is very much not open sourcing anything.

Maybe that distinction is too arcane for general technology audiences, but I don’t really think it is?

	▲	spencerap a day ago \| parent [-]
		The Verge's headline is misleading > Bose is open-sourcing its old smart speakers Bose, though, makes a more nuanced distinction in their announcement, which is linked to in the article > Open-source options for the community \| We’re making our technical specifications available so that independent developers can create their own SoundTouch-compatible tools and features. Bose never claims they're making the speakers open-source, it's lazy reporting by The Verge. They're just making it a little easier for the community to build stuff if they want. While actually releasing the source code for the speakers would be best, there might be some legitimate business concerns. To me this is a step in the right direction, and their official announcement accurately represented that.

▲ danw1979 a day ago | parent | prev | next [-]

The question on my mind is will the SoundTouch app continue to be supported on new mobile OS versions ?

Is it the same app that caters for other speakers too ? If it is, and Bose continue to include their old speakers on the functionality of the app, then I can hardly see how this is a true EoL. They’re really continuing to support the speakers in their app, at least.

	▲	0xbadcafebee a day ago \| parent \| next [-]
		They're discontinuing support for SoundTouch Speakers. The SoundTouch App controls SoundTouch Speakers. Put two and two together... From their announcement: `What will no longer work: • Presets (preset buttons on the product and in the app) • Browsing or playing music services directly from the SoundTouch app Important note: Your system will no longer receive security and software updates. Please make sure to always use your system on a secure, private network.`
	▲	egwor a day ago \| parent \| prev [-]
		Considering that new speakers don't use SoundTouch, I wonder too. I hope that they keep the app running for a while. This kit is expensive and it can't have a short life time!

▲ kitesay a day ago | parent | prev [-]

They are claiming open source, without doing it.

Reality: users are still getting a feature cut with an update.