Cant get Snapclient config to work the same as CMD

[siparker]

I am trying to have the output from snapclient work at the same time as still allowing notifications from rhasspy

I can start snapclient using

snapclient -h 192.168.1.20 -s 3 --player alsa

it will start and play the audio out of my snapcast server at the above host. Specifically it will also allow Rhasspy to play at the same time.

If i start the snapclient service with the following options

SNAPCLIENT_OPTS="-h 192.168.1.200 --user=pi:audio --player=alsa -s 3"

Then the audio from snapcast server will play but it prevents the rhasspy output from working at all.

I have tried pretty much every solution i can find over the past 4 weeks now

My snapclient runs as my pi user and group as it would not work normally otherwise. I had to edit the systemd entry for this to work.

It also works in the same way from command line with --player pulse. but again not from the config as a service

Just to summarise. snapclient works and plays my music from the server. but when started with systemctl it wont mix its own output with the rhasspy output.

If i start it from command line then it will play audio and allow the rhasspy playback at the same time.

Any ideas at all please? im sure its some sort of obvious permissions thing somehow but i have tried everythign and cannot get past this hurdle.

Hardware is a rpi 4 and a generic usb soundcard.

[siparker]

I have now found half a workaround for this.
I wrote a bash script to start the snapclient and then added a line to run this in /home/pi/.bashrc
Im sure there is a much simpler way to achieve this but at least it works for now, although if i ssh into the pi then it starts a second snapclient instance and gives an interesting phasing sound to the audio.

It also appears that snapclient works alongside the voice assistant as long as its running as root. if it is run as non root then it does the same as when it runs as systemd service