New Volumio Spotify Plugin Open Beta-Testing

[tiggr]

I have exactly the same behavior!

[volumio]

@gergo

I am running version 3.423, with Spotify plugin 3.0.7. What I experience is the following: when I click on a song in a list in Spotify (e.g. in a list of search results), the plugin starts playing the NEXT song, and I can never start the very first. Any clue from anybody why this is happening? Otherwise seems working, with some inconveniences, like when I pause a song for a longer period, cannot continue it, have to start another one, but I can live with that.

Working on it

[michel8166]

now solved, the problem was in the reclocker that was in between that caused the spotify stream to stop.

[gergo]

Fantastic news! Thanks a lot for the update.

[hifiswede]

could librespot be installed in console (latest version) like in the old days?

[volumio]

Hi guys,
a big rework of Spotify plugin is in the works, and testing done over the weekend showed really promising improvements.
We hope to release it soon

[chourmovs_vs]

Great news, have fun coding that

[hifiswede]

awesome news, thank you guys

[TheToneCapone]

Hey all! Anyone else having an issue with any music being played over Spotify Connect immediately pausing after hitting play? I can’t get any song to play for more than a second.

Hopefully the new plugin solves this!

Edit: A reflash and rebuild of Volumio has fixed this issue for now, but I can’t wait for the updates. Anything to make Spotify more stable is welcome in my book!

[gergo]

Fantastic news!

[GlennBurnett]

Awesome let me know if you want early beta testing again. Happy to help out with that!

[mervinio]

Ciao!

We have released an update to the spotify plugin (3.0.8). Please update from the plugins store, reboot your device and enjoy!

This update has improvements for playlists, gapless playback and volume control. If there are any issues, please put your issue with logs in this thread.

Technical explination for playlist handling
In previous versions of the spotify plugin, when playing from the volumio UI, the playlist would be handled by Volumio. This means that after every track Volumio had to start a new track. This caused a lot of issues and made it impossible to have gapless playback.

In the new version we send the complete playlist or album to spotify. This has the following advantages:

• The playlist is also available in the spotify app
• The next track can be preloaded for gapless playback
• The Volumio UI becomes more responsive

Technical limitations:

• When the current queue is changed on Volumio side it will not be synced to Spotify. To sync, stop playback and start a track from the edited queue.
• We can only send the bottom part of the queue, so when an album is started from track 2, track one will not be available from the spotify playlist.

[SimonE]

I’ve been switching between Spotify playlists within the updated plugin and via Spotify on my phone. So far, so perfect. Seems to start a bit quicker as well and the right song is displayed on my screen immediately.
Note, you do need to login to Spotify again after updating and rebooting.

Thanks for all the hard work!

[Wheaten]

To avoid issues:

• Uninstall old Spotify plugin
• Reboot
• Install new Spotify plugin (V3.0.8)
• Login
• reboot

Have fun

[tiggr]

Hi,

I updated, and now I get many errors:

Spotify API Error
WebapiError: API rate limit exceeded

and that one too:

Spotify API Error
WebapiError: Bad OAuth request

[Wheaten]

please provide a log as requested by Mervinio

[tiggr]

Thanks, that link was a great help to me! Didn’t know how to send the logs!

Here they are: http://logs.volumio.org/volumio/VIJvE1J.html

[Wheaten]

@tiggr
Did you follow the instructions as posted by me. As I got this error when I just updated the plugin?

@mervinio
I see a lot of errors in tiggr log with:

Mar 08 19:10:46 musicliving volumio[830]: (node:830) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)

[tiggr]

Yes, I followed your instructions!

• I removed the plugin using the GUI
• Reboot
• Installed the plugin using the GUI
• logged in to Spotify
• Reboot
• Test

And I did it again… I never belive the first try!

Now I have a hard time to login at all. The spotify login allways jumps back to the login form insteadt of login me in. I did a video of that process: Rodgauer Workshop

[Wheaten]

if you reboot after the login, spotify is still logged out?