Giter Club home page Giter Club logo

lovelace-multiple-entity-row's Introduction

multiple-entity-row

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

GH-release GH-downloads GH-last-commit GH-code-size hacs_badge

NOTE: This is not a standalone lovelace card, but a row element for the entities card.

Installation

Manually add multiple-entity-row.js to your <config>/www/ folder and add the following to the configuration.yaml file:

lovelace:
  resources:
    - url: /local/multiple-entity-row.js?v=4.5.1
      type: module

OR install using HACS and add this (if in YAML mode):

lovelace:
  resources:
    - url: /hacsfiles/lovelace-multiple-entity-row/multiple-entity-row.js
      type: module

The above configuration can be managed in the Configuration -> Dashboards -> Resources panel when not using YAML.

Configuration

This card produces an entity-row and must therefore be configured as an entity in an entities card.

Name Type Default Description
type string Required custom:multiple-entity-row
entity string Required Entity ID (domain.my_entity_id)
attribute string Show an attribute instead of the state value
name string/bool friendly_name Override entity friendly name
unit string/bool unit_of_measurement Override entity unit of measurement
icon string icon Override entity icon or image
image string Show an image instead of icon
toggle bool false Display a toggle (if supported) instead of state
show_state bool true Set to false to hide the main entity
state_header string Show header text above the main entity state
state_color bool false Enable colored icon when entity is active
column bool false Show entities in a column instead of a row
styles object Add custom CSS styles to the state element
format string Formatting Format main state/attribute value
entities list Entity Objects Additional entity IDs or entity object(s)
secondary_info string/object Secondary Info Custom secondary_info entity
tap_action object Actions Custom tap action on entity row and state value
hold_action object Custom hold action on entity row
double_tap_action object Custom double tap action on entity row

Entity Objects

Similarly as the default HA entities card, each entity can be specified by an entity ID string, or by an object which allows more customization and configuration.

If you define entities as objects, either entity, attribute or icon needs to be specified. entity is only required if you want to display data from another entity than the main entity specified above. attribute is necessary if you want to display an entity attribute value instead of the state value. icon lets you display an icon instead of a state or attribute value (works well together with a custom tap_action).

Name Type Default Description
entity string A valid entity_id (or skip to use main entity)
attribute string A valid attribute key for the entity
name string/bool friendly_name Override entity friendly name (or false to hide)
unit string/bool unit_of_measurement Override entity unit of measurement (or false to hide)
toggle bool false Display a toggle if supported by domain
icon string/bool false Display default or custom icon instead of state or attribute value
state_color bool false Enable colored icon when entity is active
default string Display this value if the entity does not exist or should not be shown
hide_unavailable bool false Hide entity if unavailable or not found
hide_if object/any Hiding Hide entity if its value matches specified value or criteria
styles object Add custom CSS styles to the entity element
format string Formatting Format entity value
tap_action object Actions Custom entity tap action

Note that hold_action and double_tap_action are currently not supported on additional entities.

Special attributes

Some special data fields from HA can be displayed by setting the attribute field to the following values:

Value Description
last-changed Renders the last_changed state of the entity if available
last-updated Renders the last_updated state of the entity if available

Secondary Info

The secondary_info field can either be any string if you just want to display some text, an object containing configuration options listed below, or any of the default string values from HA (entity-id, last-changed, last-updated, last-triggered, position, tilt-position, brightness).

Name Type Default Description
entity string A valid entity_id (or skip to use main entity)
attribute string A valid attribute key for the entity
name string/bool friendly_name Override entity friendly name (or false to hide)
unit string/bool unit_of_measurement Override entity unit of measurement (or false to hide)
hide_unavailable bool false Hide secondary info if unavailable or not found
hide_if object/any Hiding Hide secondary info if value matches specified criteria
format string Formatting Format secondary info value

Actions

This card supports all the default HA actions. See Lovelace Actions for more detailed descriptions and examples.

Name Type Default Description
action string Required more-info, toggle, call-service, url, navigate, fire-dom-event, none
entity string Override entity-id when action is more-info
service string Service to call when action is call-service
service_data object Optional data to include when action is call-service
url_path string URL to open when action is url
navigation_path string Path to navigate to when action is navigate
confirmation bool/object false Enable confirmation dialog
haptic string none Haptic feedback (success, warning, failure, light, medium, heavy, selection)

Formatting

The format option supports the following values:

Value Type Description
relative timestamp Convert value to relative time (5 minutes ago)
total timestamp Convert value to relative time (5 minutes)
date timestamp Convert timestamp value to date
time timestamp Convert timestamp value to time
datetime timestamp Convert timestamp value to date and time
brightness number Convert brightness value to percentage
duration number Convert number of seconds to duration (5:38:50)
duration-m number Convert number of milliseconds to duration (5:38:50)
duration-h number Convert number of hours to duration (5:38:50)
invert number Convert number from positive to negative or vice versa
kilo number Divide number value by 1000 (ex. 1500 W -> 1.5 kW)
position number Reverses a position percentage (ex. 70% open -> 30% closed)
precision<0-9> number Set decimal precision of number value (precision3 -> 18.123)
celsius_to_fahrenheit number Converts a Celsius temperature to its Fahrenheit equivalent
fahrenheit_to_celsius number Converts a Fahrenheit temperature to its Celsius equivalent

Hiding

The hide_if option can be used to hide an entity if its state or attribute value matches the specified criteria. It can be used directly with a string, number or boolean value (i.e. hide_if: 'off'), as a list with several values, or as an object with one or more of the options listed below.

Name Type Description
above number Hidden if entity number value is above the specified value
below number Hidden if entity number value is below the specified value
value list/any Hidden if value matches specified value or any value in a list

Examples

multiple-entity-row

type: entities
entities:
  - entity: sensor.bedroom_temperature
    type: custom:multiple-entity-row
    name: One entity
    secondary_info: last-changed
    entities:
      - sensor.bedroom_max_temp

  - entity: sensor.bedroom_temperature
    type: custom:multiple-entity-row
    name: Two entities
    secondary_info: last-changed
    entities:
      - sensor.bedroom_min_temp
      - sensor.bedroom_max_temp

  - entity: sensor.bedroom_temperature
    type: custom:multiple-entity-row
    name: Three entities
    secondary_info: last-changed
    entities:
      - entity: sensor.bedroom_humidity
        name: humidity
      - sensor.bedroom_min_temp
      - sensor.bedroom_max_temp

  - entity: sensor.bedroom_temperature
    type: custom:multiple-entity-row
    name: Custom secondary_info
    secondary_info:
      attribute: battery_level
      name: Battery
      unit: '%'

  - type: section
  - entity: vacuum.xiaomi_vacuum_cleaner
    type: custom:multiple-entity-row
    name: Attributes
    entities:
      - attribute: battery_level
        name: Battery
        unit: '%'
      - attribute: status
        name: Status

  - entity:  sensor.lovelace_multiple_entity_row
    type: custom:multiple-entity-row
    name: Attributes (show_state=false)
    show_state: false
    entities:
      - attribute: stargazers
        name: Stars
      - attribute: open_issues
        name: Issues
      - attribute: open_pull_requests
        name: PRs

  - type: section
  - entity: sensor.bedroom_temperature
    type: custom:multiple-entity-row
    name: Hide headers (name)
    entities:
      - entity: sensor.bedroom_min_temp
        name: false
      - entity: sensor.bedroom_max_temp
        name: false

  - entity: sensor.bedroom_temperature
    type: custom:multiple-entity-row
    name: Main state header
    state_header: current
    entities:
      - sensor.bedroom_min_temp
      - sensor.bedroom_max_temp

  - type: section
  - entity: switch.livingroom_tv
    type: custom:multiple-entity-row
    name: Toggle
    toggle: true
    state_color: true
    entities:
      - entity: sensor.livingroom_tv_power
        name: Power
      - entity: sensor.livingroom_tv_power_total
        name: Total

  - entity: switch.livingroom_tv
    type: custom:multiple-entity-row
    name: Multiple toggles
    state_header: main
    toggle: true
    state_color: true
    entities:
      - entity: switch.livingroom_light
        name: toggle1
        toggle: true
      - entity: switch.livingroom_light_2
        name: toggle2
        toggle: true

  - type: section
  - entity: light.living_room
    type: custom:multiple-entity-row
    name: Toggle with hold_action
    state_header: Livingroom
    toggle: false
    hold_action:
      action: toggle
    entities:
      - entity: light.nightstand
        name: Bedroom
        tap_action:
          action: toggle

  - entity: light.living_room
    type: custom:multiple-entity-row
    name: Icons with tap_action
    secondary_info: last-changed
    entities:
      - entity: light.living_room
        icon: mdi:palette
      - icon: mdi:lightbulb-off-outline
        state_color: true
        tap_action:
          action: call-service
          service: light.turn_off
          service_data:
            entity_id: light.living_room
      - icon: mdi:lightbulb-outline
        state_color: true
        tap_action:
          action: call-service
          service: light.turn_on
          service_data:
            entity_id: light.living_room
          confirmation:
            text: 'Are you sure?'

  - type: section
  - entity: sensor.bedroom_temperature
    type: custom:multiple-entity-row
    name: Customization
    icon: mdi:fire
    unit: °F
    secondary_info: last-changed
    entities:
      - entity: sensor.bedroom_max_temp
        name: custom name
        unit: temp

  - type: section
  - entity: sensor.bedroom_temperature
    type: custom:multiple-entity-row
    name: Styles
    styles:
      width: 80px
      text-align: right
    secondary_info:
      attribute: battery_level
      styles:
        font-weight: bold
    entities:
      - entity: sensor.bedroom_max_temp
        styles:
          width: 80px
          text-align: left

My cards

xiaomi-vacuum-card | multiple-entity-row | github-entity-row | battery-entity-row | attribute-entity-row

BMC

lovelace-multiple-entity-row's People

Contributors

benct avatar bratanon avatar carlos-sarmiento avatar drzony avatar fragmenthor avatar hjbotha avatar kamtschatka avatar mill1000 avatar noxhirsch avatar sebr avatar techillin avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

lovelace-multiple-entity-row's Issues

Toggle on climate entity, turns from toggle to text of state

Hi,

I'm using this with toggles on climate entities. When they are 'off' the toggle appears, when they are on the text of the state appears, e.g. 'cool'.

This wasn't happening before a recent update. At some point I think a HA upgrade broke the toggle functionality, then I upgraded the js file for this and now it's half working as described. Could well be a feature of the climate component maybe?

Using in replacement for entity-attributes-card

The entity-attributes-card worked well for me when fleshing out details of each media_player. Now that looks like it's gone I am exploring this feature to get at attributes. The multi attributes per line is not helpful in this case as the attributes are words so I have used one line per attribute.
I'd like to be able to compact the rows and hide the icon. I really don't want to have to create masses of sensors.
Any suggestions?
media_player

Haptic Feedback

Awesome Card! Love the update for extra entity support - great amount of flexibility!

Would it be possible to add haptic support for call-service ?
It works for the standard entity toggle, but not if using call-service.

JS errors if entity is not available

Uncaught (in promise) Error: Entity not available: sensor.slave1_aqi_eco_marywilska_pm25
    at HTMLElement.set hass [as hass] (multiple-entity-row.js:136)
    at HTMLElement.value (hui-entities-card.ts:219)
    at HTMLElement.e.renderEntity (card-mod.js:1)
    at hui-entities-card.ts:144
    at Array.map (<anonymous>)
    at HTMLElement.value (hui-entities-card.ts:143)
    at HTMLElement.update (lit-element.ts:217)
    at HTMLElement.performUpdate (updating-element.ts:704)
    at HTMLElement._enqueueUpdate (updating-element.ts:653)

'sensor.slave1_aqi_eco_marywilska_pm25' is defined as primary entity

URL tap action

Would it be possible to add a tap_action called 'url' (like implemented for the standard 'Entities Card') for linking to web pages, so that one could set the tap action something like:

- type: 'custom:multiple-entity-row'
  entity: sensor.sensor1
  entities:
    - icon: 'mdi:link-variant'
      tap_action:
        action: url
        url_path: 'http://x.x.x.x'

Many thanks in advance!

Support for timer

3 things 😬:

  1. It would be great if we could show info, primary or secondary based on conditional states.

  2. Also cool if timers could show remaining time rather than "active".

  3. Would like to have control over the display format: e.g. 00:02:30, 02:30, 2 min 30 sec, 150 sec

timer

E.g. in this example switch activates a 2 min timer, when it reaches 0 an automation turns off the switch. Would like to be able to hide the timer when inactive, currently shows as "idle". Realise this might be bit niche 😕

Click on entity name doesn't trig "default" tap action

Hi,
I have this card installed for 6+ months and it used to trigger the default tap action clicking on the "name" ("Front camera" or "Mobile camera" in the example below) or on the icon on the left of the name (in my case, the picture from last captured video).

So, clicking on the name or icon used to play the last captured video, but something has recently changed and when I click on the name or the icon on the left, it doesn't open the screen to play the last captured video.

I saw that if I show the state (remove "hide_state: true") and click on the state (mostly "Idle" in my case), it triggers the default action, but I didn't want to show the state.

Is it a new expected behavior? Is there an option to trigger the default tap action clicking on the entity name?

Thank you!

  - entity: camera.aarlo_front
    name: Front camera
    primary:
      entity: sensor.aarlo_captured_today_front
      name: Captured today
    type: 'custom:multiple-entity-row'
    hide_state: true
  - type: section
  - entity: camera.aarlo_mobile
    name: Mobile camera
    primary:
      entity: sensor.aarlo_captured_today_mobile
      name: Captured today
    type: 'custom:multiple-entity-row'
    hide_state: true
show_header_toggle: false
title: Arlo
type: entities```

Cards not working anymore.

Hi.

I think this is related to the new update recently.

I have this config which worked perfectly before:

  - entity: sensor.netatmo_ude_temperature
    name: Ude
    name_state: Current
    primary:
      entity: sensor.netatmo_ude_min_temp
      name: Min
    secondary:
      entity: sensor.netatmo_ude_max_temp
      name: Max
    secondary_info: last-changed
    tertiary:
      entity: sensor.netatmo_ude_humidity
      name: Humid
    type: 'custom:multiple-entity-row'
  - entity: sensor.netatmo_stue_temperature
    name: Inde
    name_state: Current
    primary:
      entity: sensor.netatmo_stue_min_temp
      name: Min
    secondary:
      entity: sensor.netatmo_stue_max_temp
      name: Max
    secondary_info: last-changed
    tertiary:
      entity: sensor.netatmo_stue_co2
      name: Co2
    type: 'custom:multiple-entity-row'
  - entity: sensor.netatmo_regn_rain
    name: Regn
    name_state: Current
    primary:
      entity: sensor.netatmo_regn_sum_rain_1
      name: Sum 1
    secondary:
      entity: sensor.netatmo_regn_sum_rain_24
      name: Sum24
    secondary_info: last-changed
    type: 'custom:multiple-entity-row'
type: entities

But I can't figure out how to get it to work with the new version. Can you help?

Main entity state is invisible

Hi. First of all, thank you for your great job!

I'm trying to figure out where is the problem with showing main entity in my example.
Here is the code:

      - entity: sensor.hue_dimmer_child_room_link
        type: custom:multiple-entity-row
        primary:
          entity: sensor.przycisk_u_samuela
          attribute: battery
          name: Bateria
          unit: '%'

and this is what I have on UI:
obraz

This entity should have "online" state but it's null.

But when I have another entity witch state different than "online" everything works fine.

Add spacing enhancement (and option[s])?

Enhancement request (but even without any of these, thank you making this awesome addition to Lovelace!)

I'm looking for a way to get my primary entity more towards the middle rather than right justified to spread out the white space and make it not look so busy. Someone might want to do the same with a primary/secondary or (rarely?) even a primary/secondary/tertiary setup.

One obvious solution is a row-level justification option.

The second solution would be a blank entity. It could solve my use case, and would also cover a case where someone wants to display two extra entities, either with extra space to the right of the two entities, or extra space between them (i.e primary and tertiary contain real entities, and secondary would be blank).

Adding both would obviously open up the additional spacing possibilities.

image

          - entity: lock.front_door_lock_9
            secondary_info: last-changed
            type: custom:multiple-entity-row
            justify: center               # option 1.  Someone might want left also
            primary:
              attribute: changed_by_name
              name: Last opened by
            secondary:
              name: "                   "  # option 2: dummy using spaces for width 

When I thought about the above, I realized spacing in the blank name could solve a different issue. Take my Leak sensors below as an example. It would look better if Fridge (and the entity value below it) was moved to the left slightly. I tried adding spaces to the name, but they appear to be ignored:

image

          - entity: sensor.dishwasher_sensor_battery
            name: Leak sensors
            type: custom:multiple-entity-row
            name_state: Dishwasher
            primary:
              entity: sensor.fridge_sensor_battery
              name: "  Fridge  "              # honoring spaces could make spacing look nicer
            secondary:
              entity: sensor.waterheater_sensor_battery
              name: Hallway

tap_action per entity

Hi there,
first of all, thanks for this card, it is very useful for my current project :)

I would like to ask if it would be possible to have the "tap_action" to work for each defined entity so that I can decide nothing have to happen, or more spefiically for my case, to open a browser_mod.popup using call-service

Here what I am trying now:

                entities:
                  - type: custom:multiple-entity-row
                    entity: input_number.climate_t1_house_workday
                    icon: mdi:timer
                    primary:
                      entity: input_datetime.climate_t1_house_workday_start
                    secondary:
                      entity: input_datetime.climate_t1_house_workday_end
                    tap_action:
                      action: call-service
                      service: browser_mod.popup
                      service_data:
                        title: T1 Workday
                        card:
                          type: entities
                          entities:
                            - input_datetime.climate_t1_house_workday_start
                            - input_datetime.climate_t1_house_workday_end
                            - input_number.climate_t1_house_workday

Unfortuntately for now it seems that it is completely ignored, even if I set on each other entity to do nothing:

                    primary:
                      entity: input_datetime.climate_t1_house_workday_start
                      tap_action:
                        action: none

Would that be possible to integrate?

Thanks
Andrea

Display last-changed from other entity

Hi there,

i dont know if it's a problem with my understanding of the code but i'm trying to display on info the "last-changed" from another entity.

Backgroundstory:
The ioBroker Addon "radar2" stores 2 Objects for one device:
objects

In my custom card i tried the following:

type: entity-filter
entities:
  - entity: _.monitoring_device_brotherscanner_here
    type: 'custom:multiple-entity-row'
    name: Brother Scanner
    info:
      entity: _.monitoring_device_brotherscanner_last_here

state_filter:
  - false

card:
  title: Devices offline
  show_header_toggle: false

On the info line it shows me the value (timestamp) but i need the last-changed from this object.
How do i do this?

Broken change ?

Hi
With the last update ( the first one of today)
I cant see the card in the lovelace...
custom element doesn’t exist...
something change in the configuration ? I dont see any change in the configuration

Expected a value of type ... but received ...

I'm suspecting this might be rooted in the ha-wyzesense component, but:

Adding this Lovelace card:

type: entities
entities:
  - entity: binary_sensor.outer_front_door
    primary:
      attribute: battery_level
      entity: binary_sensor.outer_front_door
      name: Battery
      unit: '%'
    secondary:
      attribute: rssi
      entity: binary_sensor.outer_front_door
      name: Wi-Fi
    type: 'custom:multiple-entity-row'
show_header_toggle: false

The card appears to render fine, but below the editor window, we have:

Expected a value of type `{entity,name,icon} | entity-id` 
for `entities.0.primary` 
but received `{"attribute":"battery_level","entity":"binary_sensor.outer_front_door","name":"Battery","unit":"%"}`.

Maybe that component isn't returning something you're expecting as standard?

For my sensor's states:

binary_sensor.outer_front_door
{
  "assumed_state": true,
  "battery_level": 93,
  "device_class": "door",
  "friendly_name": "Outer front door",
  "mac": "7788E675",
  "rssi": -62,
  "timestamp": "2019-09-22T08:28:51.400000"
}

Appreciate your thoughts.

Templating in the future?

Loving the card, but really craving some templating! I've seen others using card-tools to interpret the template for arbitrary config keys - would it be possible to add something like this in the near future?

Compatibility with cover entity

Hi, can you add compatibility with cover entity? When I add only info with attribute then the control buttons disappear and there is state shown instead. I tried to set hide_state to true, but controls are still hidden. Thank you.
image

Further simplify config

Now that the primary, secondary and tertiary entities have been simplified into just a list of entities I was thinking it should be possible to also include the main "entity" into that same list.

Is there a special reason it needs to be separated from the rest?

so from:

  • type: 'custom:multiple-entity-row'
    name: Gas use
    entity: sensor.hourly_gas_consumption
    state_header: Current
    entities:
    • entity: sensor.daily_gas
      name: Daily
    • entity: sensor.monthly_gas
      name: Monthly

to:

  • type: 'custom:multiple-entity-row'
    name: Gas use
    entities:
    • entity: sensor.daily_gas
      name: Daily
    • entity: sensor.monthly_gas
      name: Monthly
    • entity: sensor.hourly_gas_consumption
      name: Current
      type: 'custom:multiple-entity-row'

Add toggle for pri+sec and tertiary option

Is it possible to add the following;

  • A toggle for the primary and secondary objects
  • Name above the entity value (value at the end of the row)
  • A tertiary object?

Thanks :)

info: name is false, but display 'null'

Hi,

I use info and set name as false, but it shows letter 'null' not blank. Actually it has been showed correctly before a few weeks.
Please check it out.

Icon - entity state

Is it possible to make the icon change (or change the color) as the entity state changes? (e.g. windows open / close)

Support for Special Row Elements in an Entity Row

Looking at this link: https://www.home-assistant.io/lovelace/entities/ -- see the section on "Special Row Elements." Specifically, having the ability to launch a script from a button in-line on the entity row would be excellent.

I could see the config being something like:

 entities:
 - entity: input_datetime.sleep_time_shutoff
   name: Sleep Timer
   type: custom:multiple-entity-row
   secondary_info: last-changed
   hide_state: true
   primary:
     type: call-service
     name: false
     action_name: '+30'
     service: script.sleep_timer_add_30

What this would show is a single row (sorry for the ASCII only -- the "[+ 30]" represents a button that launches the script):

Sleep Timer ----------------------------- [+ 30] 22:34

Let me know if you think this makes sense and if I can help in any other way.

Multiple entity row isn't displaying correctly?

I'm not sure if it's a bug or feature, but something is off I guess.
multiple row displays correct values, but design of the row is different than other elements.

Example:
temp_screen

I'd love to see multiple row in the same style as the rest - is there something I can do? or maybe it's just my lovelace behaving odd? I didn't "turned off" the styles so it supposed to display correctly, right?

State changes not being displayed until refresh

Not sure why, but when the state of an entity changes (e.g. from off to on), the state change is not reflected until a refresh of the web page is done (using F5 or the browser refresh button).

Hassio, running on a Raspberry Pi Model 3B+, 0.96.5.

Allow not specifying the entity for Entity objects.

I often automate the filling of entries with auto-entities... but I still have to use attribute-entity-row in some instances (when automating the filling of entities) because it actually doesn't require specifying an entity name ... can you make the entity and attribute fields conditional so that at least one must be specified.
If attribute is entered with no entity, then the primary entity will be used.

timestamp sensors format

Timestamp sensor like a doorbell will show only the long date/time format.
For instance

  - entity: sensor.front_door_last_activity   
    type: 'custom:multiple-entity-row'
    name: Doorbell

Will output: 2020-02-20T20:02:14+00:00

Whereas regularly:

  - entity: sensor.front_door_last_activity     
    name: Doorbell

Will output: 1 day ago

Is there a way to work around this? I tried with format variable, but it seems to ignore those.

format time

hi i am trying to use this with multiple UTc timestamps with format time, that works OK with the regular entities card but on this card it does not work

  • entity: sensor.jewish_calendar_upcoming_havdalah
    format: time

Confirmation for tap action

Is it possible to add a confirmation option for tap actions (tipically for call-service)?
Would be similar to entity button or glance.

Thanks in advance, this is a wonderful plugin.

No graph when clicking an entity

Don't know when it happened. Perhaps since last update of multiple-entity-row or after a HA update but now I don't get the graph when I click on an entity in lovelace.
Known bug?

Add name above icon

Is it possible to add a name above the icon?

Adnotacja 2020-02-14 234957

Thank you for the plugin, it's wonderful

Some attributes showing as Unavailable

I have a sensor for my Fully Kiosk Tablet. A lot of the attributes will not show using this card.
For example:
screenBrightness and
currentPage

I thought it might have something to do with upper case letters in the attribute name but
SDK and
versionCode
work.

My Lovelace config is like this,

          - type: entities
            title: '-- Hall Panel --'
            show_header_toggle: false
            entities:
              - entity: light.hallpanel
                type: custom:multiple-entity-row
                name: Screen
                icon: mdi:tablet
                info:
                  entity: sensor.hall_panel_fully_kiosk_info
                  attribute: versionCode
                  name: ' '
                primary:
                  entity: sensor.hall_panel_fully_kiosk_info
                  attribute: currentPage
                  name: 'Brightness: '

image

And the sensor is like this

image

allow use of entity in the multiple entity row

HI,

please consider allowing referencing the config entity in the multiple entity rows, (ie when not referencing an outside entity):

  - entity: vacuum.vacuum_cleaner
    type: custom:multiple-entity-row
    primary:
      entity: entity
      attribute: battery_level
      name: Battery
      unit: '%'
    secondary:
      entity: entity
      attribute: status
      name: Status

or maybe even:

  - entity: vacuum.vacuum_cleaner
    type: custom:multiple-entity-row
    primary:
      attribute: battery_level
      name: Battery
      unit: '%'
    secondary:
      attribute: status
      name: Status

instead of:

  - entity: vacuum.vacuum_cleaner
    type: custom:multiple-entity-row
    primary:
      entity: vacuum.vacuum_cleaner
      attribute: battery_level
      name: Battery
      unit: '%'
    secondary:
      entity: vacuum.vacuum_cleaner
      attribute: status
      name: Status

there's no need to keep repeating the entity, if set in the main config. Keep things short and simple.

And, it would make it so much easier to use the card in other cards or templates (like decluttering templates) Maybe even auto entities, though I am not sure that will go...

anyways,
thanks!

Icon not in row

Is it possible to fix icon not in row with other information?
image

Enhancement: tap_action = none

I would be nice to have tap_action = none (on individual entities) to limit interaction on selected entities. thanks.

Tap_action: toggle rather tap_action: more-info?

This seems slightly different than #31, but if you don't consider it so, my apologies - please close.

I have a z-wave lock that I would like to show the changed_by_name attribute, and your card works well for that. But in doing so, the default UNLOCK button (which locks/unlocks directly) is replaced with a state (LOCKED) which will pop-up the more-info with the UNLOCK button.

The top row is the "normal" entity behavior... you can simply touch the word UNLOCK and it'll unlock. It would be my preference to keep it that way - is there a way to with multiple-entity-row that I'm overlooking?

The closest I could figure out is adding toggle: true, which works but I'd rather not use the ambiguous toggle switch for this.

image

          - entity: lock.front_door_lock_9
            secondary_info: last-changed
            toggle: true
            type: custom:multiple-entity-row
            primary:
              attribute: changed_by_name
              name: Last unlocked

LitElement has already been declared

hi, after last update (ca8030c), plugin stops working ;(
i got error in log:
https://[myip]/community_plugin/lovelace-multiple-entity-row/multiple-entity-row.js:1:1 Uncaught SyntaxError: Identifier 'LitElement' has already been declared
any help appreciated

Toggle triggers multiple lights

Hi,

I have a strange issue, when I toggle "Staande lampen" it also toggles "Spot TV" for some reason. These entities are not in a group together or what so ever. When I do it the other way around (toggle "Spot TV") the "Staande lampen" stays off.

I have multiple of these "grouped" toggels for some reason. this only happens in this lovelace-multiple-entity-row feature. When I toggle "Staande lampen" in a default entity card, there is no issue.

I've downloaded the latest version this morning from this github page.

Is someone having the same issue and/or has a solution for this?

For this specifiek case this is my code:

entities:
 - label: Woonkamer
   type: section
 - entity: input_boolean.lightonoffstaandelampen
   hide_state: false
   name: Staande lampen
   toggle: true
   type: 'custom:multiple-entity-row'
 - entity: light.spot_tv
   hide_state: false
   name: Spot TV
   toggle: true
   type: 'custom:multiple-entity-row'
 - label: Achtertuin
   type: section
 - entity: light.achtertuin
   hide_state: false
   name: Achtertuin
   toggle: true
   type: 'custom:multiple-entity-row'
 - label: Hal
   type: section
 - entity: input_boolean.lightonoffhal
   name: Hal
   primary:
     entity: input_number.hal_brightness
   toggle: true
   type: 'custom:multiple-entity-row'
 - entity: light.voordeur
   name: Voordeur
   toggle: true
   type: 'custom:multiple-entity-row'
 - label: Overloop
   type: section
 - entity: light.hal_boven
   name: Overloop
   toggle: true
   type: 'custom:multiple-entity-row'
 - label: Zolder
   type: section
 - entity: light.voorzolder
   name: Zolder
   toggle: true
   type: 'custom:multiple-entity-row'
title: Lampen
type: entities

Unused entities with multiple-entity-row

Thank you for your great component. If possible please have a look, for now entities used only with multiple-entity-row stays in unused entities list. It will be better if entities utilised with multiple-entity-row will disappear from unused entities list.

Wrong installation patch

I'm at the beginning of using Home Assistant, so maybe it's my fault, but I might found a bug. I installed the plugin with HACS, and by default the component is in "/config/www/community/lovelace-multiple-entity-row", but I had the error below. Moving the files into "/config/www" error goes away
image

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.