# No audio from 3.5mm running 32-bit OS on RPi 3 **URL:** \ **Category:** balenaSound\ **Created:** [June 23, 2021, 10:43pm UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126 "2021-06-23T22:43:26Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![jonmitten](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/jonmitten/32/6164_2.png) [@jonmitten](https://forums.balena.io/u/jonmitten)\ **Post date:** [June 23, 2021, 10:43pm UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126/1 "2021-06-23T22:43:27Z")
I’ve perused the seemingly related topics, and am aware of the bug in 64-bit OS, but I downloaded the armv7hf 32-bit, and everything appeared to go swimmingly. However, I’m not getting audio from the 3.5mm output, and I’m finding it difficult to troubleshoot. The speaker is tested, the audio port “crackles” when it reboots. But other than that, there’s no sound emitting from any of the options, neither Airplay, Bluetooth, nor Spotify Connect. I’ve attempted to run `amixer` and `speaker-test`, but in both cases I get `command not found` - I’m doing this via the Dashboard OS terminal. I was also getting `[Fatal] (Snapclient) Exception: No audio player support for: pulse` but can’t find any documentation about what that means, or if it’s related. Aside from the 32-bit solutions, I’m not seeing anything that fits my case. Does anybody have any tips on troubleshooting this issue? ---
**Author:** ![alanb128](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/alanb128/32/2839_2.png) [@alanb128](https://forums.balena.io/u/alanb128)\ **Post date:** [June 24, 2021, 1:16am UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126/3 "2021-06-24T01:16:29Z")
Hello, are you having this issue with the 64 bit or 32 bit OS? If it’s the 64 bit, have you tried removing the `vc4-kms-v3d` overlay from the “Define DT overlays” setting on the dashboard? (see [No sound output with balenaOS 64 bit on Raspberry Pi 3 · Issue #82 · balenalabs/balena-sound · GitHub](https://github.com/balenalabs/balena-sound/issues/82)) Otherwise, please provide the OS version you’re using. ---
**Author:** ![jonmitten](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/jonmitten/32/6164_2.png) [@jonmitten](https://forums.balena.io/u/jonmitten)\ **Post date:** [June 24, 2021, 8:22pm UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126/5 "2021-06-24T20:22:27Z")
Thanks, @alanb128 . Like the title states, I’m running the 32-bit OS (the default for RPi3). The image I used with Etcher is `balena-cloud-balena-sound-raspberrypi3-2.80.3+rev1-v12.7.0`, and the Host OS Version on dashboard, likewise, says `balenaOS 2.80.3+rev1`. Does that answer the question? Am I correct in ascertaining the operating system as 32-bit? ---
**Author:** ![dtischler](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/dtischler/32/2483_2.png) [@dtischler](https://forums.balena.io/u/dtischler)\ **Post date:** [June 25, 2021, 11:57pm UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126/6 "2021-06-25T23:57:50Z")
Well this is odd, Jon. I just tested a Pi3, 32-bit, version 2.80.3+rev1 with Supervisor 12.7.0 myself, and it worked great within minutes of deploying it. I built the project by clicking the blue “Deploy with Balena” button located on the GitHub repo, and once it finished building and downloading the containers, I used my laptop, loaded Bluetooth settings, scanned for devices, found the Pi3, connected to it, browsed to YouTube and started playing a video, and audio came out of the headphones I had attached to the Pi3 3.5mm audio jack. So, let’s check some basics here. First, are all the containers built and running properly? It should look like this: ![Screen Shot 2021-06-25 at 4.51.53 PM](https://global.discourse-cdn.com/balena/original/2X/6/621ddbfe4c622ef81496212a1a99d44a30e0b545.png) Next, make sure the headphones are plugged prior to powering up the Pi. Sometimes the Pi doesnt like to “recognize” new speakers being plugged in after it has already booted. And press them all the way in, mine you have to give a firm push on. Finally, what kind of an SD Card do you have. I have noticed they can be very finicky and the faster the SD Card, the better. ---
**Author:** ![jonmitten](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/jonmitten/32/6164_2.png) [@jonmitten](https://forums.balena.io/u/jonmitten)\ **Post date:** [June 29, 2021, 5:12pm UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126/8 "2021-06-29T17:12:24Z")
@dtischler, thank you for the reply. I’m running `2.80.3+rev1` with supervisor version `12.8.8`. Services appear to be in good shape from my end. I see our release numbers are different, and the Supervisor versions are different. ![Screen Shot 2021-06-29 at 9.53.46 AM](https://global.discourse-cdn.com/balena/original/2X/7/7fc959c047cc5dba980d6ed8ae5e45a92dd3703f.png) I booted up with the speaker connected to the 3.5mm audio jack, and the logs read like it should be playing - that the Spotify client is playing on the RPi, albeit lots of errors on the multiroom services: ```auto Rebooting Supervisor starting airplay Starting AirPlay plugin... airplay Device name: balenaSound AirPlay 5455 airplay Shairport-sync started. Device is discoverable as balenaSound AirPlay 5455 airplay fatal error: pa context is not good -- the error message "Connection terminated". spotify Starting Spotify plugin... spotify Device name: balenaSound Spotify 5455 spotify Volume normalization enabled. spotify Spotify audio cache disabled. spotify [2021-06-29T17:07:22Z INFO librespot] librespot (raspotify v0.16.0) 0adb851 (2020-12-15). Built on 2020-12-30. Build ID: KLdkAvgt spotify [2021-06-29T17:07:23Z INFO librespot_core::session] Connecting to AP "guc3-accesspoint-a-26lq.ap.spotify.com:4070" spotify [2021-06-29T17:07:24Z INFO librespot_core::session] Authenticated as "jonmitten" ! spotify [2021-06-29T17:07:24Z INFO librespot_playback::audio_backend::alsa] Using alsa sink spotify [2021-06-29T17:07:24Z INFO librespot_core::session] Country: "US" multiroom-client multiroom-client --- Multiroom --- multiroom-client Starting multiroom service with settings: multiroom-client - Mode: server multiroom-client - Snapcast version: v0.25.0 multiroom-client Waiting for sound supervisor to start at 172.17.0.1:80 multiroom-client Waiting for sound supervisor to start at 172.17.0.1:80 multiroom-client Waiting for sound supervisor to start at 172.17.0.1:80 multiroom-client Starting multi-room client... multiroom-client - balenaSound mode: MULTI_ROOM multiroom-client - Target snapcast server: 192.168.0.68 multiroom-client 2021-06-29 17-07-40.616 [Error] (Snapclient) PCM device "default" not found multiroom-client 2021-06-29 17-07-40.678 [Error] (Connection) Error reading message header of length 0: End of file multiroom-client 2021-06-29 17-07-40.678 [Error] (Connection) Error in socket shutdown: Socket not connected multiroom-client 2021-06-29 17-07-40.678 [Error] (Connection) Failed to send message, error: Bad file descriptor multiroom-client 2021-06-29 17-07-40.678 [Error] (Controller) Time sync request failed: Bad file descriptor multiroom-client 2021-06-29 17-07-41.746 [Error] (Connection) Error reading message header of length 0: End of file multiroom-client 2021-06-29 17-07-41.747 [Error] (Connection) Error in socket shutdown: Socket not connected multiroom-client 2021-06-29 17-07-41.747 [Error] (Connection) Failed to send message, error: Bad file descriptor multiroom-client 2021-06-29 17-07-41.747 [Error] (Controller) Time sync request failed: Bad file descriptor multiroom-client 2021-06-29 17-07-42.678 [Error] (Controller) Failed to send hello request, error: Operation timed out multiroom-client 2021-06-29 17-07-42.678 [Error] (Controller) Time sync request failed: Operation timed out multiroom-client 2021-06-29 17-07-43.679 [Error] (Connection) Failed to connect to host '192.168.0.68', error: Connection refused multiroom-client 2021-06-29 17-07-43.679 [Error] (Controller) Error: Connection refused multiroom-client 2021-06-29 17-07-43.679 [Error] (Connection) Error in socket shutdown: Socket not connected multiroom-client 2021-06-29 17-07-43.747 [Error] (Controller) Failed to send hello request, error: Operation timed out multiroom-client 2021-06-29 17-07-43.747 [Error] (Controller) Time sync request failed: Operation timed out multiroom-client 2021-06-29 17-07-44.748 [Error] (Connection) Failed to connect to host '192.168.0.68', error: Connection refused multiroom-client 2021-06-29 17-07-44.748 [Error] (Controller) Error: Connection refused multiroom-client 2021-06-29 17-07-44.748 [Error] (Connection) Error in socket shutdown: Socket not connected multiroom-client 2021-06-29 17-07-47.755 [Error] (Controller) Failed to send hello request, error: Operation timed out multiroom-client 2021-06-29 17-07-47.756 [Error] (Controller) Time sync request failed: Operation timed out multiroom-client 2021-06-29 17-07-47.756 [Error] (Connection) Error reading message header of length 0: Operation canceled multiroom-client 2021-06-29 17-07-48.765 [Error] (Connection) Error reading message header of length 0: End of file multiroom-client 2021-06-29 17-07-48.765 [Error] (Connection) Error in socket shutdown: Socket not connected multiroom-client 2021-06-29 17-07-48.765 [Error] (Connection) Failed to send message, error: Bad file descriptor multiroom-client 2021-06-29 17-07-48.765 [Error] (Controller) Time sync request failed: Bad file descriptor multiroom-client 2021-06-29 17-07-49.774 [Error] (Connection) Error reading message header of length 0: End of file multiroom-client 2021-06-29 17-07-49.774 [Error] (Connection) Error in socket shutdown: Socket not connected multiroom-client 2021-06-29 17-07-49.774 [Error] (Connection) Failed to send message, error: Bad file descriptor multiroom-client 2021-06-29 17-07-49.774 [Error] (Controller) Time sync request failed: Bad file descriptor logging % Total % Received % Xferd Average Speed Time Time Time Current logging Dload Upload Total Spent Left Speed 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: PATCH logging % Total % Received % Xferd Average Speed Time Time Time Current logging Dload Upload Total Spent Left Speed 0 0 0 --:--:-- --:--:-- --:--:-- 0 logging curl: (7) Failed to connect to 127.0.0.1 port 48484: Connection refused bluetooth Running balena base image entrypoint... bluetooth --- Bluetooth --- bluetooth Starting bluetooth service with settings: bluetooth - Device name: balenaOS 5455 bluetooth - HCI interface: hci0 bluetooth - Pairing mode: SSP bluetooth - PIN code: 0000 bluetooth Available HCI interfaces: hci0 bluetooth Resetting hci0 bluetooth Configuring selected interface: hci0 bluetooth hci0 Set Connectable complete, settings: powered connectable ssp br/edr le secure-conn bluetooth hci0 Set Bondable complete, settings: powered connectable bondable ssp br/edr le secure-conn bluetooth hci0 Set Discoverable complete, settings: powered connectable discoverable bondable ssp br/edr le secure-conn bluetooth hci0 Set Secure Simple Pairing complete, settings: powered connectable discoverable bondable ssp br/edr le secure-conn bluetooth Pairing mode set to 'Secure Simple Pairing Mode (SSPM)'. PIN code is NOT required. bluetooth Bluetooth agent started! bluetooth Checking for known bluetooth devices... bluetooth - Attempting to reconnect to Jon Mittenâs iPhone XR (FC:18:3C:6F:AB:16)... bluetooth - Bluetooth profile not available or not initialized. Retrying (attempt 1/5)... bluetooth - Bluetooth profile not available or not initialized. Retrying (attempt 2/5)... bluetooth - Bluetooth profile not available or not initialized. Retrying (attempt 3/5)... bluetooth - Bluetooth profile not available or not initialized. Retrying (attempt 4/5)... bluetooth - Bluetooth profile not available or not initialized. Retrying (attempt 5/5)... sound-supervisor sound-supervisor > sound-supervisor@1.0.0 start /usr/src sound-supervisor > node build/index.js sound-supervisor sound-supervisor Sound supervisor listening on port 80 sound-supervisor Error connecting to audio block - Retry failed: connect ECONNREFUSED 192.168.0.68:4317 sound-supervisor Error connecting to audio block - Retry failed: connect ECONNREFUSED 192.168.0.68:4317 sound-supervisor Error connecting to audio block - Retry failed: connect ECONNREFUSED 192.168.0.68:4317 sound-supervisor Error connecting to audio block - Retry failed: connect ECONNREFUSED 192.168.0.68:4317 sound-supervisor Error connecting to audio block - Retry failed: connect ECONNREFUSED 192.168.0.68:4317 multiroom-server multiroom-server --- Multiroom --- multiroom-server Starting multiroom service with settings: multiroom-server - Mode: server multiroom-server - Snapcast version: v0.25.0 multiroom-server Waiting for sound supervisor to start at 172.17.0.1:80 multiroom-server Waiting for sound supervisor to start at 172.17.0.1:80 Warning: Suppressed 28 message(s) due to slow reading audio Routing 'balena-sound.input' to 'snapcast'. audio Routing 'balena-sound.output' to 'alsa_output.bcm2835-jack.stereo-fallback'. audio curl: (7) Failed to connect to 10.114.104.1 port 48484: Connection refused audio audio --- Audio --- audio Starting audio service with settings: audio - pulseaudio 13.0 audio - Pulse log level: NOTICE audio - Default output: RPI_HEADPHONES audio audio Detected audio cards: audio 0 bcm2835-jack bcm2835_headphonbcm2835Headphones-bcm2835Headphones audio audio multiroom-client 2021-06-29 17-07-51.767 [Error] (Connection) Failed to connect to host '192.168.0.68', error: Connection refused multiroom-client 2021-06-29 17-07-51.767 [Error] (Controller) Error: Connection refused multiroom-client 2021-06-29 17-07-51.767 [Error] (Connection) Error in socket shutdown: Socket not connected multiroom-client 2021-06-29 17-07-51.774 [Error] (Controller) Failed to send hello request, error: Operation timed out multiroom-client 2021-06-29 17-07-51.774 [Error] (Controller) Time sync request failed: Operation timed out sound-supervisor Error connecting to audio block - Retry failed: connect ECONNREFUSED 192.168.0.68:4317 bluetooth - Could not connect to Jon Mittenâs iPhone XR (FC:18:3C:6F:AB:16)... multiroom-server multiroom-server --- Multiroom --- multiroom-server Starting multiroom service with settings: multiroom-server - Mode: server multiroom-server - Snapcast version: v0.25.0 multiroom-server Starting multi-room server... multiroom-server 2021-06-29 17-07-54.604 [Error] (Avahi) Failed to create client: Daemon not running multiroom-server ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: Connection refused multiroom-server multiroom-server 2021-06-29 17-07-54.624 [Error] (Snapserver) Exception: Can't open device 'pulse', error: Connection refused multiroom-client 2021-06-29 17-07-54.781 [Error] (Controller) Failed to send hello request, error: Operation timed out multiroom-client 2021-06-29 17-07-54.781 [Error] (Controller) Time sync request failed: Operation timed out Service exited 'multiroom-server sha256:3776d56898f4e6d8b384ce52fe18ea201c8c249c7060244224f804372df57f7a' multiroom-client 2021-06-29 17-07-54.782 [Error] (Connection) Error reading message header of length 0: Operation canceled multiroom-client 2021-06-29 17-07-55.788 [Error] (Connection) Error reading message header of length 0: End of file multiroom-client 2021-06-29 17-07-55.788 [Error] (Connection) Error in socket shutdown: Socket not connected multiroom-client 2021-06-29 17-07-55.788 [Error] (Connection) Failed to send message, error: Bad file descriptor multiroom-client 2021-06-29 17-07-55.788 [Error] (Controller) Time sync request failed: Bad file descriptor Restarting service 'multiroom-server sha256:3776d56898f4e6d8b384ce52fe18ea201c8c249c7060244224f804372df57f7a' Service exited 'multiroom-server sha256:3776d56898f4e6d8b384ce52fe18ea201c8c249c7060244224f804372df57f7a' multiroom-client 2021-06-29 17-07-56.789 [Error] (Connection) Failed to connect to host '192.168.0.68', error: Connection refused multiroom-client 2021-06-29 17-07-56.789 [Error] (Controller) Error: Connection refused multiroom-client 2021-06-29 17-07-56.789 [Error] (Connection) Error in socket shutdown: Socket not connected multiroom-client 2021-06-29 17-07-57.787 [Error] (Controller) Failed to send hello request, error: Operation timed out multiroom-client 2021-06-29 17-07-57.787 [Error] (Controller) Time sync request failed: Operation timed out audio Setting audio routing rules... audio Routing 'balena-sound.input' to 'snapcast'. audio Routing 'balena-sound.output' to 'alsa_output.bcm2835-jack.stereo-fallback'. audio OKW: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified). sound-supervisor Error connecting to audio block - Retry failed: connect ECONNREFUSED 192.168.0.68:4317 audio W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 audio W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 Restarting service 'multiroom-server sha256:3776d56898f4e6d8b384ce52fe18ea201c8c249c7060244224f804372df57f7a' multiroom-server multiroom-server --- Multiroom --- multiroom-server Starting multiroom service with settings: multiroom-server - Mode: server multiroom-server - Snapcast version: v0.25.0 multiroom-server Starting multi-room server... multiroom-server 2021-06-29 17-07-59.561 [Error] (Avahi) Failed to create client: Daemon not running multiroom-client metadata:{"STREAM":"balenaSound"} multiroom-client 2021-06-29 17-07-59.843 [Fatal] (Snapclient) Exception: No audio player support for: pulse multiroom-server 2021-06-29 17-07-59.843 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file Service exited 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' Restarting service 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' multiroom-client multiroom-client --- Multiroom --- multiroom-client Starting multiroom service with settings: multiroom-client - Mode: server multiroom-client - Snapcast version: v0.25.0 multiroom-client Starting multi-room client... multiroom-client - balenaSound mode: MULTI_ROOM multiroom-client - Target snapcast server: 192.168.0.68 multiroom-client 2021-06-29 17-08-04.043 [Error] (Snapclient) PCM device "default" not found multiroom-server 2021-06-29 17-08-04.060 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file multiroom-client metadata:{"STREAM":"balenaSound"} multiroom-client 2021-06-29 17-08-04.060 [Fatal] (Snapclient) Exception: No audio player support for: pulse Service exited 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' sound-supervisor Connected to PulseAudio at 192.168.0.68:4317 sound-supervisor Server protocol version: 33 sound-supervisor Client protocol version: 33 Restarting service 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' multiroom-client multiroom-client --- Multiroom --- multiroom-client Starting multiroom service with settings: multiroom-client - Mode: server multiroom-client - Snapcast version: v0.25.0 multiroom-client Starting multi-room client... multiroom-client - balenaSound mode: MULTI_ROOM multiroom-client - Target snapcast server: 192.168.0.68 multiroom-client 2021-06-29 17-08-07.970 [Error] (Snapclient) PCM device "default" not found multiroom-client metadata:{"STREAM":"balenaSound"} multiroom-server 2021-06-29 17-08-07.991 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file multiroom-client 2021-06-29 17-08-07.991 [Fatal] (Snapclient) Exception: No audio player support for: pulse Service exited 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' sound-supervisor Joining the fleet, requesting master info with fleet-sync... multiroom-client multiroom-client --- Multiroom --- multiroom-client Starting multiroom service with settings: multiroom-client - Mode: server multiroom-client - Snapcast version: v0.25.0 multiroom-client Starting multi-room client... multiroom-client - balenaSound mode: MULTI_ROOM multiroom-client - Target snapcast server: 192.168.0.68 multiroom-client 2021-06-29 17-08-11.997 [Error] (Snapclient) PCM device "default" not found multiroom-client metadata:{"STREAM":"balenaSound"} multiroom-client 2021-06-29 17-08-12.019 [Fatal] (Snapclient) Exception: No audio player support for: pulse multiroom-server 2021-06-29 17-08-12.021 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file Restarting service 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' Service exited 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' multiroom-client multiroom-client --- Multiroom --- multiroom-client Starting multiroom service with settings: multiroom-client - Mode: server multiroom-client - Snapcast version: v0.25.0 multiroom-client Starting multi-room client... multiroom-client - balenaSound mode: MULTI_ROOM multiroom-client - Target snapcast server: 192.168.0.68 multiroom-client 2021-06-29 17-08-16.362 [Error] (Snapclient) PCM device "default" not found multiroom-client metadata:{"STREAM":"balenaSound"} multiroom-client 2021-06-29 17-08-16.385 [Fatal] (Snapclient) Exception: No audio player support for: pulse multiroom-server 2021-06-29 17-08-16.385 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file Restarting service 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' Service exited 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' Restarting service 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' multiroom-client multiroom-client --- Multiroom --- multiroom-client Starting multiroom service with settings: multiroom-client - Mode: server multiroom-client - Snapcast version: v0.25.0 multiroom-client Starting multi-room client... multiroom-client - balenaSound mode: MULTI_ROOM multiroom-client - Target snapcast server: 192.168.0.68 multiroom-client 2021-06-29 17-08-21.382 [Error] (Snapclient) PCM device "default" not found multiroom-client metadata:{"STREAM":"balenaSound"} multiroom-client 2021-06-29 17-08-21.400 [Fatal] (Snapclient) Exception: No audio player support for: pulse multiroom-server 2021-06-29 17-08-21.402 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file Service exited 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' multiroom-client multiroom-client --- Multiroom --- multiroom-client Starting multiroom service with settings: multiroom-client - Mode: server multiroom-client - Snapcast version: v0.25.0 multiroom-client Starting multi-room client... multiroom-client - balenaSound mode: MULTI_ROOM multiroom-client - Target snapcast server: 192.168.0.68 multiroom-client 2021-06-29 17-08-28.369 [Error] (Snapclient) PCM device "default" not found multiroom-client metadata:{"STREAM":"balenaSound"} multiroom-server 2021-06-29 17-08-28.404 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file multiroom-client 2021-06-29 17-08-28.404 [Fatal] (Snapclient) Exception: No audio player support for: pulse Restarting service 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' Service exited 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' Restarting service 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' multiroom-client multiroom-client --- Multiroom --- multiroom-client Starting multiroom service with settings: multiroom-client - Mode: server multiroom-client - Snapcast version: v0.25.0 multiroom-client Starting multi-room client... multiroom-client - balenaSound mode: MULTI_ROOM multiroom-client - Target snapcast server: 192.168.0.68 multiroom-client 2021-06-29 17-08-38.548 [Error] (Snapclient) PCM device "default" not found multiroom-client metadata:{"STREAM":"balenaSound"} multiroom-client 2021-06-29 17-08-38.566 [Fatal] (Snapclient) Exception: No audio player support for: pulse multiroom-server 2021-06-29 17-08-38.566 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file Service exited 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' Restarting service 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' multiroom-client multiroom-client --- Multiroom --- multiroom-client Starting multiroom service with settings: multiroom-client - Mode: server multiroom-client - Snapcast version: v0.25.0 multiroom-client Starting multi-room client... multiroom-client - balenaSound mode: MULTI_ROOM multiroom-client - Target snapcast server: 192.168.0.68 multiroom-client 2021-06-29 17-08-54.818 [Error] (Snapclient) PCM device "default" not found multiroom-server 2021-06-29 17-08-54.844 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file multiroom-client metadata:{"STREAM":"balenaSound"} multiroom-client 2021-06-29 17-08-54.844 [Fatal] (Snapclient) Exception: No audio player support for: pulse Service exited 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' Restarting service 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' multiroom-client multiroom-client --- Multiroom --- multiroom-client Starting multiroom service with settings: multiroom-client - Mode: server multiroom-client - Snapcast version: v0.25.0 multiroom-client Starting multi-room client... multiroom-client - balenaSound mode: MULTI_ROOM multiroom-client - Target snapcast server: 192.168.0.68 multiroom-client 2021-06-29 17-09-23.763 [Error] (Snapclient) PCM device "default" not found multiroom-client metadata:{"STREAM":"balenaSound"} multiroom-server 2021-06-29 17-09-23.784 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file multiroom-client 2021-06-29 17-09-23.784 [Fatal] (Snapclient) Exception: No audio player support for: pulse Service exited 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' spotify [2021-06-29T17:10:02Z INFO librespot_playback::player] Loading with Spotify URI spotify [2021-06-29T17:10:03Z INFO librespot_playback::player] (230373 ms) loaded sound-supervisor Playback started, announcing 192.168.0.68 as multi-room master! Restarting service 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' multiroom-client multiroom-client --- Multiroom --- multiroom-client Starting multiroom service with settings: multiroom-client - Mode: server multiroom-client - Snapcast version: v0.25.0 multiroom-client Starting multi-room client... multiroom-client - balenaSound mode: MULTI_ROOM multiroom-client - Target snapcast server: 192.168.0.68 multiroom-client 2021-06-29 17-10-18.211 [Error] (Snapclient) PCM device "default" not found multiroom-client metadata:{"STREAM":"balenaSound"} multiroom-client 2021-06-29 17-10-18.252 [Fatal] (Snapclient) Exception: No audio player support for: pulse multiroom-server 2021-06-29 17-10-18.255 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file Service exited 'multiroom-client sha256:9f3361d7bf3a9dfa615264b3bc2e0dba48a3281d017043f180deaca83b059f3c' ``` ---
**Author:** ![jonmitten](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/jonmitten/32/6164_2.png) [@jonmitten](https://forums.balena.io/u/jonmitten)\ **Post date:** [June 29, 2021, 5:49pm UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126/9 "2021-06-29T17:49:19Z")
When I run Diagnostic Checks, everything except `check_service_restarts` reads good: ```auto { "name": "check_service_restarts", "success": false, "status": "Some services are restarting unexpectedly: (service: /multiroom-client_3747072_1839466 restart count: 46) (service: /multiroom-server_3747071_1839466 restart count: 3) (service: /audio_3747068_1839466 restart count: 1)" }, ``` ---
**Author:** ![jonmitten](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/jonmitten/32/6164_2.png) [@jonmitten](https://forums.balena.io/u/jonmitten)\ **Post date:** [June 29, 2021, 5:50pm UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126/10 "2021-06-29T17:50:48Z")
I’m also seeing this in the logs: ```auto PCM device "default" not found ``` but I’ve set the `AUDIO_OUTPUT` Device Variable to `RPI_HEADPHONES` ---
**Author:** ![dtischler](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/dtischler/32/2483_2.png) [@dtischler](https://forums.balena.io/u/dtischler)\ **Post date:** [June 30, 2021, 12:24am UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126/11 "2021-06-30T00:24:22Z")
Ok, let’s do two more tests. First, what happens if you set a variable for `SOUND_MODE` to `STANDALONE`? Next, I know you said you were testing Spotify, but what about Bluetooth? Do you get any output if you connect to the device via Bluetooth, like I did on mine? ---
**Author:** ![jonmitten](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/jonmitten/32/6164_2.png) [@jonmitten](https://forums.balena.io/u/jonmitten)\ **Post date:** [June 30, 2021, 6:51pm UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126/13 "2021-06-30T18:51:07Z")
@dtischler , thanks for your reply 🙂 It seems that, yes, setting the `SOUND_MODE` to `STANDALONE` does allow Spotify to play through the Spotify service on the device. ~~However, I’m unable to connect to the Bluetooth service permanently, as it kicks back to Disconnected almost immediately and then will not reconnect. (MacOS)~~ Actually, while I wrote this out, Bluetooth eventually connected consistently. I’m not sure how or why it didn’t do it right away. As soon as I remove the `STANDALONE` variable from the sound mode, though, the sound again goes mute. So, I can get one device to work at a time, perhaps? But not multi-room, it seems. That may be a limitation of Spotify that I’m unaware of. Is that the case? Spotify Premium, for what it’s worth. My second device is hanging on “VPN Only”, I assume that issue is out of scope for this discussion, so perhaps I’ll open another forum thread if I can’t resolve that through research. Thanks for the help so far! I really appreciate it. To summarize: - Running 32-bit balenaOS on RPi 3 B+ will work! - Setting `AUDIO_MODE` to `STANDALONE` does appear to allow sound through a single device. - Bluetooth is unpredictable, but is working as of this writing - Spotify Premium works with the Spotify Connect remote player (Icon is speaker in a circle) from the Spotify client on desktop / mobile - I’m trying to get multiroom working with multiple RPi 3B+ with the same release mode, which `STANDALONE` seems to prevent (`multiroom-server` and `multiroom-client` services are stopped) - Airplay does not appear to be working, unless I misunderstand the relationship between Spotify Connect and Airplay Any tips on getting multiroom working with my hardware configuration? Do I need to bite the bullet and order a few RPi 4s? Thanks so much! ---
**Author:** ![nitish](https://avatars.discourse-cdn.com/v4/letter/n/34f0e0/32.png) [@nitish](https://forums.balena.io/u/nitish)\ **Post date:** [July 2, 2021, 1:33pm UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126/15 "2021-07-02T13:33:37Z")
Hi, Thanks for getting back and great summary. I see we had some issues with multiroom setup back in Mar’ and then some more updates more recently. Can you help us understand two things: - How you deployed balenaSound i.e. what route ? - What commit or version of balenaSound are you running (hoping greater than v3.5.2+)? RaspberryPi 3 B+ is one of the [recommended device] ([Getting started - Home](https://sound.balenalabs.io/docs/)), so you’d not need an upgrade to get balenaSound to work. Having said that the above two can help us see if there is something with a version which is currently running. Cheers, N ---
**Author:** ![jonmitten](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/jonmitten/32/6164_2.png) [@jonmitten](https://forums.balena.io/u/jonmitten)\ **Post date:** [July 2, 2021, 4:47pm UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126/16 "2021-07-02T16:47:30Z")
Thank you for checking in on this @nitish . The deployment route was to use Balena Etcher to flash microSD card with the selected Production version of the 32-bit RPi 3-supported OS, then deploy via the “Deploy with balena” button on the [sound.balenalabs.io](http://sound.balenalabs.io) page. The balenaSound version is `3.6.5` / commit `b8f7eaf` The Source value is `cloud`, which I believe is informed by the deployment method, but I’m new to this infrastructure so I don’t know if that’s true. Let me know if I’ve reported everything accurately - I think I have - and if there’s a more reliable or stable deployment method. Thanks again! ---
**Author:** ![zwhitchcox](https://avatars.discourse-cdn.com/v4/letter/z/8e7dd6/32.png) [@zwhitchcox](https://forums.balena.io/u/zwhitchcox)\ **Post date:** [July 2, 2021, 8:01pm UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126/17 "2021-07-02T20:01:20Z")
Hi Jon, thanks for the diagnostic feedback you’ve already provided. It looks to me like there is a problem with the audio block which is causing the snapcast server to be unable to start and thus the snapcast client. From the logs you posted: ```auto audio Setting audio routing rules... audio Routing 'balena-sound.input' to 'snapcast'. audio Routing 'balena-sound.output' to 'alsa_output.bcm2835-jack.stereo-fallback'. audio OKW: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified). sound-supervisor Error connecting to audio block - Retry failed: connect ECONNREFUSED 192.168.0.68:4317 audio W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 audio W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 ``` I am not exactly sure why no one else would be having this error though. I will ping the creator and see if he has any ideas. ---
**Author:** ![zwhitchcox](https://avatars.discourse-cdn.com/v4/letter/z/8e7dd6/32.png) [@zwhitchcox](https://forums.balena.io/u/zwhitchcox)\ **Post date:** [July 2, 2021, 8:05pm UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126/19 "2021-07-02T20:05:55Z")
Actually, scratch that, can you try re-deploying balena sound? it looks like there was a [bug](https://github.com/balenablocks/audio/issues/62) that was fixed that might be related. It might not be the problem, but worth a try. You can redeploy with the “Deploy With Balena” button [here](https://github.com/balenalabs/balena-sound) ---
**Author:** ![jonmitten](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/jonmitten/32/6164_2.png) [@jonmitten](https://forums.balena.io/u/jonmitten)\ **Post date:** [July 4, 2021, 6:40pm UTC](https://forums.balena.io/t/no-audio-from-3-5mm-running-32-bit-os-on-rpi-3/330126/23 "2021-07-04T18:40:28Z")
@zwhitchcox , good call. I upgraded to `3.6.8` and I am able to run sound out of the 3.5mm output jack directly from the RPi, with multiroom-server and multiroom-client enabled (removing the `AUDIO_MODE=STANDALONE` from the device variables). I’m not sure how to enable the multiroom playback, but that’s something I can research on my own. Thanks, all, for your patience and assistance.