I’m having a few teething issues getting Mycroft to start at boot, but they seem different to those mentioned here.
There are two issues I would be grateful to have some advice on:
#1 - I’ve made a systemd service (shown below), and Mycroft starts at boot, but there’s no sound - it appears to be a permissions issue accessing ALSA?
The error that shows up is the below, but the other symptom is that there’s no mic level shown in mycroft-cli-client.
2022-03-18 20:45:54.753 | ERROR | 969 | VolumeSkill | Couldn't allocate mixer, ALSAAudioError('Unable to find mixer control Master,0 [default]')
My systemd service is pasted below:
[Unit] Description=Mycroft AI After=alsa-restore.service network-online.target Wants=network-online.target [Service] User=pi Group=pi WorkingDirectory=/home/pi/ ExecStart=/home/pi/mycroft-core/bin/mycroft-start all ExecStop=/home/pi/mycroft-core/bin/mycroft-stop Type=forking Restart=no [Install] WantedBy=multi-user.target
If I run mycroft-start from the command line, I have no issues… (outside #2 below, which I don’t think is related to this) I’m guessing permissions for audio, but I’m not really sure how to start troubleshooting this?
#2 - The Mark 1 enclosure will not work right unless I launch it after the bus is booted. If I use:
Then the eyes / mouth / etc don’t work - I get an ‘Attempting to use a port that is not open’ error in the 'enclosure.log file. Simply starting the bus first, allowing some time, then starting everything, works fine:
mycroft-start bus sleep 10 mycroft-start all
The above workaround is totally fine for me - I can write a wrapper script for the 3 lines above, and use that as the start script for Mycroft, but I figured perhaps someone else has come across this issue and may have some advice on a better way to tackle it?
Thanks in advance for any help - I’ve had a lot of fun dusting off my Mark 1 and seeing the general improvements in the Mycroft ecosystem!