MMM-Spotify

[Cr4z33]

@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:

[Cr4z33]

@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?

[A Former User]

@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?

[A Former User]

@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)

[Cr4z33]

@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.

[Cr4z33]

@Sean working now!

For some reason previous installation generated a token without .JSON at the end (I know because I made a backup on the Desktop) while this time it was generated properly!

Thanks for your support anyway. :grinning_face_with_smiling_eyes:

[mmmmh]

@Sean Is it intentional that the z-index of the artwork (or the Spotify logo) is equal to or higher than whatever the Alert module shows? Alerts do not cover the Spotify module’s content.

[A Former User]

@mmmmh not intentional. i rarely use alert module, so i didnt know about it. if you can make PR to fix it, feel free to contribute.

[larrougos]

Hi all! i ve set a config as

SPOTIFY_MA_PLAYLIST: {
            notificationExec: {
                notification: "SPOTIFY_PLAY",
                payload: (params) => {
                    console.log("SPOTIFY_MA_PLAYLIST")
                    return {
                        context_uri: "spotify:playlist:1EaTnmluBfauzzcOdjebNG", // Uri of a personnal playlist or album
                    }
                },
                notification: "SPOTIFY_SHUFFLE", // added this to toogle shuffle
                notification: "SPOTIFY_NEXT" // added this to not always have the same song starting first 
            }
        },

and activate it with

SPOTIFY_MA_PLAYLIST: {
            pattern: "play my playlist on spotify", // (.*)  is an action  eg: play my playlist / run my playlist etc... 
            command: "SPOTIFY_MA_PLAYLIST"
        },

but every time i get this result which is very weird
weird response

any ideas plz?

[A Former User]

@larrougos
It seems MMM-AssistantMk2’s commands.
You made some mistakes.

This is somewhat similar what you want.

"SPOTIFY_MA_PLAYLIST": {
  notificationExec: {
    notification: "SPOTIFY_PLAY",
    payload: "spotify:playlist:1EaTnmluBfauzzcOdjebNG"
  }
}

notificationExec cannot emit multiple notifications. It will emit just one - In your case, the last “SPOTIFY_NEXT” would be emitted. that’s why your issue happened.

If you want to emit several notifications, use MMM-NotificationTrigger to relay and chain notifications. Or you can use moduleExec to make some logics. (Anyway that is not the point).

And SPOTIFY_SHUFFLE is just toggle flag for current status, so it will not guarantee to be a shuffle mode.