Failed to get device id from Spotify (3.5.4) #196
Comments
hmmbob
changed the title
|
I'm getting the same issue (no known devices), however I get it for all accounts (default and two others that are configured). Spotcast sadly doesn't work for me at all right now :/ |
|
Did you setup spotify in HA? It is required. |
|
Yes for two accounts. It was working fine for a few months now, but now I receive an empty device array similar to you. |
|
Yeah, I see the same. Until yesterday it worked with the main account, now that is broken too. |
hmmbob
changed the title
|
@fondberg Did some fiddling around. With the 'dirty fix' that has been used before, it works again. If I trace the errors, it appears that there is a valid Chromecast found, but this device isn't visible/available through spotify hence why Would it be possible to bypass the Dirty fix also fixes the secondary account issue (again, with a valid Chromecast): |
|
I'll have a look |
|
Thanks for looking into this! I think that this might have something to do with spotcast using the wrong Spotify account by default. When I checked the logs, I saw a device listing which only could have been from a different account, although the service call did not specify an account but should have used the default one. The spotify-card also sometimes shows the wrong playback state from a different account (i.e. a playlist is highlighted in blue although a different account listens to a different playlist that happens to share the same name) Sadly the log is no longer in home assistant, but I'll keep my eye on it to see whether it happens again. |
|
With fixing the playback issues a couple of weeks back we now use the device list from spotify media player core which has its account and spotcast MIGHT have another account. Can you confirm that this is the case for you (that you are using different accounts between them)? |
|
As I can't solve the multiple accounts issue there is only one alternative and that is to either leave it semi-broken or remove multi-account support. |
This could be the case. Core Spotify has 3 accounts setup, with Spotcast I am using 2. So, it could be that Spotcast account "T" (in my case) is talking to the "Hmmbob" core Spotify account. This shouldn't be too much of a problem though, as T us my son and thus uses the same devices as I do ;-) |
|
OK, then we need to map this to the correct core player. Do you have a proposal on how to do this? |
|
The code that needs to get the "correct" player is |
|
@hmmbob maybe we should readd the dirty fix Can you do a PR for it? |
|
Sure. It is at least a little band aid on the error. |
|
Please try with https://github.com/fondberg/spotcast/releases/tag/v3.5.7 |
|
Hi @fondberg , I tried with the latest and still have the issue with v 3.5.7. Thoughts?
This is my spotify card and if I choose "pioneer receiver" from the spotify card, it'll play on the device just fine. |
|
@gabosom I think there might be something else that is a problem for you. Feel free to post a new bugreport if you have the problem. closing this seeing as it solved it for the actual reported issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Niklas,
Tried the new release, but it is throwing errors at me when I am using a 2nd account:
Spotcast config (3.5.4):
Error in the log:
What I can see with my non-dev eye, is that the requested Cast device is actually found (media_player.hmt) by
get_cast_devices, but that it isn't listed as known spotify device (inget_spotify_devicesand thus throws an error. To be sure it wasn't a token error or something, I've already updated thesp_dcandsp_keyvalues for both accounts (default andtaccount), without any difference.When using the default account, it all works fine: --edit: later proved wrong, see comments below
(interestingly enough, here
get_spotify_devicesalso seems to return[])(Spotify M is another spotify account loaded in the core spotify integration, but not being used with Spotcast)
The text was updated successfully, but these errors were encountered: