-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Error when starting module #3
Comments
As a temporary workaround, running this fixes the sound:
|
Looks like the audio container changed recently: $ docker exec -ti hassio_audio pactl load-module module-suspend-on-idle |
Any chance to get an update? |
Finally solved the issue by applying: https://community.home-assistant.io/t/solved-hassio-audio-is-in-boot-loop-and-spams-my-syslog-with-errors/282538/93 |
I needed a different pulseaudio config, because it messes with my non-audio bluetooth devices. After lots of trial and error I settled for this solution injecting a shell-script into the hassio-audio s6 startup: #!/bin/sh
# disable bluetooth module
sed -i -E 's|(load.+bluetooth-discover)|#\1|' /usr/share/tempio/system.pa
# enable suspend-on-idle
grep -q -F "module-suspend-on-idle" /usr/share/tempio/system.pa || \
echo "load-module module-suspend-on-idle" >> /usr/share/tempio/system.pa Save this shellscript under The script changes the template, used by hassio_audio to create |
Hello, I get this error when starting the module:
400 Client Error for http+docker://localhost/v1.38/containers/e5995588e5c493324bca0da8cf11cf170c3c61aa776e720834c70ec1009e1318/start: Bad Request ("OCI runtime create failed: container_linux.go:348: starting container process caused "exec: "/dev/init": stat /dev/init: no such file or directory": unknown")
The text was updated successfully, but these errors were encountered: