I do not want the card to show the state of my covers (screens) because they don’t have any. The state is always unkown. It does need to show me the buttons to move the cover up or down. How do I do that?
type: entities
entities:
* entity: cover.opslagkamer
type: custom:multiple-entity-row
entities:
* entity: sensor.screen_sensor_opslagkamer
name: false
you can use the slider only with secondary info-entity-row
- type: custom:secondaryinfo-entity-row
entity: input_number.home_theater_lux
secondary_info: >
Mean living secondary info: {{states('sensor.mean_living_lux')}} lx
or even better with card-mod:
- type: custom:slider-entity-row
entity: input_number.home_theater_lux
secondary_info: true
card_mod:
style:
hui-generic-entity-row$: |
.secondary::after {
content: "Mean living: {{states('sensor.mean_living_lux')}} lx"
}
this is what I do:
- type: entities
title: Screen Keuken
<<: *header
entities:
- entity: cover.screen_keuken
name: Keuken
secondary_info: last-updated
- type: custom:slider-entity-row
entity: cover.screen_keuken
hide_state: false
full_row: true
however, for use with an rts motor (2 to be precise) I set it up like this:
- type: entities
title: Lamellen Garage
card_mod:
style: |
.card-header {
background-color: var(--background-color-off);
color: var(--text-color-off);
font-weight: bold;
margin: 0px 0px 8px 0px;
}
.header-footer.footer {
--mdc-icon-size: 30px;
padding-bottom: 10px;
font-weight: bold;
font-size: 20px;
color: orange;
}
entities:
- entity: cover.lamellen_garage
name: Lamellen
secondary_info: last-updated
# - entity: script.garage_lamellen_my
# name: Set Lamellen Garage
# action_name: My
- type: divider
- entity: cover.lamel_links
name: Lamel links
secondary_info: last-updated
- entity: cover.lamel_rechts
name: Lamel rechts
secondary_info: last-updated
footer:
type: buttons
entities:
- entity: script.garage_lamellen_open
icon: mdi:arrow-up
# name: Open
- entity: script.garage_lamellen_my
name: My
show_icon: false
- entity: script.garage_lamellen_close
icon: mdi:arrow-down
# name: Close
as you can see, these are Somfy screens with a pre-programmed ‘My’ position. Which I call in the script in the footer 
Could someone let me know what is wrong with the code below? I would like either (a) confirmation to toggle switch on tap or (b) deliberate hold action to toggle switch.
What currently happens below is that the hold_action does not respond at all. When I change to tap_action the switch toggles, but I receive no confirmation.
Is it even possible to have a confirmation after a hold action ?
- type: custom:multiple-entity-row
entity: group.garage_doors
show_state: false
state_color: true
secondary_info: last-changed
entities:
- entity: switch.gdora
name: Left
icon: true
state_color: true
hold_action:
action: toggle
confirmation:
text: Toggle garage door?
- entity: switch.gdock
name: Right
icon: true
state_color: true
hold_action:
action: toggle
confirmation:
text: Toggle garage door?
How to hide a header for some entity?
Usually we use "name: false" option.
Now see the difference:
type: entities
entities:
- type: custom:multiple-entity-row
entity: sun.sun
entities:
- entity: sun.sun
name: xxx
styles:
width: 100px
- entity: sun.sun
name: "\u2003"
styles:
width: 100px
name: ''
show_state: false
- type: section
- type: custom:multiple-entity-row
entity: sun.sun
entities:
- entity: sun.sun
name: xxx
styles:
width: 100px
- entity: sun.sun
name: false
styles:
width: 100px
name: ''
show_state: false
We need to use the “\u2003” special character (wide space).
P.S. You may use transparent font color & card-mod as well (a longer way).
I will share my version of the card
Animated consumption card
type: entities
title: 'Living Room: Energy Monitoring'
entities:
- entity: sensor.gostinaia_rozetka_dlia_konditsionera_current
type: custom:multiple-entity-row
name: Current strength
show_state: false
entities:
- entity: sensor.gostinaia_rozetka_dlia_konditsionera_current
name: Conditioner
styles:
width: 70px
- entity: sensor.gostinaia_rozetka_dlia_umnogo_udlinitelia_current
name: Smart filter
styles:
width: 90px
- entity: sensor.gostinaia_rozetka_dlia_nas_current
name: NAS
styles:
width: 60px
- entity: sensor.gostinaia_rozetka_dlia_konditsionera_current
type: custom:multiple-entity-row
name: Total consumption
show_state: false
entities:
- entity: sensor.gostinaia_rozetka_dlia_konditsionera_energy
name: Conditioner
styles:
width: 75px
- entity: sensor.gostinaia_rozetka_dlia_umnogo_udlinitelia_energy
name: Smart filter
styles:
width: 85px
- entity: sensor.gostinaia_rozetka_dlia_nas_energy
name: NAS
styles:
width: 60px
- entity: sensor.gostinaia_rozetka_dlia_konditsionera_current
type: custom:multiple-entity-row
name: Current consumption
show_state: false
entities:
- entity: sensor.gostinaia_rozetka_dlia_konditsionera_power
name: Conditioner
styles:
width: 75px
- entity: sensor.gostinaia_rozetka_dlia_umnogo_udlinitelia_power
name: Smart filter
styles:
width: 85px
- entity: sensor.gostinaia_rozetka_dlia_nas_power
name: NAS
styles:
width: 60px
Поделюсь своим вариантом карточки
Анимированная карта потребления
New Custom UI card to show animated power consumption
type: entities
title: 'Гостиная: Энергомониторинг'
entities:
- entity: sensor.gostinaia_rozetka_dlia_konditsionera_current
type: custom:multiple-entity-row
name: Сила тока
show_state: false
entities:
- entity: sensor.gostinaia_rozetka_dlia_konditsionera_current
name: Кондиционер
styles:
width: 70px
- entity: sensor.gostinaia_rozetka_dlia_umnogo_udlinitelia_current
name: Сетевой фильтр
styles:
width: 90px
- entity: sensor.gostinaia_rozetka_dlia_nas_current
name: NAS
styles:
width: 60px
- entity: sensor.gostinaia_rozetka_dlia_konditsionera_current
type: custom:multiple-entity-row
name: Общее потребление
show_state: false
entities:
- entity: sensor.gostinaia_rozetka_dlia_konditsionera_energy
name: Кондиционер
styles:
width: 75px
- entity: sensor.gostinaia_rozetka_dlia_umnogo_udlinitelia_energy
name: Сетевой фильтр
styles:
width: 85px
- entity: sensor.gostinaia_rozetka_dlia_nas_energy
name: NAS
styles:
width: 60px
- entity: sensor.gostinaia_rozetka_dlia_konditsionera_current
type: custom:multiple-entity-row
name: Текущее потребление
show_state: false
entities:
- entity: sensor.gostinaia_rozetka_dlia_konditsionera_power
name: Кондиционер
styles:
width: 75px
- entity: sensor.gostinaia_rozetka_dlia_umnogo_udlinitelia_power
name: Сетевой фильтр
styles:
width: 85px
- entity: sensor.gostinaia_rozetka_dlia_nas_power
name: NAS
styles:
width: 60px
I will share another option for combining two user integrations, and then there are few examples and it is difficult to assemble such panels, so I would like to have more ready-made options
To create such a panel in Lovelace, we will need two integrations
Configuration lovelace
type: entities
entities:
- type: custom:fold-entity-row
head:
entity: sensor.ups_cyberpower_livingroom
name: ИБП
type: custom:multiple-entity-row
secondary_info:
attribute: Уровень заряда
name: Батарея
unit: '%'
state_header: Статус
entities:
- entity: group.livingroom_ups
name: Сенсоры
icon: mdi:information-outline
- entity: sensor.ups_load
name: Нагрузка
- entity: sensor.ups_load_watts
name: Нагрузка
entities:
- entity: switch.ups_beeper
secondary_info: last-changed
icon: mdi:volume-high
- entity: switch.ups_test_battery_quick
secondary_info: last-changed
icon: mdi:battery
- entity: switch.ups_test_battery_deep
secondary_info: last-changed
icon: mdi:battery
Поделюсь еще одним вариантом совмещения двух пользовательских интеграции, а то примеров то мало и сложно собирать такие панели, поэтому хотелось, чтобы было больше готовых вариантов
Для создание такой панели в Lovelace, нам понадобятся две интеграции
Конфигурация lovelace
type: entities
entities:
- type: custom:fold-entity-row
head:
entity: sensor.ups_cyberpower_livingroom
name: ИБП
type: custom:multiple-entity-row
secondary_info:
attribute: Уровень заряда
name: Батарея
unit: '%'
state_header: Статус
entities:
- entity: group.livingroom_ups
name: Сенсоры
icon: mdi:information-outline
- entity: sensor.ups_load
name: Нагрузка
- entity: sensor.ups_load_watts
name: Нагрузка
entities:
- entity: switch.ups_beeper
secondary_info: last-changed
icon: mdi:volume-high
- entity: switch.ups_test_battery_quick
secondary_info: last-changed
icon: mdi:battery
- entity: switch.ups_test_battery_deep
secondary_info: last-changed
icon: mdi:battery
Is there a way to change the color of the entity based on it’s state?
something like this (this doesn’t work):
- entity: sensor.main_roi
type: custom:multiple-entity-row
name: ROI
unit: "$"
icon: mdi:currency-usd
state_header: ROI
styles:
width: 275px
text-align: center
color: >
{% if states('sensor.main_roi') < 0 %} red {% else %} green {% endif %}
Also is there a way to hide the name? I tried name: false but it doesn’t work. The only thing that worked is name: " " but it keeps the tab of the name…
So card-mod does work, to change the text of the card:
card_mod:
style: |
:host {
color:
{%- set sensor = (states('sensor.main_roi')| float) %}
{%- if sensor < 0 %}red
{%- else %}green
{%- endif %}
}
Is anyone having trouble getting the extra entities to pop-up their more-info boxes when clicked?
I’m positive this used to work but no longer does.
Do not confirm this.
2021.11.5, latest multiple-entity-row
Thanks. Could be an issue with 2021.12 then.
Yes, it’s an issue in 2021.12
Confirm the issue.
The only walkaround - disable tap_action for the main entity:
- type: entities
entities:
- type: custom:multiple-entity-row
entity: sun.sun
tap_action: none
entities:
- entity: binary_sensor.net_is_available_internet
name: internet
- entity: sensor.cleargrass_1_co2
name: co2
- entity: sensor.cleargrass_1_pm25
name: pm25
- entity: person.ildar
name: ildar
English probably isn’t your first language but for future reference it is “Work-around”.
Disabling the tap action isn’t great if your main item is a switch or input boolean.
Oh, thank you!
Agreed, that was a solution for some cases.
(btw, I am not usually using more-info, prefer having all graphs & important logbooks on the card itself)
And in this particular case I would probably place a toggle on the card - using a toggle sometimes is more intuitive than tapping an icon. It’s a matter of habits.
Is it possible that the columns are correctly aligned?
type: entities
entities:
- entity: sensor.koelkast_power_mqtt
icon: mdi:flash
type: custom:multiple-entity-row
name: Koelkast
show_state: false
entities:
- entity: sensor.koelkast_power_mqtt
name: false
- entity: sensor.koelkast_energy_daily
name: false
- type: section
- entity: sensor.vaatwasser_power_mqtt
icon: mdi:flash
type: custom:multiple-entity-row
name: Vaatwasser
show_state: false
entities:
- entity: sensor.vaatwasser_power_mqtt
name: false
- entity: sensor.vaatwasser_energy_daily
name: false
...
...
...
- entity: sensor.vaatwasser_power_mqtt
name: false
styles:
width: 50px