MMM-Spotify

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.

larrougos

@Sean said in MMM-Spotify:

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

ok!! thats a start! can you please help me with that! i mean how this should have a proper syntax! i would really appreciate.

Also another problem that i have is that if spotify is not already playing in the background i am not able to play anything. whatever command i give. and the frontend does not even show the spotify logo. it just disappears on after one sec on start.

A Former User

@larrougos

Also another problem that i have is that if spotify is not already playing in the background i am not able to play anything. whatever command i give. and the frontend does not even show the spotify logo. it just disappears on after one sec on start.

In that case, maybe, the module cannot find available active devices. It doesn’t mean you have no device. But by default, Spotify doesn’t know which device is yours unless it is powered and logged as your account.
So at least one of your devices need to be activated when this SDK is used. I recommend to install Raspotify, that could makes your spotify always on.

larrougos

@Sean said in MMM-Spotify:

@larrougos

Also another problem that i have is that if spotify is not already playing in the background i am not able to play anything. whatever command i give. and the frontend does not even show the spotify logo. it just disappears on after one sec on start.

In that case, maybe, the module cannot find available active devices. It doesn’t mean you have no device. But by default, Spotify doesn’t know which device is yours unless it is powered and logged as your account.
So at least one of your devices need to be activated when this SDK is used. I recommend to install Raspotify, that could makes your spotify always on.

i am running from ubuntu laptop with Spotify application! i tried with raspotify to install but from what i understood it does not support the laptop arch!

rabbit83ka

First of all thanks for the module and the effort you put in it.

@Sean said in MMM-Spotify:

updated

1.1.0 (2019-03-25)

Device Limitation : Now you can allow or limit devices to display its playing on MM.

One question regarding the device limitation: if I leave it empty, the module shows the cover etc. as it should. If I try to limit it to my echo dot with

 allowDevices: ["myechodot"],

the spotify logo appears if I start playback on the echo dot, but no cover etc. is shown. Any hints?

A Former User

@rabbit83ka
When you play something on your echodot, nothing been displayed?

rabbit83ka

@Sean
If I comment out

//allwoeDevices: ["myechodot" ]

it shows the album cover/etx/progress etc. when I play something on my echo dot. With

 allowDevices: ["myechodot"],

the spotify logo appears when something is played on the echodot, but no cover/text/progress etc. is shown.