https://www.bose.com/soundtouch-end-of-life
SoundTouch API Documentation (pdf) linked from the announcement:
https://assets.bosecreative.com/m/496577402d128874/original/...
More companies should follow this approach - especially as right-to-repair becomes a bigger issue.
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: https://web.archive.org/web/20251201051242/https://www.bose.... https://arstechnica.com/gadgets/2025/10/bose-soundtouch-home...
They received the backlash, they responded to it by properly addressing the criticism and doing the right thing. It should be praised. Especially since it wasn't some PR-centric damage control, but an actual direct address of the specific points their original approach was criticized for.
Compare Bose's response to that of Sonos (another large techy audio brand). Sonos had an absolutely massive backlash recently (within the past few years iirc) in regards to deprecating software support for their older speakers that I'd read about everywhere (including HN) for months and months.
Afaik, it didn't lead to Sonos doing the right thing in the end (unlike the scenario at hand here), despite the online outrage being way more widespread than in the Bose's case.
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.
If your belief is that some other tactic works, then I can see why you'd do that. For my part, carrot + stick has always worked better than stick + more stick.
When presented with information that you're acting in bad faith, if you choose to change: that is praiseworthy.
It's very brave to take that in, and not worry about "brand damage" or "appearing weak". It's brave to even challenge yourself when someone tells you you're wrong. It's entirely admirable.
It's the default human behaviour to double-down.
I'm not sure I get the logic here.
Slowly but steadily I'm comprehending why companies are getting tired of some people. No matter what companies do, people will always complain. Don't get me wrong, there's always room for more improvement, but a slight complement for their slight improvement won't hurt anyone + a change in tone from complaining to suggesting improvements would be a nice bonus.
Also remember that there is no believer like a convert. A community helping guide a company towards open source culture could make for a very strong ally.
Then again I know nothing about Bose’s open source culture so take it with a grain of salt.
Isn't that still gonna happen now?
From [1]:
What will no longer work:
• Presets (preset buttons on the product and in the app)
Of course Bluetooth and AirPlay continues to work, but isn't that what a "dumb speaker" is?
That's a good outcome for the community, and refusing to "praise" Bose's actions just because they didn't originally do what you wanted is petty and churlish.
"Bose blows" is a popular comment amongst the audiophile community but, to me, it seems like they don't blow at all[0]. In fact quite the opposite: this is a fantastic example for other companies to follow. Top marks, Bose!
[0] What is actually true is that they are opinionated about sound reproduction in ways that a bunch of people don't agree with but which in the right context are often effective and enjoyable to listen to.
> Uhhh I’m gonna tell all my friends to stop eating there
I have decided to not spit in your food after all. Praise me.
I'd avoid, even if they happened to do this.
Maybe the general rule should be like, if something isn’t in the users control and the user doesn’t want it anymore or can no longer function despite not being damaged, then the company should take back the hardware and refund the user.
So the company still have two options, either refund or open-source the systems needed for the device so that the user or third-party can continue supporting it.
...
Planet is burning and the zillionaires have enough zillions already so I vouch for the Mando too.
Once single EU / US legislation introduced that force manufacturers into opening end-of-life products all IP right owners will either immediately make it possible or go out of business.
Since everyone will be forced to do the same no one will gain any advantages.
Or across the board, since they are absurdly powerful right now. Nintendo could not legally keep you from hacking a console before the DMCA.
At least people can create their own implementation of the API tho.
No, the law must mandate that. You either provide active support, or if you end it you must open-source all tools necessary to perform maintenance. It's one of those things that has to be mandated by law to provide a uniform floor on all companies and manufacturers, like food safety laws, fire codes, or accessibility for the physically disabled.
I do not get why not more companies are doing this! Also it pays so much into your brand perception etc.; also you will always have all ecological folks on your side because of "not producing new stuff".
This is the cheapest and best way to get the most out of your investment after it entered end-of-life.
I loved their camera tracking and picture frame along with their speaker quality.
I am no fan of Bose for a lot of reasons, but this is seriously standup behavior for sure.
Plus, I purchased my product thinking it will last forever. Sudden announcements for EOL is a terrible trend. Laws should regulate having proper disclosures that a product is promised to be serviced for x number of years at minimum, and/or mandate manufacturers themselves provide updates to allow the product to work independently of them.
> 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.
[1]https://arstechnica.com/gadgets/2026/01/bose-open-sources-it...
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...
( Their announcement: https://www.bose.com/soundtouch-end-of-life The API doc: https://assets.bosecreative.com/m/496577402d128874/original/... )
Sometimes, an open API is all you need.
Maybe that distinction is too arcane for general technology audiences, but I don’t really think it is?
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.
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.Reality: users are still getting a feature cut with an update.
* Removing cloud-server dependency from the app.
* Publishing API documentation for the speaker.
I actually think this is worth noting not so much in a "well aktshully it's not open source!" kind of way, but as a good lesson for other manufacturers - because this is meaningfully good without needing to do any of the things manufacturers hate:
* They didn't have to publish any Super Secret First or Third Party Proprietary IP.
* They didn't have to release any signing keys or firmware tools.
* They get to remove essentially all maintenance costs and relegate everything to a "community."
But yet people are happy! Manufacturers should take note that they don't have to do much to make customers much happier with their products at end of life.
On that case, no, that wouldn't make me consider buying them. Because the one I can buy lacks exactly the feature that would make me consider it.
E.g.: https://www.audiosciencereview.com/forum/index.php?threads/b...
I hope Bose continues to do this for future products and is rewarded financially for it.
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 connect that way.
Stay away from Sonos.
The quality of the software, and the fact that it isn't really updated, is another thing, but the actual software availability is there.
Also FWIW first step for QC35 support on https://gadgetbridge.org/gadgets/headphones/bose/?h=bose which is IMHO the way to go.
When my kid was born, I bought a brand-new Snoo. After six months, I wanted to sell it since we no longer needed it. That's when I discovered stories of people whose used Snoos had been bricked by the company. For such an expensive product, that is such a waste. If I'd known about this beforehand, I never would have made the purchase in the first place.
It sounds like there are two main pieces to me:
1. Removal of cloud dependency
2. Making usable the API (and providing documentation)
With a minor 3rd piece:
3. The official app will be updated to support the "offline" mode without losing as many features as possible now that the cloud service is going away.
All very laudable things IMHO. I'm actually going to buy one of these
This is making them controllable.
The headline may be inaccurate, but I'm not clear on what source code you'd even want. To the firmware do you mean?
A documented API seems like the most useful option here.
I assumed they meant the firmware, and was quite surprised they would do that...
Secondly, these devices are basically one step above embedded. It's highly unlikely you can load and run anything custom on them.
Since they are opening up the API, you can keep using them for what they were made for, which is at least a solid basic liberty
Seeing that, I expected the ability to build and run a custom firmware, like with an Android device with its bootloader unlocked. But it is not that, and they didn't open source their app either.
What they did is that they removed dependence on their servers, and opened their device to be controlled by third party apps. That is, they let users use their device past its end of life, including when the first party app will stop being maintained, but not to the point of letting user add features.
In understand why they would do that, they don't want users to backport features only available on their latest models that are sold at a premium, therefore competing against themselves. After all, the value in smart speakers is not the sound producing device, which I think is a problem that has been solved more than a decade ago at the consumer level, it is all about software features.
Evolution v. Revolution. I'd prefer the latter, but realistically the former is the more likely to succeed short of people like us getting control of regulatory bodies and forcing it.
Unless you want to actually develop ON the device (and build binaries etc...), this completely allows you to use the device and connect it to whatever, so I don't know what more we should expect.
No one else is doing this, so yeay applause
https://github.com/captivus/bose-soundtouch
This library provides a clean, Pythonic interface to control SoundTouch speakers over your local network, ensuring your speakers remain fully functional even after cloud services end.
Lyrion Music Server (LMS) is a streaming audio server supported by the LMS community and formerly supported by Logitech, developed in particular to support their Squeezebox [discontinued in 2012] range of digital audio receivers.. [LMS] also works with networked music players, such as the Roku SoundBridge M1001, Chumby, O2 Joggler, RPi and the SqueezeAMP open source hardware player.Is that a word? Seems interesting but never read it before.
> 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 accessible via some bose developer portal. It doesn't seem like they are open sourcing anything. This API just allows you to make basic requests to do things like change volume on the speaker.
To support the smart features of the SoundTouch speakers, we would the soundtouch user management service. Speakers connect to this very frequently and its where refresh tokens for music services and presets are stored. The speaker firmware itself has lots of source code, including the bit to handle music services and playback. There is an abstraction layer for music service APIs. There is a process on the speaker that reaches out to a music service registry, which is an index of bose music service adapters. Each of these adapters essentially proxies a music service like tunein, spotify, and even the "stream a custom station" feature.
If bose open-sourced the speaker firmware, we could make a firmware build which talks to a 3rd party user management service, and reaches out to a 3rd party music service registry. Then we could add and maintain music service playback for the community. But there is no open sourcing of any actual code here and this soundtouch web api cannot change the URLs on the existing firmware of the user management service or the music service registry.
So to my eye this story seems misleading and just some PR nonsense. It's a little frustrating reading all of the "great job, Bose!" comments here like anything was actually done... Disclaimer: I used to work at Bose.
One time I got a free Harman Kardon bluetooth speaker from Microsoft (the Invoke from 2017). They were $100* but went on sale for $50 and I snagged one.
Then Microsoft discontinued Cortana for it, but they didn't kill the speaker. They released firmware that turned it into a perfectly good bluetooth speaker (which I still use today.) And they sent me a $50 gift card* to buy something else from Microsoft. Good will! I was a big fan of Microsoft hardware. Shame about the software...
* Apparently $200 initially but they had some steep sales because Cortana as a voice assistant wasn't reviewing well. Reviews are a bit negative on the sound quality. Probably true enough at $200, but for $0-50, I think it's actually really good sound quality.
I was the engineering lead on that product, and built a SW platform from scratch for it (Microsoft provided an SDK to Cortana which they developed in parallel.)
The internal build could actually run Cortana, Alexa and Google Assistant simultaneously and you could e.g. set an alarm with one of them and query it with another, and they could interrupt each other based on priority. Obviously nobody wanted that feature, but it was hella cool that it worked. Oh, and you could make Skype calls from across the room, and the microphone array lived up to Skype's tough certification requirements which took weeks of testing in Microsoft's anechoic chamber for the DSP/algorithm team to fine tune.
I tried to push for open-sourcing the platform but it was tricky because 1) the director of engineering in Harman didn't know what open source meant and for a hardware focused business to understand the value was a hard sell, 2) it used a HW module that came with a SW stack I mostly got rid off but a few parts were remaining that would need to be replaced which would require additional resources, 3) I was burned out at that point and had limited energy left to fight the good fight. Really too bad, it could have been a cool voice agent development platform, and I honestly think it would have sold in large volumes as a developer-friendly device.
Glad you like it, sorry about the remaining Bluetooth bugs nobody got around to fix, since it basically flopped instantly.
Now there used to be a way to play music (notifications, if I remember correctly) directly to the speaker, but that required an App_Key. Bose stopped handing out App_key's quite a while ago when they shutdown down their developer forums, see also: https://www.reddit.com/r/bose/comments/102ptjg/is_there_any_...
https://assets.bosecreative.com/m/496577402d128874/original/...
From a quick glance it looks like you are just able to do high level playback controls, similar to what you'd do using their on-device UI. Perhaps that's enough?
Why would I buy something that a vendor intends to kill off in an attempt to make me buy again?
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.
I'll admit, I don't want or use 'smart' anything, and am currently trying to disable smart devices that were already present in my home from the previous owner.
Being able to say “play this stream in room 1,3,6 and this in room 4 and nothing in room 2,5,7” is a valuable feature for people who don’t live alone in a studio flat.
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 better than they were on stock firmware. eBay prices are probably going to double by tomorrow morning.
Maybe in an era where software can be carefully engineered to a point of actual completion it will make sense, but for now it’s mostly stupid.
Open sourcing potential ongoing support and tinkering is good, but it doesn’t get the core problem that it wad probably never the right thing to put the smarts in the speakers in the first place.
The trends decide the standard. Many EVs use 18650 but I can see that for competition and weight reduction they may switch to a more proprietary standard like blade batteries in BYD for competition. It all depends on where the competition is going with it.
For earwear, I would say that portability and weight is a big area for competition.
Sometimes companies fuck up, what's really refreshing is to see a company backpedal on a shit choice, and decide to do better. Nicely done Bose!
Still a fantastic multi-room setup to this day... I run a server as well as a client from a Raspberry Pi.
I assumed it was probably discarded due to the frequent situation here, of student who is moving away, and who doesn't want the hassle or expense of moving things that don't fit in their luggage.
Now I wonder whether it was discarded because the owner heard it was being bricked, so not worth moving with them.
(Don't worry, I'm a curb Jawa master. I carried it home, realized it was IoT that required an icky closed app thing to use it, and so gave it to an MIT student. I just emailed them the URL of this good news. Possible bummer for the previous owner, though.)
Now will need to fiddle with your phone to connect with bluetooth or something.
Still, props to Bose for actively helping to keep their old devices usable.
Now users like me can't configure their devices (because the login is mandatory for using anything in the app). Some users report they aren't even able to use it with a VPN.
The over-reliance on closed source apps with mandatory logins for configuring devices you own must come to an end.
I've loved their product and support ever since. Glad to see this happening as well. Kudos.
In fact, given the full-throated open source nature of that platform (you can even build your own player with a raspberry pi[1]), I doubt I'll ever need to use anything else for the rest of my life for playing music in my home, even as my devices die and need replacement over time.
... which does make me wonder: that's great for me, but I can definitely see it as a deterrent for companies to do similar. If they want to make a competing future product, they'll be competing against an open-sourced version of their past selves, too.
* Is that what it's called? The top part that goes over your head...
- Python: https://github.com/captivus/bose-soundtouch - TypeScript: https://github.com/cssinate/bose-soundtouch
Bose official announcement https://www.bose.com/soundtouch-end-of-life
Applies to games, hardware, whatever - if it isn’t economically viable to run, let the users.
API docs probably wouldn't help here so much, as open sourcing it's firmware. One can dream.
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!
Has anyone found or started related github repos?
Has anyone read the API documentation EULA and can comment on if it really meets some recognizable standard for "open source?"
I think I bought one of these ten years ago.
My parents' sound system is from the mid 90s
Shame on you, Google. You disabled my Nest thermostat and Nest Secure alarm — I will never buy your products again.