Spotify Lovelace Card

media_player
lovelace
Tags: #<Tag:0x00007fd077b2b430> #<Tag:0x00007fd077b2b250>

#63

got

INVALID_CLIENT: Invalid redirect URI

and its saved on the developer as you said


#64

For older browsers I have now spent the weekend fixing transpiling.
If this works I can focus on enhancements next weekend
New release:

https://cdn.jsdelivr.net/gh/custom-cards/[email protected]/dist/spotify-card.umd.js

#65

@carlostico You don’t have the proper URL configured in the Spotify developer console.


#66

I do have the correct address on the redirect , that is the weir part


#67

Everytime when i enter my lovelace page i have to click on the authenticate button.
I use Google Chrome as browser.


#68

@Cinamon see Spotify Lovelace Card


#69

I would love to hear from someone which had issues with Firefox if it is solved now.


#70

I get this in my log:

http://hassio.cqm.local:8123/lovelace/0:0:0 Uncaught TypeError: Failed to resolve module specifier “@babel/polyfill”. Relative references must start with either “/”, “./”, or “…/”.


#71

It worked after updating the URL in ui-lovelace resources to:

https://cdn.jsdelivr.net/gh/custom-cards/[email protected]/dist/spotify-card.umd.js

and clearing browser cache.

Thanks a bunch!
This is an awesome card!!


#72

Made the change, card now works again.

If the card (for now) downloads whenever used, does it need or use the custom-updater?


#73

@Dansker There are plenty of references to this question in this thread and because I don’t use customer updater I wouldn’t be able to answer but a lot of people do have it working


#74

Thanks for your reply, I did have custom updater working, it updated, -which broke the card. See my post about 4 up.

Appreciate your work


#75

that should be solved now with the transpiled version (checked into dist/directory) which you can download OR download the one from releases. Your one is the polyfill version which was just for a try before


#76

New release 1.3 which is both smaller as well as fixes the reauth issue.


#78

Why i get only one media player device when i have many of them?
Actually i can see only my echo plus device, and not any of the google home, of the sonos or of the chromecasts or the other echo devices i own…


#79

I read many different URL’s to put in the resource of lovelace… can you tell me which is the latest and the best to use?


#80

The reauth issue has been solved I can confirm it :slight_smile: works perfectly.


#81

@maurizio53 if you want the latest stable you have the info in the README on the repo


#82

spoti

Hi,

I think, I configured everything properly, but there ain’t no playlists showing up and ‘choose mediaplayer’ is not clickable, although I have players online…

What am I missing?


#83

INVALID_CLIENT: Invalid redirect URI

for some reason is redirecting to lovelace/default_view

https://accounts.spotify.com/authorize?client_id=000000000000000&redirect_uri=https://myaddress.com:8123/lovelace/default_view&scope=user-read-private%20user-read-email%20playlist-read-private%20user-read-birthdate%20user-read-playback-state%20user-modify-playback-state&response_type=token

even the correct information is on the spotify app

https://myaddress.com:8123/lovelace/media/