Hi all,
I’ve put together (with a lot of help from Claude) a custom Lovelace card that makes a card that is very close to the energy flow Sankey graph within Sigenergy’s mySigen phone/tablet app — Solar / Battery / Grid as sources on the left, Battery / Load / Grid as destinations on the right — directly in Home Assistant, with its own Day / Week / Month / Year period selector.
Why**
The Sigenergy integrations give you plenty of raw sensors, but nothing that reproduces the at-a-glance flow picture the phone app shows. I wanted that picture on my own dashboard, with full history rather than just live power.
What it looks like**
How it works (the honest version)
Sigenergy doesn’t meter the individual sub-flows (e.g. “solar that went straight to the battery” vs “solar that went to load”) — only totals: solar produced, battery charged/discharged, grid imported/exported, and load consumed. This card allocates those totals across the ribbons using the same priority order HA’s own core Energy Distribution card uses (solar → load → battery → grid export; battery/grid → whatever load is left), computed at an hourly/daily/monthly bucket size depending on the period so a day where the battery both charged and discharged doesn’t cancel itself out. Full writeup in the README if you’re curious, along with a worked example from real data.
The colours and layout are trued up against a real mySigen screenshot, but I’ve only tested it against my own system’s data — if something looks off against yours, let me know.
If your setup does expose real sub-flow sensors, wire them in — the allocation model only fills in the gaps.
Requirements
Any Sigenergy integration that gives you daily energy (kWh) sensors for solar/battery/grid (Sigenergy Local Modbus, sigenergy2mqtt, etc.) — this card doesn’t talk Modbus itself, it just reads whatever entities you point it at. I have only tested this with the one I use which is Sigenergy ESS. HA’s recorder keeping long-term statistics for those entities (the default).
Install
Via HACS as a custom repository for now (details in the README) — happy to submit it to the default HACS store once it’s had a bit of real-world use.
Feedback welcome
This is my first attempt at this and as I say a lot of assist and credit goes to Claude.
Include which Sigenergy integration/entity-naming you’re on, if it’s not covered in the README yet.
Anything that looks wrong in the flow allocation for your own system.
— kjmcfall