MMM-Spotify

bolish

@sean thanks for feedback.
I liked the default view, but wanted it to be a little bit smaller.

I was a bit lost into the .css but I will try to play around with it and see what happens.

Good idea would have been to have a single entry to modify ( like in %) so that user could adjust itself but I believe it’s very personal need, it’s maybe not worth to implement into the module.

A Former User

@bolish
Add this into your css/custom.css.

:root {
  --sp-width: 300px;
}
#SPOTIFY {
 width: var(--sp-width);
}
#SPOTIFY_INFO {
  width: calc(var(--sp-width) - 20px);
}
#SPOTIFY_INFO .text {
  width: calc(var(--sp-width) - 70px);
}
#SPOTIFY_COVER {
  width: calc(var(--sp-width) - 40px);
  height: calc(var(--sp-width) - 40px);
}

--sp-width:300px is magic point. adjust it as your wish. I think 200px is the minimal value possible.

bolish

@sean, thanks I will try in the evening

bolish

@Sean Works great. Tx

mmmmh

Another awesome module, thank you!

The displayed album cover goes dim when there is no playback which is nice. Would it be possible to add an option to completely hide the module when there is no playback?

A Former User

@mmmmh
Add this into your css/custom.css

#SPOTIFY.pausing {
display:none;
}

mmmmh

@Sean said in MMM-Spotify:

#SPOTIFY.pausing {
display:none;
}

Simple and works perfectly. Thanks!

Cr4z33

@Sean said in MMM-Spotify:

@mmmmh
Add this into your css/custom.css

#SPOTIFY.pausing {
display:none;
}

I stopped and quit the Windows 10 Spotify app, but the artwork keeps showing.

A Former User

@Cr4z33
That checks only playing and pausing. Inactive device is another issue.
This module is pooling to pull current playback data per 1~2 secs.
PPL may have several spotify devices, so if one device is deactivated, but others could be alive. And there’s no way to receive one device’s activeness at event time. (Spotify API doesn’t support pushing to client)
To check “ALL DEVICES” are inactive, another pooling be needed to pull data about available devices per 1~2 sec. I’m not sure whether it’s good approach or not. It would make API usage double. (Somebody be already worrying about too many DNS calling by this module)
Anyway, I’ll consider it.

Cr4z33

@Sean OK thanks.