Heat Pump Optimizer blueprints

tvofi · September 16, 2026, 12:04pm

Heat Pump Optimizer is a custom integration (HACS) that plans heat-pump
space heating and hot water 24 hours ahead against hourly electricity
prices and a self-learning model of your house, publishing the plan on
sensors for your own automations to act on.

Three blueprints, one per worked example in the documentation:

Charge an EV from grid headroom — starts a charger switch while the
Cost Power Headroom sensor (min(main fuse, capacity threshold) −
current house draw, clamped at zero, in kW) sits above your start
threshold, stops it below your stop threshold.
https://raw.githubusercontent.com/tvofi/heatpump_optimizer/main/blueprints/automation/charge_ev_from_grid_headroom.yaml
Economy mode through the evening price peak — switches the optimizer’s
operating mode when the current electricity price crosses your
expensive threshold, and back when it falls. Economy rides out
expensive hours up to 1.5 °C below the comfort floor (never below
15 °C); auto hands full optimization back.
https://raw.githubusercontent.com/tvofi/heatpump_optimizer/main/blueprints/automation/economy_mode_on_price_peak.yaml
Notify when a manual plan takes over — raises a persistent
notification while an apply_manual_plan override pins the heating
slots, with the expiry time from the plan sensor’s manual_override
attribute.
https://raw.githubusercontent.com/tvofi/heatpump_optimizer/main/blueprints/automation/notify_on_manual_plan.yaml

Import any of them from Settings → Automations & Scenes → Blueprints →
Import Blueprint. Each blueprint takes the sensor and the thresholds as
inputs, so nothing is hard-coded to the default entity ids. The same
examples as inline YAML, with the sensor’s availability rules spelled out:

github.com/tvofi/heatpump_optimizer

docs/automations.md

cb30d98bf

# Automations

Without a heat pump on/off switch — and without the ECL110 or
frequency-control paths — the optimizer's plan is published on sensors for
your own automations to act on ([configuration.md](configuration.md) says
exactly that where the trade-off is made). The examples below are complete and
use only entities and services this integration actually creates. The entity
prefix follows the name you gave the entry: these examples assume the default
`Heat Pump Optimizer`, so they read
`sensor.heat_pump_optimizer_power_headroom` — change the prefix if you named
yours differently.

## Automation example: charge an EV from the Cost Power Headroom sensor

The Cost Power Headroom sensor (`sensor.heat_pump_optimizer_power_headroom`) is
`min(main fuse, capacity threshold) − current house draw`, clamped at zero, in
kW — a number an EV charger can follow. It stays unavailable only while
nothing bounds the house: set a main fuse size in the options, or enable a
capacity tariff, and it appears — the fuse is unset by default, so a
tariff-only install has the sensor too. Until the month's first metering

This file has been truncated. show original

Sir_Goodenough · September 16, 2026, 5:38pm

Hello tvofi,
Thanks for contributing to the community with a new Blueprint.
I have a suggestion for you. Many people who are not familiar with directory structures will have problems installing this without the Home Assistant MY tools.
Adding a MY link for this Blueprint to your top post would help them a lot.
Here is the link to make that.
Create a link – My Home Assistant