Another one, updated ui-lovelace.yaml to this content, this is the entire file. Commented the decluttering line from configuration.yaml and restarted HA. The error in dashboard remains the same!
Do you put that in configuration.yaml or lovelace-ui.yaml? Because it needs to be in configuration.yaml, like all resources when using YAML mode. Only card-mod has a different setup.
The correct way inside configuration.yaml if you use YAML is:
Also show some extra code of your lovelace-ui.yaml where you use the card decluttering. Where in lovelace yaml do you use it, is it nested inside another card? Reason I ask is because of this:
Try above things and then create the most basic decluttering template and test that. Also post your code of what you tested if that doesn’t work also.
Ok so that’s not YAML mode but GUI, since you’re literally using the GUI card editor… So you’re not even using lovelace-ui.yaml You need to put the decluttering template at the top of your dashboard. Since you’re not using YAML, that lovelace-ui.yaml file doesn’t do anything for you. You need to press RAW editor and paste it there at the top… Hit the dots in GUI editor and then RAW editor.
When I drive my car I can shift gears without using the shift pedal. It make an awful noise, but it still works. Doesn’t mean it’s the correct way though.
When using GUI mode like you are, you need to add resources through Dashboard settings page. Which is located here (use your own IP and add config/lovelace/resources behind url).
Then you should read the docs, they’re very well writen and there for a reason . I simply pointed out what the correct way is to add resources in GUI and YAML, in order to prevent issues later on and prevent issues troubleshooting.
Anyway, this thread is about decluttering-card, while your issue actually had more to do with not loading up your resources correctly and not decluttering-card itself. Let’s not misuse this thread with off-topic subjects. There are many threads in the Configuration section in this forum if you are interested in why and how resources and stuff works.
Did try that before asking any questions. There is no docs page the explains the difference between or even explains lovelace > resources in any meaningful way
You may solve the problem faster if your issue is a bit changed: imagine this is a standard Entities card with “entity” entries; and try to apply same question to this case. Reason - many people do not use mushrooms.
I’ve been having a play with this and it’s broadly working great!
My only issue is the fact that I have to use so much YAML.
This is either a feature request or me missing something here, so bear with…
It would be great if you could create a card (visually) in Lovelace (perhaps in a view that isn’t visible), then change this card to change all other instances of it. I guess this is defining a template.
I’m using it to duplicate the left column of this wallpanel - as such, there is quite a lot of code if I want to make changes to it. Creating the card visually and copying the code kinda works, but this throws out the indentations in the YAML which is a bit of a pain to correct: