Okay…I will test with it, although the default volume is loud enough when I turn the USB audio volume up. I was just curious.
I also have a RPi 3b with LibreElec/Kodi installed, where also a spotify connect (based on fornoth) add-on can be installed from the default libreElec add-ons. User “awiouy” created it. This also works like a charm, I will test this start-stop problem also on the LibreElec/Kodi machine. If this works there, maybe you can get in touch with this guy.
Hi balbuze,
many thanks for your great work. I enjoy music with your plugin every day!
I’m wondering if and how the spotify cache path can by modified to keep the lifetime of the SD-card as high as possible.
On Volumio 1.5 it was possible to use a RAM-disk for the caching. Is there a similar possibility?
small question:
do I need to uninstall the standard spotify plugin before I can install / use this plugin with spotify connect. Or can I run them both?
No problem of having both installed. But you can’t have both playing in the same time… And Volumio mustn’t play something (local file or radio) to be able to use it.
thanks!
yes it does work 
but if i want to play something else after using spotify Connect… I must reboot volumio?
No just stop playing in Spotify…
works fine. thanks!
(will this be offered as a default plugin in volumio shortly?)
At home i have pre-installed volumio 2 with volspotconnect for a friend.
Everything worked fine however i did not check if spotify multi user login worked.
When installed the pi2 at my friends house i noticed that multi user (avahi) login didn’t work.
Only the premium user that types the credentials in the volspotconnect plugin is able to see spotify connect.
Is it possible that the usb dac plugged in a different usb slot (i unplugged it for the transport to my friend) might cause this error?
Multi user works only with a Family account and with account included in it. Without, only the user with credentials can connect. This a Spotify rule.
Hmmm…strange, with the libreelec plug-in which also uses the fornoth, any premium user in my network sees the libreelec connect speaker in the spotify app and is able to select it and play music…but in the volspotconnect plug-in only the user which credentials are set can see the connect speaker in the spotify app!?
Interesting ! I really thought only family account was allowed. In my case, it works only with that. Do you know the config used?. I’ll have a look this weekend
Hi,
still works on my raspberry with hifiberry plus, so there might be no need to update (never touch a running system 
). But in case if? What to do. Uninstall the old version first? But what’s about the comment in the readme.md nov 30th: “chroot version should uninstall properly now ( without braking volumio)”
Any advice would be welcome.
Thanks, Caunus
In fact, the chroot version needs root right access to run. The problem is that files own by root are created in the plugin folder. When removing plugin, user Volumio is used and fails to remove this files and the plugin from register. And then it fails to reboot volumio service… It’s easy to repair, as sudo user remove the folder and the entry in config file and it should be ok. In the last version I thought I had solved it, but it seems no… And I made chroot file smaller :70Mo (previous was 170Mo). And I’m trying to reduce it. But it seems it’s not on the repo yet…
Maybe you should contact awiouy, you both can share knowledge…i think he is interested in your spotify key solution and you in his avahi login? In a previous post i already put a link to his thread
I’ve been in touch with awiouy, thanks. I’ll have a look at his config.
@gschmit : I made a modification that should help. I uploaded it on github. But if you want to test, just modify
/data/plugins/music_service/volspotconnect/volspotconnect.tmplto add -s after avahi-publish-service
cd /data/plugins/music_service/volspotconnect/spotify-connect-web
./spotify-connect-web --username '${username}' --password '${password}' --bitrate ${rate} --name '${devicename}' --playback_device ${outdev} ${mixer} ${mixind} --dbrange 45 ${familyshare} &
avahi-publish-service -s '${devicename}' _spotify-connect._tcp 4000 VERSION=1.0 CPath=/login/_zeroconf
After, save config in plugin.
let me know
Thx man, I’ll test it as soon as i visit my friend again my pi has libreelec because i like to watch some videos too
Update: I have checked the “spotify-connect-web.start” file from the libreelec addon, and there is indeed the “-s” parameter
Is it easy for a “computer illiterate” to update a new version of volspotconnect.zip file?
If running on a rpi2 or rp3 it’s dead easy : unistall plugin from the webUI, refresh the page and install the file you have downloaded…
With a RPI A, B or RPI ZERO, it’s a bit more complicated…
But you can do this
From webUI uninstall plugin even if it will fail at the end.
From a ssh console
sudo rm -Rf /data/plugins/music_service/volspotconnectand after
killall nodeand install the new plugin.
I told you, it’s a bit more complicated. But I’m working on that point…
Its a pi2b, my friend should manage then! Me know sudo 
, but live too far from friend…thx man