šŸ”¹ Auto-entities - Automatically fill cards with entities

Yes, using layout-card. Thereā€™s an example near the bottom of the readme here: https://github.com/thomasloven/lovelace-layout-card

2 Likes

That feels like a bit too much work, and a new configuration method - with associated documentation and confusement - for a minimal simplification of something thatĀ“s already very easy.

attributes:
  next_pickup_in_days: *

Just want to say that this worked brilliantly, thanks!

completely missed that option, working nicely indeed, thank you very much!

hmmm, I think I saw the sensors appear, but now only see an empty cardā€¦must have ben a cache thing, still loading my previous config.

also, using the single * without quotes results in an error:

while scanning an alias in "/config/lovelace/views/view_Tijd_agenda.yaml", line 34, column 34 expected alphabetic or numeric character, but found '\n' in "/config/lovelace/views/view_Tijd_agenda.yaml", line 34, column 35

using

  - type: 'custom:auto-entities'
    card:
      type: glance
    filter:
      include:
        - domain: sensor
          attributes:
            next_pickup_in_days: *

managed to take out the domain: sensor, but canā€™t use the *, and need to set

  - type: 'custom:auto-entities'
    card:
      type: glance
    filter:
      include:
        - attributes:
            next_pickup_in_days: '! none'

And with quotes?


  - type: 'custom:auto-entities'
    card:
      type: glance
      title: "'! none'"
    filter:
      include:
        - attributes:
            next_pickup_in_days: '! none'
    sort:
      attribute: next_pickup_in_days
      method: attribute
      numeric: true

  - type: divider

  - type: 'custom:auto-entities'
    card:
      type: glance
      title: "'*'"
    filter:
      include:
        - attributes:
            next_pickup_in_days: '*'
    sort:
      attribute: next_pickup_in_days
      method: attribute
      numeric: true

results in:

no error in the log or inspector

Hi all

Iā€™m having issue moving from monster-card to auto-entities

This is the one not working

#          - type: custom:monster-card
          - type: 'custom:auto-entities'
            card:
              type: entities
              show_header_toggle: false
            show_empty: false
            filter:
              include:
                - entity_id: 'sensor.illumination_1234567890'
                  icon: mdi:weather-sunny
                  options:
                    secondary_info: last-changed
                - entity_id: 'sensor.teclast_battery'
                  icon: mdi:battery-50
                  options:
                    secondary_info: last-changed
                - entity_id: 'sensor.lumi_plug'
                  icon: mdi:speedometer
                  options:
                    secondary_info: last-changed
                - entity_id: 'input_boolean.announce_shellies'
                  icon: mdi:alarm-light
                  options:
                    secondary_info: last-changed
                - entity_id: 'sensor.temp_shelly_2_5_finestra_sala'
                  icon: mdi:thermometer
                  options:
                    secondary_info: last-changed

When I use auto-entities I donā€™t see this card, while using the monster-card all works.
Iā€™ve tried the auto-entities with and without single quotes.

Other auto-entities card I have moved from monster-card work fines

Any suggestion?

Thanks

use a core entities cardā€¦ You donā€™t seem to use any of the special features auto-entities card offers?

if you only want to show these 5 entities, thereā€™s no need for the auto-entities card.

It could also be that icon: is not a valid filter.

Yes, itā€™s true, but probably I was using some special features before and now I changed to ā€œnormalā€ core entities card. I will try this way.

Yes, that did the trick, thanks!
Removing the icon: now itā€™s working.

Hi, thanks for all you awesome cards!

I am using your card to add entities through wildcards, but I want to rename one. For now I would like to avoid adapting the ā€œfriendly nameā€.
Using options: I indeed can change the name when adding it through entities: but due the wildcards I get duplicates which I cant avoid with unique: ??

Hi guys,

I am trying to list all my devices battery levels. Adding this:

  include:
    - entity_id: '*battery*'

Shows only battery entities, but I also have some ā€œbattery_levelā€ states for my sensors and binary_sensors - e.g. :
binary_sensor.living_room_motion - battery_level: 49
sensor.bedroom_temperature - battery_level: 49

Is there a way to combine all these into a single card using auto-entities?

Rather than states you mean attributes I think (or state attributes). But Iā€™m afradi I donā€™t know how to do it. I did it with two cards in the end.

You can add another filter to include to get the entities with a battery attribute, but youā€™d need some other kind of entity row to display them:

include:
  - entity_id: '*battery*'
  - attributes:
      battery: "*"
    options:
      type: custom:some-battery-attribute-showing-entity-row

Got similar situation. Thanks for pointing that thread.
In auto entities wiki numerical comparison it states:

 filter:
   include:
     - attributes:
       battery: "<= 50" # Attribute battery_level is 50 or less

While in reality this one throws ā€œCannot convert undefined or null to objectā€ for me :confused:
Anyway got sorted out by post referenced by Ralf

        filter:
          include:
#            - attributes:
#              battery: "<= 95" # Attribute battery_level is 50 or less
            - entity_id: sensor.*.battery_level*
              state: <= 95

Other topic:can I filter badges by this miracle?

EDIT: After one slight adjustment I donā€™t get error, but it does not return any result:

     - attributes:
         battery: "<= 50" # Attribute battery_level is 50 or less

Is it possible to use card-mod styling inside of the auto-entities card?

should be possible, you can add styles to the card. You can even have it filled custom cards automatically with the use of layout-card.

Btw, @thomasloven, we can use group and domain as a filter (for use with layout-card) however we can, not have a list of entities. If an entity is defined we need to define separate options for each entity. Would it be possible to support a list (preferable comma separated) within the filters? That would be really awesome if that would be possible.

e.g.

      - type: custom:auto-entities
        filter:
          include:
            - entity_id: switch.device_1, switch.device_2, light.light_1, media_player.living
              options:
                type: custom:button-card
                entity: this.entity_id
        sort:
          method: name
          numeric: true
        card:
          type: custom:layout-card
          min_columns: 1
          max_columns: 1
          justify_content: start
          layout: vertical
2 Likes

I just tried to add styling to a type: section and it didnā€™t work

Not sure if itā€™s what you asked for but if so here is what I use and works for me for styling entities:

type: 'custom:auto-entities'
show_empty: false
filter:
  include:
    - attributes:
        battery_level: "=0"
      entity_id: "binary_sensor.visonic*"
      options:
        icon: 'mdi:battery-10'
        style: |
          ha-card {
            margin:0px 0px 0px 0px !important;
            border: none !important;
            border-shadow: none !important;
          }                
          state-badge {
            margin: -5px 0px 0px 0px !important;
          } 

Good idea. Iā€™ll see to adding that.

1 Like