Lovelace Multiple Entity Row Versions Save

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

v4.0.0

3 years ago

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:

  • Support showing attribute instead of state on main entity (#124)
  • Support all standard HA secondary_info options (#113, #123)
  • Support standard image option for entity row (#114)
  • Support hold_action and double_tap_action (on entity row only) (#50)
  • Prevent unnecessary re-rendering with shouldUpdate function (#125)
  • Option hide_unavailable now also supports attributes (#119)
  • Several external packages and tools to improve developer experience

Changed:

  • Major refactoring and improvements of entire codebase
  • Use hui-generic-entity-row to handle generic parts of row
  • Move CSS and utility functions to separate files
  • Replace some utility methods with equivalents from custom-card-helpers
  • Simplify most configuration handling

Removed:

  • Custom styles option on secondary info

v3.5.1

3 years ago

Fixed:

  • Unit not being rendered when format option is set (#117)

v3.5.0

3 years ago

Added:

  • Support custom styling on state and entity objects (#111, #112)
  • Format option precision<0-9> for value decimal precision (#110)
  • Option hide_unavailable to hide entity if unavailable (#77)

Fixed:

  • Secondary info name not being rendered when format option is set (#60)
  • Call correct service when toggling lock or cover entity (#32)

v3.4.0

3 years ago

Added:

  • Format option duration for displaying value in seconds as hh:mm:ss (#89)
  • Display hui-warning element when main entity is not available

Changed:

  • Row tap action now affects entire row, not only state value (#107)
  • Simplify and improve tap action handling
  • Remove deprecated handling of zwave state values

v3.3.0

3 years ago

Added:

  • Support navigateaction with navigate_path on tap actions (#66, #82)
  • Support for showing entities in a column instead of the default row (#98)
  • Print version information to browser console window (#78)

Changed:

  • Improved alignment on state element by removing min-width (#64)
  • Tap action mode url now behaves similarly as other HA cards (#66)

v3.2.1

3 years ago

Fixed:

  • Compatibility issue with HA 0.116 (#103, #104)

v3.2.0

3 years ago

Fixed:

  • State display for entities with device_class (#74)
  • Default HA icon when state attribute icon is undefined (#71)

v3.1.1

4 years ago

Fixed

  • Remove unsupported optional chaining operator (#54, #56, #57)

v3.1.0

4 years ago

Broken! Upgrade to 3.1.1.

Changed

  • Display name/header above additional entity icons (#41)

Added

  • Support state_color config on additional entity icons (#45)
  • Haptic feedback on call-service and toggle actions (#44)
  • Support entity override on more-info action (#46)
  • Support confirmation dialog config on tap_action (#42)
  • Support url action config on tap_action (#49)
  • Support none action config on tap_action (#53)
  • Support any string value as secondary_info (#51)
  • Support format config for date/time values (#43, #47)

v3.0.0

4 years ago

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

  • Convert additional entity config to entities list instead of named objects (#28)
  • Merge info into secondary_info for simpler configuration
  • Rename hide_state to show_state with default true
  • Rename name_state to state_header
  • Move service call configuration to tap_action (#31)

Added

  • Support custom tap_action for main entity (#31)
  • Support for more_info, toggle and call_service actions under tap_action (#32)
  • Additional entity icons change color based on entity state (#25)

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!