State of spotify support

Q&A
1

I have a Pirate Audio Board and a Pi Zero. I have been running Mopidy and Iris plus the Mopidy Spotify extension successfully for nearly a year. Over the summer, the reliability has taken a nosedive. This weekend Spotify forced me to reset my password and everything stopped working. After a lot of messing about, I was able to browse tracks, but I cannot get any playback. I’ve tried updating to 5.0.0.a2 of Mopidy Spotify and 1.13.1-1 of the gst library. Having trawled through loads of posts I am utterly confused as to what instructions to follow and whether playback can be made to work currently. Can someone point me please? Not looking for troubleshooting help just yet - just pointers to up-to-date procedures. Thanks

2

I agree it’s currently confusing while we get things back on track.

However, playback does work if you employ one of the workarounds I linked to from the readme in Spotify disabled username/password authentication · Issue #394 · mopidy/mopidy-spotify · GitHub

3

Thanks @kingosticks, I’ll focus on one of those specific approaches and post some troubleshooting info to try and get a handle on where I am going wrong.

4

@kingosticks - thank you so much - I was able to get my Raspberry Pi happily beepy - boop, thumpa - thumping tracks to itself again with your help. I am hoping that it will not give up in a hour or a day. You never know with Spotify. However, I am left with some questions I hope you can might be able to answer so I can understand better what is broken and what needs to be fixed going forward. As a developer myself, I might even be able to lend a hand.

  1. I got my credentials file using the spotify-connect route. If I want to use oauth rather than spotify-connect to get a new credentials file, how the fluff do I do that? I see the cargo command to do start librespot and I understand that there has to be a browser involved somewhere for most oauth flows, but how do I work it in this case?
  2. Is the intention to use oauth for authentication in Mopidy-Spotify going forward?
  3. Am I right that Spotify provide a public API for metadata and an embeddable JavaScript player, but no ‘official’ means for getting an audio stream for playback, which is why it has been so difficult to support Spotify in Mopidy?
  4. Are Manage Apps and Developer Dashboard connected in any way?
5
  1. I’m due to update the librespot docs but essentially it’s just librespot --enable-oauth --cache .
  2. We already use oauth in Mopidy-Spotify (client_id and _secret) for providing Spotify data. The intention is to integrate that with Spotfy playback, therefore removing a need for username and password config. That code is checked in and will be released soon (waiting on something upstream).
  3. Yes
  4. I don’t understand the question.