🔹 Auto-entities - Automatically fill cards with entities

AleXSR7001 · November 24, 2021, 8:18pm

Hmmm, works with history-graph but not yet with ApexCharts. Still seem to have something wrong

type: custom:auto-entities
card:
  type: vertical-stack
card_param: cards
filter:
  include:
    - entity_id: sensor.eq_3_temperature*
      options:
        type: custom:apexcharts-card
        series:
          - entity: this.entity_id

Gives error: /// apexcharts-card version 1.10.1-dev.1 /// value.entity is extraneous
But series needs to be specified, otherwise error that series is missing.

Ildar_Gabdullin · November 24, 2021, 9:00pm

The generated card is:

What you can do is:

either open an issue for auto-entities - “generated card includes extraneous line”;
or open an issue for apexcharts-card - “allow extraneous options”

Update:

github.com/thomasloven/lovelace-auto-entities

`auto-entities` inserts extraneous `entity` option into the destination card

opened 12:50AM - 25 Nov 21 UTC

ildar170975

Let's create a stack of graph cards. Here is one graph card w/o auto-entities…: ``` type: custom:apexcharts-card series: - entity: sensor.cleargrass_1_co2 graph_span: 1h ``` ![image](https://user-images.githubusercontent.com/71872483/143331216-c7cda166-77ee-41b3-9ef2-f24553ef180e.png) The code for the stack: ``` type: custom:auto-entities card: type: vertical-stack title: auto-stack unique: true show_empty: true card_param: cards filter: include: - entity_id: sensor.cleargrass_1_* options: type: custom:apexcharts-card series: - entity: this.entity_id graph_span: 1h ``` The output: ![image](https://user-images.githubusercontent.com/71872483/143331885-5709c6d6-139e-4cbe-b58a-21c1d529a789.png) Seems that `auto-entiites` inserts an `entity` option into the destination card. Since `apexcharts-card` does not accept extraneous options - the error is shown. The error is not shown when using with `history-graph` card since the `history-graph` accepts extraneous options: ![image](https://user-images.githubusercontent.com/71872483/143332116-4019b1f5-c6dd-425c-bcb3-0c11fac7397a.png) But the `apexcharts-card` gives an error: ![image](https://user-images.githubusercontent.com/71872483/143332234-c6f8709a-ffcc-4bf1-93d6-57c53873290e.png)

Ildar_Gabdullin · December 11, 2021, 2:13am

Unfortunately, auto-entities still gives unstable results with map.
Sometimes this card does not show a map:

type: vertical-stack
cards:
  - type: entity
    entity: sun.sun
  - type: custom:auto-entities
    card:
      type: map
    show_empty: false
    filter:
      include:
        - entity_id: device_tracker.life360*
          options:
            default_zoom: 14

When it does:

breinonline · December 15, 2021, 8:23pm

I used to have a auto-entities card with the types of waste that are going to be picked up (GitHub - pippyn/Home-Assistant-Sensor-Afvalbeheer: Provides Home Assistant sensors for multiple Dutch and Belgium waste collectors). It worked great until two days ago. I have an empty card with only the title.
I don’t know if it was the update to HA 2021.12 or just after that. The individual sensors are working if I look them up. I did not make any changes to the card. Does anyone have an idea what goes wrong?

type: custom:auto-entities
card:
  show_header_toggle: false
  type: entities
  title: Afvalkalender
filter:
  include:
    - attributes:
        Days-until: < 14
      options:
        secondary_info: Nog [[ {entity}.attributes.Days-until ]] dag(en)
        type: custom:secondaryinfo-entity-row
      entity_id: sensor.meerlanden*
  show_empty: false
sort:
  method: attribute
  attribute: Days-until
  numeric: true

xisio · December 16, 2021, 4:41pm

Hi, how can i hide entities with some state (where are unavailable) ?
exp.

type: custom:auto-entities
card:
  type: entities
filter:
  include:
    - entity_id: '*sensor.washmaschine*'
      not:
        state: '*unavailable*'
  exclude: []

ASNNetworks · December 16, 2021, 6:19pm

put the filter under exclude not include since your goal is to EXCLUDE unavailable entities. It’s explained in the ReadMe in Github pretty well. Did you bother to check there? Like this example there:

type: custom:auto-entities
show_empty: false
card:
  type: entities
  title: Lights on
  show_header_toggle: false
filter:
  include:
    - domain: light
  exclude:
    - state: "off"
    - state: "unavailable"

xisio · December 16, 2021, 6:58pm

Thank you, I tried the examples in the first place only in a stupid way I tried to filter out the unavailable state in Polish instead of English and it didn’t work.

type: custom:auto-entities
card:
  type: entities
filter:
  include:
    - entity_id: '*sensor.pralka*'
  exclude:
    - state: "off"
    - state: "niedostępny"

works very well in English

Ildar_Gabdullin · December 16, 2021, 7:08pm

Surely since Polish values are only for UI, internally the state is “unavailable”.

breinonline · December 16, 2021, 8:19pm

Solved: the attribute Days-until has been altered to Days_until apparently. Changed that in the code and it’s working again

minifranske · December 17, 2021, 2:15pm

Now that HA provides a button to trigger the OTA update for Shelly devices I thought is was time to add a card to my maintenance dashboard that shows me what device have an update pending.

type: custom:auto-entities
card:
  type: entities
  title: Shelly OTA Updates
filter:
  template: |
    {% for sensor in states.binary_sensor -%}
      {% if 'firmware_update' in sensor.entity_id and sensor.state == 'on' %}
        {{ sensor.entity_id | regex_replace('^binary_sensor.([a-z0-9_]+)_firmware_update$','button.\\1_ota_update') }}, 
      {% endif %}
    {%- endfor %}

To get this to work make sure you are on HA 2021.12, use the official Shelly integration and have the firmware sensor of your Shelly devices enabled.

@thomasloven tnx for this great card

Cafun · December 22, 2021, 9:55am

Hi hope someone can help me with this.
I would like a card for birthdays. So far so good.

The problem is, I need 2 filters because of different attributes I want to show in the card and for one filter 1 need 2 states: > 0 and < 20.
But I don’t get that to work.

Here is the code:

type: custom:auto-entities
card:
  type: entities
  title: 'Verjaardagen'
filter:
  include:
    - entity_id: sensor.anniversary*
      options:
        type: custom:multiple-entity-row
        entity: this.entity_id
        entities:
          - attribute: years_at_next_anniversary
            unit: jaar
      state: '< 20'
    - entity_id: sensor.anniversary*
      options:
        type: custom:multiple-entity-row
        entity: this.entity_id
        entities:
          - attribute: current_years
            unit: jaar
      state: '= 0'
sort:
  method: state
  numeric: true
show_empty: false

cavester · December 27, 2021, 11:14am

Hi All,
I’ve been using this card for a while now and created quite a comprehensive list of warnings. I’ve a new challenge and I can’t think how to solve it.
I’ve created enhanced sensors for local river level sensors, adding their maximum ‘normal’ level (and locations for showing on a map).
I’ve set a filter group for sensors containing the word “flood” but of course I get all the flood sensors regardless of their level. I want them to only appear when their state value exceeds this attribute value, I’m having a mental block and can’t sus how to express this in a filter.

Can anyone help?

Thanks

Ildar_Gabdullin · December 27, 2021, 11:20am

Post a simplified code for your attempts for auto-entities-card containing your sensors.
Have you tried this?

cavester · December 27, 2021, 8:50pm

That’s not quite what I’m trying to achieve, here is some code that doesn’t work:


    - domain: sensor
      entity_id: /flood/
      state: ‘> this.entity_id.maximum_normal’

I know it’s wrong but I’m not thinking clearly as to what it should be

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 %}