I’m having an issue of anything playing off the Spotify streams now since updating. Device will connect, pause Spotify, lose the connection, can’t be found again. Have tried rebooting multiple times, deleting the sources/readding the sources.
UPDATE:
went back to 4.4, worked.
updated to 4.5 again, still not working. do not see any errors triggering though?
That’s odd. We haven’t seen this behavior in any of our testing. Some additional information from the go-librespot spotify client is logged in /home/pi/.config/amplipi/srcs/v*/log. Would you mind sending the contents of that file as well as http://amplipi.local:19531/entries when this happens?
Thanks AmpliPi Team!
The Spotify connection has been working well for me so far (installed yesterday). I will let you know if I have any other connectivity issues.
The only issue I noticed is that it seems to completely ignore the volume changes I make on the device. I have to change it from the AmpliPi app. Not a huge deal for me, but just wanted to let you know.
Yeah when we tested the new Spotify client’s integrated volume control it degraded the audio quality so initially we disabled it. I realize this a pretty useful feature. We are hoping to add back volume control in the future via the volume control pass-through capability that the new client has.
@matchmee after checking in with the go-librespot guys the next steps are to get a stack trace of the failure condition. The Spotify client, go-librespot, uses a SIGABRT signal to dump the current state of each go thread to its logfile. This should provide a ton of info about the state the Spotify client gets into when it is in this failure condition.
Would you mind running the following commands on you unit over an SSH connection right after you experience the Spotify failure? I tested them on one of our internal development units.
After sending those commands, please send us the contents of matchmee_spotify_logs.txt
Also relevant may be any extra details about you internet connection that could be adding delay. Is this running through a VPN or something like a pi hole? Or does the unit live on a VLAN restricted in another way?
I am very sorry, holiday travel and everything had a long time getting through. Your message about asking Pihole got me thinking, and sure enough my pihole was blocking the requests! I was able to whitelist the issue and then it started working! Apologies on that one!
Would you happen to be able to share what you had to whitelist to get this to work? I have a feeling future Pihole (or similar firewalls) users will thank you.
