Sound outputting on master rpi4 but not outputting on secondary rpi3

I followed the instructions listed in the 2 links: Turn your old speakers or Hi-Fi into Bluetooth, Airplay and Spotify receivers with a Raspberry Pi and this step-by-step guide

and: Build your own multi-room audio system with Bluetooth, Airplay, and Spotify using Raspberry Pis

yet I can only hear audio output from one device. I have a raspberry pi 4 and raspberry pi 3B+. Using the pi 4 as the master my log showed this:

12.03.21 17:01:40 (-0500) bluetooth AuthorizeService (/org/bluez/hci0/dev_E4_B2_FB_85_C5_46, 0000110d-0000-1000-8000-00805f9b34fb)
12.03.21 17:01:43 (-0500) audio W: [pulseaudio] module-loopback.c: Configured latency of 200.00 ms is smaller than minimum latency, using minimum instead
12.03.21 17:01:43 (-0500) audio W: [pulseaudio] module-loopback.c: Cannot set requested source latency of 66.67 ms, adjusting to 250.00 ms
12.03.21 17:02:09 (-0500) sound-supervisor Playback started, announcing 192.168.10.246 as multi-room master!
12.03.21 17:05:41 (-0500) Supervisor starting
12.03.21 17:00:37 (-0500) audio Setting audio routing rules…
12.03.21 17:00:37 (-0500) audio Routing ‘balena-sound.input’ to ‘snapcast’.
12.03.21 17:00:37 (-0500) audio Routing ‘balena-sound.output’ to ‘alsa_output.bcm2835-jack.stereo-fallback’.
12.03.21 17:00:37 (-0500) audio W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).
12.03.21 17:00:37 (-0500) 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
12.03.21 17:00:37 (-0500) 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
12.03.21 17:01:43 (-0500) audio W: [pulseaudio] module-loopback.c: Configured latency of 200.00 ms is smaller than minimum latency, using minimum instead
12.03.21 17:01:43 (-0500) audio W: [pulseaudio] module-loopback.c: Cannot set requested source latency of 66.67 ms, adjusting to 250.00 ms
12.03.21 17:00:42 (-0500) multiroom-server 2021-03-12 22-00-42.436 [Notice] (StreamServer) StreamServer::NewConnection: 172.17.0.1
12.03.21 17:00:47 (-0500) multiroom-client 2021-03-12 22-00-47.469 [Notice] (Alsa) No chunk received for 5000ms. Closing ALSA.
12.03.21 16:58:16 (-0500) bluetooth Bluetooth agent started!
12.03.21 16:58:16 (-0500) bluetooth Checking for known bluetooth devices…
12.03.21 17:01:40 (-0500) bluetooth AuthorizeService (/org/bluez/hci0/dev_E4_B2_FB_85_C5_46, 0000110d-0000-1000-8000-00805f9b34fb)
12.03.21 16:57:42 (-0500) spotify Starting Spotify plugin…
12.03.21 16:57:42 (-0500) spotify Device name: balenaSound Spotify 85db
12.03.21 16:57:42 (-0500) spotify Volume normalization enabled.
12.03.21 16:57:42 (-0500) spotify Spotify audio cache disabled.
12.03.21 16:57:42 (-0500) spotify [2021-03-12T21:57:42Z INFO librespot] librespot (raspotify v0.16.0) 0adb851 (2020-12-15). Built on 2020-12-30. Build ID: KLdkAvgt
12.03.21 17:01:00 (-0500) airplay Waiting for audioblock to start…
12.03.21 17:01:05 (-0500) airplay Waiting for audioblock to start…
12.03.21 17:01:10 (-0500) airplay Waiting for audioblock to start…
12.03.21 17:01:15 (-0500) airplay Waiting for audioblock to start…
12.03.21 17:01:20 (-0500) airplay Waiting for audioblock to start…
12.03.21 17:01:25 (-0500) airplay Waiting for audioblock to start…
12.03.21 17:01:25 (-0500) airplay Shairport-sync started. Device is discoverable as balenaSound AirPlay 85db
12.03.21 16:56:39 (-0500) upnp gmediarender 0.0.7-git started [ gmediarender 0.0.7-git (libupnp-1.8.4; glib-2.58.1; gstreamer-1.14.4) ].
12.03.21 16:56:39 (-0500) upnp Logging switched off. Enable with --logfile= (or --logfile=stdout for console)
12.03.21 16:56:39 (-0500) upnp Ready for rendering.
12.03.21 17:00:17 (-0500) sound-supervisor Error connecting to audio block - Retry failed: connect ECONNREFUSED 192.168.10.246:4317
12.03.21 17:01:22 (-0500) sound-supervisor Connected to PulseAudio at 192.168.10.246:4317
12.03.21 17:01:22 (-0500) sound-supervisor Server protocol version: 33
12.03.21 17:01:22 (-0500) sound-supervisor Client protocol version: 33
12.03.21 17:01:27 (-0500) sound-supervisor Joining the fleet, requesting master info with fleet-sync…
12.03.21 17:02:09 (-0500) sound-supervisor Playback started, announcing 192.168.10.246 as multi-room master!

On the Other hand, my pi3 showed this:
12.03.21 16:58:09 (-0500) upnp Ready for rendering.
12.03.21 16:58:03 (-0500) spotify [2021-03-12T21:58:03Z INFO librespot] librespot (raspotify v0.16.0) 0adb851 (2020-12-15). Built on 2020-12-30. Build ID: KLdkAvgt
12.03.21 16:58:04 (-0500) bluetooth Bluetooth agent started!
12.03.21 16:58:04 (-0500) bluetooth Checking for known bluetooth devices…
12.03.21 16:58:30 (-0500) airplay Waiting for audioblock to start…
12.03.21 16:58:30 (-0500) airplay Shairport-sync started. Device is discoverable as balenaSound AirPlay a605
12.03.21 16:58:19 (-0500) multiroom-server 2021-03-12 21-58-19.311 [Notice] (StreamServer) StreamServer::NewConnection: 172.17.0.1
12.03.21 16:58:19 (-0500) multiroom-server 2021-03-12 21-58-19.456 [Notice] (StreamServer) StreamServer::NewConnection: 172.17.0.1
12.03.21 16:58:19 (-0500) multiroom-server 2021-03-12 21-58-19.459 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file
12.03.21 16:58:19 (-0500) multiroom-server 2021-03-12 21-58-19.460 [Error] (StreamSession) StreamSession write error (msg length: 0): Broken pipe
12.03.21 16:58:19 (-0500) multiroom-server 2021-03-12 21-58-19.460 [Error] (StreamSessionTCP) Error in socket shutdown: Transport endpoint is not connected
12.03.21 16:58:31 (-0500) sound-supervisor Joining the fleet, requesting master info with fleet-sync…

I connected to the pi 4 using bluetooth, and began playing music through the Spotify app. I can hear audio coming from the pi 4, but nothing out of the pi 3. I have started from scratch and even tried a new SD card, but am not sure how to get the multi-room functionality working.

Hi @sameer-gupta7447.
Could you please make sure you are using a newer version of the balenaSound project? I see here https://sound.balenalabs.io that our newest version is v3.4.2. You can use the “deploy with Balena” button to push your code. Moreover, you can read here some workarounds about audio issues and how to resolve them.

You can also find this useful piece of advice at the second link you’ve shared with me: Note: You can mix device types as long as your application type supports it. A great way of maximizing device compatibility is to select Raspberry Pi 1/Zero as your application type. This enables you to add any board from the Pi family, and even the balenaFin.

Hope these tips help. Please let me know if you have any other questions and I’ll be happy to assist further.
Georgia

I used the deploy to Balena and it is deploying v3.5.2. It says that the build was uploaded successfully, but it has been about an hour and it is still running. I will update with what the outcome is. I also built a new application with Rpi zero as application type.

Hi Sameer,

Could you get your device to update? Did you manage to solve the problem? Please let us know if we can help with anything else

I could not get the device to update. It still says it is deploying. It seems to be stuck. Although, when I click on the deploy, it doesn’t seem to be running any processes.

Hi there, might be the device has some problem unrelated to the application you are trying to deploy. There is a “Device diagnostics” section on your device dashboard page (check the sidebar on the left side) where you can run a few basic checks to test for some common problems. Can you run those and report back the result?

I have run the device diagnostics on both devices. What specific information should I look for in the output, or should I paste the entire outputs here?

Hello, It may be best if you post the whole output, so we can be sure we’ve covered everything.