🔹 Auto-entities - Automatically fill cards with entities

[Ildar_Gabdullin]

@cloudbr34k

to show the Device names per area? not entities by the actual device name? I

There is no card for displaying a device.
You may only list devices in markdown (w/o auto-entities).
Kind of this (could be optimized for sure):

{% for AREA_ID in areas() -%}
  {%- if area_devices(AREA_ID) |count > 0 -%}
    Area: {{area_name(AREA_ID)}}
    {% for DEVICE_ID in area_devices(AREA_ID) -%}
      {{device_attr(DEVICE_ID,'name')}}
    {% endfor %}
  {% endif -%}
{%- endfor %}

[cloudbr34k (Apples)]

yeah ok i got that already, just checking, thanks for the reply

[fusterclucker (Jeff)]

That did not work, but good news! ScottG on the discord helped me work through the options to get a working version! For all those struggling to get Auto Entities to work with Mushroom Chips, here is a working code block:

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

Here were my mistakes, in order:

1. Options are your friend for the auto entities card. For scenes to work, the chips must be of the entity variety, and I really recommend having the name
2. You really want to use the tap_action: action: toggle blurb. This has to be separate lines! ScottG pointed out I was trying to make tap_action: toggle work when in the chips card it is passed as an object, not as a string (therefor the action part must be indented on the line below)

I hope this helps, and if it does, you should buy Scott a coffee:

[Mariusthvdb (Marius)]

@fusterclucker

That did not work,

cant be.
the config I posted works fine.
ofc all choices you can make have an effect, so yes, using the content_info: name adds the name in stead of the state.
setting a tap action other than default makes a difference.

as long as you use the magic card_param to populate the correct parameter in the auto-entities config, and set a few options of your choice, you should be good. as I suggested here

@Mariusthvdb

you should add the options: field with the type

[d13g0m0nt3s]

Hi , I need help with auto entities and the Maxi media player card. I do not if it’s posible but I would like to show the correctly playing media player. With mini media player I have no problem. I made a group of media players and with auto entities I show the currently player one but I,m not able to do it with the Maxy media player card.

This is the code I use for mini media player and I do no know how adapt it to Maxi media player. Any help will be appreciated.

    - type: custom:auto-entities
      card:
        type: entities
        show_header_toggle: false
      filter:
        include:
          - domain: media_player
            state: playing
            group: media_player.media_salon
            options:
              artwork: full-cover-fit
              hide:
                power: true
                icon: true
                source: true
                progress: false
                volume: true
                controls: true
                name: false
                info: false
              type: custom:mini-media-player
        exclude: []
      sort:
        method: last_changed
        count: 1
        numeric: true
        reverse: true
        show_empty: true
      else:
        type: picture
        image: /local/stand-by-tv-card.jpg
        tap_action:
          action: none
        hold_action:
          action: none

[Mariusthvdb (Marius)]

did you test it without any of the configuration options, and only set options to use the maxi-media-player card?

next step would be to add any of the config options you require it supports, not just copy and past options from another card

Maxi Media Player

Maxi Media Player Media card for Home Assistant UI with a focus on managing multiple media players! (If this looks familiar to you, it’s probably because it’s almost identical to my Sonos Card, except this one is focused on supporting all players, not just Sonos.) Features: Group/Ungroup speakers If the individual speakers support it Control multiple speakers Play favorites from list Media browser button Control individual volumes in a group Artwork background Possibility to override artwo…

[d13g0m0nt3s]

Yes I tried but show no supported players found

Sorry the code as image I’m on my phone and I cant paste clean code on iOS, all with strange characters

[Mariusthvdb (Marius)]

tbh, I dont use that card, but I have installed it quickly, and can not get it right either… seeing the same as you do, and inspector clearly shows its the mapping not getting it right.

might have to go back to the author, or check auto-entities documentation here…

btw see Maxi Media Player - #16 by Mariusthvdb, Ive asked the author in the dedicated thread to check the error being reported

and also found the reason this cant be done, as auto-entities author explained, that generates a list like

entities:
  - entity: media_player.x
  - entity: media_player.y
  - ...etc...

which cant be handled by maxi-media-player card because it wants:

entities:
  - media_player.x
  - media_player.y
  - ...etc...

see: FR add option to list entity: media_player.abc · Issue #52 · punxaphil/maxi-media-player · GitHub

[d13g0m0nt3s]

Thanks you for your help. Hope this can be fix

[Mariusthvdb (Marius)]

this works

    - type: custom:auto-entities
      card:
        type: vertical-stack
      filter:
        template: >
          [{{ dict(type='custom:maxi-media-player', entities=states.media_player | map(attribute='entity_id') | select('has_value') | list) }}]
      card_param: cards

@petro made this in a separate chat (thanks!), and we’ve not yet added other config options to that. downside of template in auto-entities is that you have to get all other options also inside that template. so, depending on how complex you want it to be, you might be up for a challenge yet

should be able to add those options to the dict

[petro]

pretty sure you can use options too, the normal way. You’d have to try it out.

[d13g0m0nt3s]

This is awesome I will try that. Thanks!

[Mariusthvdb (Marius)]

there still is something iffy about that card, because even after I deleted all configs, I still see this in inspector

[Mariusthvdb (Marius)]

@pioioTwo

help me, how to generate auto entities with conditional

works with is card

and your question is what?

please dont put large irrelevant configs here, only the auto-entities section you need help with

[Eoin]

The following template is working in Dev Tools but I cannot get it to work in auto-entries, any suggestions?

type: custom:auto-entities
filter:
  template: >-
    {{  states['binary_sensor'] 
    |selectattr('entity_id','in',label_entities('External Doors'))
    |selectattr('state','==','on') |map(attribute='entity_id') |list }} 
  options:
    type: custom:mushroom-entity-card
    layout: horizontal
    secondary_info: last-changed
card:
  type: custom:layout-card
  cards: []
  layout_type: masonry
sort:
  method: friendly_name

[Ildar_Gabdullin]

@Eoin

filter:
  template: >-
    ...
  options:

Not checked your template - but you cannot combine “template” & “options”.
All options must be defined as a part of “template”. See examples in the thread.

[petro]

You can only do that with advanced templating.

type: custom:auto-entities
filter:
  template: >-
    [{% for e in label_entities('External Doors') 
          | select('search', '^binary_sensor.') 
          | select('is_state','on') %}
      {{ 
        dict(
          entity=e,
          type='custom:mushroom-entity-card',
          layout='horizontal',
          secondary_info='last-changed'
        )
      }},
    {% endfor %}]
card_param: cards
card:
  type: custom:layout-card
  layout_type: masonry
sort:
  method: friendly_name

[Mariusthvdb (Marius)]

@petro

{% for e in states.binary_sensor 
        | map(attribute='entity_id') 
        | select('in',label_entities('External Doors'))
        | select('is_state','on') %}

why not first select label_entities and next domain binary_sensor? in my setup, that at least starts with a smaller set of entities…

[petro]

sure, I was just being lazy and correcting what they had

{% for e in label_entities('External Doors') | select('search', '^binary_sensor.') | select('is_state','on') %}

[Mariusthvdb (Marius)]

exactly those label_entities templates are really powerful!

and probably your first post (without the select) would be ok too, considering there wont be other entities than those binaries with on/off state…