Power Flow Card Plus

[!TIP] 📖 Full documentation: cards.flixlix.com/power-flow-card-plus

The docs site has the complete configuration reference, an interactive configurator with copy-pasteable YAML, and ready-made examples — much easier to navigate than this README.

• Installation
• Configuration reference
• Interactive configurator
• Examples

[!NOTE] This card is distributed via flixlix/power-flow-card-plus, but the source code lives in the monorepo at flixlix/flixlix-cards. Issues and feature requests will be tracked there going forward.

Additional Features / Enhancements

• UI Editor!!! 🥳
• Multiple Language support (🇺🇸, 🇩🇪, 🇵🇹, 🇪🇸, 🇧🇷, 🇳🇱, 🇮🇹, 🇫🇷, 🇷🇺, 🇫🇮, 🇵🇱, 🇩🇰, 🇸🇰, 🇨🇿)
• Bidirectional Individual Entities ↕️
• Secondary Information for all circles ℹ️
• Display Grid Power Outage ⚡️
• Template functionality 📙

Goal

The Goal of this card is to provide an easy to understand and visualize way of displaying the current Power Distribution coming from and to different sources, such as solar, grid, home batteries etc. Furthermore, this card aims to expose a lot of customizability and control of its behavior to the configuration, allowing users to tailor it to their specific requirements.

Scope

This card does not aim to display Energy Values (Meaning accumulated power over 1 day, for example). If this is your goal, check out the Energy Flow Card Plus.

Guides

In case you want to watch a tutorial instead of reading through this very long readme 😅, I recommend the following videos:

• Power Flow Card Plus in Home Assistant - Jetzt noch besser? Anleitung from Smartzeug - in german, up to date with version 0.2.2
• Power Flow Card Plus for Home Assistant from Speak to the Geek - changes in indvidual configuration

Installation

Marketplace or HACS (recommended)

This card is in the default catalog. On Home Assistant 2026.11 and newer, go to Settings → Marketplace, search for "Power Flow Card Plus" and install it. Before 2026.11, search for it in HACS and download it 🙂

resources:
  - url: /local/power-flow-card-plus.js
    type: module

Usage

[!IMPORTANT] The reference below is kept for offline reading. The canonical, easier-to-navigate version is at cards.flixlix.com/power-flow-card-plus/configuration — with grouped options, an interactive configurator, and copy-pasteable examples.

[!WARNING]
This card offers a LOT of configuration options. Don't worry, if you want your card's appearance to match the official Energy Flow Card, you will only need to setup the entities. The rest of the options only enable further customization. If this is your goal, please go to Minimal Configuration or the Examples page on the docs site.

Options

Card options

Action Configuration

The card supports Home Assistant action configs on entity circles and other clickable entity surfaces.

If none of these actions are configured for a clickable entity surface, the card falls back to opening more-info when clickable_entities: true.

Entities object

At least one of grid, battery, or solar is required. All entites (except battery_charge) should have a unit_of_measurement attribute of W(watts) or kW(kilowatts). Entities in other units, e.g. m³, are read as they are, without scaling.

Grid Configuration

Solar Configuration

Battery Configuration

Individual Configuration

The Individual fields must be an array of objects. Each object must follow the following structure:

Home Configuration

Fossil Fuel Configuration

Color Object

Split entities

Can be use with either Grid or Battery configuration. The same unit_of_measurement rule as above applies.

Secondary Info Configuration

This Feature allows you to configure an additional small text for each Individual Device. Here you can put , for example, the state of charge of an electric car.

Power Outage

This feature allows you to configure how the card handles a Grid Power Outage scenario.

Display Zero Lines

This object allows you to control the behavior of the flow lines that are inactive.

Minimal Configuration

Don't forget to change the entity ids

The following configurations will allow you to achieve your results with the least amount of lines of code / complexity. In these examples I decided to use the Split entities option, but feel free to use the combined entity option. More Info

Only Grid

type: custom:power-flow-card-plus
entities:
  grid:
    entity: sensor.grid_power
    power_outage:
      entity: sensor.power_outage
    display_state: one_way
    color_circle: true
kilo_threshold: 10000

This should give you something like this:

Grid and Solar

type: custom:power-flow-card-plus
entities:
  grid:
    entity:
      consumption: sensor.grid_consumption
      production: sensor.grid_production
      display_state: one_way
      color_circle: true
  solar:
    entity: sensor.solar_production

This should give you something like this:

Grid, Solar and Battery

type: custom:power-flow-card-plus
entities:
  grid:
    entity:
      consumption: sensor.grid_consumption
      production: sensor.grid_production
    display_state: one_way
    color_circle: true
  solar:
    entity: sensor.solar_production
  battery:
    entity:
      consumption: sensor.battery_consumption
      production: sensor.battery_production
    state_of_charge: sensor.battery_state_of_charge
    display_state: one_way
    color_circle: true
  home:
    color_icon: true
kilo_threshold: 10000

This should give you something like this:

Mix & Match Config aka "Full Config"

This Configuration is a little bit random, it's just here to demonstrate the capabilities of this card.

type: custom:power-flow-card-plus
entities:
  home:
    entity: sensor.home_consumption
    color_icon: solar
  fossil_fuel_percentage:
    entity: sensor.fossil_fuel_percentage
    icon: mdi:pine-tree
    color_icon: true
    display_zero: true
    name: Non Fossil
    state_type: power
  grid:
    icon: mdi:ab-testing
    name: Provider
    entity:
      production: sensor.grid_production
      consumption: sensor.grid_consumption
  solar:
    icon: mdi:solar-panel-large
    entity: sensor.solar_production
  battery:
    name: Bateria
    icon: mdi:bat
    entity:
      consumption: sensor.battery_consumption
      production: sensor.battery_production
  individual:
    - entity: sensor.car_power
      icon: mdi:car-electric
      color: "#80b8ff"
      name: Denim Flash
      color_icon: false
    - entity: sensor.motorbike_power
      name: Qivi
      color_icon: true
      display_zero: true
      color: "#ff8080"
      icon: mdi:motorbike-electric
base_decimals: 0
kilo_decimals: 2
min_flow_rate: 0.9
max_flow_rate: 6
kilo_threshold: 10000
clickable_entities: true
title: Power Flow Card Plus

This should give you something like this:

Random Configurations

UI Editor (available in version 0.2)

[!TIP] I've made a lot of improvements in version 0.2 for the UI-Editor. Now each field has its own subpage, meaning there is now much less scrolling. The biggest change in the editor is the fact that you can now add up to 4 individual devices, all through the UI! 🥳

Flow Formula

flow_rate_model picks how a line's value becomes the time one dot takes to travel it:

Seconds per dot with the default min_flow_rate: 0.75, max_flow_rate: 6, min_expected_power: 0.01 and max_expected_power: 2000 (for relative, the line's share of all lines):

You may want to play around with max_expected_power, min_expected_power, max_flow_rate and min_flow_rate to get the speeds that you wish. use_new_flow_rate_model is the older way to choose: false means relative, true or unset means duration; flow_rate_model wins when both are set.

Duration model (default)

The time per dot shrinks linearly with the value, independently from other lines: a state of 10W always flows with the same velocity, no matter what other lines are doing. This is how the card behaved before 0.4.0-beta.0.

if (value > maxIn) return minOut; // above max_expected_power, use the fastest speed
return ((value - minIn) * (minOut - maxOut)) / (maxIn - minIn) + maxOut;

// value = value of the current line to calculate (eg: grid to home)
// minIn = min_expected_power, maxIn = max_expected_power
// maxOut = max_flow_rate (seconds per dot at min_expected_power)
// minOut = min_flow_rate (seconds per dot at max_expected_power)
// Below min_expected_power, dots move slower than max_flow_rate.

Speed model

Like duration it is independent from other lines, but the dot speed (one over the duration) grows linearly with the value, so twice the power looks about twice as fast. Mid-range values move noticeably faster than with duration. Values outside the expected range use the slowest or fastest speed.

progress = clamp((value - minIn) / (maxIn - minIn), 0, 1);
speed = 1 / maxOut + progress * (1 / minOut - 1 / maxOut);
return 1 / speed; // seconds for one dot to travel the line

Relative model

Based on the official formula used by the Energy Distribution card. Each line's flow rate is relative to all the other lines.

max - (value / totalLines) * (max - min);
// max = max_flow_rate
// min = min_flow_rate
// value = line value, solar to grid for example
// totalLines = gridConsumption + solarConsumption + solarToBattery +
//   solarToGrid + batteryConsumption + batteryFromGrid + batteryToGrid

The following video aims to show the difference between the relative and an absolute flow formula:

Notice that when the Power changes to only coming from the sun, the old formula accelerates to maintain a constant amount of dots/second. Using the new formula is more intuitive, since you can immediately see that the Solar Power is relatively low since the dots are flowing very slowly. On the old Flow Formula you might think that the sun is producing a lot of power, which in this case is not true.

At the end of the day these are two options and depending on what you're interested, one might suit you better than the other, that's why I kept the old formula, you have the choice. 🙂

To-Do List

Here is my to-do list containing a few enhancements I am planning in adding. The ones at the top are bigger priorities, so they’ll probably be available before the ones at the bottom.

• Change Tap Action Behavior to be compatible with Browser Mod
• Fill the circles #89
• More than two Individual Devices #54
• More than one solar source #23
• Display Connected/Disconnected status #111
• Grid Feed In Circle #119
• Improve performance #144

I am still just one person working on this project and obviously have other things going on in my life, so feel free to contribute to the project. You can also feel free to create a PR with a new feature and I'll try my best to review it 😊

Structured names

Requires Home Assistant 2026.4 or later. On earlier versions a structured name falls back to the entity's friendly name.

Home Assistant composes an entity's display name out of its registry context (entity, device, area, floor) rather than one friendly_name string. Any name option in this card can be a list of those parts instead of a plain string, so labels keep following renames and match what the built-in cards show:

entities:
  grid:
    entity: sensor.grid_power
    name:
      - type: area
      - type: entity

Available part types are entity, device, area, floor, and text (a literal, written as {type: text, text: 'Grid'}). Parts that resolve to nothing are dropped. A plain string name keeps working exactly as before, as does use_metadata, which now takes the entity's composed name rather than its friendly_name.

See the Home Assistant developer documentation for details.

License

This card is released under the MIT License.