logoalt Hacker News

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

2491 pointsby rayreylast Thursday at 3:07 PM388 commentsview on HN

Comments

yoavmlast Thursday at 10:13 PM

After my last Sonos, I gave up on smart speakers. Recently I discovered Squeezelite-ESP32 / piCorePlayer and I'm not going back. I'm free to choose my own speakers (and people sell great 2nd hand dumb speakers for nothing!), I can stream, sync, etc - and they integrate great with Home Assistant. No more proprietary protocol for me, thank you...

borborigmusyesterday at 7:30 AM

If the software gains traction in a public git repo this could be a good purchase for someone wanting a cost effective, great sounding, customisable, retro styled speaker.

crablyesterday at 6:38 PM

i'm curious to see whether this creates a large secondary market for EoL'd devices!

dashzebralast Thursday at 8:22 PM

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!

calflegallast Thursday at 6:46 PM

The arguments in this thread about sound quality crack me up. Reminds me of when a famous mix engineer was in a best buy and the guy said 'These sound just like it did in the studio!' He said, no it doesn't. We used NS10s.

wkoszeklast Thursday at 8:29 PM

This is an amazing idea - whoever came up with it, should get a promotion. I'd not be surprised that if this continues, Bose could be what e.g.: ThinkPad became and will have a steady customer and fan base

0xWTFlast Thursday at 5:10 PM

Really glad to hear this, I've been so close to throwing out my SoundTouch 20, which makes me sad because it looks great and sounds better than my Google Nest speaker (placement issue? hard to say).

Has anyone found or started related github repos?

zippyman55last Thursday at 4:44 PM

I am not a big fan of Bose for personal reasons, but they get my respect for this action.

smallvariancelast Thursday at 3:45 PM

Great move Bose! I hope this trend continues - it's really nice to see a vibrant market for used/vintage electronic products in some categories (e.g. old iPods) rather than them just contributing to more e-waste.

hardlianotionlast Thursday at 5:23 PM

Something Sonos could learn from perhaps (sorry - I have an interest here).

onemoresooplast Thursday at 3:48 PM

I think it would be a good idea to tax companies significatnly when bricking their devices, it's creating e-waste. Open sourcing them like this would be a way for them to avoid fines.

wg0last Thursday at 4:51 PM

This is where EU needs to put its weight and at least in Europe - if you sell something but not willing to support - open source client, server and device all sorts of software.

teejmyalast Thursday at 5:08 PM

I really hope Logitech is paying attention, because when Harmony finally dies, I'm not sure how I'm going to replace it.

lysacelast Thursday at 3:42 PM

The released documentation:

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?

show 2 replies
NL807last Thursday at 9:21 PM

Legends. Open source, create a community of hackers around your products, everyone is happy.

GaryBlutolast Thursday at 5:34 PM

I wish Apple did this with the older iPhone models that can't even connect to cellular networks anymore.

dathinabyesterday at 11:38 AM

love it, but I'm surprised after the experiences I had with Bose in the past

fkarglast Thursday at 3:23 PM

it's sad that this is not the default behaviour. hopefully the stop killing games movement will put something similar into law with potentially further-reaching side-effects eventually. Because frankly, sunsetting products like this should be common sense, not the exception it currently is.

MSFT_Edginglast Thursday at 3:21 PM

Some good news

aizklast Thursday at 9:18 PM

Sadly this is not the norm, but this is a great step in the right direction.

benttlast Thursday at 5:23 PM

Take that Sonos!

stivatronlast Thursday at 5:50 PM

That's very good, props to Bose.

kn100last Thursday at 6:18 PM

and suddenly Bose is on the list of consumer products I will consider for my home. Good job!

eductionlast Thursday at 5:11 PM

On the one hand it’s great Bose is doing this — on the other it sucks that this is so remarkable. Having stuff you bought that does not actually need the cloud continue to work should be the default.

fallatlast Thursday at 7:12 PM

How do I upvote 3 times

orefalolast Thursday at 5:36 PM

Great move Bose

Shame on you, Google. You disabled my Nest thermostat and Nest Secure alarm — I will never buy your products again.

cantalopeslast Thursday at 6:18 PM

Finally someone!

gigel82last Thursday at 11:25 PM

Ooh, I might consider actually buying Bose products now. Way to go!

css_apologistlast Thursday at 6:43 PM

this should be required by law

sublinearlast Thursday at 5:44 PM

This is a great PR move for Bose in a market that doesn't care about name brands like it used to. Maybe they can win some customers back and be considered cool again.

d--blast Thursday at 4:33 PM

"Smart" things get old quickly...

I think I bought one of these ten years ago.

My parents' sound system is from the mid 90s

idiotsecantlast Thursday at 4:25 PM

The headline is somewhat questionable, but that's not Bose's fault.

mrcwinnlast Thursday at 4:06 PM

Good job Bose!

hktlast Thursday at 4:01 PM

I'm glad this has happened, but I'm be gladder if this was a legal requirement.

ForHackernewslast Thursday at 3:22 PM

Good for them! I own two sets of noise-cancelling Bose headphones and a (dumb) speaker, and they've all been pretty solid, and for half the price of equivalent Apple headphones.

show 1 reply
adolphlast Thursday at 6:05 PM

ianal and kudos to Bose for their relatively graceful hardware depreciation approach and releasing their API documentation; the license for said documentation does not appear to be easily recognized as "open source" by using a standard GPL, MIT, Apache, etc license.

Has anyone read the API documentation EULA and can comment on if it really meets some recognizable standard for "open source?"

bschmidt240yesterday at 3:43 PM

[dead]