Hi, can you download the entire logs and share them? There is a button on the top right corner in the dashboard. I’ll take a look and see what’s going on. Thanks!
@B.Shah to give it a try you’d need to deploy it again by using the same method you used the first time; or by going to balenaHub and clicking Deploy with balena on balenaSound, then choosing your existing application when you get to the dashboard (no need to create a new one - see below).
I am having the same problem. I have reinstalled and recreated the application already but it came out the same:
08.07.21 16:17:40 (+0200) multiroom-server Waiting for sound supervisor to start at 172.17.0.1:80
08.07.21 16:17:41 (+0200) audio Waiting for sound supervisor to start at 172.17.0.1:80
08.07.21 16:17:45 (+0200) multiroom-client Waiting for sound supervisor to start at 172.17.0.1:80
08.07.21 16:17:45 (+0200) multiroom-server Waiting for sound supervisor to start at 172.17.0.1:80
08.07.21 16:17:46 (+0200) audio Waiting for sound supervisor to start at 172.17.0.1:80
And so on and so forth. Spotify still does work but I am still wondering:
What is the Sound-Supervisor for? I reckon it has a pretty essential role but apparently it does work without it.
Can you help me get the status from “Exited” to “Running”? I am planning on building a big hive with many Pi Zero W’s and I do not want the project to end already. It is a great software so far! Sorry if I am missing something obvious. I have already looked through the guide, documentation and many threads.
Hey @u53r-0x539, the sound supervisor is mostly for the multi room audio feature. Running balenaSound on a single device won’t make use of it so it makes sense that it would work without it.
That said, I’m a bit confused with your previous statements. If you say spotify is working (and I assume sound is coming out of the speakers) then the sound supervisor must have started successfully. Getting a few “Waiting for sound supervisor to start” is fine as it takes a bit to start up, but eventually it should come up. Can you share a screenshot with the state of your device’s services as seen in balenacloud dashboard? Which services have exited?
I just noticed you are using Raspberry Pi Zero W. Pi Zeros can’t be used to be multiroom master servers so by default they run on what we call standalone mode. This means multiroom services will be “exited” and that’s fine. You can read more about modes of operation here: Usage - Home
For my clients I went with the cheapest option as the Raspberry Pi Zero WH or should I go higher than that to have a stable running system?
And for the funny little extra I bought an Pirate Audio HAT Line Out with a screen but the screen is not supported yet, right?
I saw both listed as compatible on the website when I bought them.
Thanks for the clarification of the sound supervisor!
Here is a screenshot with the state of the services:
I wasn’t trying to use it as multiroom master. When I wrote my first comment I only used it for playing music via Spotify. After that I started checking if I can use it as a client but it did not look like it was making attempts to be a client of my Pi4. Even though I set it to “SOUND_MODE: MULTI_ROOM_CLIENT” now it does not turn off the spotify service, and so on - as you can see in the screenshot.
And for the funny little extra I bought an Pirate Audio HAT Line Out with a screen but the screen is not supported yet, right?
What did you mean by the screen being supported? Are you looking to show some stats like which song is playing,etc on the screen?
if so, this is not a feature yet but i think it would be a cool one? We always accept contributions
The multiroom server service should exit by default on a pi zero WH. can you please share some logs from that service?
Can you also please share a screenshot for the SOUND_MODE: MULTI_ROOM_CLIENT variable you set?
I started the Pi4 and it registered as the multi-room master when I started playing music via Spotify.
Now I am starting the Pi0. I have a flag “Heartbeat not received.” for 5 minutes and “No logs yet”. I am restarting the Pi0. Same happens.
So I am flashing the sd card again with a new img.zip from the website. Now I am waiting until there are no downloading/installing flags anymore.
Here is the log of the Pi0 WH with a filter for the multiroom server service after i freshly reinstalled the OS:
The multiroom-server service is actually “Exited” this time and the multiroom-client is “Exited” too due to “STANDALONE”. Therefore the log is empty.
I am setting the device variable “SOUND_MODE” now:
Multiroom-server is still the only one that is “Exited”.
I get a lot of these:
multiroom-client 2021-07-14 16-37-09.860 [Error] (Connection) Failed to connect to host '192.168.178.56', error: Connection refused
multiroom-client 2021-07-14 16-37-09.861 [Error] (Controller) Error: Connection refused
multiroom-client 2021-07-14 16-37-09.861 [Error] (Connection) Error in socket shutdown: Socket not connected
multiroom-client 2021-07-14 16-37-10.863 [Error] (Connection) Failed to connect to host '192.168.178.56', error: Connection refused
multiroom-client 2021-07-14 16-37-10.864 [Error] (Controller) Error: Connection refused
multiroom-client 2021-07-14 16-37-10.864 [Error] (Connection) Error in socket shutdown: Socket not connected
I forgot to set the audio interface, so I set it and restart. I always get this now: “Request error: tunneling socket could not be established, statusCode=500”
About the sceen on the pirate, yes, we don’t support it yet though hopefully we will in the future.
So I am flashing the sd card again with a new img.zip from the website. Now I am waiting until there are no downloading/installing flags anymore.
Here is the log of the Pi0 WH with a filter for the multiroom server service after i freshly reinstalled the OS:
The multiroom-server service is actually “Exited” this time and the multiroom-client is “Exited” too due to “STANDALONE”. Therefore the log is empty.
I am setting the device variable “SOUND_MODE” now:
Multiroom-server is still the only one that is “Exited”.
This is correct, the multiroom server service wont be used on the Pi0.
The rest of the errors you describe to me sound like the Pi0 is not getting a good WiFi connection:
Now I am starting the Pi0. I have a flag “Heartbeat not received.” for 5 minutes and “No logs yet”. I am restarting the Pi0. Same happens.
multiroom-client 2021-07-14 16-37-09.860 [Error] (Connection) Failed to connect to host '192.168.178.56', error: Connection refused
multiroom-client 2021-07-14 16-37-09.861 [Error] (Controller) Error: Connection refused
multiroom-client 2021-07-14 16-37-09.861 [Error] (Connection) Error in socket shutdown: Socket not connected
“Request error: tunneling socket could not be established, statusCode=500”
This is a clear indicator that the Pi0 can’t reach our API server through the internet, and that’s also having trouble reach the Pi4 on 192.168.178.56.
Can you confirm the IP address of the Pi4 is 192.168.178.56? Also, can you verify the Pi0 has a stable WiFi connection? Try moving it closer to the router and see if that helps. A “hard reset” might be required, rebooting all devices.
Previously I layed down the Pi0 at a place where my laptop gets all the reception bars of the WiFi logo but I moved it up to 1m from the router away now.
I always turn off the Pi’s at night if that is the same as a “hard reset”?
What I get now from the Pi0 is a lot of these:
audio Waiting for sound supervisor to start at 172.17.0.1:80
Even though the Pi4 is on IP 192.168.178.55.
And it is constantly killing services:
Killed service 'logging sha256:065b139567278a1f...'
Service exited 'logging sha256:065b139567278a1f...'
Killing service 'audio sha256:46a465f397dcc7fbf25...'
Now they are all “Exited”.
I am trying the “Reboot” button but it is giving me:
“Request error: tunneling socket could not be established, statusCode=500”
Sorry to hear you’re having trouble. It’s this kind of feedback that lets us better troubleshoot things and see what’s going on. I wanted to echo my teammate’s comment about your pi0 not having a strong connection. I have a few questions about your setup:
what kind of router are you using? 2.4Ghz? 5Ghz? Is your 2,4Ghz band jammed with other devices that might be interfering with the pi0?
does it stop throwing 500 network errors when you move it back to its original spot?
are there a lot of wireless devices in the room where you’re testing that might be causing interference?
Also, I recommend giving us some deeper logs so that our team can better investigate what’s going on with your device. Please see the kernel log section of this masterclass to learn more about how to generate this for us. Hope this helps and best of luck!
The router is set to 2.4Ghz (2.422, 2.427, 2.432, 2.437, 2.442). There are 2 other networks on this spectrum. I have the router connected to a Repeater via Ethernet. But in the network are not more than 5 wireless devices.
Before moving it: Trying to shut it down = ESOCKETTIMEDOUT
After moving it: Trying to shut it down = ESOCKETTIMEDOUT
At the router: ~ 3 devices.
Old position: ~ 3 devices + 1 Pi4
I am not exactly sure how long I am supposed to wait before starting the “dmesg” command but here is the log. Please let me know if I was doing it wrong. pi0_22072021.txt (40.2 KB)
It is a great software so far! Sorry if I am missing something obvious. I have already looked through the guide, documentation and many threads.
