If not, go back to your Spotify Application and ensure you have the right Redirect URIs. If the Redirect URIs are correct you will be returned and the entry should show you are authorized with you Spotify user name/id. This will take you either to the login page of Spotify or directly to the authorization screen. Your newly added bridge should be listed there.
Choose new Id for the player, unless you like the generated one, put in the Client ID and Client Secret from the Spotify Application registration in their respective fields of the bridge configuration.
Install the binding and make sure the Spotify Binding is listed on your server.When you have authorized with Spotify, this Redirect URI is where authorization tokens for your openHAB Spotify Bridge will be sent and they have to be received by the servlet on /connectspotify.
This is important since the authorize process with Spotify takes place using your client web browser and Spotify will have to know the right URLs to your openHAB server for the authorization to be completed.
Here you have to specify the URL to the Bridge Authorization Servlet on your server.įor example if you run your openHAB server on you should add (opens new window) as the redirect URIs. When registering your new Spotify Application for openHAB Spotify Bridge you have to specify the allowed "Redirect URIs" aka white-listed addresses.
Swap browsers and retry Spotify web player. As most of us will have a couple of browsers installed on our devices, using another shouldn’t be too much of an issue. Skirting the issue by using an alternative is never ideal but if you got this far and still cannot get Spotify web player working properly, you may have no choice. This is often enough to get it working again. What should happen is that Spotify will play on your second device and then when you switch to Spotify web player, it should begin playing on your computer.