MMM-Spotify

A Former User

@ForrestFire2222
It’s not issue of module. You just executed MagicMirror twice.

ForrestFire2222

@Sean I really appreciate the reply.

Im new so maybe I didn’t convey my issue/logs correctly. As I mention above, when I try to execute Step 4, I get the error below…

pi@raspberrypi:~/MagicMirror/modules/MMM-Spotify $ node first_auth.js
[SPOTIFY_AUTH] creating server { USERNAME: 'MyName',
  CLIENT_ID: 'My_ID',
  CLIENT_SECRET: 'My_Secret',
  AUTH_DOMAIN: 'http://localhost',
  AUTH_PATH: '/callback',
  AUTH_PORT: '8888',
  SCOPE:
   'user-read-private app-remote-control playlist-read-private streaming user-read-playback-state user-modify-playback-state',
  TOKEN: './MyName_token.json' }
[SPOTIFY_AUTH] Opening URL.(https://accounts.spotify.com/authorize?response_type=code&client_id=My_ID&scope=user-read-private%20app-remote-control%20playlist-read-private%20streaming%20user-read-playback-state%20user-modify-playback-state&redirect_uri=http%3A%2F%2Flocalhost%3A8888%2Fcallback&state=1587478945270&show_dialog=true)

At this point the terminal just stalls out. Hope this clarifies the above, my configs are still above. Thanks again

A Former User

@ForrestFire2222
If browser couldn’t open the url automatically, copy the URL and paste it into your web browser.

ForrestFire2222

@Sean Thanks.

I’ve tried a couple things…

through ssh i tried the link on my laptop browser, and I got an error displayed on the page of “INVALID_CLIENT: Invalid client”.

And on my Mirror, through the command line i executed node first_auth.js and the browser opened up to login to Spotify (this is a good sign, haven’t got this far yet), however, when I enter my Spotify Acct info I get the same error as above, Invalid Client.

ForrestFire2222

I started from scratch, loading MMM-Spotify first to my mirror and it works with no issues… sorry I didn’t try that sooner. Thanks again!

Telliman

Set this up and works great! Thanks so much! Now next for me is to set up Assistant and this will be sweet!
Thanks so much!

mmmmh

@Sean Is there a way to make the connection watchdog more forgiving/resilient? Even though I set the refresh rate to 5 seconds I see API connection timeouts and recently also this:

[SPOTIFY] API Request fail on : /v1/me/player
[2020-05-05 16:43:27.591] [LOG]
{ Error: socket hang up
    at createHangUpError (_http_client.js:332:15)
    at TLSSocket.socketOnEnd (_http_client.js:435:23)
    at TLSSocket.emit (events.js:203:15)
    at endReadableNT (_stream_readable.js:1145:12)
    at process._tickCallback (internal/process/next_tick.js:63:19) code: 'ECONNRESET' } undefined

mmmmh

What would the best approach to hide other specific modules when this module is active, i.e. when music is being played?

It may be to early to ask this since @Bugsounet just volunteered a few minutes ago to take over this project so take your time with your feedback.

A Former User

leave me a few days … I have to inspect the entire API :)

sdetweil

@mmmmh i tried to use watchdog for another problem, but there were normal disconnects between the front and back ends, which WOULD have recovered, had watchdbog not restarted MM… I gave up