For it to automatically detect the name needs to start with spotify_ i think. Otherwise just specify it in the config under advanced settings
1 Like
Too little information to help I’m afraid.
The delay for the media player spotify is nothing we can control from this card. Core HA has set the refresh to 30s which is a bit long so all you can do is to ask for a change there
Ok thanks. Just a question is “hidden_cast_devices” the right option to hide some cast devices?
No it’s not. Have you updated to the lastest version v2.0.3? The correct option then is filter_devices
Ok… yes already updated but still not changed the option…
I just released a new version which fixes this.
Are you using the GUI editor or yaml mode?
Yaml mode. Is still filter_devices?
See https://github.com/custom-cards/spotify-card:
filter_devices:
- .*room <hides all devices ending with room>
- bath.*,kids.* <hides all devices which start with bath or kids>
1 Like
Hey, i have made some screens :
as you can see i have a denon receiver in the list, but its not as default selected with this code …
how cna i make it default? so i dont have to select the device?
also, is it possible to have the “choose player” at the top of the grid of playlists? now its at the bottom
default_device: "Denon AVR-X4000"
device: "Denon AVR-X4000"
Thanks for the screenshots. I can reproduce this now by myself. I’ll keep you informed if an update is available.
1 Like
Regarding the menu at the top… this is not something we currently plan but you are always welcome to create PR
I don’t have program skills 
Is it difficult? Only in JavaScript?
I have a problem while manually installing spotcast.
I’m getting the following error in my config file:
Error loading /config/configuration.yaml: secret xyz not defined
The section in my config file is:
spotcast:
sp_dc: !secret sp_dc
sp_key: !secret sp_key
I have substituted sp_dc and sp_key for the content in my spotify account as mentioned in the docs.
Perhaps my HA config is not set up to recognise the non-specific tags?
Are you saying you have something like
spotcast:
sp_dc: !secret ABCDd31c67598e7640711ff0a2972198ee01....
sp_key: !secret d31c67598e7-640711ff-0a2972198ee01....
In your config?
You would either need
spotcast:
sp_dc: ABCDd31c67598e7640711ff0a2972198ee01......
sp_key: d31c67598e7-640711ff-0a2972198ee01.....
Or
spotcast:
sp_dc: !secret sp_dc
sp_key: !secret sp_key
And add the following to a new file called secrets.yaml
sp_dc: ABCDd31c67598e7640711ff0a2972198ee01......
sp_key: d31c67598e7-640711ff-0a2972198ee01.....
It is suggested to use secrets.yaml, as you can then share parts of you config withour being afraid of secrets being published somwhere they should not.
1 Like
Thank you very much, that explains it.
Yes, that’s what I currently have in my config file.
I’ll create a secrets.yaml file and make the entry like you suggested.
My apologies, I’m still learning this stuff. I appreciate the assistance.
1 Like
How do I add the card via Lovelace?
It’s not in my list of existing cards, so I assumed that I have to add it as a custom card as follows:
type: 'custom:spotify-card'
When I did this I got an error:
Custom element doesn't exist: spotify-card.
type: 'custom:spotify-card'
I’ve never added a custom card before, perhaps I am doing something wrong?
Have you tried to restart home-assistant? And sometimes clearing the browser cache also helps.
The card should normally appear in the list of available cards
I have restarted and cleared my browser cache, but still no card appears.
What is the card called?