🔹 Auto-entities - Automatically fill cards with entities

Ildar_Gabdullin · December 27, 2021, 9:40pm

Is it an attribute?
What possible values does it have? Are they [0…9, 10…99, 100…999], [0…9], [10…99] or …?
Also, what do you want to display - this attribute or a state?

cavester · December 27, 2021, 10:20pm

Hi yes an attribute.
It’s variable, ie flood level sensor specific and is measure in metres. It seems to vary from about 0.7 to 2.5. I only want to show flood sensors that are above the maximum normal figure that is applicable to that entity.

Maximum normal: 0.85m which is an attribute of sensor.any_Flood_level and is fixed for each sensor but different for each sensor.
Sensor.any_Flood_level: 0.75
And sensor does not showin my auto list.
Sensor.any_Flood_level: 1.1
The sensor shows in my auto list. It can just shown an icon, or the state, not bothered, but did assume it would show a state if it could be done

Ildar_Gabdullin · December 27, 2021, 10:55pm

As far as I understood:

There are some sensors.
Every sensor has an attribute my_attr.
There is an Entities card with these sensors.
Some sensor must be displayed in the card if its state <= its attribute my_attr (or >=, whatever).

If I got your idea right - then try to adapt this code for your case:

    filter:
      template: >
        {% set GROUP = 'group.my_sensors' -%}
        {%- set MY_SENSORS = expand(GROUP) -%}
        {% for my_sensor in MY_SENSORS | sort(attribute="attributes.my_attr") -%}
          {%- set STATE_VALUE = states(my_sensor.entity_id) -%}
          {%- set ATTR_VALUE = state_attr(my_sensor.entity_id,"my_attr") -%}
          {%- if STATE_VALUE|float(default=0) <= ATTR_VALUE|float(default=0) -%}
            {{my_sensor.entity_id}},
          {%- endif -%}
        {%- endfor %}

The group.my_sensors must contain all your sensors.
This code was verified for another case, then I changed it for your case and then was not able to verify it again.

Note that sort(..) may give wrong results like “1,10, 111, 2, 3, 31, 4”.
But if values are like “0.4, 0.45, 0.7, 1.1, 2.3” - I think that sorting will be OK.

Clement_Valentin · January 1, 2022, 11:03pm

Hello,

it’s possible to attribute severity color of custom:bar-card according to an attribute sensor ?

Ildar_Gabdullin · January 2, 2022, 7:27pm

Sorry, but how is it related to auto-entities?
Severity color is supposed to be defined for different ranges “from… to…” in bar-card.

Clement_Valentin · January 2, 2022, 10:59pm

Yep i didn’t use Severity but style :
I try this but it’s not working

direction: up
type: custom:auto-entities
style: |
  ha-card {
    box-shadow: none !important;
  }
card:
  type: custom:bar-card
  title: Filaments
  show_header_toggle: false
  direction: up
  height: 709px
  stack: horizontal
  icon: mdi:printer-3d-nozzle
  attribute: state_percent
  unit_of_measurement: '%'
  positions:
    name: inside
    icon: inside
  style: |-
    bar-card-title {
      text-shadow: none;
    }
    ha-icon {
      color: white;
    }
    bar-card-card {
      text-shadow: none;
      color: white;
    }
    bar-card-currentbar {
      border-radius: 10px;
    }
sort:
  method: domain
filter:
  include:
    - entity_id: sensor.filament_*
      options:
        type: custom:bar-card
        name: test
        style: |-
          bar-card-currentbar {
            --bar-color: #FF0000 !important;
          }
          bar-card-value{         
            color: black;
          }
  exclude:
    - entity_id: sensor.filament_select
view_layout:
  grid-area: filament

EDIT : when i use color attribute it’s work
But if you use state_attr it doesn’t work

It is not loaded correctly

EDIT 2 : I have found solution :

  template: |
    {% for state in states.sensor -%}
      {%- if state.entity_id | regex_match('sensor.filament_',ignorecase=False) -%}
      {%- set NAME = state_attr(state.entity_id,"friendly_name") -%}
      {%- set COLOR = state_attr(state.entity_id,"color") -%}
        {{
          { 'entity': state.entity_id,
            'name': NAME,
            'color': COLOR
          } }},
      {%- endif -%} 
    {%- endfor %}

elgatho · January 3, 2022, 1:54pm

Hello all,
I’m strugling with list of tasmota devices.
it is possible to create hyperlink from list with ip?

tap_action:
  action: url
  url_path: this.entity_id

cavester · January 3, 2022, 9:33pm

Happy Bew Year to you! I’ll give it a go tomorrow. Thanks for your help

Mariusthvdb · January 3, 2022, 11:44pm

only now starting with dark mode, I stumble upon this issue of not being able to set options for it using the auto-entities card with Map. Filed (edit: and closed, see below) an issue in the repo options not functional on Map card · Issue #241 · thomasloven/lovelace-auto-entities · GitHub but thought it might be good to post/ask here too:

        - type: custom:auto-entities
          card:
            type: map
          show_empty: false
          filter:
            include:
              - domain: person
                options:
                  hours_to_show: 48
                  dark_mode: true
                not:
                  state: home

card works fine, with the exception of the options, which are simply not applied.

please have a look? thanks!

EDIT

o dear, how stupid of me. this is all there is to it:

        - type: custom:auto-entities
          card:
            type: map
            hours_to_show: 48
            dark_mode: true

nvm me.

Ildar_Gabdullin · January 4, 2022, 10:27am

Yes, these are card-wide options.

Mariusthvdb · January 6, 2022, 12:04pm

new challenge…

replace:

        filter:
          include:
            - entity_id: sensor.*_actueel
              state: '>30'

with a state following an input_number.power_threshold

        filter:
          include:
            - entity_id: sensor.*_actueel
              state: '> input_number.power_threshold' # or states('input_number.power_threshold')

would be awesome ofc (like we can do with numeric state triggers, but I believe we need to use the template option, which is still a bit more complex…

anyone with a quick fix, that doesnt iterate over all states|sensor ?

Michael_Baadsgaard · January 9, 2022, 11:20am

hi i try to make a card with a tap action. The tap action need a id that is in the attribute of the sensor.
{{state_attr("this.entity_id", "id")}}
how can i do this?
This code dont work - it works if i insert 1 instead of ‘{{state_attr(“this.entity_id”, “id”)}}’, but the id is different for every one of the sensores.

card:
  show_header_toggle: false
  title: Fryser
  type: entities
filter:
  include:
    - entity_id: sensor.*template_grocy_stk_*
      options:
        tap_action:
          action: call-service
          service: grocy.consume_product_from_stock
          service_data:
            product_id: '{{state_attr("this.entity_id", "id")}}'
            amount: 1
            transaction_type: CONSUME
  exclude:
    - state: unavailable
sort:
  method: state
  numeric: true
  reverse: true
type: custom:auto-entities

Ildar_Gabdullin · January 9, 2022, 1:15pm

I do not think that product_id supports templates. Also, this.entity_id is not supposed to be used in quotes.

Michael_Baadsgaard · January 9, 2022, 1:51pm

ok do you have any idea how i can do this with auto entities?

Ildar_Gabdullin · January 9, 2022, 3:03pm

Use “template” option of the card.

Michael_Baadsgaard · January 9, 2022, 6:53pm

i have tryed this and a lot more

action: call-service
          service: grocy.consume_product_from_stock
          service_data:
            product_id:
              template: '{{state_attr("this.entity_id", "id")}}'
            amount: 1
            transaction_type: CONSUME

but this dont work. how would you do it?

Ildar_Gabdullin · January 9, 2022, 8:15pm

Does the “product_id” option has a “template” option?
I guess - NO.
Use only options accordingly to Docs.
Earlier I advised to use a “template” option of “auto-entities” card. This option allows to specify lists by using jinjia.

Michael_Baadsgaard · January 10, 2022, 6:51am

maybe this is an option, but i dont know about jinjia. could you please help?

arganto · January 11, 2022, 6:26pm

Is there a way to template options? Or anyone has any other idea?

Instead of changing my entity name, I only want to change the name, which is displayed.

So instead of “abc Rssi Device” the rows should only display “abc”.

I thought about

      options:
        type: custom:multiple-entity-row
        secondary_info: last-changed
        show_state: false
        name: |
          {{ states('this.entity_id') }}
        entities:
          - entity: this.entity_id
            name: false

and then have some jinja2 instead of the states() above. This here was only for test purposes, if I can template, but this seems to be not the case?

Ildar_Gabdullin · January 11, 2022, 7:14pm

Possible with auto-entities::template option.