-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spotify not working #52
Comments
Hey friend, glad you found the image useful 👍🏻 I have commented out the Mopidy-Spotify extension in my custom I gave up using it for a while as it is a WIP, so things are constantly broken, whenever I want to listen on multi-room speakers I'm using There is an image which was working a while ago which I forked my new repository from, you can find it here. But as I said, since this is WIP I completely parked Mopidy + Spotify for a while until the whole integration is fixed with a new release of the extension. |
Thanks for all the info, very much appreciated. As I understand, you might need to install Mopidy-Spotify==5.0.0a2, even though this does not help with the authentication issue happening in librespot currently. But I will definitely have a look at your snapcast/snapserver docker images. |
Humm this is cool, I will try building with this version, and I'll let you know how it goes. Have you tried this somehow and got it to work? |
I can't get it to work and I'm getting the error outlined on this issue here: |
So you installed Mopidy-Spotify==5.0.0a2 and gst-plugin-spotify from https://github.com/kingosticks/gst-plugins-rs-build/releases? Opened the mentioned link on my laptop and granted access. Then I copied the credentials.json into the /mopidy/data/spotify/credentials-cache folder. Could you update the docker image to install the above mentioned Mopidy-Spotify==5.0.0a2 and gst-plugin-spotify? As it gets lost if I start the docker container again. I'm attaching my librespot binary just in case you don't want to compile it on your own. |
I see, looks like a lot of stuff progressed since the last time I looked into this. I'll have a look at what you sent above and get back to you. |
Could you also migrate to "FROM debian:12-slim" in the Dockerfile? |
OK, got it to work, I had to downgrade libshout3 to version 2.4.1 using https://packages.debian.org/buster/libshout3 |
Was that using my image? If you guide me through everything you've done, I can reflect that on the Dockerfile. |
Yes, sure, I used your image. What I've done: |
I have pushed the images, and they are already on DockerHub, however I don't have an easy way to test them myself now, I'm still setting up the steps you mentioned here in order to have the Still haven't changed to debian:12-slim though, this will come later on. |
Hi,
thanks a lot for your docker images! I'd like to use the Spotify extension, but in the Iris webinterface, it shows "Mopidy-Spotify extension is not running - you will not be able to play any Spotify tracks".
Both Mopidy-Spotify and Iris are authenticated via the Spotify API.
Could you please give some advice how to get it running?
May I suggest to use the APT packages as described at https://docs.mopidy.com/stable/installation/debian/?
Thanks,
meiser
The text was updated successfully, but these errors were encountered: