Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spotify card stuck in loading since HomeAssistant 2023.3 #197

Open
jason-glynn opened this issue Mar 27, 2023 · 12 comments
Open

Spotify card stuck in loading since HomeAssistant 2023.3 #197

jason-glynn opened this issue Mar 27, 2023 · 12 comments

Comments

@jason-glynn
Copy link

spotify card stuck on "loading" message with no playlists displaying since Home Assistant 2023.3. Using v2.4 of card.

@Agimgrue
Copy link

Same here! Always appear loading

@leothlon
Copy link

I have two accounts, first one (my wifes) fetches playlist perfectly.
Second account (mine) just say "Loading..." (but it does say correctly for currently playing)

i have removed and re-added both accounts multiple times, but its always the same.. wifes account works, mine does not

@jurand71
Copy link

jurand71 commented Apr 29, 2023

Did you find any solution, I have exactly the same effect, It starts from 2023.3 v

Edit: the problem solved, sp_key as sp_dc changed

@tstill88
Copy link

Did you find any solution, I have exactly the same effect, It starts from 2023.3 v

Edit: the problem solved, sp_key as sp_dc changed

What did you mean sp_key as sp_dc?

Mine is still loading and says Spotify integration needs to be installed for this to work which it as as im using the media_player.spotify_username without issues.

@jurand71
Copy link

All information you need about sp_key and sp_dc you find here: https://github.com/fondberg/spotcast

@tstill88
Copy link

All information you need about sp_key and sp_dc you find here: https://github.com/fondberg/spotcast

Ahh perfect, didnt think to check that integration. Just had to rebuild HA and must have missed it. Thanks!

@skavan
Copy link

skavan commented Apr 10, 2024

Did all the above.
The spotcast service works fine when run.
But still "Loading..."
Ugh! Any ideas --- anyone?

@javiges
Copy link

javiges commented May 7, 2024

Hizo todo lo anterior. El servicio spotcast funciona bien cuando se ejecuta. Pero aún "Cargando..." ¡Uf! ¿Alguna idea? ¿Alguien?

+1

@skavan
Copy link

skavan commented Nov 9, 2024

reauthenticate spotify with new web credentials...and grab the new keys from cookies. fixed.
I must have changed my password and forgot. Or maybe spotify updated the credentials themselved.

@Pirol62
Copy link

Pirol62 commented Dec 7, 2024

Hi, does anyony find a solution here. Since 2024.12.1 spotcast is working fine here. So I don't habe any issues with the keys. But the lovelace card is permanetly loading

@JOHLC
Copy link

JOHLC commented Dec 22, 2024

Hi, does anyony find a solution here. Since 2024.12.1 spotcast is working fine here. So I don't habe any issues with the keys. But the lovelace card is permanetly loading

Mine is as well. In my web browser console, I am seeing these errors:

2services.js:31  Uncaught (in promise) TypeError: this.chromecast_devices.filter is not a function
    at Qe.getFilteredDevices (services.js:31:82)
    at Qe.generateDeviceList (services.js:31:82)
    at Qe.render (services.js:31:82)
    at Qe.update (spotify-card.js?hacstag=173955605240:186:1183)
    at Qe.performUpdate (spotify-card.js?hacstag=173955605240:148:6614)
    at Qe._enqueueUpdate (spotify-card.js?hacstag=173955605240:148:6302)
index.m.js:1  Uncaught (in promise) Error: Failed to fetch playlists: [object Object]
    at Re.fetchPlaylists (index.m.js:1:4274)
    at async entities.js:28:83
index.m.js:1  Uncaught (in promise) Error: Failed to fetch playlists: [object Object]
    at Re.fetchPlaylists (index.m.js:1:4274)
    at async entities.js:28:83

I have completely rebuilt my config for my account, spotcast, and the card and everything is working fine except for the card.

@JOHLC
Copy link

JOHLC commented Dec 22, 2024

Just realized this repo is no longer being developed and that they are talking about this issue over here:
mikevanes#16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants