Sankey Chart Card

A Home Assistant lovelace card to display a sankey chart. For example for power consumption.

This card is intended to display connections between entities with numeric state. It is not a general graph card.

Options

Name	Type	Requirement	Default	Description
type	string	Required		custom:sankey-chart
sections	list	Required		Entities to show divided by sections, see sections object for additional options.
energy_date_selection	boolean	Optional	false	Integrate with the Energy Dashboard. Filters data based on the energy-date-selection card. Use this only for accumulated data sensors (energy/water/gas) and with a type:energy-date-selection card. You still need to specify all your entities as HA doesn't know exactly how to connect them but you can use the general kWh entities that you have in the energy dashboard. In the future we may use areas to auto configure the chart.
title	string	Optional		Optional header title for the card
unit_prefix	string	Optional		Metric prefix for the unit of measurment. See https://en.wikipedia.org/wiki/Unit_prefix . Supported values are m, k, M, G, T
round	number	Optional	0	Round the value to at most N decimal places. May not apply to near zero values, see issue #29
height	number	Optional	200	The height of the card in pixels
wide	boolean	Optional	false	Set this to true if you see extra empty space in the right side of the card. This will expand it horizontally to cover all the available space. Enable if you see empty space on the right size.
show_icons	boolean	Optional	false	Display entity icons
show_names	boolean	Optional	false	Display entity names
show_states	boolean	Optional	true	Display entity states
show_units	boolean	Optional	true	Display unit of measurement
min_box_height	number	Optional	3	Minimum size of an entity box
min_box_distance	number	Optional	5	Minimum space between entity boxes
throttle	number	Optional		Minimum time in ms between updates/rerenders

Sections object

Name	Type	Requirement	Default	Description
entities	list	Required		Entities to show in this section. Could be just the entity_id as a string or an object, see entities object for additional options. Note that the order of this list matters

Entities object

Name	Type	Requirement	Default	Description
entity_id	string	Required		Entity id of the sensor
attribute	string	Optional		Use the value of an attribute instead of the state of the entity. unit_of_measurement and id will still come from the entity. For more complex customization, please use HA templates.
type	string	Optional	entity	Possible values are 'entity', 'passthrough', 'remaining_parent_state', 'remaining_child_state'. See entity types
children	list	Optional		List of entity ids describing child entities (branches). Only entities in subsequent sections will be connected.
name	string	Optional	entity name from HA	Custom label for this entity
color	string	Optional	var(--primary-color)	Color of the box
color_on_state	boolean	Optional	false	Color the box based on state value
color_limit	string	Optional	1	State value for coloring the box based on state value
color_above	string	Optional	var(--paper-item-icon-color)	Color for state value above color_limit
color_below	string	Optional	var(--primary-color)	Color for state value below color_limit
remaining	object	Optional		This configures wheter to display a box for the remaining state if the sum of entity states from children is less than this entity's state.

Remaining object

Name	Type	Requirement	Default	Description
name	string	Required		Label for this entity. For example 'Other'
color	string	Optional	var(--primary-color)	Color of the box

Entity types

• entity - The default value, representing an entity from HA
• passthrough - Used for connecting entities across sections, passing through intermediate sections. The card creates such passtroughs automatically when needed but you can create them manually in order to have the connection pass through a specific place. See issue #9. Here is an example passthrough config:

- entity_id: sensor.child_sensor
  type: passthrough
  children:
    - sensor.child_sensor #Note that the child sensor has itself as a single child

• remaining_parent_state - Used for representing the unaccounted state from this entity's parent. Formerly known as the remaining configuration. Useful for displaying the unmeasured state as "Other". See issue #2 & #28. Example:

- entity_id: whatever # as long as it is unique
  type: remaining_parent_state
  name: Other

• remaining_child_state - Used for representing the unaccounted state in this entity's children. Like remaining_parent_state but in reverse. Useful for displaying discrepancies where the children add up to more than the parent. See issue #2 & #15. Example:

- entity_id: whatever # as long as it is unique
  type: remaining_child_state
  name: Discrepancy

Examples

Simple

- type: custom:sankey-chart
  show_names: true
  sections:
    - entities:
      - entity_id: sensor.power
        children:
          - sensor.washing_machine_power
          - sensor.other_power
    - entities:
      - sensor.washing_machine_power
      - sensor.other_power

Energy use

- type: custom:sankey-chart
  show_names: true
  unit_prefix: k
  round: 1
  wide: true
  sections:
    - entities:
        - entity_id: sensor.solar
          color: var(--warning-color)
          children:
            - sensor.total_energy
        - entity_id: sensor.grid
          children:
            - sensor.total_energy
        - entity_id: sensor.battery
          color: var(--success-color)
          children:
            - sensor.total_energy
    - entities:
        - entity_id: sensor.total_energy
          children:
            - sensor.floor1
            - sensor.floor2
            - sensor.garage
    - entities:
        - entity_id: sensor.garage
          color: purple
          children:
            - sensor.ev_charger
            - garage_other
        - entity_id: sensor.floor1
          children:
            - sensor.living_room
            - sensor.washer
        - entity_id: sensor.floor2
    - entities:
        - sensor.ev_charger
        - entity_id: garage_other
          type: remaining_parent_state
          name: Other
        - sensor.living_room
        - sensor.washer

You can find more examples and help in the HA forum https://community.home-assistant.io/t/anyone-using-the-sankey-chart-card/423125

Energy Dashboard

This card supports partial Energy dashboard integration. You still need to specify the entities and connections for now. See energy_date_selection option.

Currently this chart just shows historical data based on a energy-date-selection card. It doesn’t know/care if your entities are in the default energy dashboard.

Total [daily] energy

There isn’t a general Consumed Energy sensor in the HA Energy dashboard AFAIK. HA calculates it based on all the in/out kWh values. I can’t tell you exactly how to calculate it because it depends on what values you can monitor. Some people already have a Total Consumption sensor, others have a Current Consumption and create an integration sensor from that, etc.

Development

1. npm i
2. npm start
3. The compiled .js file will be accessible on http://127.0.0.1:5000/ha-sankey-chart.js.
4. On a running Home Assistant installation add this to your Lovelace resources:

- url: 'http://127.0.0.1:5000/ha-sankey-chart.js'
  type: module