🔹 Auto-entities - Automatically fill cards with entities

Haningback · September 27, 2024, 12:03pm

Just wanted to share this little thing i came up with:

Auto entities lists all my areas and creates a area-card with temp, humidity and lux… still working on how to get a different icon for each area, dont wanna rename my rooms, but could be a possibility…

type: custom:auto-entities
filter:
  template: |
    [ {% for omrade in areas()|sort %}
      {{ 
        {
        'type': 'custom:streamline-card', 
        'template': 'klimakort',
        'variables': [
        {'entry': omrade}
          ]
        } 
      }} 
      , 
    {% endfor %}  ]
  include: []
  exclude: []
card:
  square: false
  type: grid
  columns: 2
show_empty: true
card_param: cards
sort: {}

and a decluttering card (streamline-card… because that has a gui-editor lol)

streamline_templates:
  klimakort:
    card:
      type: custom:mushroom-template-card
      primary: '{{area_name(''[[entry]]'') | title }}'
      secondary: >-
        {% set temp = (area_entities('[[entry]]') | select('is_state_attr',
        'device_class', 'temperature') | map('states') | select('is_number') |
        map('float') | list or [0]) | average | round(1) %}

        {% set hum = (area_entities('[[entry]]') | select('is_state_attr',
        'device_class', 'humidity') | map('states') | select('is_number') |
        map('float') | list or [0]) | average %}

        {% set lux = (area_entities('[[entry]]') | select('is_state_attr',
        'device_class', 'illuminance') | map('states') | select('is_number') |
        map('float') | list or [0]) | average | round(1) %}

        {{ [ ('🌡️' ~ temp|int ~ '°C') if temp, ('💧' ~ hum | int ~ '%') if hum,
        ('🔆' ~ lux | int ~ 'lx') if lux] | select() | join(' ') }}
      icon: hue:room-office
      entity: '[[entry]]'
      fill_container: true
      tap_action:
        action: navigate
        navigation_path: '#popup-[[entry]]'
      layout: vertical

mtrista · September 27, 2024, 3:13pm

Doesn’t the normal area card do exactly what the custom area template card you’re making does? Even shows the icons for each area

Haningback · September 27, 2024, 6:56pm

Yes it does but imo its fugly and dosent fit the rest of my design

Timsche2210 · October 2, 2024, 8:34am

I just activated all “last seen” attributes of the entities:

It should be possible to sort the entities regarding to their last seen status or not?
Can anybody help me to get the correct yaml working?
I am struggling with it

edit:
got it:

type: custom:auto-entities
card:
  type: entities
filter:
  include:
    - entity_id: sensor.*_last_seen
sort:
  method: last_changed
  numeric: false
  reverse: false

ggonmar · October 9, 2024, 2:54pm

Does this mean that, if I have 20 sensors with a specific attribute I want to show on this card, I need to create 20 template sensors out of that attribute to be able to use the auto entities card?

Ildar_Gabdullin · October 9, 2024, 8:21pm

Probably that advice was given when Entities card was not supporting “attribute”.

fusterclucker · October 11, 2024, 1:37am

Alright, I’ve come back to this - I have a lot of great auto-entities cards made on my dashboard now and yet it’s the original one that is messing with me the worst. Here’s what I’ve got:

type: custom:auto-entities
show_empty: true
card_param: chips
card:
  type: custom:mushroom-chips-card
  alignment: justify
filter:
  include:
    - domain: scene
      area: Living Room
      options:
        type: entity
        content_info: name
        tap_action:
          action: toggle
  exclude: []
sort:
  method: friendly_name

This is nice, except that it causes the scene to toggle on instantly. This is kind of abrupt when I’m wanting to set the scene when we have guests.

Here’s the data from the chips card if I want to have it call the action to turn on a scene:

type: custom:mushroom-chips-card
chips:
  - type: entity
    entity: scene.SCENENAME
    icon_color: accent
    tap_action:
      action: perform-action
      perform_action: scene.turn_on
      target:
        entity_id: scene.SCENENAME
      data:
        transition: 5

I’ve tried just copying and pasting the tap-action into the options field in Auto Entities but it does not want to pick a specific entity to target. I’m not even messing with the transition value until I can get the auto entities - chips interaction to work. The syntax I used to try to accomplish that is

tap_action:
  action: perform-action
  perform_action: scene.turn_on
  target:
    entity_id: []

What am I missing?

Ildar_Gabdullin · October 11, 2024, 1:49am

Not using any mushrooms. Try this way:

type: custom:auto-entities
card:
  type: entities
filter:
  include:
    - domain: switch
      options:
        type: simple-entity
        tap_action:
          action: perform-action
          perform_action: switch.toggle
          target:
            entity_id: this.entity_id

Mariusthvdb · October 11, 2024, 7:44am

I am simply listing the scenes with their picture, like this (decluttering card template):

    - type: custom:auto-entities
      card:
        type: grid
        columns: 8
      card_param: cards
      filter:
        include:
          - domain: scene
            area: '[[area_id]]'
            options:
              type: custom:button-card
              template: button_scene

resulting in:

or with a simple listing:

      - type: custom:auto-entities
        card:
          type: entities
          title: Nu scening
          card_mod:
            class: class-header-margin
        show_empty: false
        filter:
          include:
            - attributes:
                dynamics: dynamic_palette

resulting in

and nothing gets initiated automatically

what happens if you just leave out the action?

fusterclucker · October 11, 2024, 2:07pm

Edited the original post - realized I had the bad syntax in instead of the working one on the original example

@Ildar_Gabdullin why no mushroom cards? I have been using these cards since day 1 - I like the look and the ease of configuration.

@Mariusthvdb The lack of action on each button gets me a nice list on the dashboard with no way to easily apply them from the dashboard. Using

action: 
  action: toggle

Works, but it applies the scene with zero fade. There is no option with the toggle to have a transition - I tried.

Ildar_Gabdullin · October 11, 2024, 2:27pm

Do not like round design, do not like seeing lot of space wasted.
I already proposed you a way of defining a target, did it work in your card?

fusterclucker · October 11, 2024, 2:36pm

I get the mushroom cards aren’t for everyone. As far as your example, that’s essentially the same as I have, which works by instantly applying the scene. My goal is to have a transition period.

Mariusthvdb · October 11, 2024, 3:08pm

How odd… if I click these scene pictures, they’re applied directly.
Maybe it is the mushroom specifics toying with you here… I try to avoid Mushroom though, so cant really help you there

you are aware of Scenes - Home Assistant ?
meaning, you cant click on the scene itself to have it have a transition, you need to add that to the action data

nevermind me, you had that in your example above… sorry

fusterclucker · October 15, 2024, 2:17am

Found my answer in the auto entities docs. Here is the working YAML to put in options:

type: entity
content_info: name
tap_action:
  action: call-service
  service: scene.turn_on
  target:
    entity_id: this.entity_id
  data:
    transition: 5

rothman · October 26, 2024, 8:25am

Hi,
I’m trying to exclude lights that are in a group, why does not this work?

type: custom:auto-entities
show_empty: false
card:
  show_name: true
  show_icon: true
  show_state: false
  type: entities
  title: All lights that are on
  state_color: false
filter:
  include:
    - domain: light
      state: "on"
      options:
        tap_action:
          action: toggle
  exclude:
    - domain: group
sort:
  method: name

The group “Hobbyrum” should not be in the list… right?

reste_narquois · October 26, 2024, 1:02pm

How did you create the light group? Old style via YAML? Or new style via the Helper GUi?

If you did it via the GUI, it will likely be part of the light domain and not excluded by your filter. The entity_id will confirm it either way.

Mariusthvdb · October 26, 2024, 2:39pm

please search this thread, there is a rather large section about the exact same issue you are trying to solve now

rothman · October 27, 2024, 11:12am

yes, via gui… .I will check further in this thread, thanks

loocd · October 27, 2024, 7:50pm

If you use the current groups you can set in the UI, then these are still a light.something entity → they are under the light domain, not the group domain (then it would be group.something). I believe group is an integration. Try it with

exclude:
  - integration: group

If that fails, have a look at this

🔹 Auto-entities - Automatically fill cards with entities - #1489 by loocd

I have a somewhat more complicated setup where I want to hide both groups as well as their members and display those separately. I’ve managed to get this done with the help of @Christian-1982 and @Mariusthvdb.

I’ve made some adjustments to perfect this, so let me know if this is what you need. But I’m fairly sure that you just need to fix your exclude statement.

koburg · October 30, 2024, 3:34pm

hi all how would you include this:

light.lamp01

min_color_temp_kelvin: 2000
max_color_temp_kelvin: 6666
min_mireds: 150
max_mireds: 500
effect_list:
  - blink
  - breathe
  - okay
  - channel_change
  - candle
  - fireplace
  - colorloop
  - finish_effect
  - stop_effect
  - stop_hue_effect
supported_color_modes:
  - color_temp
  - xy
effect: null
color_mode: null
brightness: null
color_temp_kelvin: null
color_temp: null
hs_color: null
rgb_color: null
xy_color: null
color:
  h: 25
  hue: 25
  s: 45
  saturation: 45
  x: 0.382
  "y": 0.354
color_temp_startup: 370
linkquality: 51
power_on_behavior: null
update:
  installed_version: 16786434
  latest_version: 16786692
  progress: 5.82
  remaining: 17153
  state: updating
update_available: false
friendly_name: Lys Econic 2
supported_features: 44

i want to display the progress in % I can make a template sensor like this

{{ state_attr('binary_sensor.loftlampe02_update_available' , 'update').progress }}

then I get the progress but not sure how to do this in auto entities if possible?

i have tried like bellow but not there yet

filter:
  include:
    - domain: light
      attributes:
        update.progress: < 100

anybody knows ?