Skip to content
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

Audio input\output devices not seen in the Rhasspy Home Assistant Add-on #316

Open
Yari117 opened this issue Feb 2, 2023 · 2 comments
Open

Comments

@Yari117
Copy link

Yari117 commented Feb 2, 2023

Hello there!
I have a Pi4 with Home Assistant OS installed.
I installed Rhasspy as an add-on from the add-on store, it starts fine and I can see the web-interface.
I planned on using a USB speakerphone device connected to the Pi. It was detected by the Pi after a complete reboot, and now I can select it in the device settings in the add-on configuration tab.
2023-01-28 01_07_22-Home Assistant

However, in the Rhasspy web-interface settings I cannot see this device, only the default ones
2023-01-28 01_01_58-default _ Rhasspy

I tried using all of them and the thing did not work. The wakeword is not recognized, nor does it recognize any phrases if I wake the system manually. For playback testing I tried using TTS and it does not work either.

I know this might be related to Docker configuration, but supposed since this is a Home Assistant add-on it was supposed to be tested with it and work by default....

The thing is that one cannot configure Docker through command line in Home Assistant OS, it is disabled. There is however an special command of
ha docker
which can do the following
2023-02-02 23_11_22-Terminal – Home Assistant

ha docker info
outputs the following
2023-02-02 23_12_21-Terminal – Home Assistant

Please help!

@DivanX10
Copy link

DivanX10 commented Mar 11, 2023

Depending on how you have HAOS installed, if HAOS is installed on Debian, you can do the following

Open client.conf and add

sudo nano /etc/pulse/client.conf

Instead of default-server = insert

default-server = unix:/usr/share/hassio/audio/external/pulse.sock 

In the autospawn line, put no instead of yes

autospawn = no

We lead to this view
image

Save client.conf, log out of root and restart pulseaudio from a non-root user

pulseaudio -k && pulseaudio --start

We reboot the Debian OS completely, after the sound and microphone from the built-in sound card or from the usb sound card will work in rhasspy, but unfortunately I can't transfer the usb bluetooth microphone, since the HFP/HSP profile is not available, although in Debian 11 this HFP/HSP profile works fine

You can read more details here

@r14n
Copy link

r14n commented Apr 17, 2023

Depending on how you have HAOS installed, if HAOS is installed on Debian, you can do the following

Open client.conf and add

sudo nano /etc/pulse/client.conf

Instead of default-server = insert

default-server = unix:/usr/share/hassio/audio/external/pulse.sock 

In the autospawn line, put no instead of yes

autospawn = no

We lead to this view image

Save client.conf, log out of root and restart pulseaudio from a non-root user

pulseaudio -k && pulseaudio --start

We reboot the Debian OS completely, after the sound and microphone from the built-in sound card or from the usb sound card will work in rhasspy, but unfortunately I can't transfer the usb bluetooth microphone, since the HFP/HSP profile is not available, although in Debian 11 this HFP/HSP profile works fine

You can read more details here

Thank you this helped me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants