so its not possible to use the same decluttering templates for multiple dashboards?
ups… I should read the whole comment. Thanks a lot for the explanation!
Edit: Sad that it’s not really worth to dive into this card, as everything seems to slow down if this card is used. Plus there have not been any updates for almost 3 years now…
It would declutter my code so much, but those are deal breakers imo
explain please? can not state the same experience on this side, using a rather extended frontend, and some serious decluttering going on.
Maybe you have another issue at hand?
now that is true. otoh, there have been no real issues to solve and it keeps doing its job nicely
Right, I see.
not using that myself, so I couldn’t respond to that really, but are you sure there’s nothing else in that card config that might cause the delay? The decluttering card really only ‘rewrites’ the yaml, and once that is loaded shouldn’t be any different than writing the card without it.
Note I say ‘shouldnt’… ofc there is always the exception to the rule
I only tested this with custom mushroom cards. But the delay is definitely not there if I use them regularly. Would you mind to test this on your environment?
Thanks for the reply, that is too bad really. I wanted to show a mushroom card with a simple string on one lovelace page, but showing the template on another page. I guess there’s now way around this unless decluttering card gets an update?
I can confirm, I have a simple camera card with more-info popup which shows instantly, and multiple declutter cards in a stack-in-card (so different card, but same popup) where the popup shows with a slight delay. I’d say it’s almost unnoticeable (can’t be more than 0.3 seconds), but when compared to the popup of the camera card there is definitely a difference.
Have terrible experience with camera cards and especially the more info myself, but also without the decluttering card so that might be another issue. See this post
On the template , give us an idea in yaml what you would like and we can see.
Maybe it’s just taking it 1 step earlier in the yaml rebuild sequence
I guess I just found the issue. The delay is only happening if double_tap_action is defined in the card. if not it just pops up right away. That is great news as I can now use the decluttering card
I don’t have a lovelace-ui.yaml, I guess because I only edit my lovelace from the UI itself. I added decluttering_templates: in the raw configuration editor, on the same level as views:, but the card I added says No card type configured. Anyone have any idea?
Is there an option to check the output of the template, so what is pasted in the file through decluttering card?
I have the problem that some code does not work and i do not know what’s wrong.