Energy Dashboard: Add native Heat Pump support (electric input + delivered heat output, COP and cost metrics)

[derolli1976]

What type of request is this?

New dashboard feature

Existing card or feature name

{"Card" => "Energy"}

Describe the enhancement

Add native Heat Pump support to the Energy Dashboard so heating can be modeled correctly as two separate energy flows:

1. Electrical input energy (kWh) consumed by the heat pump (from a dedicated sub meter or an existing consumption sensor).
2. Delivered thermal energy (kWh) produced by the heat pump (from the heat pump integration or a heat meter).

The dashboard should let the user configure which electricity energy sensor represents the heat pump input (or choose an already calculated heat pump consumption sensor). Based on these two entities, the dashboard should provide built in KPIs such as COP, electricity consumption, heating cost, and cost per kWh of delivered heat.

This avoids misusing the existing “Gas consumption” section for heat pump output and provides correct semantics and charts for heat pump based heating.

Use cases

• Track heat pump performance: show COP over time for day, week, month, year based on delivered heat divided by electricity input.
• Track heating electricity use: attribute the correct kWh and cost to the heat pump, especially when a dedicated heat pump meter exists.
• Compare efficiency and cost: show “cost per kWh heat” and “cost based on electricity consumption” to evaluate settings, weather impact, or system changes.
• Support mixed setups: some users have separate meters for the heat pump, others derive consumption from whole home monitoring. Both should be supported by selecting an input energy entity.
• Enable consistent reporting: avoid confusing labels and incorrect totals that happen when mapping heat output to “gas”.

Visual examples

No mockups available yet.

Suggested UI direction:

• Add a new “Heat pump” section in the Energy configuration where each heat pump is an item.
• Each item selects:
  ** Electricity input energy entity (kWh)
  ** Delivered heat energy entity (kWh)
  ** Optional: tariff or price source
• Add charts in the Energy dashboard:
  ** Electricity consumed vs heat delivered
  ** COP trend (daily or weekly aggregation)
  ** Heating cost and cost per kWh heat

Anything else?

Notes and acceptance criteria:

• Entity requirements should match existing Energy Dashboard expectations (long term statistics, energy device_class, total_increasing, unit kWh).

• Calculations:

** COP for a period = delivered_heat / electricity_consumed
** Cost = electricity_consumed * electricity_price
** Cost per kWh heat = cost / delivered_heat
** Handle divide by zero by showing “not available”.

• Support multiple heat pumps.
• Optional future extensions:
  ** Separate delivered heat for space heating vs DHW if available
  ** Include or exclude auxiliary electric heater consumption

Current workaround:
Users map delivered heat to “Gas consumption” or build custom template sensors and Lovelace charts, but this loses correct semantics and a consistent built in experience.

[ximex]

also split up heating and cooling

[TCWORLD]

I've been planning on having a look at trying to contribute something like this for a while, finally decided to have a go.

If we're adding a "Heating" dashboard, it would be nice if it could work for different heating sources than just a heat-pump (although like you that's why I want it). So I'm trying to think about how that might look.

Heating systems I can think of

• Gas/Oil/etc - energy in is based the fuel source (currently only gas, but that's a separate discussion). Input energy may not be possible to track if no separate meter, so needs to be optional
• Solar (not PV) - energy input from the sun (obvs) is hard to track, so for such cases we need "input" energy to be optional
• Heat-pump - energy input from electricity (plus the "free" energy from air/water/ground) - for these we want COP measurements to indicate .
• Electric heaters - energy input == energy delivered = electricity consumption (includes e.g. immersion heater for DHW).

There are also questions then about tracking cooling, so the name "Heating" for such a dashboard may not be ideal. Essentially the graphs there are basically the same, just the direction the energy is flowing.

In terms of tracking energy costs, for those which use electricity this is already tracked on the electricity dashboard, the same for gas. Do we need a specific tracking for heating? If so I guess we'd have to simply not want to show heating on the overview dashboard tally of costs to avoid double consumption?

For real-time, would we want something that can calculate heating power delivered from supply/return temps and flow rate, though that might be a bit too advanced for many users, so could just allow a "power delivered" sensor and leave it up to integrations that produce heating data provide that calculation.

[catdogmaus]

• Solar (not PV) - energy input from the sun (obvs) is hard to track, so for such cases we need "input" energy to be optional

I have one of those things and it has Consumption, Consumption Today, Today's Energy, Collector Total Energy so adding it theoretically is strait forward. I am whining for years why they dont add other so obvious heating options to energy dashboard.