libsoundtouch
libsoundtouch copied to clipboard
CharlesBlonde
Is it dead?
It certainly appears that way. I'd really like some updates but it looks like the original developers have moved on. It might be up to us users to try and dig in, I have limited time but will start reading the source.
I wrote a bose soundtouch asyncio library a while ago, hoping to integrate it into homeassistant. For some reason this library was chosen in favor of mine.
I think only missing feature is multi-room. As I only have one, there's no way for me to implement/test this feature.
https://github.com/trunet/aiobosest
I could help with testing @trunet and @schneekluth as well as he seems to have a multiroom setup (according to his HA activity :) ). So if you have a custom HA component using your lib, I'd be happy to test
I only wrote the library. Component will have to be coded.
I think the multi room setup would have to be implemented anyway. Iām not sure if homeassistant would like to implement a new component version with less features.
@trunet if you would be willing to update your lib and keep it maintained, it seems that the HA guys would be willing to switch, since libsoundtouch seems to be dead. Got this reply in a HA PR where I mentioned your lib.
If the maintainer of https://github.com/trunet/aiobosest is active and the maintainer of https://github.com/CharlesBlonde/lib soundtouch is not, I suggest we change to the active library.
I'm willing to update it. I think first step would be to write a HA module. After implement multi room/speaker support.
Hi Guys. Sorry I have been so quiet on this topic after making some good progress. Note that I have posted a zip file with my changes to libsoundtouch here https://github.com/kalkih/mini-media-player/issues/155#issuecomment-538826712 I am quite happy with the way its working and anyone is welcome to continue from there. I am also happy to test this alternative implementation but I am very short on time right now because work is relocating me to Dublin Ireland. I might have time in about 3 months to get back involved.
I only wrote the library. Component will have to be coded.
I think the multi room setup would have to be implemented anyway. Iām not sure if homeassistant would like to implement a new component version with less features.
@trunet I quickly went over your source code, it looks like you handle all sources the speaker handles, right ? libsoundtouch only handles AUX and Bluetooth.
I have 2 Soundtouch 10 and a Wireless Link adapter and would be very happy to contribute.
@trunet I quickly went over your source code, it looks like you handle all sources the speaker handles, right ? libsoundtouch only handles AUX and Bluetooth.
yes, all sources reported by the speaker will be made available.
I have 2 Soundtouch 10 and a Wireless Link adapter and would be very happy to contribute.
any help is welcome.
I'm willing to update it. I think first step would be to write a HA module. After implement multi room/speaker support.
@trunet How would we go about that ? I'm not skilled enough as a developer to start a whole new module. I was however able to adapt the existing module to handle AUX and Bluetooth source, see https://github.com/home-assistant/home-assistant/pull/31669
I'm new to Python programming, but I'll happily aid wherever possible with some guidance.
First step though, I assume github dosen't "move" ownership from unmaintained packages? If not, first step would be to formalize a fork. Question is who is who can take lead on the technical maintaining and coding - @jpearce73 / @trunet seems to be the most enaged candidates? š
I'd be happy to participate but I don't think I have the time to lead this. It's two days before I was able to even reply to this! Also, I have no experience with git and workflows used in the check-in process, so I am not well qualified to lead it.
@jpearce73 I could take care of the overall management of the repo and the "gitting" / release management as well as testing, as long there's at least one person taking care of the code development š If you (or anyone else reading this) find the time and motivation further ahead - let me know š©
Just received a Bose SoundTouch 300... Firmware was from 2016... so I updated it not knowing this was going to break it (I run all IOT type stuff on a VLAN). After the firmware update, Home Assitant can't find it anymore (oh no!).
After digging into the issue, I came upon this chain - so is there any progress on this? It seems like some people know what the problem is - we just don't have it fixed...
Correct me if I am wrong, but basically, we need someone to volunteer to maintain a new fork of libsoundtouch?
Once forked, is there a known fix already for the VLAN issue among other things? Or is the VLAN a lost cause?
Also - I saw the comments about another option of using https://github.com/trunet/aiobosest instead...
So I guess another possibly earlier question is... should this be forked, or should the dependency be changed?
From what I've read some people have already gone around with this - but it doesn't appear anything came of it.
Thanks! DeadEnd
All,
As a temporary fix, I found this posting: https://community.bose.com/t5/SoundTouch-Speakers/SoundTouch-on-different-subnet/m-p/538532/highlight/true#M90188
I was able to set up Avahi-Daemon to do mDNS across my subnet, and then added a NAT rule - and it WORKED! The Bose ST300 can now be connected to via app and Home Assistant across the subnet without issue.
I would still like to help further development of the component and its dependent library if we can to get it up to do, but as a temporary (or possibly permanent) fix, I wanted to share this.
Thanks, DeadEnd
@DeadEnded you are awesome - thanks for sharing this š
I didn't know about aiobosest, is it compatible with all bose soundbars?
In any case, I would encourage you to fork this module into your own so people can gather around it and have access to a more updated software. I'll gladly contribute where possible.
Yeah, I checked out the existing forks.
Looks like there are half a dozen with updates to different things.
I expect if we merged all that together it would benefit.
Alternatively again, the aiobosest was updated earlier this year as well - so either approach would work.
Not sure how much re-writing the HA component would need to change the dependency - but I expect someone who knows what they are doing could get it changed over. Just a question of which approach is "better" - or more likely, which approach is whoever takes this over going to take :-)
Cheers! DeadEnd
Beyond this module, I think the HA soundtouch (which uses libsoundtouch) component needs some work to convert it to async https://developers.home-assistant.io/docs/asyncio_working_with_async/
Although this says the API is backwards compatible, I recall trying to make some changes and finding the methods could not be called. In the end I believe that the limiting case is the BOSE systems themselves are unreliable. I power cycle them every night at 3am to get a semi-reliable operation but I have become demotivated to keep trying to fix something on a shaky foundation.
Good sound engineers, poor firmware team :(
Hi, any news here? As communication stopped last year I assume the library is dead forever š¢
