Luxtronik 2.0 – bringing an older heat pump into the Home Assistant era

Luxtronik 2.0 – bringing an older heat pump into the Home Assistant era

Auf Deutsch lesen →

Heat pumps are long-lived. A unit with a Luxtronik 2.0 controller – found in systems from Alpha Innotec, Novelan or ait, among others – runs reliably in the basement for a decade and a half. The snag: getting this older controller generation comfortably into a smart home used to be fiddly. That is exactly what luxtronik2-hass is for: enter the IP address, done – no YAML tinkering, everything through the UI.

From by-product to main product

The project didn’t start as an integration at all, but as a Modbus proxy: a small translator turning Luxtronik’s idiosyncratic binary protocol into Modbus TCP – handy, for instance, to connect the heat pump to the charging tool evcc. Building that proxy led to the realisation that a native Home Assistant integration is the better path. So the priorities were flipped: today the integration talks to the controller directly, and the proxy has become an archived footnote.

More than just reading values

luxtronik2-hass surfaces more than 30 entities – temperatures, operating modes, setpoints, a heat-quantity meter for the energy dashboard. More interesting are the functions that require real heat-pump knowledge:

  • Solar boost: when your PV system is feeding into the grid, the integration raises the flow setpoint – surplus sun goes into the buffer tank as heat instead of into the grid for little money.
  • Bath boost: hot water on demand, with a progress indicator.
  • Night pause for heating, and the hot-water hysteresis read straight from the controller parameter.

Because a Luxtronik controller allows only one connection at a time, the integration handles clean connection and write management in the background – so it doesn’t collide with other access.

An honest classification

Two things belong in the picture. First: Home Assistant already has an older Luxtronik integration maintained by others. luxtronik2-hass is deliberately a standalone alternative with its own focus (smart-energy features, single-connection handling) – not a fork. Second: it is a young one-person project. Its maturity should be read as exactly that – even though the version has already reached productive territory (v1.2.x).

Three attempts to reach the HACS store

The road into the HACS default catalogue was instructive: on 13 April 2026 it took three submission attempts in a single day before the automated checks (including “hassfest”) went green. After that it took until 2 July 2026 for the acceptance to be finally merged – about two and a half months. Since then luxtronik2-hass installs normally via HACS search. It is not (yet) in Home Assistant Core – it lives as a HACS extension.


Do you run a heat pump with a Luxtronik controller? Let me know which function you’ve been missing in Home Assistant.


Sources (selection):