Fold away and hide rows in lovelace entities cards.
Install using HACS or see this guide.
Add this to an entities card:
type: entities
entities:
- light.bed_light
- type: custom:fold-entity-row
head: light.bed_light
entities:
- light.bed_light
- light.ceiling_lights
- light.kitchen_lights
This will show the row specified in head:
with an arrow next to it. When clicked, the rows specified in entities:
will be revealed.
NOTE: You wouldn't believe how many people miss the first line in this section.
Add this TO AN ENTITIES CARD.
This is NOT meant to be used except in an entities card. Any usage outside an entities card is entirely unsupported, and I won't help you fix it.
head:
and any row in entities:
can be customized in exactly the same ways as ordinary entities card rows.type: entities
entities:
- type: custom:fold-entity-row
head:
type: section
label: Customizations
entities:
- light.bed_light
- entity: light.ceiling_lights
name: A light
- light.kitchen_lights
NOTE: I'm sorry, dear reader, for insulting your intelligence and including the two lines:
type: entities entities:
in every example, even though it is implied and the fact that fold-entity-row shall only ever be used in an entities card has been thoroughly beaten to death at this point.
I really, really wish I didn't have to...
Another example of customizing the head entity:
type: entities
entities:
- light.bed_light
- entity: light.bed_light
icon: mdi:lamp
- type: custom:fold-entity-row
head:
entity: light.bed_light
icon: mdi:lamp
entities:
- light.ceiling_lights
- light.kitchen_lights
NOTE: On a regretably similar note as above; if it's not entirely obvious to you why the configuration of
head:
looks this way, please do both of us a favor and go back to read the documentation of the entities card again. \ Then play around with just the entities card for a while, get to know it, try things out, experiment. Then come back to fold-entity-rows in a week or two.That also applies if you've never seen
type: section
before and think that's something I just made up. \ I will not answer any more questions about its use. It's a Home Assistant feature, not a fold-entity-row one.
group_config:
will be applied to all rows in the fold.type: entities
entities:
- type: custom:fold-entity-row
head:
type: section
label: group_config
group_config:
secondary_info: last-changed
icon: mdi:desk-lamp
entities:
- light.bed_light
- light.ceiling_lights
- light.kitchen_lights
padding:
parameter (value in pixels).type: entities
entities:
- type: entities
entities:
- type: custom:fold-entity-row
head:
type: section
label: padding
padding: 5
entities:
- light.bed_light
- light.ceiling_lights
- light.kitchen_lights
head:
to a group (including light group or cover group ) will populate the entities list with the entities of that group.type: entities
entities:
- type: custom:fold-entity-row
head: group.all_lights
open:
to true will make the fold open by default.type: entities
entities:
- type: custom:fold-entity-row
head:
type: section
label: open
open: true
entities:
- light.bed_light
- light.ceiling_lights
- light.kitchen_lights
tap_action:
action: fire-dom-event
fold_row: true
clickable: true
or clickable: false
. \
This should only be used in exceptions, though. If your row supports tap_action
use fire-dom-event
instead.type: entities
entities:
- type: custom:fold-entity-row
head:
type: section
label: Nested
entities:
- type: custom:fold-entity-row
head: light.bed_light
entities:
- type: custom:fold-entity-row
head: light.bed_light
entities:
- light.bed_light
entities:
parameter, such as entity-filter or auto-entitiestype: entities
entities:
- type: custom:auto-entities
filter:
include:
- domain: sensor
card:
type: custom:fold-entity-row
head:
type: section
label: Automatically populated
entity
(not entities
) is set and is a group, it will be expandedtype: custom:auto-entities
card:
type: entities
title: All groups
filter:
include:
- domain: group
options:
type: custom:fold-entity-row
All my test cases are available in the test/views
directory.
You can a demo in docker by going to the test
directory and running:
docker-compose up
Then going to http://localhost:8125
and logging in with username dev
and password dev
.
Or you could use the vscode devcontainer and run the task "Run hass
".
This is a limitation in Home Assistant. The header toggle will look at each entry in the entities
card, and if it has an entity
option, it will toggle that. Nothing more.
Because that's how the Home Assistant Section Entities Row looks.
I'm just So Bloody Tired of this - that's why.
NOT EVERYTHING IN LOVELACE IS A CARD!
No
Please leave