MMM-Spotify

[A Former User]

Right,

I hope this suits you, because it starts to take head ;)

[sbonn13]

Somehow the authorization process does not work.

...node first auth.js
[SPOTIFY] Initialized

Browser opened and the log in was succesful as well as accepting the app, but then instead of creating the token.js I receive an error:

[SPOTIFY] Error in authentication flow!
[SPOTIFY] ERROR: undefined
[SPOTIFY] Authorization process finished!

In spotify I can see that I have the mirror app available in approved apps, but there is not token in the modules folder. Therefore the connection does not work.

Does anybody have an idea?
Thanks

[sdetweil]

@sbonn13 there will be a message popup on the browser with a code (press the copy icon)
then return to the terminal window and paste the code in at the little app prompt, and hit enter
(make sure u don’t hit enter on that window before the browser opens, as the little app will take you enter key as the ‘token’ and not wait)

you run the node auth… app
and see

Opening OAuth URL. Return here with your code.
Paste your code: 

then the browser opens, you pick your userid, then it asks for allow, then presents this screen

where u need to copy that and then return to app

[sbonn13]

@sdetweil
Thanks unfortunately probably I do it completely wrong, I do not get it. Is there any instruction? OAuth was working fine for google services, but not with this Spotify solution :-(
My procedure:
1.) node first_auth.js as described in MMM-Spotify instruction.
-> [SPOTIFY] Initialized appeared in terminal window
2.) Browser opens with Spotify login, after having entered, spotify requesting access
-> No code yet, no additional terminal window, also no change in existing terminal window
3.) Click on accept access in browser (spotify)
-> callback localhost:8888 appeared in domain and shows ?code=**** in parameter.
But in the meantime the mentioned error has appeared immediately in the terminal window. No time or place to paste the code somewhere else. Where shall I put this code and at what point in the procedure?

[sdetweil]

@sbonn13 said in MMM-Spotify:

callback localhost:8888 appeared in domain

what does ‘appeared in domain’ mean?? sorry

[sbonn13]

@sdetweil
Following address is opened in browser: https://accounts.spotify.com/de/authorize?response_type=code&client_id=XXXXX&scope=user…

-> Press Agree button in Browser in order to agree access to spotify

Afterwards address in browser is changed to:
http://localhost:8888/callback?code=XXXXX&state=XXXXX…

I assume the code (anonymized XXXXX) in this address is the relevant one. But how to proceed with that? Because at the time I have received this code I already have the errors in my terminal window.

[sdetweil]

@sbonn13 i do not know … @Bugsounet will have to help here

[A Former User]

I’m going to inspect the first_auth script. there is too much problem, I think.
a little patience within a few days this should be fixed

[ChanceTime]

hi @Bugsounet ! I’m working on my first smart mirror and was very happy to just get mmm-GoogleAssistant up and running! It’s able to do normal searches and that kind of thing, so I just tried to install MMM-Spotify.

Unfortunately, MMM-GoogleAssistant doesn’t seem to be recognizing the commands, and I don’t see any changes on the screen when I try to use the commands for it (for example, “Michael Jackson on Spotify”).

The code I used in the .config is below. Did I miss something?

Thanks!!

		{
		  module: "MMM-GoogleAssistant",
		  position: "fullscreen_above",
		  config: {
		    debug: false,
		    assistantConfig: {
		      lang: "en-US",
		      projectId: "magic-mirror-79d8d", // Required to use gaction.
		      modelId: "", // (OPTIONAL for gaction)
		      instanceId: "", // (OPTIONAL for gaction)
		      latitude: 45.255299,
		      longitude: -75.729048,
		    },
		    responseConfig: {
		      useScreenOutput: true,
		      screenOutputCSS: "screen_output.css",
		      screenOutputTimer: 5000,
		      activateDelay: 250,
		      useAudioOutput: true,
		      useChime: true,
		      newChime: false
		    },	
		    micConfig: { // put there configuration generated by auto-installer
		      recorder: "arecord",
		      device: "plughw:2",
		    },
		    customActionConfig: {
		      autoMakeAction: false,
		      autoUpdateAction: false, // in RPI, gaction CLI might have some trouble.(current version should be 2.2.4, but for linux-arm, Google haven't updated) so leave this as false in RPI. I don't know it is solved or not.
		      actionLocale: "en-US", // At this moment, multi-languages are not supported, sorry. Someday I'll work.
		    },
		    snowboy: {
		      audioGain: 2.0,
		      Frontend: true,
		      Model: "jarvis",
		      Sensitivity: null
		    },
		    A2DServer: {
		      useA2D: false,
		      stopCommand: "stop"
		    },
		    recipes: [ "with-MMM-TelegramBot.js", "with-MMM-Spotify" ]
		  }
		},
		{
			module: "MMM-Spotify",
			position: "bottom_left",
			config: {
				 style: "mini", // "default" or "mini" available
				 control: "hidden", //"default", "hidden" available
				 updateInterval: 1000,
				 onStart: null, // disable onStart feature with `null`
				 allowDevices: [], //If you want to limit devices to display info, use this.
				 // allowDevices: ["RASPOTIFY", "My iPhoneX", "My Home speaker"],
				},
		},

[A Former User]

natively, MMM-Spotify and MMM-GoogleAssistant can’t read directly music on Spotify.
MMM-Spotify can display only what you are listening on a device
and you can change music ONLY with a premium account with vocal request
if you want listening music on your mirror you have to install Raspotify or librespot on your mirror (but needed again a premium spotify account)
After, A2D is coded to read +/- native google response without Spotify recipe