Several Problems on Pi Zero: refresh audio recording, audio playing, wakeword and running as service

Hi,

Today my Seeed 2 mic array was delivered. So I installed the drivers, which are working.

What I’ve done so far.

  1. Install recent raspbian lite version
  2. install recent rhasspy version via .deb file
  3. create service to run rhasspy automatically on boot

Issues:

  1. When I choose Audio recording: arecord and hit refresh I get an timeout
  2. When I choose Audio playing: aplay and hit fefresh I get an timeout, too
  3. When I set porcupine as wakeword, I need as usual to save and then hit refresh, also here I get a timeout. So in fact its not possible to choose snowboy from this as example.
  4. When starting rhasspy via systemd it’s not working with audio. Either way not for recording nor for playing. It just does not work. When I stop the service and just run rhasspy manually, audio is working as expected. I have absolutely no clue whats wrong here.

/etc/systemd/system/rhasspy-satellite@rhasspy.service

[Unit]
Description=Rhasspy
After=syslog.target network.target

[Service]
Type=simple
ExecStart=/usr/bin/rhasspy -p de
User=user
Group=user
UMask=0002

RestartSec=1
Restart=on-failure

StandardOutput=syslog
StandardError=syslog

SyslogIdentifier=rhasspy

[Install]
WantedBy=multi-user.target

the weird thing is, that the user is part of audio group, so this should not be the problem at all.

Any ideas?

  1. Is solved. Found a hint here in the forum.

To solve it:
add: sed -i ‘s//dev/stdout//home/user/rhasspy.log/g’ “${conf_path}”
Just before supervisord will get started. e.g

trap finish EXIT
fi

# FIX
sed -i 's/\/dev\/stdout/\/home\/user\/rhasspy.log/g' "${conf_path}"


# Run assistant
log_path="${profile_dir}/supervisord.log"
pid_path="${profile_dir}/supervisord.pid"

echo 'Starting services...'
supervisord \
1 Like

Hi,

it’s interesting. It seems that Issue 1-2 were also related to issue 4. So now I can hit the “refresh” Button for audio input and output and it will find devices. :man_dancing:

Checked now for issue 3 as well. Result is: FIXED :smiley:

So if you also have a weird behavior, just check if #4 is also wrong for you.

Cheers & thanks for reading :wink: