Skip to content

Feature request: configurable energy flow logic #56

@Nero201988

Description

@Nero201988

Feature request: configurable energy flow logic

My real system flow is:

  • PV → battery
  • battery → house
  • grid → house
  • house → grid (export if surplus)
  • no direct PV → house
  • no direct battery → grid

The battery always supplies the house first.
Only if the house does not need the available energy, the surplus flows from the house to the grid.

Example 1 (battery supplying the house):
The battery has sufficient charge and can dynamically provide power (e.g. controlled by a Shelly or similar device).
If the house currently needs 1800 W and the battery provides 800 W, then:

  • 800 W come from battery → house
  • 1000 W come from grid → house

Example 2 (battery full, PV surplus):
If the battery is already full and the PV produces 800 W while the house only needs 200 W, then:

  • 200 W go to house
  • 600 W go from house → grid

There is no direct PV → house connection and no direct battery → grid connection in this topology.
All energy always passes through the house node.

Currently the card always visualizes an implicit PV → house flow.
In my setup this is incorrect and cannot be represented.

Many real installations with a battery are wired this way:
PV is connected to the battery first, and the house is supplied from the battery.
However, most energy flow visualizations I tested — including the Home Assistant Energy Dashboard — assume a direct PV → house path and cannot represent this topology.

Request:
Option to disable PV → house and allow explicit flow definition:

  • pv → battery
  • battery → house
  • grid → house
  • house → grid

This would allow accurate visualization for systems where PV always charges the battery first and the house is supplied via the battery.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions