Hi - the 104 error is a direct result of a TCP stream connection drop - somwhere along the chain from your device to the spotify servers - it’s not uncommon for the Spotify servers to drop a few packets. Unfortunately this means the session is dropped and the daemon is restarted - but not the WebUI doesn’t know of it - thus hanging in the old state.
I will look into handling this error in a more robust fashion.
@Balbuze
Maybe you could revert my (compulsive) renaming of the binary – that way people can just reinstall the plugin rather than await the patch to be merged?
I have been asked if my mpd_oled OLED display program could have a working spectrum analyser with the Volumio Spotify plugin.
The mpd_oled program calculates the spectrum using a copy of the the audio stream sent to a FIFO. This is normally provided by MPD, but as the Spotify plugin does not use MPD there is no spectrum data displayed when using the plugin. However, it looks like librespot supports copying the audio data to a FIFO
How could I configure the Spotify plugin to provide a FIFO the same as the MPD FIFO (format “44100:16:2”)? Also, is it possible to re-use the same FIFO that is being used by MPD?
The aim is to produce installation instructions for the mpd_oled program. If necessary I can provide patches to make system changes if the area being changed would not be expected to change often.
I don’t currently use Spotify. I thought I would check if it seems reasonable to implement this before signing up for the Premium trial.
Hi,
Everything is kind of working, but I have problems with it being very slow to respond to starting and skipping tracks. It usually takes around 11 seconds before a track will start playing. Watching on the my-player-url/dev page I can watch the track change to a new track instantly and the “seek” value starts counting up from zero to around 11 seconds (~11000) with silence, it then it reset to 0 and starts playing properly.
I have rebuilt the pi once and tried every dev version, but to no avail. Is there something else I can try?
(I have tried buffering settings etc. - my download speed is around 16MBps so I don’t think this is the cause).
Thanks again for a great plugin
John
I’m a bit confused if I should install the plugin with ssh or just the one in the web gui. I used the one in the web gui which states Volumio Spotify Connect2 0.7.4 is that the current version or should I remove this and install with ssh?
Hello,could you please tell me step by step how should I install this plugin ? I tried but something goes wrong or I dont know how to use this plugin. From the beginning: In volumio I had installed only Spotify plugin. Then I logged in to volumio using putty, then typed following lines:
wget github.com/balbuze/volumio-plug … nnect2.zip
mkdir ./volspotconnect2
miniunzip volspotconnect2.zip -d ./volspotconnect2
cd ./volspotconnect2
volumio plugin install
New plugin in volumio appeared, I eneabled it but what now ? I have spotify app on my phone and PC, but when I play one of the songs nothing happens.
I am constantly losing the connection to the volspotconnect2. I can only play a couple of songs before I lose the connection. If I restart the plugin by saving the settings once again I can play of couple of songs before losing the connection. Reboot the device is the same.
I am running my RPI 3 on my network with a ethernet cable. I have installed the plugin over ssh using the guide from GitHub (dev. v. 0.7.8) and I have updated my Volumio to the latest version (2.457). Switching to multi-user in settings doesn’t fix the problem…
Have anyone tried the same og know a potential fix?
Does this happen to you all of the time or just occasionally? I have intermittent issues with spotify all of the time I don’t think they are related to Volumio or the volspotconnect2 plugin itself as I had the exact same issues on chromecast audio devices and my Yamaha network A/V receivers.
For reference I use the Spotify app on Android and the app is junk it only works when it wants for me, not sure if you have a similar experience. I think all (or most at least) of my issues are on their end.