Home Assistant Community

Spotify Lovelace Card

lovelace
media_player
Tags: #<Tag:0x00007f374d02cca0> #<Tag:0x00007f374d02cb10>
#13

You have to add the URL address of your site that contains the card (e.g. https://blablablahassio.duckdns.org/lovelace/3) to your developers.spotify.com-> my dashboard-> edit settings->rediect URLs.

0 Likes

#14

Thank you, works!

0 Likes

#15

@dkramer74 choosing a mediaplayer can only be done with online mediaplayers. Try starting spotify on a device or use the web player (https://open.spotify.com) and load the card. Now these player(s) will appear. The device list on the player is using the Spotify connect api and because opening spotify on a chromecast device requires authentication I can’t initiate a chromecast playback I’m afraid.

0 Likes

#16

This is now moved to https://github.com/custom-cards/spotify-card

1 Like

#17

Really love this custom card, gives so much extra function, so many thanks for it :slight_smile: Great work.

A minor question, I need to re-authenticate a few times per day via the card, is there any possibility to make it more permanent or it is something that handled on backend side?

0 Likes

#18

I will fix the reauthorization bug as soon as I have time. I think it is fixed by trying to auth with the old token even if the old token is expired but I need to investigate further.

0 Likes

#19

Thanks for your help. Let me know if you need a helpful hand to test it.

1 Like

#20

tying to get this to work but neither the master source nor the source for my local js file will work. i still get “no card type configured”

0 Likes

#21

I got it working but choosing sources they dont all show up same as the other spotify component

0 Likes

#22

open a ticket on the repo: https://github.com/custom-cards/spotify-card/issues and add your browser details and the lovelace configuration you use for the card as well as the resource section where you add the spotify-card to lovelace (top one)

0 Likes

#23

Hi, looks really nice! Why this setup:

  - type: module
    url: >-
      https://cdn.jsdelivr.net/gh/fondberg/[email protected]/src/spotify-card.js 

instead of this?

  - url: /customcards/lovelace/spotify-card.js
    type: module

Does it work with custom_updater?

Thanks!

0 Likes

#24

You can download it and att it like that as well. I haven’t tried with the custom_updater, if you try please feedback the results

0 Likes

#25

Ok, I will!

0 Likes

#26

Unfortunately it doesn’t work with custom updater for me.

0 Likes

#27

Do you know how I can add support for it? Also I moved the repo to custom-cards yesterday and haven’t had time to update.
https://cdn.jsdelivr.net/gh/custom-cards/[email protected]/src/spotify-card.js Is the new URL

0 Likes

#28

Sorry but I don’t know but I’ll try it with the new URL.

0 Likes

#29

As I see the updater gets data from the “custom_components.json” (or similar) at the others.

0 Likes

#30

I read up on the code and docs for custom_updater https://github.com/custom-components/custom_updater/wiki/How-it-works and it seems it works only with downloaded cards.
I would say that adding the URL resource is far superior and you if you choose the master url (the one I pasted) you will always get the latest card.

0 Likes

#31

https://cdn.jsdelivr.net/gh/custom-cards/[email protected]/src/spotify-card.js
so should I to add this URL for the Custom updater component in the configuration?
when I installed this card this form didn’t worked for me:

  • type: module
    url: >-
      https://cdn.jsdelivr.net/gh/fondberg/[email protected]/src/spotify-card.js 
    

I mean I had to download it manually. The custom updater can’t find it now.

0 Likes

#32

What I mean is that the custom updater doesn’t give you anything extra if you use the URL I provided. The CU will try to help you upgrade custom things right? The URL will give you this without you having to do anything

0 Likes