Read the statement by Michael Teeuw here.
MMM-Spotify
-
@Cr4z33 Show me the log. Usually I’m not in front of PC on weekends. :D
-
@Sean oh OK. :grinning_face_with_smiling_eyes:
I ran
npm start
, but unfortunately no error came up.Same thing for PM2 logs.
At the end I tried to delete and reinstall MMM-Spotify, but the issue is still happening.
By the way this is my current config entry:
{ module: "MMM-Spotify", position: "top_left", disabled: false, config: { onStart: null, // disable onStart feature with `null` // allowDevices: ["Cr4z33 Mirror"], control: "hidden", //"default", "hidden" available } },
-
@Cr4z33
Try it without any config (default setup).
And nothing in log? Not only Error but also normal log can help to examine.
At least these(or similar) logs should be shown.Connecting socket for: MMM-Spotify [SPOTIFY_AUTH] Token is expired. It will be refreshed [SPOTIFY_AUTH] Token refreshing... [SPOTIFY_AUTH] Token is written. ## or [SPOTIFY_AUTH] Token is fresh.
-
@Sean OK here is the console log output of default config with above module entry.
Please note that I also launched Spotify playing (after launching MM).npm start > magicmirror@2.7.1 start /home/pi/MagicMirror > sh run-start.sh Starting MagicMirror: v2.7.1 Loading config ... Loading module helpers ... No helper found for module: alert. Initializing new module helper ... Module helper loaded: MMM-Spotify Initializing new module helper ... Module helper loaded: updatenotification No helper found for module: clock. Initializing new module helper ... Module helper loaded: calendar No helper found for module: compliments. No helper found for module: currentweather. No helper found for module: weatherforecast. Initializing new module helper ... Module helper loaded: newsfeed All module helpers loaded. Starting server on port 8080 ... Server started ... Connecting socket for: MMM-Spotify [SPOTIFY_AUTH] Token is fresh. Connecting socket for: updatenotification Connecting socket for: calendar Starting node helper for: calendar Connecting socket for: newsfeed Starting module: newsfeed Sockets connected & modules started ... Launching application. Create new calendar fetcher for url: http://www.calendarlabs.com/templates/ical/US-Holidays.ics - Interval: 300000 Create new news fetcher for url: http://www.nytimes.com/services/xml/rss/nyt/HomePage.xml - Interval: 300000
-
@Cr4z33
Hmmm weird. It seems nothing special suspicious point at all.
The only thing I suspect is that you are using different account on MMM-Spotify and your real spotify player. but i think it would have bare chance.
TryonStart
to activate it by force, at least it would show some errors.onStart: { device: null, search: { type: "playlist", keyword: "death metal", random:true, } }
-
@Sean tried this config
{ module: "MMM-Spotify", position: "top_left", disabled: false, config: { // onStart: null, // disable onStart feature with `null` // allowDevices: ["Cr4z33 Mirror"], control: "hidden", //"default", "hidden" available } },
and the white big Spotify logo came up at MM loading and then disappeared.
Isn’t it enough to
//
onStart line to let the module show all the time? :thinking_face: -
@Sean said in MMM-Spotify:
The only thing I suspect is that you are using different account on MMM-Spotify and your real spotify player.
Even if wasn’t the token OK at MM loading log?
-
@Cr4z33 said in MMM-Spotify:
The only thing I suspect is that you are using different account on MMM-Spotify and your real spotify player.
Even if wasn’t the token OK at MM loading log?
Token might be OK with different account, but if different account is used, it cannot derive current playback info. (You cannot get spotify info from your friend’s account playback with your account). Have you several accounts for spotify?
-
@Cr4z33 said in MMM-Spotify:
white big Spotify logo came up at MM loading and then disappeared.
This is normal. Unless you should customize CSS, with no playback, the module will be disappeared by default. (Some PPL have wanted so I added that feature.)
When playing on any Spotify player starts, module will be appeared. (If it can get current playback info from server) -
@Sean OK so to be 100% sure everything is set properly I start installing the module from scratch again generating once more the JSON file and the token.