3. August 2017 at 10:40 #30362
meine Spotify Connect Installation funktioniert grundsätzlich. Aber nach etwa 1 Tag verliert Spotify Connect die Verbindung und die Player werden bei Spotify nicht mehr angezeigt. Ich muss dann den Spotify Connect Dienst neustarten. Dann werden die Player wieder erkannt.
Die folgende Version ist installiert:
INFO:librespot: librespot cc9dba8 (2017-03-26). Built on 2017-07-17. Build ID: 8zQE3Bpb3. August 2017 at 12:46 #30368
Have you done the steps in the web interface, yet?
When using other players on this device, like Squeezelite, make sure that these players do not exclusively block or mute the sound card. Add ‚-C 10‘ to the Squeezelite commandline settings in advanced options on the Audioplayer tab, to tell Squeezelite to disconnect from the soundcard after 10 seconds if nothing is playing and make sure to remove the ‚-Q‘ option. Otherwise, the volume will be set to 0 when Squeezelite is paused.
Make sure to ‚Disable IPv6‘ in Raspberry Pi Settings (if not disabled yet).
Also, do you have any command line options set up in the player’s interface?3. August 2017 at 13:27 #30373
If you are using Squeezelite or any other player as well, have you tried disabling it for a while to see whether the problem with Spotify Connect persists?
Generally, this issue is probably related to the Spotify servers. But this step would rule out Squeezelite interference as the source of the error, which could also be related.9. August 2017 at 8:52 #30501
I have the same problem. The player is no longer displayed in the spotify list somtimes already after a view minutes.
My Pi is over LAN connected on the same hub like my pioneer receiver with „spotify connect“. The pioneer is always displayed in the spotify list.
Is there a log file to check the spotify connect player on the pi, so that you can see what is happen?11. August 2017 at 12:41 #30567
I was now able to test it and while it took a long time to occur, I was able to recreate the error once.
However, unfortunately this issue is not related to Max2Play or the implementation of librespot on it. Here it is: https://github.com/plietar/librespot/issues/156
It is a bug that will probably soon be fixed. Once this is the case, this fix will also occur in Max2Play and will inform you.
If this issue is so persistent with your setup that you need an alternative, please have a look at this solution with the Squeezebox Server:
You must be logged in to reply to this topic.