-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration tts_bluetooth_speaker not found with more recent home assistant core versions #19
Comments
Thanks @miikama for the detailed message, I was able to add tts_bluetooth thanks to you ! But when testing with the service Text-to-speech (TTS): Say an TTS message with google_translate, no sound is outputting... Is it working for you ? I can output audio from my BT speaker with the mplayer -ao pulse::bluez_sink command, so the device is behaving correctly on the Debian host Thanks for the help you already provided and maybe the help you could provide :) |
The module seems to use two command line utilities, Which environment are you running the homeassistant on? Is it the docker container, the home assistant operating system on raspberry pi, or the home assistant installed in a python virtual environment? I am running it from a Python virtual environment so it is not containerized. If you are running it in a container, can you also run the |
And to answer your question @archit3kt , I am actually able to use the TTS to output speech from the speaker :) |
I'm running HA in supervised mode on latest Debian 11, to stay in a supported environment ! Indeed the amd64-hassio-audio container, which configure all the audio stuff, wasn't getting the bluetooth conf from the pulseaudio host... I could configure the conf file inside the container to access the bluetooth sink, but the conf would be lost at every reboot. I went another way and installed mpd on the Debian host, configure it to use the pulseaudio bluez sink on the host, and configure HA in this very simple way : `media_player:
Now it is workiing like a charm, this page gave me the right instructions to add the BT player on the host, and mpd is doing the rest :) Thanks for your help, was appreciated ! |
I'm on the same boat, just not as advanced as you. I can get audio via bluetooth, but not tts. |
Hey @elektrinis, I followed this guide until point 5 included, so bluetooth audio was working on the Debian host. pactl list sinks is listing correctly : bluez_sink.11_75_58_9D_B7_73.a2dp_sink I installed mpd and configured /etc/mpd.conf with the following : audio_output { Ofc enable and start the service, that's all on the Debian part. Connect to your HA instance and add to configuration.yaml : media_player:
It will connect the mpd HA object to your mpd server on Debian host. You can then use this mpd object to play audio files in HA. For TTS, don't forget to configure it in the configuration.yaml : tts:
or if you like marytts like me and you run the container to get local voice generation on your debian host : tts:
Should be working after all this :) |
Or as the simplest way to output audio to a bluetooth speaker, this is through the Mopidy addon, where we select a bluetooth speaker from the list as an audio output. in configuration.yaml, we add
for example, audio output via a portable bluetooth speaker using a local rhasspy voice assistant with Silero TTS Service speech synthesis
|
Unfortunately it did not work. Not sure if HASS 2023 or 2024 has more changes, but I still get this:
Anybody knows where to look? |
I have
hass
version2022.3.1
I had some issues when adding the tts_bluetooth_speaker as a custom component. I manually added the component into the configuration.yaml as
After adding, and checking the configuration
The component should be at the correct location
(env) homeassistant@raspberrypi:~/.homeassistant $ ls /home/homeassistant/.homeassistant/custom_components/tts_bluetooth_speaker/ __init__.py manifest.json media_player.py
It seems that more recent hass versions require a version key in the custom component
manifest.json
file.See e.g. https://community.home-assistant.io/t/no-version-key-in-the-manifest-file-for-custom-integration-environment-canada/311313/7
Also, the class
MediaPlayerDevice
has been renamed toMediaPlayerEntity
. See https://community.home-assistant.io/t/media-player-not-working-after-upgrading-to-2022-2-6/391841.The
tts_bluetooth_speaker
component can be loaded after updating the filemedia_player.py
The text was updated successfully, but these errors were encountered: