MMM-Spotify

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

mmmmh

@Bugsounet Take your time.

Currently, the module already has awareness about playback activity. An API call to an endpoint of my choosing on state change would already solve it for me. The endpoint could also be MMM-Remote-Control’s API.

I guess I can sift through the module’s code and see if with my humble skills can insert a simple request at the proper place. We’ll see how it goes.

A Former User

don’t worry ;)
I was trained by @eouia!

A Former User

MMM-Spotify

new owner, new version, new change :)

v1.3.0 (2020-05-13)

Fixed: on lost internet connexion
Added: SPOTIFY_CONNECTED SPOTIFY_DISCONNECTED notification
Added: debug mode
Added: deviceDisplay feature
Added: handling for extra device icons
Added: debug mode for Hiding console logs (memory leaks)
Added: fade in transition on cover
Added: box shadow around cover to highlight from background

Again, not in the change log

Fixed : Spotify Free ads errors solved

mmmmh

@Bugsounet Cool additions and fixes. I need to find out more about the notifications to learn how to disable other modules when music is streaming.

A Former User

I make a developer tools module for displaying notification and payload Read there :)

I think it can help you

mmmmh

@Bugsounet Very interesting. This also looks promising. I’ll comment in the other topic.

mmmmh

@Bugsounet I noticed in my pihole logs that there were at least 10 DNS queries for Spotify per second, something is not right. The actual refresh rate for the module is set to 3000 ms. I had to disable the module.

A Former User

i correct it with last update :)

1.3.2 (2020-05-15)
Modified: onStart script (Now launched if Spotify initialized)
Added: "Cast" Icons
1.3.1 (2020-05-14)
Modified: 'progress bar'
Fixed: number of request on idle (depend now of updateInterval config)

A Former User

@mmmmh :

sorry, I take over the project … and its bugs!
I correct little by little :)

note: after … I understand why my mirror crashed with this module!
now it’s better :)

thinking to @eouia who love when I fixed bugs

mmmmh

@Bugsounet, thanks for fixing it. From the changelog, should I expect that many requests again when not on idle?

A Former User

I will try to improve it…
actually i’m working arround another bug …
multi account and connected / disconnected notification …

with one account it’s works correctly but not with multi :(

bouah !

it’s horrible, in multi-account mode, MMM-Spotify tries to connect to all accounts to send news live

I really wonder if the multi-account mode is really a good feature

and of course … wow it spam like it can not connect to the account that we do not use

humm, how to manage this mess !?
i will impect …

Note:

with multi account, I think It can crash the RPI … (so so so so … more loop)
in my dev platform (desktop with debian linux):
- in idle: CPU 3%
- with buggy playing multi-account : CPU 36%

It’s very very high !!!

A Former User

So…

I propose this (and i have already coded a part of it in other dev) :

a single account checking and displaying (default account in config)
Changing account is by vocal (like Jarvis ... Spotify account name)

name is the USERNAME defined in the spotify.config.json file
Of course, i will add this function in AMk2 Spotify recipe

Result:
Less CPU time, Less DNS request, Less Loop for Checking … More Free Memory and RPI will be better

what do you think about this ?

A Former User

v1.4.0 (2020-05-16)

Added & Modified: Multi-account management by notification SPOTIFY_ACCOUNT
Fixed: Loop CONNECTED/DISCONNECTED on multi-account
Fixed: Less CPU time, Less DNS request
Fixed: Maybe RPI crashed when using multi-account (memory leaks)