Examples - Entities card, Glance-card, history-graph, custom:mini-graph-card, custom:apexcharts-card, ā¦
If you want to fill the some_objects list by auto-entities:
type: custom:auto-entities
card:
type: some-card ### your card
card_param: some_objects ## by default = "entities"
filter:
include:
- ...
options:
.... options for a particular entity
As for your case - check if the custom:simple-thermostat accepts a list of objects.
If not - then your way is using that card inside a STACK:
type: custom:auto-entities
card:
type: vertical-stack
card_param: cards
filter:
include:
- ...
options:
type: some-card ### your card
.... options for a particular card
I noticed that this card currently includes entities that are hidden using the new 2022.4 functionality. Is there an easy filter to exclude those? As the card is intended for the UI I feel like these should not be included by default.
As far as I know, there is no āhiddenā attribute among the state objects.
And we cannot use the āhiddenā attribute inside a ātemplateā option, for instance.
I have one autogenerated dashbord to easily get at entities I did not care to include in my ānormalā dashboards, which of course I maintain myself. But this card is the perfect balance between control of the dashboard and not having to maintain a lot of entity lists by hand. That is why I hope to find a way to hide unwanted entities.
For instance, when using the Switch as X feature, the original entities should not show up as well. The same goes for a lot of other template entities I use to enhance the original ones. I use template covers that block normal operation when it isnāt safe (wind, open window blocking a rollerblind). I hide the original unprotected ones now. It would be nice if I can take advantage of that with the auto-entities card.
I could list them as excludes, but that kind of defeats the purpose, as Iād then be listing the other half.
As I said, this āhiding thingā is not available in āstate objectsā. But probably this āhiding thingā is available for custom cards via some programming interface - I do not know.
You may start monitoring this issue:
I will try templating. As this is relatively new to me, I will need to do this during the weekend.
But something else I ran into last night:
I would like to use auto-entities within cards like horizontal stack, grid and picture-elements. But of course, when I have a lot of entities, then the auto-entities creates one long list.
Is it possible to somehow break this list into sections or make it create columns?
One idea would be to only display entites 1-10, then 11-20 and so on. So a filter which is not based on the entity information but only on the amount of entities returned?
OK group or @thomasloven ā¦ I am a bit lost on this one and I am trying to figure out whether this can be done.
Background ā because of the demise of Insteon, I have been doing some GUI work to make things easier. As part of this, I created a sensor that can give me entity_idās for all insteon devices and then I put them into an option list. Selecting an option list I can get the currently selected entity. Now because the auto-entities card only takes templates in the ātemplateā of filter, I pass in that via jinja.
But I would have expected the āauto-entitiesā card to toggle auto-magiclly to the type selected or even by setting the type to āslider-entity-rowā ā¦ instead it seems to only use a switch with on/off.
Your last version (with it unindented) looks the most correct to me, or at least it works for me.
But what happens if you add a sort by name method? Does it put the HACS sensor first in this case?
The reason I ask is that it maybe working for me because the entity Iām including always alphabetically precedes the filtered entities, so I wonāt have noticed it not working. In that case, it does sound like a bug.
yeah, I reread the docs again, and the unindented is what is was supposed to be apparently. So that was officially a āuser-errorā
didnt use the sort option yet, which would rely on the coincidental fact sensor.hacs would always precede the update domain entities alphabetically ā¦
So this is my first time using this card, and the possibilities seem great. I just messed up somewhere, or at least the behavior is unexpected. It is actually a modification of another post of @Mariusthvdb.
I have the following configuration. However, it seems as if the sorting isnt working.
type: custom:auto-entities
filter:
include:
- entity_id: sensor.afvalwijzer_gft
options:
type: custom:template-entity-row
secondary: >
{% set count =
state_attr('sensor.afvalwijzer_gft','days_until_collection_date')|int
%}
{% set unit = 'Dag' if count == 1 else 'Dagen' %}
{% if count == 0 %} Vandaag
{% else %} Over {{count}} {{unit}}
{% endif %}
- entity_id: sensor.afvalwijzer_pmd
options:
type: custom:template-entity-row
secondary: >
{% set count =
state_attr('sensor.afvalwijzer_pmd','days_until_collection_date')|int
%}
{% set unit = 'Dag' if count == 1 else 'Dagen' %}
{% if count == 0 %} Vandaag
{% else %} Over {{count}} {{unit}}
{% endif %}
- entity_id: sensor.afvalwijzer_papier
options:
type: custom:template-entity-row
secondary: >
{% set count =
state_attr('sensor.afvalwijzer_papier','days_until_collection_date')|int
%}
{% set unit = 'Dag' if count == 1 else 'Dagen' %}
{% if count == 0 %} Vandaag
{% else %} Over {{count}} {{unit}}
{% endif %}
- entity_id: sensor.afvalwijzer_restafval
options:
type: custom:template-entity-row
secondary: >
{% set count =
state_attr('sensor.afvalwijzer_restafval','days_until_collection_date')|int
%}
{% set unit = 'Dag' if count == 1 else 'Dagen' %}
{% if count == 0 %} Vandaag
{% else %} Over {{count}} {{unit}}
{% endif %}
- entity_id: sensor.afvalwijzer_luiers
options:
type: custom:template-entity-row
secondary: >
{% set count =
state_attr('sensor.afvalwijzer_luiers','days_until_collection_date')|int
%}
{% set unit = 'Dag' if count == 1 else 'Dagen' %}
{% if count == 0 %} Vandaag
{% else %} Over {{count}} {{unit}}
{% endif %}
sort:
attribute: days_until_collection_date
method: state
numeric: true
reverse: true
ignore_case: true
show_empty: true
card:
type: entities
as you can see the sorting doesnāt work as I expect. I would expect the PMD entry would be sorted between the once that take 2 days and 18 days. But somehow it doesnāt do that. Note that in displaying the attribute is correctly interpreted, but in sorting somehow this is not the case.
thanks! that fixed it! I was aware that auto-entities was capable of automatically listing entities that satisfied a certain criteria. However, I wasnāt sure on how to access the attribute of that entity to get the ādaysā until. I guess that config.entity refers to all the entities that are selected by the sensor.afvalwijzer_* āfilterā? Sorry if Iām not using the right terminology, Iām still fairly new to this.
