I installed the new version of Volumio, 2.114, img downloaded from the web burning a new SD.
I can not get My Spotify Playlists, the other functions of Spotify work correctly. In fact in the previous version this worked correctly.
Any idea?
I can access my playlists without problems on v2.114 on a RPi3, so looks like a local problem. Not sure how useful it would be, but you could try looking at logs and journal output.
Said this:
Mar 04 12:44:50 volumio volumio[856]: info: CoreCommandRouter::executeOnPlugin: spop , handleBrowseUri
Mar 04 12:44:50 volumio volumio[856]: info: [1488631490038] ControllerSpop::sendSpopCommand
Mar 04 12:44:50 volumio volumio[856]: info: ADDING DEFER FOR COMMAND ls
Mar 04 12:44:50 volumio volumio[856]: info: SPOP command error:
Mar 04 12:44:50 volumio volumio[856]: info: Error: This socket has been ended by the other party
Mar 04 12:44:50 volumio volumio[856]: at Socket.writeAfterFIN [as write] (net.js:291:12)
Mar 04 12:44:50 volumio volumio[856]: at applyWithContext (/data/plugins/music_service/spop/node_modules/fast.js/function/applyWithContext.js:15:22)
Mar 04 12:44:50 volumio volumio[856]: at /data/plugins/music_service/spop/node_modules/fast.js/function/bind.js:63:14
Mar 04 12:44:50 volumio volumio[856]: at onBoundPromise (/data/plugins/music_service/spop/node_modules/kew/kew.js:834:10)
Mar 04 12:44:50 volumio volumio[856]: at ncall (/data/plugins/music_service/spop/node_modules/kew/kew.js:816:44)
Mar 04 12:44:50 volumio volumio[856]: at Object.nfcall (/data/plugins/music_service/spop/node_modules/kew/kew.js:803:16)
Mar 04 12:44:50 volumio volumio[856]: at Promise._successFn (/data/plugins/music_service/spop/index.js:1201:16)
Mar 04 12:44:50 volumio volumio[856]: at nextTickCallback (/data/plugins/music_service/spop/node_modules/kew/kew.js:47:28)
Mar 04 12:44:50 volumio volumio[856]: at _combinedTickCallback (internal/process/next_tick.js:67:7)
Mar 04 12:44:50 volumio volumio[856]: at process._tickCallback (internal/process/next_tick.js:98:9)
Any idea?
Regards
When I deactivate Spotify and re-enable it, it says this:
login as: volumio
volumio@192.168.0.25’s password:
___
/_ \ __
__ __ //\ \ __ __ ___ ___ /_\ ___
/\ /\ \ / __\\ \ \ /\ \/\ \ /' __ __\/\ \ / __
\ \ _/ |/\ \L\ \\ _\ \ _\ /\ /\ /\ \ \ /\ \L\
\ _/ \ _//_\ _/\ _\ _\ _\ _\ _/
// // // // /////////___/
Free Audiophile Linux Music Player - Version 2.0
C 2015 Michelangelo Guarise - Volumio Team - Volumio.org
Volumio Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
volumio@volumio:~$ sudo journalctl -f
– Logs begin at Sat 2017-03-04 14:13:08 UTC. –
Mar 04 14:23:30 volumio systemd[1125]: Starting Basic System.
Mar 04 14:23:30 volumio systemd[1125]: Reached target Basic System.
Mar 04 14:23:30 volumio systemd[1125]: Starting Default.
Mar 04 14:23:30 volumio systemd[1125]: Reached target Default.
Mar 04 14:23:30 volumio systemd[1125]: Startup finished in 44ms.
Mar 04 14:23:30 volumio systemd[1]: Started User Manager for UID 1000.
Mar 04 14:23:30 volumio sshd[1119]: lastlog_openseek: Couldn’t stat /var/log/lastlog: No such file or directory
Mar 04 14:23:30 volumio sshd[1119]: lastlog_openseek: Couldn’t stat /var/log/lastlog: No such file or directory
Mar 04 14:23:36 volumio sudo[1139]: volumio : TTY=pts/0 ; PWD=/home/volumio ; USER=root ; COMMAND=/bin/journalctl -f
Mar 04 14:23:36 volumio sudo[1139]: pam_unix(sudo:session): session opened for user root by volumio(uid=0)
Mar 04 14:23:41 volumio volumio[841]: info: [{“prettyName”:“GPIO Buttons”,“name”:“gpio-buttons”,“category”:“miscellanea”,“version”:“0.7.6”,“icon”:“fa fa-cube”,“enabled”:true,“active”:true},{“prettyName”:“Spotify”,“name”:“spop”,“category”:“music_service”,“version”:“1.2.0”,“icon”:“fa-spotify”,“enabled”:true,“active”:true}]
Mar 04 14:23:45 volumio volumio[841]: info: Stopping plugin spop
Mar 04 14:23:45 volumio volumio[841]: info: Killing SpopD daemon
Mar 04 14:23:45 volumio volumio[841]: info: Disabling plugin spop
Mar 04 14:23:45 volumio volumio[841]: info: Done.
Mar 04 14:23:45 volumio sudo[1146]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/killall spopd
Mar 04 14:23:45 volumio sudo[1146]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 04 14:23:45 volumio sudo[1146]: pam_unix(sudo:session): session closed for user root
Mar 04 14:23:45 volumio volumio[841]: info: Cannot kill spop Daemon
Mar 04 14:24:01 volumio volumio[841]: info: Enabling plugin spop
Mar 04 14:24:01 volumio volumio[841]: info: Loading plugin “spop”…
Mar 04 14:24:01 volumio volumio[841]: info: Applying required configuration parameters for plugin spop
Mar 04 14:24:01 volumio volumio[841]: PLUGIN START: spop
Mar 04 14:24:01 volumio sudo[1155]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl start spop.service
Mar 04 14:24:01 volumio sudo[1155]: pam_unix(sudo:session): session opened for user root by (uid=0)
Mar 04 14:24:01 volumio systemd[1]: Starting Spotify Daemon…
Mar 04 14:24:01 volumio systemd[1]: Started Spotify Daemon.
Mar 04 14:24:01 volumio sudo[1155]: pam_unix(sudo:session): session closed for user root
Mar 04 14:24:01 volumio volumio[841]: info: SpopD Daemon Started
Mar 04 14:24:01 volumio volumio[1160]: 2017-03-04 14:24:01 [SPTF] 14:24:01.507 I [offline_authorizer.cpp:297] Unable to login offline: no such user
Mar 04 14:24:01 volumio volumio[1160]: 2017-03-04 14:24:01 [SPTF] 14:24:01.512 I [ap:1752] Connecting to AP ap.spotify.com:4070
Mar 04 14:24:06 volumio volumio[841]: info: Connecting to daemon
Mar 04 14:24:06 volumio volumio[1160]: 2017-03-04 14:24:06 [SPTF] 14:24:06.516 E [ap:1694] AP Socket Error: Timeout reached (20000)
Mar 04 14:24:06 volumio volumio[1160]: 2017-03-04 14:24:06 [SPTF] 14:24:06.517 E [ap:3953] Connection error: 117
Mar 04 14:24:06 volumio volumio[1160]: 2017-03-04 14:24:06 [SPTF] 14:24:06.517 I [ap:1752] Connecting to AP ap.spotify.com:443
Mar 04 14:24:06 volumio volumio[841]: info: CoreCommandRouter::volumioAddToBrowseSources[object Object]
Mar 04 14:24:06 volumio volumio[841]: info: [1488637446536] CoreMusicLibrary::Adding element Spotify
Mar 04 14:24:06 volumio volumio[841]: info: Done.
Mar 04 14:24:06 volumio volumio[841]: info: FIRST BRANCH
Mar 04 14:24:11 volumio volumio[1160]: 2017-03-04 14:24:11 [SPTF] 14:24:11.523 E [ap:1694] AP Socket Error: Timeout reached (20000)
Mar 04 14:24:11 volumio volumio[1160]: 2017-03-04 14:24:11 [SPTF] 14:24:11.525 E [ap:3953] Connection error: 117
Mar 04 14:24:11 volumio volumio[1160]: 2017-03-04 14:24:11 [SPTF] 14:24:11.527 I [ap:1752] Connecting to AP ap.spotify.com:80
Mar 04 14:24:12 volumio volumio[841]: info: Spotify access token expires at 1488641046518
Mar 04 14:24:12 volumio volumio[841]: info: Spotify access token is BQCNRQQxFC2iVsehmL0a4TxTtkdOnfNv42fDcZOaEJL5LS8cSiheG_urIYEEYTFYDczmNrD3lV_J0RfuxL76EA
Mar 04 14:24:12 volumio volumio[841]: info: Spotify credentials grant success
Mar 04 14:24:16 volumio volumio[1160]: 2017-03-04 14:24:16 [SPTF] 14:24:16.533 E [ap:1694] AP Socket Error: Timeout reached (20000)
Mar 04 14:24:16 volumio volumio[1160]: 2017-03-04 14:24:16 [SPTF] 14:24:16.534 E [ap:3953] Connection error: 117
Mar 04 14:24:16 volumio volumio[1160]: 2017-03-04 14:24:16 [SPTF] 14:24:16.534 I [ap:1752] Connecting to AP ap.spotify.com:4070
Mar 04 14:24:21 volumio volumio[1160]: 2017-03-04 14:24:21 [SPTF] 14:24:21.538 E [ap:1694] AP Socket Error: Timeout reached (20000)
Mar 04 14:24:21 volumio volumio[1160]: 2017-03-04 14:24:21 [SPTF] 14:24:21.538 E [ap:3953] Connection error: 117
Mar 04 14:24:21 volumio volumio[1160]: 2017-03-04 14:24:21 [SPTF] 14:24:21.538 I [ap:1752] Connecting to AP ap.spotify.com:443
Mar 04 14:24:26 volumio volumio[1160]: 2017-03-04 14:24:26 [SPTF] 14:24:26.542 E [ap:1694] AP Socket Error: Timeout reached (20000)
Mar 04 14:24:26 volumio volumio[1160]: 2017-03-04 14:24:26 [SPTF] 14:24:26.542 E [ap:3953] Connection error: 117
Mar 04 14:24:26 volumio volumio[1160]: 2017-03-04 14:24:26 [SPTF] 14:24:26.543 I [ap:1752] Connecting to AP ap.spotify.com:80
Mar 04 14:24:31 volumio volumio[1160]: 2017-03-04 14:24:31 [SPTF] 14:24:31.546 E [ap:1694] AP Socket Error: Timeout reached (20000)
Mar 04 14:24:31 volumio volumio[1160]: 2017-03-04 14:24:31 [SPTF] 14:24:31.547 E [ap:3953] Connection error: 117
Mar 04 14:24:31 volumio volumio[1160]: 2017-03-04 14:24:31 [WARN] Login failed: Cannot connect to Spotify
Mar 04 14:24:31 volumio volumio[1160]: 2017-03-04 14:24:31 [ERR ] Could not get the playlist container.
Mar 04 14:24:31 volumio systemd[1]: spop.service: main process exited, code=killed, status=5/TRAP
Mar 04 14:24:31 volumio systemd[1]: Unit spop.service entered failed state.
For some reason does not connect with Spotify, will it be a local problem or is there something wrong with Volumio?
I installed the previous version that did work?
Regards
I have the same issue: Since I updated to V2.114 Spotify My Playlists doesn’t work any more. Nothing happens when I choose it. The other Spotify functions work fine.
System: Pi 2 Model B, HifiBerry DAC+, Wifi: TP-Link TL-WN725N, Volumio 2.114, router: FritzBox 7272
Appreciate any help on this.
Greetings.
This is definitely a regression - personal playlists are broken in 2.114. I can’t figure out why as I don’t think this code has been touched for months. The rest of the Spotify interface uses the new Spotify Web API, the personal playlists uses the old and deprecated libspotify. Nothing in my log file helps, so I’m stumped.
So … if we go back to Volumio 2.0 will it work again?
Regards
2.095 (from late February) or earlier should work.
Where can I download it from?
Regards
I was worried Spotify might have shut down usage of Libspotify, but that’s not the case. Until we can figure out what’s wrong here, a slow workaround is to use the CLI for Libspotify, documented here:
So ssh into your Volumio system and type:
telnet localhost 6602
Then to list your playlists type:
ls
Each playlist has an index, and you can play it with:
play
To stop type:
stop
Hopefully we will have a fix soon.
I had the same feeling, (since the shutdown of libspotify is due in 2017).
I really wonder what could have happened… I’m investigating…
While the new Spotify Web API replaces the need for Libspotify for metadata (e.g. listing personal playlists), there is still no replacement for playback of Spotify audio tracks. Spotify has promised they will provide that in 2017, so hopefully they’ll put out a new, supported library for playback first, then remove life support libspotify a few months later.
Can I just repeat gently, that my playlists are still working fine (tried on 3 devices).
Could it be that the Spanish translation of Volumio causes the plugin not to install correctly?
When I tried to install Spotify in Spanish Volumio it took a lot and there was no way login. Uninstallation did not complete the uninstallation.
I went to English and I was able to uninstall, install it and log in without problems.
I know this is very unlikely, but I wanted to talk about it.
Regards
Wow, this is strange. Spotify personal playlists no longer show up on my Volumio 2.041 system running on a Raspberry Pi 1 B+ model. I click on “My Playlists” and nothing happens. The log file shows this:
2017-03-05T18:29:31.130Z - info: [1488738571123] ControllerSpop::sendSpopCommand
2017-03-05T18:29:31.142Z - info: ADDING DEFER FOR COMMAND ls
2017-03-05T18:29:31.224Z - info: FIRST BRANCH
2017-03-05T18:29:31.232Z - info: BEFORE: SPOP HAS 1 PROMISE IN STACK
2017-03-05T18:29:31.241Z - info: AFTER: SPOP HAS 0 PROMISE IN STACK
2017-03-05T18:29:31.266Z - info: FIRST BRANCH
2017-03-05T18:29:31.274Z - info: BEFORE: SPOP HAS 0 PROMISE IN STACK
2017-03-05T18:29:31.280Z - info: AFTER: SPOP HAS 0 PROMISE IN STACK
On 2.114 I click on “My Playlists” and I go to a blank screen and the log file show this:
2017-03-05T18:32:23.051Z - info: [1488738743048] ControllerSpop::sendSpopCommand
2017-03-05T18:32:23.055Z - info: ADDING DEFER FOR COMMAND ls
2017-03-05T18:32:23.066Z - info: FIRST BRANCH
2017-03-05T18:32:23.068Z - info: BEFORE: SPOP HAS 1 PROMISE IN STACK
2017-03-05T18:32:23.071Z - info: AFTER: SPOP HAS 0 PROMISE IN STACK
But, Balbuze’s Spotify Connect plugin is still working for me on my older Volumio system! No idea what’s happening here.
Mmhh… I did a downgrade to V2.06 now. Same problem! “My Playlists” doesn’t work.
Other Spotify functions are ok.
Already uninstalled and reinstalled the Spotify plugin. Didn’t help. Although I did a factory reset and reinstalled the Spotify plugin. Didn’t help.
Interesting: Directly after I installed the Plugin I could access My Playlists once. I get my list, but many rows are empty.
Every other attempt by selecting “My Playlists”: Nothing happens.
Anything new about this problem? I returned to version 2.041 and everything is perfect.
Regards
“My Playlist” still not working on my system 
So far I tried the following Volumio versions: 2.001 / 2.06 / 2.114 / 2.118
Always the same behavior:
Featured Playlists / What’s New / Genres And Moods: Working fine.
My Playlists: Nothing happens.
This is whats’s going on in the journal when I select MyPlaylists:
Mar 12 11:15:45 volumio volumio[891]: info: CoreCommandRouter::executeOnPlugin: spop , handleBrowseUri
Mar 12 11:15:45 volumio volumio[891]: info: [1489317345259] ControllerSpop::sendSpopCommand
Mar 12 11:15:45 volumio volumio[891]: info: ADDING DEFER FOR COMMAND ls
Mar 12 11:15:45 volumio volumio[891]: info: FIRST BRANCH
Mar 12 11:15:45 volumio volumio[891]: info: BEFORE: SPOP HAS 1 PROMISE IN STACK
Mar 12 11:15:45 volumio volumio[891]: info: AFTER: SPOP HAS 0 PROMISE IN STACK
Mar 12 11:15:45 volumio volumio[891]: info: FIRST BRANCH
Mar 12 11:15:45 volumio volumio[891]: info: BEFORE: SPOP HAS 0 PROMISE IN STACK
Mar 12 11:15:45 volumio volumio[891]: info: AFTER: SPOP HAS 0 PROMISE IN STACK
From time to time this is added to the journal:
Mar 12 11:25:20 volumio volumio[955]: 2017-03-12 11:25:20 [SPTF] 11:25:20.166 E [ap:4210] ChannelError(0, 1, playlist)
Mar 12 11:28:35 volumio volumio[955]: 2017-03-12 11:28:35 [SPTF] 11:28:35.263 E [ap:4210] ChannelError(0, 1, playlist)
Mar 12 11:30:40 volumio volumio[955]: 2017-03-12 11:30:40 [SPTF] 11:30:40.391 E [ap:4210] ChannelError(0, 0, playlist
Is there anyting I can do to solve this?
Any suggestions for debugging?
Thanks!
Do you have another spotify instance running elsewhere? (pc, phone etc)
In my case, no.