Show multiple entity states and attributes on entity rows in Home Assistant's Lovelace UI
This release includes a major refactoring of the codebase, but should not contain any (significant) breaking changes. Please report any bugs or issues here.
Added:
attribute
instead of state on main entity (#124)secondary_info
options (#113, #123)image
option for entity row (#114)hold_action
and double_tap_action
(on entity row only) (#50)shouldUpdate
function (#125)hide_unavailable
now also supports attributes (#119)Changed:
hui-generic-entity-row
to handle generic parts of rowcustom-card-helpers
Removed:
Fixed:
format
option is set (#117)Added:
precision<0-9>
for value decimal precision (#110)hide_unavailable
to hide entity if unavailable (#77)Fixed:
format
option is set (#60)lock
or cover
entity (#32)Added:
duration
for displaying value in seconds as hh:mm:ss
(#89)hui-warning
element when main entity is not availableChanged:
Added:
navigate
action with navigate_path
on tap actions (#66, #82)column
instead of the default row (#98)Changed:
url
now behaves similarly as other HA cards (#66)Fixed:
0.116
(#103, #104)Fixed:
device_class
(#74)Fixed
Broken! Upgrade to 3.1.1.
Changed
Added
state_color
config on additional entity icons (#45)call-service
and toggle
actions (#44)more-info
action (#46)confirmation
dialog config on tap_action
(#42)url
action config on tap_action
(#49)none
action config on tap_action
(#53)secondary_info
(#51)format
config for date/time values (#43, #47)Breaking changes!
Several main configuration options have been changed to better match the default Lovelace cards, as listed below. See README for more info and examples on all possible breaking configuration changes.
Changed
entities
list instead of named objects (#28)info
into secondary_info
for simpler configurationhide_state
to show_state
with default true
name_state
to state_header
tap_action
(#31)Added
tap_action
for main entity (#31)more_info
, toggle
and call_service
actions under tap_action
(#32)It is now possible to define as many (of few) additional entities as you want. However, make sure they all fit into the entity row!