Read the statement by Michael Teeuw here.
MMM-SPOTIFY I cannot for the life of me get this to run propperly
-
Hey Folks
I cant seem to get MMM-Spotify to work at all.
First it started with not being able to generate a user token, as the callback routing always resulted in a unknown URL. So I found an alternate way to generate a token. There is nothing in the logs to tell me that I’m not authorized, but there is also nothing say that I am.
When MM is running, the module does nothing. I’d really like the functionality if I can, but for now I’m just gong to rem the module out of my config and work on setting up others.
I’m new to MM, so lets start by blaming it on that.Running MM on RPI4B
spotify.config.json
{
“USERNAME”: “Family Account”,
“CLIENT_ID”: “edXXXXXXXXXXXXXXXXXXXXXXXea”,
“CLIENT_SECRET”: “3eXXXXXXXXXXXXXXXXXXXXb635”,
“TOKEN”: “./FamilyAccount_token.json”,
“AUTH_DOMAIN”: “http://127.0.0.1”,
“AUTH_PORT”: “8888”
}
]FamilyAccount_token.json
{
“access_token”: "BQXXXXXXXXXXXXXXXXXXXXXXXXXXXXi>
“expires_in”: 3600,
“timestamp”: 1762903217
}Module config.js
{
module: “MMM-Spotify”,
position: “top_left”,
config: {
style: “mini”,
control: “default”,
updateInterval: 1000,
clientID: “ed5XXXXXXXXXXXXXXXXXXXXXXXcea”,
clientSecret: “3eXXXXXXXXXXXXXXXXXXXXXXXX635”,
accessToken: "BXXXXXXXXXXXXXXXXXXXXXXXXXXU>
refreshToken: “YOUR_SPOTIFY_REFRESH_TOKEN”
}
}, -
@spistachio the Spotify module needs a premium account and you must follow the redirect url rules exactly
Then the module will attempt to call your redirect, which doesn’t exist, but the token is in the url shown on the not found page
So you copy that out for the value in config
