🔹 fold-entity-row - Hide away stuff in entities cards

yes

 

1 Like

Ok cool. I use this one a LOT it is so damn useful! Thanks again.

It is now.

Thank you !

is it possible to hide the state of a group entry? I would like to hide the “unbekannt” state of a the group

image

- type: custom:fold-entity-row
  head: group.battery_status_xiaomi

@thomasloven Is it possible to put a markdown card in a fold-entity-row?

Thanks

If you’re careful, you can put anything in anything: https://github.com/thomasloven/hass-config/wiki/Misc-tricks#cardelemententity-row-triality

2 Likes

Thanks!!! @thomasloven

@thomasloven great work!
I have reordered all lights at home using the fold-entity-row and looks great
However what I am not being able to do is to show the group light icon in yellow when it is turned on (as each individual entity do).

Is there a way I can achieve this ?

Also it would be great if I can use a the custom button-card for the top level group instead of a toggle button

Thanks
Claudio.

Just set the head type to whatever you want.

must be missing the obvious, … , but I cant get an auto-entities card to show under the fold-entity-row.

this is what I have now:

  - type: entities
    title: Telefoon Mobile app
    show_header_toggle: false
    entities:
      - device_tracker.telefoon
      - sensor.telefoon_battery_level
      - type: custom:fold-entity-row
        head:
          type: section
          label: Details
        entities:
          - sensor.telefoon_activity
          - sensor.telefoon_average_active_pace
          - sensor.telefoon_battery_level
          - sensor.telefoon_battery_state
          - sensor.telefoon_bssid
          - sensor.telefoon_connection_type
          - sensor.telefoon_distance
          - sensor.telefoon_floors_ascended
          - sensor.telefoon_floors_descended
          - sensor.telefoon_geocoded_location
          - sensor.telefoon_last_update_trigger
          - sensor.telefoon_sim_1
          - sensor.telefoon_ssid
          - sensor.telefoon_steps

showing as:

29


and also this works as standalone card:

  - type: custom:auto-entities
    card:
      type: entities
    filter:
      include:
        - entity_id: "sensor.telefoon_*"

but if I try to put the auto-entities under the fold like this:

  - type: entities
    title: Telefoon Mobile app
    show_header_toggle: false
    entities:
      - device_tracker.telefoon
      - sensor.telefoon_battery_level
      - type: custom:fold-entity-row
        head:
          type: section
          label: Details
        entities:
          - type: custom:auto-entities
            card:
              type: entities
            filter:
              include:
                - entity_id: "sensor.telefoon_*"

I do see the fold, but its not populated.

checking the example on https://github.com/thomasloven/lovelace-fold-entity-row which says:

type: custom:auto-entities
filter:
  include:
    - domain: sensor
card:
  type: custom:fold-entity-row
  head:
    type: section
    label: Automatically populated

makes my head spin… I dont see it, please help?

thanks

unless… this would do it?

  - type: entities
    title: Telefoon Mobile app auto
    show_header_toggle: false
    entities:
      - device_tracker.telefoon
      - sensor.telefoon_battery_level
      - type: custom:auto-entities
        filter:
          include:
            - entity_id: "sensor.telefoon_*"
        card:
          type: custom:fold-entity-row
          head:
            type: section
            label: Details

update
yes it does… sorry for the post, was just very confused by the order of the config which seems upside down.

Auto-entities fills the entities: list of the card contained inside it.

Generally in lovelace any card can affect cards inside it (i.e. further to the right in the indentation), but not the other way around. So you’ll just need to think about what should do what to what?

yes, Thomas, I see now how this works, and does so beautifully! thank you very much indeed!

Let me ask to go 1 step further…

I have many devices with the mobile_app, and they all create sensors and a device_tracker with the entity_id.

Would there be a way to have the config I posted above created automatically for these devices? Would compress the amount of yaml even further :wink:

  - type: entities
    title: {{device_id}} Mobile app
    show_header_toggle: false
    entities:
      - device_tracker.{{device_id}}
      - sensor.{{device_id}}_battery_level
      - type: custom:auto-entities
        filter:
          include:
            - entity_id: "sensor.{{device_id}}_*"
        card:
          type: custom:fold-entity-row
          head:
            type: section
            label: Details
1 Like

I think that could be done with lovelace_gen or maybe the decluttering card.

yes, of course! had only used that for buttons until now…
decluttering template

card:
  type: entities
  title: '[[id]] Mobile app'
  show_header_toggle: false
  entities:
    - 'device_tracker.[[id]]'
    - 'sensor.[[id]]_battery_level'
    - type: custom:auto-entities
      filter:
        include:
          - entity_id: 'sensor.[[id]]_*'
      card:
        type: custom:fold-entity-row
        head:
          type: section
          label: Details

does the trick, (only need to find a way to capitalize the title field)

update

posted the question in the relevant thread for decluttering card: Lovelace: Decluttering Card - #107 by Mariusthvdb

There might a way, since lovelace_gen allows for Jinja 2 templating.
According to this, using :

{{ 'my First cAR'|capitalize }}

will output

My first car

I haven’t tested it yet, but I’m looking for something similar. i’ll have a look at it in the next few days.

Edit: It works

    - !include
      - ../../templates/button_chore.yaml
      - chore: chores_livingroom_clean_floor
        name: {{ 'Nettoyer Le Sol'|capitalize }}

Gives me
image

you’re suggesting this would work for my decluttering template also? All I can see is the actual code with the {{ }} braces…

Not sure about decluttering template … However you can achieve a similar result with lovelace_gen only, this I’m pretty sure of. Use an include statement with id as parameter and it should work as intended.

ok thanks.
Don’t use lovelace_gen though, thought that to be the auto ui-lovelace.yaml generator? I use yaml mode for lovelace so need to write it myself :wink:

not to clutter this thread any further, I’ll take this to the decluttering card thread