Power Flow Card Plus draws your Home Assistant energy as a circuit diagram

Power, not energy, and the difference is stated up front

The scope statement is the first thing worth reading, because it prevents a category of confusion. The card does not aim to display energy values, meaning accumulated power over a day for example, and the README points to the Energy Flow Card Plus for that goal. So the picture shows instantaneous power moving between the grid, solar, the battery and the home, and the flow lines animate in the direction the power is going. The stated goal is to provide an easy to understand and visual way of displaying the current power distribution coming from and to different sources such as solar, grid and home batteries, and to expose a lot of customizability and control of its behaviour to the configuration. The card is described as inspired by the official Energy Distribution card in Home Assistant, so the intent is a richer version of something the platform already ships.

The configuration surface is deliberately enormous

The README warns that the card offers a lot of configuration options, and says not to worry, because if you want the appearance to match the official Energy Flow Card you only need to set up the entities and the rest of the options only enable further customization. That framing is important, because the option list is long enough to intimidate someone who only wants a working card. The card options table starts with a required `type` of `custom:power-flow-card-plus` and a required `entities` object, then adds optional entries such as `title` and a `dashboard_link` that shows a link to an Energy Dashboard, which should be a URL path to a location of your choice. The card type and the entities are the only required configuration in the whole schema, and everything else has a default.

The features run from a grid outage indicator to curved lines

Beyond the core card options, the feature list covers both behaviour and appearance. There is a UI editor, multiple language support across fourteen locales including English, German, Portuguese, Spanish, Brazilian Portuguese, Dutch, Italian, French, Russian, Finnish, Polish, Danish, Slovak and Czech, and bidirectional individual entities, meaning each entity can be shown in both directions. There is secondary information on all circles, a display for grid power outage, and template functionality. The longer list includes an option for the card at full size, a grid tolerance for small values so the battery does not correct the grid value for noise, a new and improved flow rate model, a choice of whether to colour icons and text, per-entity control of label, icon and colour, and a setting to hide an individual entity when its state is zero or unavailable. There are clickable entities including the home node, an option for curved lines to connect to the circles, a fix for crooked lines, and the ability to keep the battery colour on the grid line even when power is not being returned to the grid.

Every node can be relabelled, recoloured and re-typed

The customisation extends to the individual entities rather than stopping at the card. You can display individual power entities, and customise each one's label, icon and colour, with separate control of the icon colour and the label. The battery, solar and home nodes each have their own colour, icon, icon colour and label settings. The low carbon energy coming from the grid gets its own display, and its label, icon, circle colour, icon colour and state type are all configurable too. That last one is worth pausing on, because a state type for a low carbon figure implies the card reads a different attribute than the plain power sensor, and the configuration tells you which. The circle and line colours are independent of the entity colours, so a solar node can keep its own colour while the flow line into the grid is drawn in a different one.

Installation is a resource file and a YAML entry

HACS is the recommended route, and the card is directly available through it, so installing means searching for the card in the HACS interface and downloading it. A manual install is documented too: download `power-flow-card-plus.js` from the latest release and copy it into your `config/www` directory, then register it as a resource. If you configure dashboards in YAML, the reference is two lines:

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

If you prefer the graphical editor, the README walks through enabling advanced mode in your user profile, navigating to Settings and then Dashboards, opening the three dot menu, selecting Resources, hitting the add resource button, and entering the URL `/local/power-flow-card-plus.js` with the type set to JavaScript Module. The note for HACS installs is that you use `/hacsfiles/power-flow-card-plus/power-flow-card-plus.js` if HACS has not already added the resource for you. The card is a JavaScript module, which is why the type matters.

The source moved to a monorepo, and the README says where

There is a note in the README that changes how you should treat this repository. The card is distributed from flixlix/power-flow-card-plus, but the source code lives in the monorepo at flixlix/flixlix-cards, and issues and feature requests will be tracked there going forward. That is a significant operational detail for anyone depending on the card, because the repository you read for installation is not the repository you watch for changes. The release artefacts still come from here, with v0.3.7 as the most recent tag on 2026-04-28 and the last push to the main branch on the same date. The top level of the repository is small and tells you the shape of the thing: a single `power-flow-card-plus.js` file, a `hacs.json` for the HACS metadata, a `package.json`, a `CHANGELOG.md` and the README. The package manifest is private, marked as an ES module, and identifies the author as flixlix.

Videos rather than documentation, and a narrow version reference

The README is candid that it is long, and it recommends two tutorial videos instead of a full read, one in German that is up to date with version 0.2.2 and one about changes in individual configuration. That tells you the documentation is a moving target relative to the releases, and that the recorded walkthroughs lag. The other structural point is that the project is a front end with no backend of its own, so it inherits everything the Home Assistant instance provides, including the entity state and the dashboard resource mechanism, and it adds no persistence and no new data source. For a card that renders what the platform already knows, that is the correct shape. What it does not do is give you history, trends or anything about accumulated energy, which is precisely the gap the sibling Energy Flow Card Plus covers.

Editorial conclusion

Adopt Power Flow Card Plus if your Home Assistant dashboard needs a live picture of where power is going right now, since the animated flow between entities is exactly what the card is built for and the minimal configuration is only the entity list. Do not adopt it to show accumulated energy over a day, because the card explicitly excludes energy values and points you to the Energy Flow Card Plus for that. Verify first where the source code lives, since the card is distributed from this repository but the code is developed in the flixlix-cards monorepo where issues are tracked, and check the release version you install against the manual install path that expects a specific file name in `config/www`.

Frequently asked questions

Official sources

1. flixlix/power-flow-card-plus on GitHub
2. Issues
3. Project website
4. README
5. Releases