🔹 Auto-entities - Automatically fill cards with entities

[Ildar_Gabdullin]

You wrote “it looks bad” but has not specified what is exactly “bad”, the “good looking picture” is not provided too. Not to mention absence of MWE.

[idominiki]

On the desktop it looks like this:

I have this custom:grid-layout configured:

- type: custom:grid-layout
    title: _living_room
    path: 1
    square: false
    layout:
      #default
      grid-gap: 1px 1px
      grid-template-columns: repeat(4, 1fr)
      grid-template-rows: auto
      grid-template-areas: |
        "  chips  chips  chips  chips  "
        "  t1     t1     t1     t1     "
        "  l1     l1     l1     l1     "
        "  t2     t2     t2     t2     "
        "  k2     k2     k2     k2     "
        "  t3     t3     t3     t3     "
        "  m1     m2     m3     .      "
        "  m4     m5     .      .      "
        "  t4     t4     t4     t4     "
        "  dw1    dw1    dw1    dw1    "
        "  t5     t5     t5     t5     "
        "  b1     b1     b1     b1     "
      mediaquery:
        #phone
        "(max-width: 800px)":
          grid-gap: 1px 1px
          grid-template-columns: repeat(2, 1fr)
          grid-template-areas: |
            "  chips  chips  "
            "  t1     t1     "
            "  l1     l1     "
            "  t2     t2     "
            "  k2     k2     "
            "  t3     t3     "
            "  m1     m2     "
            "  m3     .      "
            "  m4     m5     "
            "  t4     t4     "
            "  dw1    dw1    "
            "  t5     t5     "
            "  b1     b1     "
        #portrait
        "(max-width: 1200px)":
          grid-gap: 1px 1px
          grid-template-columns: repeat(3, 1fr)
          grid-template-areas: |
            "  chips  chips  chips  "
            "  t1     t1     t1     "
            "  l1     l2     l3     "
            "  t2     t2     t2     "
            "  k2     k2     k2     "
            "  t3     t3     t3     "
            "  m1     m2     m3     "
            "  m4     m5     .      "
            "  t4     t4     t4     "
            "  dw1    dw1    dw1    "
            "  t5     t5     t5     "
            "  b1     b1     b1     "

And this is the displayed section of the lights:

- type: custom:auto-entities
        card:
          type: grid
          #columns: 4
          column_width: 50%
          square: false
        card_param: cards
        filter:
          include:
            - domain: light
              area: wohnzimmer
              options:
                type: custom:button-card
                template: card_light
                variables:
                  ulm_card_light_enable_color: true
                  ulm_card_light_enable_slider: true
                  ulm_card_light_enable_collapse: true
                  ulm_card_light_force_background_color: true
                  ulm_card_light_enable_popup: true
        view_layout:
          grid-area: l1

On mobile it should look like this (2 columns) and on Tablet in three columns:

[Ildar_Gabdullin]

So, this is a not an auto-entities issue, this is about layout-card.

[sparkydave (🇦🇺 Dave)]

@thomasloven

That’s what template sensors are for.

Sorry to bring up a very old comment but I would like to do what ha_popbox was wanting to achieve however I can’t simply use template sensors as the entity_id’s are dynamic. (once a parcel has been delivered I remove it from SeventeenTrack, likewise any new parcel is added as has a new entity_id)

I use the SeventeenTrack integration to track parcels and this creates an entity for each parcel and as such the entity_id has the parcel description in it, which obviously changes with each parcel I tell it to track.

I currently use auto-entities to generate a card showing the incoming parcels by way of using wildcards and this shows the parcels, but as ha_popbox said, it gives the state, not an attribute. I’d like to show a particular attribute of each entity.

Current code

title: Parcel Tracking
type: custom:stack-in-card
cards:
  - type: custom:auto-entities
    card:
      type: entities
    filter:
      include:
        - entity_id: sensor.seventeen*
          state: In Transit
      exclude: []
  - type: custom:auto-entities
    card:
      type: entities
    filter:
      include:
        - entity_id: sensor.seventeen*
          state: Not Found
      exclude: []
  - type: custom:auto-entities
    card:
      type: entities
    filter:
      include:
        - entity_id: sensor.seventeen*
          state: Delivered
      exclude: []

Card view:

Entity:

I’d like it to show the attribute called ‘into_text’ rather than the state.

Is this possible? I see that the standard HA entities card allows for showing an attribute but I’m not sure if / how I can use auto-entities to generate the list of entities for that card.

Is there a way to mix this card with custom:entity-attributes-card ?

[Ildar_Gabdullin]

@sparkydave

I’d like it to show the attribute called ‘into_text’ rather than the state.

        - entity_id: sensor.seventeen*
          state: Not Found
          options:
            type: attribute
            attribute: xxxx

@sparkydave

Is there a way to mix this card with custom:entity-attributes-card ?

In case of many parcels it is better to combine auto-entities with flex-table-card - then you may display even more attributes in a compact way.

[sparkydave (🇦🇺 Dave)]

Is that options: code supposed to be in the auto-entities card like this below?

title: Parcel Tracking
type: custom:stack-in-card
cards:
  - type: custom:auto-entities
    card:
      type: entities
    filter:
      include:
        - entity_id: sensor.seventeen*
          state: In Transit
      exclude: []
    options:
      type: attribute
      attribute: info_text
  - type: custom:auto-entities
    card:
      type: entities
    filter:
      include:
        - entity_id: sensor.seventeen*
          state: Not Found
      exclude: []
    options:
      type: attribute
      attribute: info_text
  - type: custom:auto-entities
    card:
      type: entities
    filter:
      include:
        - entity_id: sensor.seventeen*
          state: Delivered
      exclude: []
    options:
      type: attribute
      attribute: info_text

…because that didn’t change the look of the card at all, still just seeing it list the ‘states’.

@Ildar_Gabdullin

flex-table-card

Thanks, I’ll look into this card.

[Ildar_Gabdullin]

@sparkydave

code supposed to be in the auto-entities card like this below?

No, check this.
Each filter may have its own set of options.

[sparkydave (🇦🇺 Dave)]

Thanks. I fixed it up so it’s now:

code

title: Parcel Tracking
type: custom:stack-in-card
cards:
  - type: custom:auto-entities
    card:
      type: entities
    filter:
      include:
        - entity_id: sensor.seventeen*
          state: In Transit
          options:
            type: attribute
            attribute: info_text
      exclude: []
  - type: custom:auto-entities
    card:
      type: entities
    filter:
      include:
        - entity_id: sensor.seventeen*
          state: Not Found
          options:
            type: attribute
            attribute: info_text
      exclude: []
  - type: custom:auto-entities
    card:
      type: entities
    filter:
      include:
        - entity_id: sensor.seventeen*
          state: Delivered
          options:
            type: attribute
            attribute: info_text
      exclude: []

…which works, however due to the length of the entity_id it gets cut off when the card displays it. Is there a way to remove part of the entity_id or even replace it with the text from another attribute?

Ideally I’d like to remove ‘seventeentrack package’ from what is displayed so it only shows the description, then the info_text from the attribute.

[Ildar_Gabdullin]

If an entity has a friendly_name - it will be displayed instead.
Or you may want to display a custom name like “Parcel from Tokyo” composed from attributes / entity_id - this may be achieved by using a “template” option, look for examples in the thread.

[sparkydave (🇦🇺 Dave)]

Yeah sorry, it is actually a very long friendly name.

[Ildar_Gabdullin]

Then extract a significant part from the name and show it instead.

Or you may reconsider a design:
– long name - as a “name”
– state (which seems to be long too) - as a “secondary_info”
– last_changed - as a state
inside a template-entity-row

[woempiej]

Hi,

Is there a way to use images insteat of icons in de auto-enitities card?

Now have this (Auto-Entities)

My wish:

[fanaticDavid (David)]

There is but it’s completely unrelated to the auto-entities card. You can set the images above as an entity_picture for each of the entities. Look here for more info.

[Ildar_Gabdullin]

This code shows a list of persons:

type: custom:auto-entities
card:
  type: entities
filter:
  include:
    - domain: person

Assume that each “person” entity has an “entity_picture” attribute specified (via “customize”) - then an image will be displayed for this row instead of an icon.
Otherwise - an icon is specified (at least for persons w/o present “entity_picture”).

You may change it like:

type: custom:auto-entities
card:
  type: entities
filter:
  include:
    - domain: person
      options:
        icon: mdi:car

then a “mdi:car” icon is displayed for each row.

This code overrides an image for every row to some fixed one:

type: custom:auto-entities
card:
  type: entities
filter:
  include:
    - domain: person
      options:
        image: /local/images/devices/ups_sua1500i.png

then the same “UPS” image is displayed for each row.

This code overrides an image for every row to some individual one:

type: custom:auto-entities
card:
  type: entities
filter:
  template: >-
    {% for ENTITY in ..... -%}
      {{
        {
          'entity': ENTITY,
          'image': .....
        }
      }},
    {%- endfor %}

This code disables showing available images:

type: custom:auto-entities
card:
  type: entities
filter:
  include:
    - domain: person
      options:
        image: null

then a default “mdi:account” is displayed for every row.

If some entity must be displayed in many places with an image and there is only one place where I want to show an icon:
– then I specify an “entity_picture”,
– and this picture is displayed everywhere (including any card with “auto-entities”),
– and for one place (some card) I need to specify something like “image: null” (as shown above) to disable the image.

If some entity must be displayed in many places with an icon and there is only one place where I want to show an image:
– then I do not specify an “entity_picture”,
– and an icon is displayed everywhere (including any card with “auto-entities”),
– and for one place (some card) I need to specify something like “image: xxxxxxxxxx” to show the image.

[woempiej]

Thank you, learned something!

[woempiej]

Triple thankyou That works!
I was playing around because you metioned the “option” on github but I think I made a mistake with the placement of the lines.

[DrSpaldo (Doctor Spalding)]

I’m not exactly sure when it stopped working, so apologies if I have missed something in the last few releases… I have just noticed that two of my sensors are no longer appearing in my auto entities list. They were both limited to be equal to or less than 7 days, so only the next upcoming bin collection was displayed. Ie. Green or Recycling. Here is the code:

          filter:
            include:
            - entity_id: sensor.anniversary*
            - entity_id: sensor.recycling
              attributes:
                days: "<= 7"
            - entity_id: sensor.green
              attributes:
                days: "<= 7"
          sort:
            method: state
            numeric: true
            count: 6

Anyone have an idea what would have stopped it from working and what I can change to get it back?

[Ildar_Gabdullin]

@DrSpaldo

            - entity_id: sensor.recycling
              attributes:
                days: "<= 7"
            - entity_id: sensor.green
              attributes:
                days: "<= 7"

A similar code works, check your sensors.

[DrSpaldo (Doctor Spalding)]

Thanks for the reply @Ildar_Gabdullin. It must be the way the sensor is reporting what the value is. I must have to change the word “days” instead, just have to work out what to!

[Ildar_Gabdullin]

I do not see the “days” attribute here.
There is a state only (probably including UoM).
If the state contains a UoM - then you cannot do math operations (I suspect), then you will have to use a templated filter here (“template” option).