The following configuration options are available on the Spotify Bridge player: Parameter You can force reinitialization by authorizing on the connect Spotify page, even if the page shows it as authorized. Should the bridge configuration be broken for any reason, the authorization procedure can be reinitiated from step 6 whenever required. You may have to trigger the openHAB discovery several times as bridge will only find active devices known by the Spotify Web API at the time the discovery is triggered.

This should make any Spotify Connect devices and Spotify Apps discoverable. If no devices show up you can start Spotify App on your PC/Mac/iOS/Android and start playing on your devices as you run discovery. Now that you have got your bridge ONLINE you can now start a scan with the binding to auto discover your devices. The refresh token is used to re-authorize the bridge with Spotify Connect Web API whenever required.

The binding will be updated with a refresh token and go ONLINE.

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.

Go to the authorization page of your server.

You have to authorize this bridge with Spotify.

The bridge thing will stay in state INITIALIZING and eventually go OFFLINE - this is fine.

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.

Add a new 'Spotify Player Bridge' thing.

Make sure you have your Spotify Application Client ID and Client Secret identities available.

Complete the Spotify Application Registation if you have not already done so, see above.

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

Step 7: setting Redirect URIs is very important.Step 6: entering Website information can be skipped.# Create Spotify Applicationįollow the instructions in the tutorial at (opens new window). The binding requires you to register an Application with Spotify Web API at (opens new window) - this will get you a set of Client ID and Client Secret parameters to be used by your binding configuration. This binding implements a bridge to the Spotify Player Web API and makes it possible to discover Spotify Connect Devices available on your Spotify Premium account.

LOGIN SPOTIFY WEB PLAYER OFFLINE

LOGIN SPOTIFY WEB PLAYER REGISTRATION

LOGIN SPOTIFY WEB PLAYER INSTALL

Login spotify web player