Domoticz

Lokonli wrote:Spotify in Dashticz works as a remote control via Spotify Connect. You must have Spotify running somewhere in your network. Do you have that?

Yes I do. Also tried this on several devices.

What I don’t understand is the redirect part. When I set the redirect in Spotify Dev I don’t get errors. But, say an hour, later Dashticz won’t start because of the redirect is not right??

*edit: Now I can’t even start Dashticz anymore. Stops at invalid redirect URI. I’ve tried all options for the redirect URI.

Spotify Dev will not create any error: it just adds the redirect you specify to the list of allowed redirects.

Is spotify in Dashticz initially working, but it stops after one hour? Or doesn't it work at all?

The spotify token needs to be refreshed after one hour. This should happen automatically with a reload of dashticz. The dashticz url is redirected to Spotify to get the new token. After that Spotify redirects back to dashticz.

It never worked. Not with any of the redirect URI’s.


Verzonden vanaf mijn iPhone met Tapatalk

What is the URL of your dashticz? You use exactly the same as redirect? With a slash at the end?
Which browser ar you using for Dashticz?

My dash is running on http://localhost:port/dashticz_v2/

I’ve tried all different redirct links suggested in this thread but to no avail.

I’ve checked on Chromium, Chrome, Safari, Firefox.
Maybe, just maybe, is there something in Spotify.js that does not correlate?



Verzonden vanaf mijn iPhone met Tapatalk

Try with the real IP address:
If you use http://192.168.1.20:8080/dashticz_v2/
then add as redirect uri in spotify dev exactly the same:
http://192.168.1.20:8080/dashticz_v2/
Don't forget to press the save button at the bottom of the page.

I suppose you've checked already that your are using the correct spotify cliend ID in CONFIG.js ...

Thanks, also tried this... Does not work either.
I’m getting headaches...

I’ve triple checked the ID, even made a new one; same issue.

I’m on the latest beta, 2.4.0 so thats not it either.
Is it possible/an option to manually set the URI in spotify.js? And copy that exact URI in the Spot Dev?

spotify.js just uses the current location as redirect URI which is send to Spotify. I don't think you can change that, because then the refresh mechanism won't work. spotify.js checks whether it's called with a refresh token in the URL. In that case it uses the new token to the subsequent calls to Spotify.

Can you try in an incognito window in Chrome? Then the spotify login should open. Can you add an exact description of the error you are getting after that? Preferably with a screen dump.

Done. Litarally all white with only this line: INVALID_CLIENT: Invalid redirect URI

Allright it works. I made a backup of the CONFIG, removed all of dashticz, removed all API's from Spotify and started over.
Somehow it worked right away. I must have made a mistake somewhere, just don't know where. Bit frustrating but hey, it works.
Thanks for your guidance @Lokonli, I would have given up otherwise.

Good to know you have it working. Enjoy

Nice plugin, works great! Thanks mate

Is there any way to customize only the width of the spotify block?

I have a existing block like this:

columns[4] = {}
columns[4]['blocks'] = ['blocktitle_5',1000,1073,344,520,1001,1021,1023,1025,1024,1122,1018,1019,1020,1119,tvguide.dutch,'spotify']
columns[4]['width'] = 12;

I would like to have the spotify block next to the tvguid block that has a width of 4. The spotify block must also have the width of 8.
With this above setting the spotify block is always 12 (like the last width config from the columns). Now the spotify block is under the tvguide.

Screenshot:

Can anyone explain this behaviour?

When using the Spotify application on a windows 10 machine it can see my Onkyo receiver which is a Spotify Connect device.
Dashticz only sees my Windows 10 spotify app and not the receiver's spotify connect.

What's up with this? And is it "fixable"?

randleman wrote: ↑Friday 14 December 2018 14:23 Can anyone explain this behaviour?

When using the Spotify application on a windows 10 machine it can see my Onkyo receiver which is a Spotify Connect device.
Dashticz only sees my Windows 10 spotify app and not the receiver's spotify connect.

What's up with this? And is it "fixable"?

I noticed similar behavior.

I don't know the exact reason, but I assume it relates to local network scanning:

The dashticz spotify module doesn't scan the local network, but receives the device info via the Spotify web api. That means that only devices that announce themselves at Spotify can be found by Dashticz spotify.

At the moment that you start a spotify device via the spotify app it also becomes visible for the Dashticz Spotify module.

Lokonli wrote: ↑Friday 14 December 2018 15:27

randleman wrote: ↑Friday 14 December 2018 14:23 Can anyone explain this behaviour?

When using the Spotify application on a windows 10 machine it can see my Onkyo receiver which is a Spotify Connect device.
Dashticz only sees my Windows 10 spotify app and not the receiver's spotify connect.

What's up with this? And is it "fixable"?

I noticed similar behavior.

I don't know the exact reason, but I assume it relates to local network scanning:

The dashticz spotify module doesn't scan the local network, but receives the device info via the Spotify web api. That means that only devices that announce themselves at Spotify can be found by Dashticz spotify.

At the moment that you start a spotify device via the spotify app it also becomes visible for the Dashticz Spotify module.

This indeed works. I started a spotify stream from my local network and suddenly my receiver popped up on my mobile phone on 4G. So far it works, and it's still visible to dashticz. I never used spotify connect on the receiver so maybe it had to initiate something.

Don't get this running.
After a long time trying I don't see the spotify block in my dash.

Using latest Beta. Filled in the right redirect URL.
Plenty of times I get the error page: INVALID_CLIENT: Invalid redirect URI
After a time I get the login page, so login to Spotify. Then I see my dash but without the spotify block.
Somebody had a great tip for me?

silver323 wrote: ↑Wednesday 20 February 2019 14:39 Don't get this running.
After a long time trying I don't see the spotify block in my dash.

Using latest Beta. Filled in the right redirect URL.
Plenty of times I get the error page: INVALID_CLIENT: Invalid redirect URI
After a time I get the login page, so login to Spotify. Then I see my dash but without the spotify block.
Somebody had a great tip for me?

For me the Spotify block is just working.

You filled in the correct value for config['spot_clientid'] in your CONFIG.js?
Which URL do you use for Dashticz? Which redirect URI did you configure at the Spotify console?

Yes I filled in the correct clientID, did also make a new one for testing but no luck.
I use different for testing. Did try it with http://192.168.33.60/dashticz_v2/, http://localhost/dashticz_v2/, also without the last /
So i don't know why it will not working.

When i'm not getting the INVALID_CLIENT: Invalid redirect URI error, I get the login screen for spotify, so I thougth it was working but then i get no spotify block which I set in de config.

silver323 wrote: ↑Thursday 21 February 2019 13:16 Yes I filled in the correct clientID, did also make a new one for testing but no luck.
I use different for testing. Did try it with http://192.168.33.60/dashticz_v2/, http://localhost/dashticz_v2/, also without the last /
So i don't know why it will not working.

When i'm not getting the INVALID_CLIENT: Invalid redirect URI error, I get the login screen for spotify, so I thougth it was working but then i get no spotify block which I set in de config.

Hi,

I have got the same issue but resolved it with accessing to the web player: https://open.spotify.com/browse/featured and just launching a song.
However, you have to be premium to have the playback function

Updated dashticz to 2.5.7 but still had this issue.
For now it only stays blank where i want the block Spotify.