As part of contributing to the Multiroom Audio app it annoyed me how much of a PITA it is to add bluetooth audio devices to home assistant for music or TTS, i was having to add and remove them constantly for testing.
All i could find were articles about how to use bluetoothctl and found that to be less than a friction free experience.
manage devices you will use with other addons (sorry apps) like VLC, multiroom audio, squeezelite, etc
What does it do:
Manage which BT adapter will be used for this purpose (i recommend dedicating an adapter but it should work well with any you have doing BLE/beacons etc)
lets one discover and pair A2DP target devices (speakers, headphones)
it ensure that pulseaudio is configured correctly for each device
provides various options for letting the device sleep or forcing it to remain on
enables hardware vol buttons to work on devices that didn’t have local overrides
provides a per device Music Player Dameon (intended for testing and TTS) for music i recommend Multiroom Audio coupled with Music Assistant
What it doesn’t do:
Fix devices that just have issues with BlueZ (linux BT stack)
HSP/HFP profiles
Microphone support
let you join A2DP sources
work with multiconnection devices (maybe i can be persuaded to add that)
For those of you that made it this far, I am intrigued to see if this app survives its first encounter in the wild with real folks, feel free to submit a bug about the software, note i suspect most bugs will be device specific and upstream with haos or bluez - but we will see.
Your questions section seems a little aggro.
In the spirit of open source and sharing, given you have said you used assistance, could you include your conversation and sources so others can duplicate it without having to reinvent the wheel?
Maybe they can build and expand it.
good point i shouldn’t have cut and paste my reddit post where those questions were to head off all the replies the anti-ai-tedious post, I will remove
sources, what are you talking about? - thats normal stuff like bluez source code, puleseaudio source code, haos source code and the dev documenation for all 3, nothing special
and no i have no plans to post any chat histories and don’t have most of them, if you are interested in how it evolved, its all there in the code and PR summaries, why would anyone need to ‘re-invent the wheel’ or ‘build it’ - its a wheel thats already built, happy for people to do good PRs or fork as they see fit, maybe you are not used to how OSS works?
Hello,
I’ve tried 1.50 release yesterday, it found my JBL 110 partybox, connected and looks fine. I couldn’t find System → Audio , nor any media player entity, so i had to do MDP integration to get it playing. A bit of a hassle but yeah, it worked.
It plays music, but sometimes it cuts off for a few miliseconds, each minute more or less.
I was testing with built-in bluetooth on Rasp4, with passive scanning.
I was about to connect a Xiaomi bluetooth adapter for 3.5mm jack to my audio system, so I can stream radio from HA. But i found it’s easier to connect my tablet (I have fully kiosk browser) to BT device and stream via media.player from the tablet
What’s new in 2.0 release?
