MMM-Spotify

[mmmmh]

@Sean I hacked together a simple bash script (dnssaver.sh) that fetches IPs and stores them in the hosts file. If I call it with ‘api.spotify.com’ as argument and put it in my crontab it should take a load of the dns server. I’ll keep an eye on it.

[Cr4z33]

@Bugsounet either I am doing something wrong or there’s a bug.

I added onStart: null, in the module config, but the big Spotify logo keeps displaying all the time.

[A Former User]

if Soptify logo not hidden after start, it’s means :
token missing or token error

you should have in console something like that :

[SPOTIFY:ERROR] USERNAME: [your username]
[SPOTIFY:ERROR] Token Error ! ./[token name].json

if you have set a token … verify the exact name
and report it to your account username specified in spotify.config.json -> “TOKEN” field

[A Former User]

when ok It display :

• default style
  

• mini style
  

• when bottom_bar position is set
  

[A Former User]

@mmmmh :

now idleInterval is set to 30000 (scan is Spotify is playing every 30 sec)
if playing : updateInterval is set by default to 1000 (1sec)

Attention it’s means that with idleInterval : when Spotify is playing to take 30 sec to display it in mirror !by default !

[mmmmh]

@Bugsounet Thanks. Do I understand this correctly. As long as the module is idle it will only check for updates every 30 seconds and when it is active (music is being played) it updates every second?

[A Former User]

Right,

I hope this suits you, because it starts to take head ;)

[sbonn13]

Somehow the authorization process does not work.

...node first auth.js
[SPOTIFY] Initialized

Browser opened and the log in was succesful as well as accepting the app, but then instead of creating the token.js I receive an error:

[SPOTIFY] Error in authentication flow!
[SPOTIFY] ERROR: undefined
[SPOTIFY] Authorization process finished!

In spotify I can see that I have the mirror app available in approved apps, but there is not token in the modules folder. Therefore the connection does not work.

Does anybody have an idea?
Thanks

[sdetweil]

@sbonn13 there will be a message popup on the browser with a code (press the copy icon)
then return to the terminal window and paste the code in at the little app prompt, and hit enter
(make sure u don’t hit enter on that window before the browser opens, as the little app will take you enter key as the ‘token’ and not wait)

you run the node auth… app
and see

Opening OAuth URL. Return here with your code.
Paste your code: 

then the browser opens, you pick your userid, then it asks for allow, then presents this screen

where u need to copy that and then return to app

[sbonn13]

@sdetweil
Thanks unfortunately probably I do it completely wrong, I do not get it. Is there any instruction? OAuth was working fine for google services, but not with this Spotify solution :-(
My procedure:
1.) node first_auth.js as described in MMM-Spotify instruction.
-> [SPOTIFY] Initialized appeared in terminal window
2.) Browser opens with Spotify login, after having entered, spotify requesting access
-> No code yet, no additional terminal window, also no change in existing terminal window
3.) Click on accept access in browser (spotify)
-> callback localhost:8888 appeared in domain and shows ?code=**** in parameter.
But in the meantime the mentioned error has appeared immediately in the terminal window. No time or place to paste the code somewhere else. Where shall I put this code and at what point in the procedure?