yeah, agreedā¦ dashboards require a lot of coding unfortunately as there is no uniformity among card development (I suspect because HAās code doesnt have a many card features/capabilities natively the card devs can leverage)ā¦ Seems like everyone is reinventing a wheel.
Auto-entities is one of the few true user friendly card integrations so I was hoping it would make something this basic, as easy as it does everything else. Its a super useful card, but was hoping not to need to use a hack to do some basic things like ādo not show the entity valueā
by chance, I found that this disables all the clicksā¦
Longtime user, with pretty simple needs. I am transitioning some of my dashboard pages to the new sections format and I am happy to be using this to move some entries cards to use the new tile cards.
Tile cards are not supported in the direct way you might think by this extension, but there is a closed issue which provides some great examples and Iāve gotten this working easily. Posting it here in case it is useful to someone else trying to use auto-entities to make tile cards:
Ok, some users probably thought that āTile card is not supportedā. But there are many examples here about using stack-like cards which these users seem to have not seen. Anyway, thanks for sharing some more examples.
Hi, Is there a way to define the filter value, lets say threshold for low battery, using a input_number helper to make it more dynamic, rather than a defined number in the card?
type: custom:auto-entities
card:
type: entities
title: test filter label auto entities
filter:
include:
- label: intercom_speler
grinds the view, and even the editor in the UI when having entered - label and not even having typed the : yetā¦
be warned, or even better, join in in testing that, because it has been the one big flaw of the last year or so.
Now there is an imminent update to the resource, letās give Thomas as much info that can help him fix this.
Solution: remove/replace the Entity name text on the buttons. Took me 2 days to figure this out after multiple templates, searches and AI. Hope this helps others since there are too few examples of complete / working code on this thread.
And below a much fancier version using Expander and color border to show if any of the devices are on.
I got mine working for motion sensors (I have more than 20 of them), but the distance between each line was too much, and the value was just āDetectedā which is of minimal use, so instead I used a markdown card that works in the same manner, but actually shows the exact time with most recent one on top, and the description, and if there is no motion - a single line message āCurrently no motion detected.ā. (I guess I could add some code to hide the card altogether instead in that case.) In my opinion, this is much more elegant (and takes up much less space):
yes, a nice feature of Markdown.
did you consider labels (it will be nicer on the system to only āwatchā the labeled entities in stead of the whole states
content: >
{% set motion_sensors = label_entities('beweging')
| select('is_state','on')|list %}
{% if motion_sensors | length > 0 %}
{% for s in motion_sensors|expand %}
{{as_local(s.last_changed).strftime('%I:%M:%S %p') }} : {{ s.name }}
{% endfor %}
{% else %} Currently no motion detected.
{% endif %}
personally, I use {{as_local(s.last_changed).strftime('%X') }} : {{ area_name(s.entity_id) }}
This has been a long standing issue for me, but since the dashboard plugin seems to be getting some development time, I wanted to see if I could get this resolved. I want to order entities by numeric state. However, the sorting seems to not convert the states into numbers, and is instead ordering them as strings.
