MMM-Spotify

[A Former User]

It’s means that the token is not set
maybe callback url is not set
after if you have used the sudo command for install MM or for install this module, it will not work (not write access)

[A Former User]

@zauberclown said in MMM-Spotify:

Good I checked the older messages in this thread to better understand the complexity with multiple accounts. I had no idea it would impact the CPU that much. Thanks for pointing out.
Being able to change it verbally is currently not an option as I don’t plan to implement vocal for my mirror. But can’t think of an alternative as of now.
BTW: Thanks a lot for your hard work on this module!

yes, I can’t display ALL account in the same time.
example 2 accounts listen at the same time -> what is the visual (complex to determinate) !?

for CPU time: X account registred = X * CPU time
So X * time DNS access, X * traffic to spotify

that’s why i use a switch for another account

[spoonek]

@Bugsounet Good point. I was thinking I needed to reuse my client ID credentials I had already setup for MMM-NowPlayingOnSpotify. DOH! I just created a “New App” on the Spotify Dev page for MMM-Spotify. Should be good to go now.

[A Former User]

when it want to works ;)

[spoonek]

@Bugsounet said in MMM-Spotify:

when it want to works ;)

pi@raspberrypi:~/MagicMirror/modules/MMM-Spotify $ node first_auth.js
[SPOTIFY:ERROR] Token not found! /home/pi/MagicMirror/modules/MMM-Spotify/token.json
[SPOTIFY] Spotify v1.0.2 Initialized…
[SPOTIFY_AUTH] Opening the browser for authentication on Spotify…
events.js:174
throw er; // Unhandled ‘error’ event
^

Error: listen EADDRINUSE: address already in use :::8888
at Server.setupListenHandle [as _listen2] (net.js:1280:14)
at listenInCluster (net.js:1328:12)
at Server.listen (net.js:1415:7)
at Function.listen (/home/pi/MagicMirror/modules/MMM-Spotify/node_modules/express/lib/application.js:618:24)
at Spotify.authFlow (/home/pi/MagicMirror/modules/MMM-Spotify/node_modules/@bugsounet/spotify/index.js:310:8)
at Promise (/home/pi/MagicMirror/modules/MMM-Spotify/first_auth.js:20:14)
at new Promise ()
at authorize (/home/pi/MagicMirror/modules/MMM-Spotify/first_auth.js:17:12)
at authorizations (/home/pi/MagicMirror/modules/MMM-Spotify/first_auth.js:33:19)
at Object. (/home/pi/MagicMirror/modules/MMM-Spotify/first_auth.js:40:1)
Emitted ‘error’ event at:
at emitErrorNT (net.js:1307:8)
at process._tickCallback (internal/process/next_tick.js:63:19)
at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)

[A Former User]

@spoonek said in MMM-Spotify:

Error: listen EADDRINUSE: address already in use :::8888

it’s mean that the port 8888 il used by another app… free this port temporarily and retry

[spoonek]

@Bugsounet said in MMM-Spotify:

@spoonek said in MMM-Spotify:

Error: listen EADDRINUSE: address already in use :::8888

it’s mean that the port 8888 il used by another app… free this port temporarily and retry

I just started over from scratch and now was able to get the authorization webpage login to work.

[A Former User]

when it want to work ;)

[requiemmg]

I understand the CPU and traffic issue, but would there be any chance to check at least 2 accounts at the same time in a future version?

[A Former User]

@Bugsounet said in MMM-Spotify:

yes, I can’t display ALL account in the same time.
example 2 accounts listen at the same time -> what is the visual (complex to determinate) !?