Hi everyone! I have some issues with Spotify Bridge, I just installed it yesterday but didn’t get it to work as should, the problem is that through Paper UI the Spotify Player Bridge doesn’t control anything, just receives the information about the track, playlists, duration, connected devices etc, but I can’t control anything through it, and can’t understand why. Log look ok without errors.
Looks like Spotify doesn’t receives commands from Openhab. Any ideas?
You can enable debug/trace level to see more details. Do you have a premium account?
No, it’s a free account.
How do I debug the spotify binding?
loger shows me:
Logger │ Level
───────────────────────────────────────────────────┼──────
ROOT │ WARN
javax.jmdns │ ERROR
javax.mail │ ERROR
org.apache.karaf.jaas.modules.audit │ INFO
org.apache.karaf.kar.internal.KarServiceImpl │ ERROR
org.apache.karaf.shell.support │ OFF
org.eclipse.lsp4j │ OFF
org.eclipse.smarthome │ INFO
org.jupnp │ ERROR
org.openhab │ INFO
org.openhab.ui.paper │ WARN
org.openhab.ui.paper.internal │ INFO
org.ops4j.pax.url.mvn.internal.AetherBasedResolver │ ERROR
org.ops4j.pax.web.pax-web-runtime │ OFF
smarthome.event │ INFO
smarthome.event.InboxUpdatedEvent │ ERROR
smarthome.event.ItemAddedEvent │ ERROR
smarthome.event.ItemRemovedEvent │ ERROR
smarthome.event.ItemStateEvent │ ERROR
smarthome.event.ThingAddedEvent │ ERROR
smarthome.event.ThingRemovedEvent │ ERROR
smarthome.event.ThingStatusInfoEvent │ ERROR
I don’t think this feature is supported for free accounts, but apparently you can get the status. I think this changed, because I if I remember correctly that wasn’t even possible.
You can debug with log:set DEBUG org.openhab.binding.spotify
Hi! log shows:
2019-11-28 22:51:44.637 [DEBUG] [potify.internal.api.SpotifyConnector] - Response Code: 403
2019-11-28 22:51:44.642 [DEBUG] [potify.internal.api.SpotifyConnector] - Bad request: Player command failed: Premium required
So you are right, need to have Premium Account 
Hovewer theres one trick I discovered, it’s by creating controls directly for Chromcast Binding, and controlling Google home, that way I can control somehow the music, hovewer the next/previouse button doesn’t work and log says:
2019-11-28 22:55:55.522 [INFO ] [omecast.internal.ChromecastCommander] - NEXT command not yet implemented
I set up 2 bridges, each one with a unique Spotify premium account but the same devices in it, e.g.
Bridge spotify:player:Alex "Spotify Alex" [clientId="123", clientSecret="123"] {
Things:
device spotifyKueche "Spotify Echo Dot 3" @ "Küche" [deviceName="Küchen Dot"]
device spotifyOnkyo "Spotify Onkyo" @ "Wohnzimmer" [deviceName="TX-NR646"]
}
Bridge spotify:player:Vany "Spotify Vany" [clientId="123", clientSecret="123"] {
Things:
device spotifyKueche "Spotify Echo Dot 3" @ "Küche" [deviceName="Küchen Dot"]
device spotifyOnkyo "Spotify Onkyo" @ "Wohnzimmer" [deviceName="TX-NR646"]
}
For testing purposes I set up those items:
String trackUri "trackUri" {channel="spotify:player:Vany:trackUri"}
String trackPlay "trackPlay" {channel="spotify:player:Alex:spotifyOnkyo:trackPlay"}
and this rule:
rule spotitest
when
Item trackUri changed
then
trackPlay.sendCommand(triggeringItem.state)
end
It does work - a song change in one bridge is reflected in the other device as well. But as you can imagine, there’s a delay between it, about 1-2s.
Do you seen any better way of syncing it?
Maybe pausing Bridge 1, waiting on Bridge 2 to start and then resume Bridge 1? Or am I likely to run into the same issue then…?
Any input appreciated.
Hi Hibrand,
Since I installed this binding the bridge is very stable and responsive. Very nice stuff.
However I’m having an issue with the devices, please see the screenshots.
This is an Openhabian installation on a Rasberry Pi, so everything was installed as standard via PaperUI.
The issue is that the devices go offline after a while.
Clicking on one of the devices…
For copy and paste purposes…
Status: OFFLINE - CONFIGURATION_ERROR Missing configuration from the Spotify Bridge (UID:null). Fix configuration or report if this problem remains.
The config in the bridge:
Here’s all I get in the log:
2019-12-05 20:27:47.932 [INFO ] [oauth2client.internal.OAuthConnector] - grant type refresh_token to URL https://accounts.spotify.com/api/token success
2019-12-05 21:27:45.841 [INFO ] [oauth2client.internal.OAuthConnector] - grant type refresh_token to URL https://accounts.spotify.com/api/token success
Would you please let me know if the setup looks ok or if you know what may be causing it?
It should be the latest version of the binding as I only installed it a couple of days ago.
Thanks again
What version of openHAB are you running? The message is unexpected, as it is only given when the devices are initialized and that should only happen when they’re first created or the configuration is updated, which should not happen under normal circumstances. It should at least also log when the devices go off line. Can you check the logs if you find anything related (you might need to check the log files itself, the browser UI only shows recent logging)
I’m on openHAB 2.4.0-1 (Release Build).
Seems like some activity going on in the log…
2019-12-05 21:55:04.463 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackProgress changed from 0:23 to 0:24
2019-12-05 21:55:05.464 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackProgress changed from 0:24 to 0:25
2019-12-05 21:55:06.174 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackProgress changed from 0:25 to 0:26
2019-12-05 21:55:06.466 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackProgress changed from 0:26 to 0:27
2019-12-05 21:55:07.467 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackProgress changed from 0:27 to 0:28
2019-12-05 21:55:08.467 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackProgress changed from 0:28 to 0:29
2019-12-05 21:55:09.288 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:50d9' changed from OFFLINE (CONFIGURATION_ERROR): Missing configuration from the Spotify Bridge (UID:null). Fix configuration or report if this problem remains. to UNINITIALIZED
2019-12-05 21:55:09.292 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:50d9' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2019-12-05 21:55:09.306 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:abc8' changed from OFFLINE (CONFIGURATION_ERROR): Missing configuration from the Spotify Bridge (UID:null). Fix configuration or report if this problem remains. to UNINITIALIZED
2019-12-05 21:55:09.310 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:abc8' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2019-12-05 21:55:09.312 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:3d41' changed from OFFLINE (CONFIGURATION_ERROR): Missing configuration from the Spotify Bridge (UID:null). Fix configuration or report if this problem remains. to UNINITIALIZED
2019-12-05 21:55:09.317 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:3d41' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2019-12-05 21:55:09.321 [hingStatusInfoChangedEvent] - 'spotify:player:fba277f5' changed from ONLINE to UNINITIALIZED
2019-12-05 21:55:09.326 [hingStatusInfoChangedEvent] - 'spotify:player:fba277f5' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2019-12-05 21:55:15.797 [temChannelLinkRemovedEvent] - Link 'spotifyAlbumName => spotify:fba277f5:6f52962fa9ca4129b0e592b4bd727df8:albumName' has been removed.
2019-12-05 21:55:15.799 [temChannelLinkRemovedEvent] - Link 'device1DeviceVolume => spotify:device:6f52962fa9ca4129b0e592b4bd727df8:fba277f5:50d9:deviceVolume' has been removed.
2019-12-05 21:55:15.801 [temChannelLinkRemovedEvent] - Link 'device2Player => spotify:device:6f52962fa9ca4129b0e592b4bd727df8:fba277f5:3d41:devicePlayer' has been removed.
2019-12-05 21:55:15.802 [temChannelLinkRemovedEvent] - Link 'device2DeviceVolume => spotify:device:6f52962fa9ca4129b0e592b4bd727df8:fba277f5:3d41:deviceVolume' has been removed.
2019-12-05 21:55:15.804 [temChannelLinkRemovedEvent] - Link 'device3Player => spotify:device:6f52962fa9ca4129b0e592b4bd727df8:fba277f5:abc8:devicePlayer' has been removed.
2019-12-05 21:55:15.805 [temChannelLinkRemovedEvent] - Link 'device1Player => spotify:device:6f52962fa9ca4129b0e592b4bd727df8:fba277f5:50d9:devicePlayer' has been removed.
Then a bit later…
2019-12-05 21:55:15.917 [temChannelLinkRemovedEvent] - Link 'spotify_player_fba277f5_trackName => spotify:player:fba277f5:trackName' has been removed.
2019-12-05 21:55:15.918 [temChannelLinkRemovedEvent] - Link 'spotify_device_fba277f5_3d41_deviceVolume => spotify:device:fba277f5:3d41:deviceVolume' has been removed.
2019-12-05 21:55:15.919 [temChannelLinkRemovedEvent] - Link 'spotify_device_fba277f5_abc8_deviceName => spotify:device:fba277f5:abc8:deviceName' has been removed.
2019-12-05 21:56:06.551 [.ItemChannelLinkAddedEvent] - Link 'spotifyAlbumName-spotify:fba277f5:6f52962fa9ca4129b0e592b4bd727df8:albumName' has been added.
2019-12-05 21:56:06.553 [.ItemChannelLinkAddedEvent] - Link 'device1DeviceVolume-spotify:device:6f52962fa9ca4129b0e592b4bd727df8:fba277f5:50d9:deviceVolume' has been added.
2019-12-05 21:56:06.556 [.ItemChannelLinkAddedEvent] - Link 'device2Player-spotify:device:6f52962fa9ca4129b0e592b4bd727df8:fba277f5:3d41:devicePlayer' has been added.
Later again…
2019-12-05 21:56:08.065 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:50d9' changed from UNINITIALIZED to INITIALIZING
2019-12-05 21:56:08.066 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:50d9' changed from INITIALIZING to OFFLINE (CONFIGURATION_ERROR): Missing configuration from the Spotify Bridge (UID:null). Fix configuration or report if this problem remains.
2019-12-05 21:56:08.068 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:3d41' changed from UNINITIALIZED to INITIALIZING
2019-12-05 21:56:08.070 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:3d41' changed from INITIALIZING to OFFLINE (CONFIGURATION_ERROR): Missing configuration from the Spotify Bridge (UID:null). Fix configuration or report if this problem remains.
2019-12-05 21:56:08.779 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackPlayer changed from NULL to PLAY
2019-12-05 21:56:08.781 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_deviceShuffle changed from NULL to OFF
2019-12-05 21:56:08.789 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackRepeat changed from NULL to off
2019-12-05 21:56:08.794 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackProgress changed from NULL to 1:28
2019-12-05 21:56:08.796 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackDuration changed from NULL to 7:50
2019-12-05 21:56:08.798 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_playlists changed from NULL to
2019-12-05 21:56:08.800 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_playlistName changed from NULL to
2019-12-05 21:56:08.812 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackName changed from NULL to Tearing Me Up
2019-12-05 21:56:08.814 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_albumName changed from NULL to Days Gone By
2019-12-05 21:56:08.832 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_artistName changed from NULL to Bob Moses
2019-12-05 21:56:08.835 [hingStatusInfoChangedEvent] - 'spotify:player:fba277f5' changed from UNKNOWN to ONLINE
2019-12-05 21:56:08.841 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_devices changed from NULL to 3d41a9ff92a68fa9b8caf3bde53a8df1685fe711
2019-12-05 21:56:08.843 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_deviceName changed from NULL to CRAIGS-LAPTOP
2019-12-05 21:56:08.844 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_deviceVolume changed from NULL to 100
2019-12-05 21:56:09.018 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_albumImage changed from NULL to raw type (image/jpeg): 13424 bytes
2019-12-05 21:56:10.073 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackProgress changed from 1:28 to 1:29
2019-12-05 21:56:11.073 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackProgress changed from 1:29 to 1:30
And now I’m getting tons of these written to the log: (which I’ve not seen before)
2019-12-05 22:28:30.348 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@6c8fff
2019-12-05 22:28:40.401 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@6c8fff
2019-12-05 22:28:50.458 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@6c8fff
2019-12-05 22:29:00.509 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@6c8fff
Update:
I just rebooted once again and the devices came online (the previous reboot did not help)
The log:
==> /var/log/openhab2/openhab.log <==
2019-12-05 22:32:00.619 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at http://172.16.30.71:8080
2019-12-05 22:32:00.621 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at https://172.16.30.71:8443
2019-12-05 22:32:00.871 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
==> /var/log/openhab2/events.log <==
2019-12-05 22:32:01.061 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:abc8' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2019-12-05 22:32:01.165 [hingStatusInfoChangedEvent] - 'spotify:player:fba277f5' changed from UNINITIALIZED to INITIALIZING
2019-12-05 22:32:01.179 [hingStatusInfoChangedEvent] - 'spotify:player:fba277f5' changed from INITIALIZING to UNKNOWN
2019-12-05 22:32:01.342 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:3d41' changed from UNINITIALIZED to INITIALIZING
2019-12-05 22:32:01.345 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:3d41' changed from INITIALIZING to UNKNOWN
2019-12-05 22:32:01.350 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:50d9' changed from UNINITIALIZED to INITIALIZING
2019-12-05 22:32:01.353 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:50d9' changed from INITIALIZING to UNKNOWN
2019-12-05 22:32:01.377 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:abc8' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2019-12-05 22:32:01.382 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:abc8' changed from INITIALIZING to UNKNOWN
==> /var/log/openhab2/openhab.log <==
2019-12-05 22:32:01.871 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@192ea37
==> /var/log/openhab2/events.log <==
2019-12-05 22:32:01.976 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:50d9' changed from UNKNOWN to ONLINE
2019-12-05 22:32:01.982 [hingStatusInfoChangedEvent] - 'spotify:device:fba277f5:3d41' changed from UNKNOWN to ONLINE
2019-12-05 22:32:02.102 [hingStatusInfoChangedEvent] - 'spotify:player:fba277f5' changed from UNKNOWN to ONLINE
==> /var/log/openhab2/openhab.log <==
2019-12-05 22:32:02.149 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@192ea37
2019-12-05 22:32:12.200 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@192ea37
2019-12-05 22:32:22.252 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@192ea37
2019-12-05 22:32:32.315 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@192ea37
2019-12-05 22:32:42.367 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@192ea37
2019-12-05 22:32:52.414 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@192ea37
2019-12-05 22:33:02.461 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@192ea37
2019-12-05 22:33:12.519 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@192ea37
2019-12-05 22:33:22.570 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@192ea37
2019-12-05 22:33:32.650 [INFO ] [nternal.handler.SpotifyBridgeHandler] - playing: org.openhab.binding.spotify.internal.api.model.CurrentlyPlayingContext@11a55a5
==> /var/log/openhab2/events.log <==
2019-12-05 22:33:32.788 [vent.ItemStateChangedEvent] - spotify_device_fba277f5_50d9_deviceName changed from NULL to Craig's phone
2019-12-05 22:33:32.793 [vent.ItemStateChangedEvent] - spotify_device_fba277f5_50d9_deviceVolume changed from NULL to 100
2019-12-05 22:33:32.797 [vent.ItemStateChangedEvent] - spotify_device_fba277f5_50d9_devicePlayer changed from NULL to PLAY
2019-12-05 22:33:32.801 [vent.ItemStateChangedEvent] - spotify_device_fba277f5_3d41_deviceName changed from NULL to CRAIGS-LAPTOP
2019-12-05 22:33:32.805 [vent.ItemStateChangedEvent] - spotify_device_fba277f5_3d41_deviceVolume changed from NULL to 100
2019-12-05 22:33:32.808 [vent.ItemStateChangedEvent] - spotify_device_fba277f5_3d41_devicePlayer changed from NULL to PAUSE
2019-12-05 22:33:32.895 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackPlayer changed from NULL to PLAY
2019-12-05 22:33:32.915 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_deviceShuffle changed from NULL to OFF
2019-12-05 22:33:32.924 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackRepeat changed from NULL to off
2019-12-05 22:33:32.928 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackProgress changed from NULL to 0:40
2019-12-05 22:33:32.936 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackDuration changed from NULL to 3:23
2019-12-05 22:33:32.938 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_playlists changed from NULL to
2019-12-05 22:33:32.940 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_playlistName changed from NULL to
2019-12-05 22:33:32.942 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackName changed from NULL to Give It Away
2019-12-05 22:33:32.951 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_albumName changed from NULL to Chemicals
2019-12-05 22:33:32.953 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_artistName changed from NULL to The Shoes
2019-12-05 22:33:32.954 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_devices changed from NULL to 50d99f768e44f3388a8d39259ae11e2b24b688c4
2019-12-05 22:33:32.957 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_deviceName changed from NULL to Craig's phone
2019-12-05 22:33:32.959 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_deviceVolume changed from NULL to 100
2019-12-05 22:33:33.184 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_albumImage changed from NULL to raw type (image/jpeg): 95908 bytes
2019-12-05 22:33:33.901 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackProgress changed from 0:40 to 0:41
2019-12-05 22:33:34.903 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackProgress changed from 0:41 to 0:42
2019-12-05 22:33:35.904 [vent.ItemStateChangedEvent] - spotify_player_fba277f5_trackProgress changed from 0:42 to 0:43
@hilbrand I’ve managed to determine what the root cause could be. It’s when I do a cold shutdown (pulled out the power cable).
Then it comes back with the errors reported. Where I live in South Africa there are many power outages, so would there be a way to recover from one and have the binding recognise the devices again?
Hi @hilbrand,
after updating openHAB and the Binding to 2.5.0 M6 the Playlists work fine but could you add another option in the thing to change the amount of playlists requestet from the API?
The default is 20 and the maximum 50 (https://developer.spotify.com/documentation/web-api/reference/playlists/get-list-users-playlists/).
If thats too much for one item, the offset function could be used too.
Would really appreciate if you could implement that.
Ive got just one device that is now showing its device name as “AEOBC” rather than “Downstairs Echo” - other devices seem fine. I recall this happening a long time ago but cant find where or what fixed it?
Hi all,
I’m currently facing a similar issue as others where the Active Device is not showing in the selection drop down. (I’ve also set the deviceId on the thing) Similarly, I have the same issue with Playlists, if I change both of these to text i get the Id much like Paper UI.
Is anyone able to help?
edit: I dont receive any errors either…
many thanks,
In the Spotify Api it’s possible to set an offset. Possible this can be used. So in a rule you then start the second player with an offset. It’s probably not possible to get it exactly synchronized as it very much depends on network latency and processing speed. But it might be enough to get it almost in sync most of the time. Pausing might work to, something to try. If that works it might be the starting with offset will work too. If you think using the offset is worth a try can you create an issue on the openhab2-addons repository and tag me in the description. I currently am short on time and otherwise it gets buried in this thread.
Do you still have the logs. These might be still in the marketplace binding. In the new release these logs are not present.
I’m not sure how I could fix this. The error messages give indicates the things didn’t get initialized correctly and I’m not sure under what conditions that happens and doesn’t seem to be something caused by the binding itself. It might be the cache is corrupted due to the sudden shutdown and a restart is the then the way to recover.
I can set the maximum to 50 by default. I’m not sure how to work with the offset. Possible implement it as an append to the playlist something like <playlist id>#<offset>. Is that something that might work?
Let me know and can you open an issue on the openhab2-addons GitHub repo and tag me in the description. Then I have it on my list otherwise it gets buried here.
It could be the Echo registered itself to Spotify after a restart or update or got renamed for some other reason and when it registerend itself it showed up with that name. Otherwise I have no idea.
You can run with log level trace to see what Spotify returns. If you use text you get the id that is correct, because the id is the value. Only when using Selection you get a selection dropdown.
Thanks for the response @hilbrand, apologies if this is a bit of a novice question; but how do I run the log trace? I’ve seen in earlier posts the syntax is:
log:set DEBUG org.openhab.binding.spotify
Thank you.
Thanks @hilbrand - any ideas on how I can determine if a flash briefing is playing? Seems the active channel is always on so this isnt for it playing - perhaps it is able to be disabled or enabled and this is what active is for?
@hilbrand Ignore my earlier post, Ive managed to get the trace log sorted and displays the below when attempting to select a device/playlist:
2019-12-17 19:47:25.895 [DEBUG] [covery.SpotifyDeviceDiscoveryService] - Starting Spotify Device discovery for bridge spotify:player:bridge
2019-12-17 19:47:25.900 [DEBUG] [ding.spotify.internal.api.SpotifyApi] - Request: (GET) https://api.spotify.com/v1/me/player/devices -
2019-12-17 19:47:25.948 [DEBUG] [potify.internal.api.SpotifyConnector] - Response Code: 200
2019-12-17 19:47:26.474 [DEBUG] [ding.spotify.internal.api.SpotifyApi] - Request: (GET) https://api.spotify.com/v1/me/player -
2019-12-17 19:47:26.515 [DEBUG] [potify.internal.api.SpotifyConnector] - Response Code: 204
2019-12-17 19:47:36.532 [DEBUG] [ding.spotify.internal.api.SpotifyApi] - Request: (GET) https://api.spotify.com/v1/me/player -
2019-12-17 19:47:36.574 [DEBUG] [potify.internal.api.SpotifyConnector] - Response Code: 204
2019-12-17 19:47:46.590 [DEBUG] [ding.spotify.internal.api.SpotifyApi] - Request: (GET) https://api.spotify.com/v1/me/player -
2019-12-17 19:47:46.631 [DEBUG] [potify.internal.api.SpotifyConnector] - Response Code: 204
Looking at the response codes from Spotify API, it seems like this is OK, besides the 204. Does this look normal to you?
Many thanks,
Not sure what ou mean by flash briefing. Spotify only allows 1 device to play at once. The device that is active is the device that can be controlled. But it doesn’t say anything about playing status.
What version of the binding do you run? I made some changes related to 204. 204 basically means that Spotify tells you that it already send that information just recently and therefor the api won’t return anything. I’m under the impression this was changed fairly recently by them and in the past they always returned the data. I made a change to the binding to be able to handle such situations better. (The marketplace version of this binding has timestamp 09/12/2019 in the name in PaperUI).