Hello, I recently tried to use may new Pi Zero 2 W for music streaming. I tried to deploy balenasound using the “one-click” and the CLI - variant. Spotify, Bluetooth, Airplay was not problem to install, but the sound supervisor failed every time.
Error Message from the build log:
[Success] Successfully built service multiroom-client
[Success] Successfully built service airplay
[Success] Successfully built service bluetooth
[Success] Successfully built service multiroom-server
[Info] Uploading images
[Success] Successfully uploaded images
[Error] Some services failed to build:
[Error] Service: sound-supervisor
[Error] Error: manifest for balenalib/raspberrypi0-2w-64-alpine-node:12 not found: manifest unknown: manifest unknown
[Info] Built on arm02
[Error] Not deploying release.
Here you can see the message “manifest unknown”. I searched for this error but found nothing.
I managed to install the other services, but not the sound supervisor. When I try to use spotify connect I am able to connect to the device using the spotify app, but as soon as I try to play music it disconnects immediately.
Log:
spotify [2021-12-20T16:41:00Z INFO librespot_playback::player] Loading with Spotify URI spotify:track:0K0JJ3QZEHYhBwkE21L2HZ
spotify [2021-12-20T16:41:01Z INFO librespot_playback::player] (178713 ms) loaded
spotify ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection terminated
spotify
spotify [2021-12-20T16:41:02Z ERROR librespot_playback::player] Audio Sink Error Connection Refused: Device default May be Invalid, Busy, or Already in Use, ALSA function ‘snd_pcm_open’ failed with error ‘ECONNREFUSED: Connection refused’
Also I am unable to connect to BT. I am able to see the device and pair with it, but connecting doen’t work. Are the Spotify / BT issuses related to the missing sound-supervisor? I also tried the develeopment / production version. Didn’t change anything.
Welcome @lunaticluke - you actually found the problem yourself already.
The error you’re seeing ("[Error] Error: manifest for balenalib/raspberrypi0-2w-64-alpine-node:12 not found: manifest unknown: manifest unknown") means that the version 12 of Docker Hub does not exist - which is really doesn’t. But it seems to be needed for the sound supervisor. Maybe @mpous knows who to ping to get node version 12 pushed to that repo
@nmaas87 beat me to it! I have created an issue here, and am currently testing a node v14 upgrade for sound-supervisor. Since node v12 is now out of LTS, I don’t believe we are building new base images for it.
Wow, I appreciate the fast replies! Do you think that the absence of the sound supervisor is responsible for the malfunction of Spotify connect and BT?
@lunaticluke I believe so yes. I’ve tested the PR on a Pi 3, but will need to test on all the other devices before we merge and upload the base image. We are working on it though, so hold tight!
Hello again, I deployed the balena sound once again to try if it works now. Initially I had a good feeling, because sound supervisor installed without a problem. But soon after I had the same issues as before.
The sound supervisor doesn’t start ( audio Waiting for sound supervisor to start at 172.17.0.1:80). This line reapeats itself over and over.
When I try to connect to Spotify and play a song it disconnects immediately. The logs are as follows:
spotify [2021-12-23T12:33:56Z INFO librespot_playback::player] Loading <Walk This Way (feat. Aerosmith)> with Spotify URI spotify:track:6qUEOWqOzu1rLPUPQ1ECpx
spotify [2021-12-23T12:33:57Z INFO librespot_playback::player] <Walk This Way (feat. Aerosmith)> (310386 ms) loaded
spotify ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection terminated
spotify
spotify [2021-12-23T12:33:58Z ERROR librespot_playback::player] Audio Sink Error Connection Refused: Device default May be Invalid, Busy, or Already in Use, ALSA function ‘snd_pcm_open’ failed with error ‘ECONNREFUSED: Connection refused’
Service exited ‘spotify sha256:b354887709a46e467701c9ea0ed1b59060e155973f9e65a25835d8b801c21de1’
audio Waiting for sound supervisor to start at 172.17.0.1:80
Restarting service ‘spotify sha256:b354887709a46e467701c9ea0ed1b59060e155973f9e65a25835d8b801c21de1’
spotify Starting Spotify plugin…
spotify Device name: balenaSound Spotify 1738
spotify Volume normalization enabled.
spotify Spotify audio cache disabled.
spotify [2021-12-23T12:34:01Z INFO librespot] librespot 0.3.1 bbd575e (Built on 2021-11-26, Build ID: a6e0Ery3, Profile: release)
spotify [2021-12-23T12:34:01Z INFO librespot_core::session] Connecting to AP “ap-gew1.spotify.com:4070”
spotify [2021-12-23T12:34:01Z INFO librespot_core::session] Authenticated as “1155180833” !
spotify [2021-12-23T12:34:01Z INFO librespot_playback::mixer::softmixer] Mixing with softvol and volume control: Linear
spotify [2021-12-23T12:34:01Z INFO librespot_playback::convert] Converting with ditherer: tpdf
spotify [2021-12-23T12:34:01Z INFO librespot_playback::audio_backend::alsa] Using AlsaSink with format: S16
spotify [2021-12-23T12:34:01Z INFO librespot_core::session] Country: “AT”
When I try to pair my phone with the BT of the Pi it won’t work either.
I alqready set the variable “AUDIO_OUTPUT” to “DAC” and the custom config. “BALENA_HOST_CONFIG_dtoverlay” to “hifiberry-dac” because I’m using the hfiberry zero dac.
Hey, sorry for the delayed response, catching up after new years leave.
The logs you shared don’t show any output from sound-supervisor which is the service that is failing. Can you restart the service sound-supervisor and share the log that’s printed when doing so?
Hi @lunaticluke, the new logs you share also don’t show much of interest. If you can grant me support access to your device I can inspect it closely and see if I can find the problem. Here is how to do it: Grant support access - Balena Documentation
