Thanks a lot, your solution is working perfect.
I just had to modify my regex for the search condition of selectattr
from: /^sensor.calendar_event[1-9]$/
to: sensor.calendar_event[1-9]
Fantastic, thanks for your help! A lot of your other posts were also really helpful to me.
Essentially, one can take their entity list from the regular entities card, put it into the filter section of the auto-entities card and it just works. Maybe a bit unintiutive, but Iāll take it.
i cannot adjust h1 tittle āShellyā size or padding , not applying , under type: custom:stack-in-card can but not in auto entities card, any help please?
Probably this is what you need:
main card mod thread - 1st post - link at the bottom title āfantasticā - other stuff - combining ā.:ā and ā$:ā
Is it possible to configure the entities card? I am trying to pass āshow_icon: falseā and canāt get it to ātakeā anywhere in yaml. I would also love to hide the state and just show the name, or even a custom name, but canāt make this work.
Would it be possible to include/exclude certain entities based on the floor they are in?
I know itās possible based on area, but in some cases I would like to see all entities of a certain floor.
would be great if someone made this into an integration so we could configure this via UI. Not having simple āfilter byā for Labels, etc is a huge gap in both the usage and admin of entities. It seems the devs think the only way people use or admin devices is by area (room)ā¦ which is incorrect. If I want to view and control all my RGB lights I must manually create a dashboard to see them all on the same screen. When providing a feature, we should be able to easily leverage the benefits across all of HA
I created a card with all my battery operated devices, and show battery status of each, sorted from min to max. But āunavailableā show at the bottom. Is there any way to show them at the top, before the min value entities?
Thanks for your awesome integration!
but we have that filter in the entities dashboard.
itās not the same as showing polished cards in the Frontend, but at /config/entities, this is exactly what you can do
as a matter of fact, Ive done away with many an auto-entities card config when that filtering was introduced, it is way faster and less consuming for the system
now if only the helpers dashboard got fixed to be as robust as the entities dashboardā¦
suppose you could write 2 auto-entities configs and stack them, I do that eg for separating inside and outside motion sensors, while all of the other parameters are identical