Not sure it will work by changing ${devicename} because the index.js will fail to fill this field and then generate an error. It is better to change it in startconnect.sh once generated by the plugin. But erased each time you save something in the plugin…( that should not happen very often)
Sorry, RaspPi3, Allo Boss DAC, now last dev Volumio.
What I did not do now is to uninstall volspotconnet before installing volspotconnect2, is it necessary?
regard
In the first version of volspotconnect, a field in setting allowed to set the name. I remove it because I don’ see the interest of setting a different name from volumio itself, that can be change. Now it is selfconfigured… But if thousand of users need it…
OK I see
But do you think it is really useful in that case? If yes, I’ll add a field for that, and if empty, the default name will be the one set in volumio… What do you think?
Well, I uninstalled volspotconnect and volspotconnect2, I rebooted, I installed volspotconnect2 and it does not connect, there’s no way.
I went back to voslpotconnect and it works correctly.
I have installed simpleequalizer without activating (it starts 100% in the last two dev versions of Volumio, before it worked correctly), LastFm Scrobbler, Autoplay and RadioParadise.
I’m in Argentina, will it be a problem with the Spotify servers?
regard
For me it would be useful, because I user upper case for the first letter of the player, and after a reboot of raspberry or restart volspotconnect2 plugin it is often only lowercase. And now with latest dev version I cannot change the name anymore if I change name in system.
It is probably my ocd talking but I like the names clean.
Thanks anyway and thanks for the great work on the plugins!
Just to update on my issue. I solved the problem by doing a factory reset and reinstalled the volspotconnect2 plugin from github. It is working fine now.
baba86, unfortunately the official plugin manager has not yet been updated (you should be able to tell from the ‘updated on’ field). So directly from the repo is the option right now.
Hey Guys,
i am currently using Raspberry Zero W connected via Wifi.
With volspotconnect2 after about 10 to 15 Minutes the music often justs stops but the cover is still showing up on the volumio homepage and is stated as playing. After that i can’t connect anymore via spotify connect.
Volspotconnect 1 seems to be much more reliable in this kind of regards, but i would like to use shuffle.
The pi can play an internetradio stream for hours without interruption, so the wifi signal seems to be stable.
Has got anybody the same problem with volspotconnect2?
Logs://
[spoiler]Jun 03 11:22:23 volumio volumio[16559]: INFO:librespot_playback::player: SpCon::metadata
Jun 03 11:22:23 volumio volumio[7074]: info: [SpConDebug] Pushing metadata::Vollibrespot:true
Jun 03 11:22:24 volumio volumio[16559]: INFO:librespot_playback::player: Loading track “I Got 5 On It - Feat. Michael Marshall” with Spotify URI “spotify:track:4IYKjN1DrYzxKXt0umJqsG”
Jun 03 11:22:24 volumio volumio[16559]: INFO:librespot_playback::player: Normalisation Data: NormalisationData { track_gain_db: -6.239998, track_peak: 1.0128862, album_gain_db: -6.6600037, album_peak: 1.0332344 }
Jun 03 11:22:24 volumio volumio[16559]: INFO:librespot_playback::player: Applied normalisation factor: 0.48752862
Jun 03 11:22:25 volumio volumio[16559]: INFO:librespot_playback::player: Track “I Got 5 On It - Feat. Michael Marshall” loaded
Jun 03 11:22:25 volumio volumio[16559]: INFO:librespot_playback::player: SpCon::kSpPlayTrackChanged
Jun 03 11:22:25 volumio volumio[7074]: info: [SpConDebug] Sink acquired
Jun 03 11:22:25 volumio volumio[16559]: INFO:librespot_playback::player: SpCon::kSpSinkActive
Jun 03 11:26:38 volumio volumio[7074]: info: [SpConDebug] Sink released
Jun 03 11:26:38 volumio volumio[16559]: INFO:librespot_playback::player: SpCon::kSpSinkInactive
Jun 03 11:26:38 volumio volumio[16559]: ERROR:librespot_core::session: Error { repr: Os { code: 104, message: “Connection reset by peer” } }[/spoiler]