benct / lovelace-multiple-entity-row

Show multiple entity states and attributes on entity rows in Home Assistant's Lovelace UI

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Using "default" option: a header is only shown when "name" is defined explicitly (+styling lost)

ildar170975 opened this issue · comments

Consider this code:

type: entities:
entities:
      - type: custom:multiple-entity-row
        entity: sun.sun
        name: 'hide_unavailable: false'
        entities:
          - entity: sensor.testing_availability
        show_state: false

      - type: custom:multiple-entity-row
        entity: sun.sun
        name: 'hide_unavailable: true'
        entities:
          - entity: sensor.testing_availability
            hide_unavailable: true
        show_state: false

      - type: custom:multiple-entity-row
        entity: sun.sun
        name: 'hide_unavailable: true'
        entities:
          - entity: sensor.testing_availability
            hide_unavailable: true
            default: xxx
        show_state: false

      - type: custom:multiple-entity-row
        entity: sun.sun
        name: 'hide_unavailable: true'
        entities:
          - entity: sensor.testing_availability
            hide_unavailable: true
            default: xxx
            name: some_name
        show_state: false

where sensor.testing_availability is a sensor which may become unavailable.
Here the results:

image

image

If the entity is hidden AND default is set -> then:

  1. If name is NOT defined explicitly:
    -header is NOT shown
    -styling IS lost.
  2. If name is defined explicitly:
    -header is shown
    -styling is not lost.

IMHO:

  1. A header must be displayed if default value is displayed (unless it is explicitly hidden by name: false).
  2. Styling should be persistent.