Live data from Hacker News

Bose has released API docs and opened the API for its EoL SoundTouch speakers

arstechnica.com

261–270 of 416 posts

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#261
post #225
post #8

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.

Bose should not receive praise for this move. Bose only took this action after community backlash. In an older version of their end-of-life announcement, most functionality of the speaker systems would have removed and transformed the devices into dumb-speakers/amps. Good that they changed their statement and took the right action. Even better for the community for stepping up and 'forcing' Bose to do so. Sources: ht…

Don't punish the behavior you want to see. Would we rather they defaulted there? Sure. But it's arguably an even better signal to see that they're willing to listen to their customers even when there is no direct financial incentive for them.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#262

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…

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/... )

Ho no, XML.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#263

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 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

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#264
Well done Bose! This puts you higher on the list for my next purchase.

I don't understand why so many comments here are negative. This is a nice move, and Bose should be thanked and encouraged to do similar moves again. It's a step in the right direction!

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#265
post #252
post #225

Earlier quoted context omitted.

Bose should not receive praise for this move. Bose only took this action after community backlash. In an older version of their end-of-life announcement, most functionality of the speaker systems would have removed and transformed the devices into dumb-speakers/amps. Good that they changed their statement and took the right action. Even better for the community for stepping up and 'forcing' Bose to do so. Sources: ht…

> Bose should not receive praise for this move. Remind me of any other vendor in recent history that end of lifed a hardware product and then open sourced it whether they got backlash or not. Because I can’t think of a single one. So yes, Bose absolutely deserves praise.

Arguably HP open-sourced webOS, but they did also got backlash because they killed that entire product line without warning.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#267
post #157
post #102

Earlier quoted context omitted.

I have my fathers Sonos soundbar and a pair of speakers at home that I bought for him as Christmas gifts years ago. I still can't believe they knowingly released an app that bricked older devices. I have to try and get them working again. The only solution I've heard of is to get an old version of the Sonos app APK, a dedicated old single purpose Android phone to acts as a bridge between your speakers and phone and c…

I have 2012 Sonos hardware. You can still get the original Sonos S1 controller, which works with old stuff. It's pretty annoying that all the new stuff is S2 (and that app is better supported), but it's not as hard as you're describing it. You can get it off Google Play and just use it. The quality of the software, and the fact that it isn't really updated, is another thing, but the actual software availability is th…

_Some_ of the software is there. They randomly intentionally broke the desktop apps for S1 devices.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#268

From https://www.bose.com/soundtouch-end-of-life : > 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. The documentation is available here: SoundTouch API Documentation ( https://assets.bosecreative.com/m/496577402d128874/original/... ). AFAIK, the soundtouch web API was already acce…

[deleted]

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#269
post #225
post #8

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.

Bose should not receive praise for this move. Bose only took this action after community backlash. In an older version of their end-of-life announcement, most functionality of the speaker systems would have removed and transformed the devices into dumb-speakers/amps. Good that they changed their statement and took the right action. Even better for the community for stepping up and 'forcing' Bose to do so. Sources: ht…

Well they still did it, thus praise (though less effusive than if they had just done it initially).

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#270
post #225

Earlier quoted context omitted.

Bose should not receive praise for this move. Bose only took this action after community backlash. In an older version of their end-of-life announcement, most functionality of the speaker systems would have removed and transformed the devices into dumb-speakers/amps. Good that they changed their statement and took the right action. Even better for the community for stepping up and 'forcing' Bose to do so. Sources: ht…

Don't punish the behavior you want to see. Would we rather they defaulted there? Sure. But it's arguably an even better signal to see that they're willing to listen to their customers even when there is no direct financial incentive for them.

Their financial incentive is negative. They were hoping to force everyone to buy new speakers, driving sales. But if the community is able to get open source firmware to run spotifyd on them, there is a non-zero (not everyone, but it's non-zero) amount of people that will just not buy new speakers from them.
Post reply on HN