Read the statement by Michael Teeuw here.
MMM-NowPlayingOnSpotify no longer working?
-
@sdetweil The steps are listed here: https://github.com/raywo/MMM-NowPlayingOnSpotify
-
@droidus are you doing this
“When the app is running you can access it by opening localhost:8888 in your browser. Provided you are doing this directly on your Raspberry Pi” -
@sdetweil said in MMM-NowPlayingOnSpotify no longer working?:
“When the app is running you can access it by opening localhost:8888 in your browser. Provided you are doing this directly on your Raspberry Pi”
No, I am accessing via the 192. address.
-
@droidus did u try on the pi?
-
@sdetweil No, this is a LXC container.
-
@droidus so are the ports mapped? 8888 on the container to something on the host?
unless u did that, that is not accessible
the request will cause a callback to that system
-
@sdetweil I don’t see port 8888 running on the container.
-
the authorization , step 2
cd authorization node appshould run forever
and app.js uses port 8888
so u have to run this IN the container, right? -
@sdetweil Yes, it looks like the ports are mapped. I can reach the IP/port from my laptop.
-
@droidus ip:8888 right?
so when u open that with your laptop browser, you should see
this page https://github.com/raywo/MMM-NowPlayingOnSpotify/authorization/public/index.html -
@sdetweil Correct. I see that.
-
@droidus and u fill in the fields from the spotify dev account
what did you do for this step in the doc?u had to do the host address, right?
Click on “Edit Settings” and add http://localhost:8888/callback to the Redirect URIs and save your settings.
I just did this on my spotify account and it brought up the auth page as expected… and authorize click brought the page with the code in
-
@sdetweil so before for the ip, I was using my 192. address, but I tried localhost, and it errors saying: “INVALID_CLIENT: Invalid redirect URI”.
-
@droidus I did that, forgot to add the /callback on the redirect on the Spotify page and the mapped port is 8888 on both sides, yes?
on the host opens the auth page from the container
-
@sdetweil This is what I am seeing after entering those fields:
-
@droidus so , is there any info on the node app running in the container?
also open the developers window on the auth page before login, ctrl-shift-i on the keyboard, select the console tab
-
@sdetweil Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.spotify.com/v1/me. (Reason: CORS request did not succeed). Status code: (null).
-
https://github.com/raywo built some nice modules but they are now unmaintained since 4 years. So there will be no fixes, may you find a fork which is still maintained.
You could may fix it using a cors proxy (google will help) or you could use the built in cors proxy of mm which is not released yet (you have to use the
developbranch for this).You find the url to proxy in this line.
-
@droidus try changing the redirect uri on spotify back to using localhost
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login