Thanks for the clarification, I tried the stripped example form Ildar_Gabdullin, tried to modify it, bit no luck.
as said, Just scratching the surface here, the problem is that it is a huuuuge surface
My naming convention is straight forward:
sensortype.TypeOfDevice_property_zone
example, in dutch
sensor.deur_batterijniveau_keuken (translate sensor.door_batterylevel_kitchen)
and another example of a temperature/humidity/pressure device
As you can see I left out the split part batterijniveau_ I had another underscore following in 2 of my sensors namely Lcd_ So I came up with the split to use only the underscore and the [-1] part, show only the last split and it works. as a bonus I added the secondary info, although this was a little bit different in format as you can see than the regular config.entity.atrributes…
An here the result:
Ofcourse the cutoff value has to be set about 20% or so, for this example it was set to 101% show all…
Regards and thanks.
Frank
Did someone now if you can set a fix height to the auto-entities card?
I have is a glance card that is sometimes empty (that’s good),
I have the “show_empty:” on true,
But when the card is empty, the height of the card is not the same height else when there are entities in it.
stuck really, editing an older card of mine, which wont show the geo_location entities anymore…
filter:
template: |
{% set km = states('input_number.quakes_near')|float %}
{% set location = states('input_select.quakes_near') %}
{% for s in states.geo_location|selectattr('attributes.source','eq','usgs_earthquakes_feed') %}
{% if distance(s.entity_id,location) < km %}
{{- s.entity_id -}}
{% endif %}
{% endfor %}
gives me the error:
Either entities or geo_location_sources must be specified
the geo_location entity is live, and the the template is correct:
template: >
{%- set ns = namespace(quakes_near=[]) %}
{% set km = states('input_number.quakes_near')|float %}
{% set location = states('input_select.quakes_near') %}
{% for s in states.geo_location|selectattr('attributes.source','eq','usgs_earthquakes_feed')
if distance(s.entity_id,location) < km %}
{% set ns.quakes_near = ns.quakes_near + s.entity_id %}
{% endfor %}
{{ns.quakes_near}}
though I believed the other template to also create a true list because the empty list showed as [] in the editor, it probably doesn’t… this should be correct., only thing is I can not really test it, because there’s no quakes near at the moment
I am trying to populate the entities with filter: template: but I would like to change the display name of each entity based on their entity_id. It seems like something using options: as in this solution. It just seems like options: won’t work with filter: template:. I am open to any approach to solve this problem.
Basically I am trying to display all the settings I have configured by room, or by behavior (motion light activation, circadian/adaptive lighting, etc.) but I have to display the input_boolean/input_select/input_switch with a different name for each of these configuration methods. When showing settings by room, I need to display the behavior as the display name of the settings entity. When showing settings by behavior, I need to display the room as the display name of the settings entity.
I created this template which gathers the data I need into lists, but I’m not sure what the best way to turn this into the display I am aiming for.
{% if states('input_select.settings_behavior') == "Motion Activation" %}
{% set behavior_entity_type = 'input_boolean' %}
{% set behavior_regex = '\'input_boolean\.((?!motion_lights)[^\'])+\',?' %}
{% elif states('input_select.settings_behavior') == "Natural Lighting" %}
{% set behavior_entity_type = 'switch' %}
{% set behavior_regex = '\'switch\.((?!adaptive_lighting_(?!adapt|sleep))[^\'])+\',?' %}
{% endif %}
{% set entity_list = (states[behavior_entity_type] | map(attribute='entity_id') | list | regex_replace(behavior_regex)) %}
{% set area_list = (entity_list | regex_replace('input_boolean.motion_lights_')) %}
{{ [entity_list, area_list] | regex_replace('"\[','[') | regex_replace('\]"',']') }}
I also tried using config-template-card to create do the switching, but I’m having trouble getting this working.
The only other way I can think to do it is with a very big custom:state-switch card containing a bunch of auto-entities cards. Which seems like a headache to come back to if I need to add more settings.
First of all, a huge thank you to @thomasloven for this fabulous card.
I confess to not having read all the posts, so please bear with me if my question has already been answered.
I would love to be able to sort by the most recent entry. Is that already possible?
I do not know any exposed property expressing a “creation time” for entity.
If it is not present - then it is not possible to sort by it.
So, first find out about this property.
Could someone help me I can NOT figure out how to make the background transparent on this card. With my code as is the background is transparent when in the editor. soon as I save it does not show as transparent.
But does it still work after you save and return to the dashboard? Soon as I do it reverts to the default theme even with red. This is really messing with me as even when i go back to “edit” it will blink red and go back to the dark mode default. I have MANY cards on my setup and this one is the ONLY 1 that wont go transparent.
I do not see any flickering.
I tested this case with a card which is not placed inside some other card.
Could you provide a whole code for your card?
Also, I am using a default Lovelace theme.
OMG, you were 100% right! I moved it to a stand-alone card and BOOM it worked! HTF I did not try that months ago I don’t know… Thank you so much go’s to show some times you just need a kick in the but. haha
Hey, is there a way to always show the newest “entry”, i.e. just showing one entry? Using layout cards it is supposed to always show the media control card of the device it is currently playing on, but due to the Spotify Integration, there are always two - The normal spotify one, and then the one from the device it is actually playing on.
