Climate

Luxtronik

BenPru/luxtronik · v2026.10.18

HACSLocal polling

Luxtronik integration for Home Assistant

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

Entity	Shows up as	Note
`switch`	Switch or outlet
`climate`	Thermostat
`binary_sensor`	Sensor (motion, contact, leak, smoke…)
`sensor`	Sensor (temperature, humidity, air quality…)
`water_heater`	Water heater (as a thermostat)
`select`	Mode picker (as switches)

What people report

Local support for Luxtronik 2 controllers in Alpha Innotec, Novelan and similar heat pumps, mostly firmware 3.9x. Firmware 1.90/2.90 writes crash the controller, so it is read-only there, and 2.x or Luxtronik1 are poorly supported.

Works3
Partly works3
Not working1

Device	In Home Assistant	What they said	Source
Alpha Innotec Hybrox 16	Works Local	Heat pump type code 90 added Saved copy 🔍 What this fixes #819: an alpha innotec Hybrox 16 reports heat pump type code 90. Our type table (and upstream python-luxtronik's) ended at 88 "LP8V", so the heat pump type sensor and the device model were blank. The manufacturer was blank for the whole LP range too, because no "LP" prefix was mapped. Evidence: the reporter's controller display (Anlagenstatus → Wärmepumpen Typ) reads LP16V, firmware V3.92.3. The nameplate says alpha innotec Hybrox 16. ## ✨ Changes - `lux_overrides.py`: add `89: "LP11V"` and `90: "LP16V"` to `HeatpumpCode.codes`. 90 comes from the display photo; 89 completes … Excerpt saved from GitHub on 2026-10-23.	PR #824 · 2026-10
Alpha Innotec WZSV 62K3M	Works Local	Firmware 3.92.3; options form bug fixed Saved copy Home Assistant Core version: 2026.8.1 Heat pump firmware: 3.92.3 Model: Alpha Innotec WZSV 62K3M ### Bug description Submitting the options form (Settings → Devices & Services → Luxtronik → Configure) with the "indoor temperature sensor" and/or "power consumption sensor" fields left empty raises: `Entity None is neither a valid entity ID nor a valid UUID`. Happens on a fresh config entry, or any time these optional fields aren't set. Since the whole form fails validation, this also blocks saving the update interval. ### Root cause In `schema_helper.py`, `build_options_schema()`, both fields … Excerpt saved from GitHub on 2026-10-23.	PR #743 · 2026-08
Luxtronik firmware 3.89.4	Works Local	Maintainer says new beta should work Saved copy Hi, In one of your latest beta version you mentioned solved fixes for Luxtronik firmware > 3.90. Does it mean that newer development would not work with firmware version like 3.89.4? Currently, I don't like to update the firmware, because when I did it run into major problems and it needs to switch back. Thanks. Klaus Excerpt saved from GitHub on 2026-10-23.	Issue #460 · 2025-10
Alpha Innotec WZS 101 H/K	Partly works Local	Firmware V1.90.0: writes don't trigger DHW demand; integration read-only Saved copy … `luxtronik2.write`/entities, only confirming locally on the panel (even re-confirming an unchanged value, or writing a genuinely new value) triggers heating, WZS 101 H/K, firmware V1.90.0 ## Environment - Heat pump: Alpha Innotec WZS 101 H/K, Luxtronik2 controller - Heat pump firmware: V1.90.0 - Home Assistant: core-2026.8.3 - Integration: installed via HACS (installed_version has shown as 2026.08.29 and 2026.08.30 during troubleshooting, the latest release is simultaneously tagged `latest-release` and `pre-release` on GitHub). Note: the diagnostics dump's own … Excerpt saved from GitHub on 2026-10-23.	Issue #785 · 2026-09
Alpha Innotec/Novelan firmware V1.90.x and V2.90.x	Partly works Local	Writes crash controller; integration made read-only Saved copy 🔍 What this fixes Fixes #831. On Alpha Innotec / Novelan firmware V1.90.x and V2.90.x, every write command on port 8889 crashes the whole Luxtronik controller (forum report). The reported workaround is a firmware downgrade. ## ✨ Changes - `coordinator.py`: new `write_blocked` property, true when the firmware package version is `1.90.x` or `2.90.x`. `async_write` raises a translated `HomeAssistantError` before anything is sent to the heat pump, so all writes (switches, numbers, selects, climate, water heater, timers, services) are blocked. - A warning is logged and a non-fixable Repairs issue … Excerpt saved from GitHub on 2026-10-23.	PR #832 · 2026-10
Luxtronik MSW2-9S	Partly works Local	No SG2 status; manual EVU2 switch added Saved copy 🔍 What this fixes The last open piece of #500 (step 3 of the plan agreed with @siedi in that thread). On the MSW2-9S, the SmartGrid status can never show a state that needs the SG2 contact closed. The controller reacts to SG2 normally but reports it nowhere the integration can read: - calc 185 `ID_WEB_HZIO_EVU2` stays 0 whatever the contact does, confirmed by two owners (@Zaschii, SG2 wired permanently closed; @mhuiskes, SG2 switched by a relay); - the RFV terminal that carries SG2 on Luxtronik 2.0 (#669) reads 0.0 on these units. The gate is an explicit model list rather than a data test. … Excerpt saved from GitHub on 2026-10-23.	PR #812 · 2026-09
Alpha Innotec LW 150H-A	Not working Local	Firmware V2.40 gives unpack buffer error; not planned Saved copy … the "unpack requires a buffer of 4 bytes" error. I've done extensive debugging and believe it's a firmware incompatibility. My Setup: * Heat Pump Model: Alpha Innotec LW 150H-A * Luxtronik Firmware Version: V2.40 * Home Assistant Version: 2024.10.4 * Home Assistant Operating System: 12.1 * Luxtronik Integration Version: 2024.9.30 Debugging Steps & Findings: 1. Connection Works: `curl -v telnet://10.0.0.3:8889` confirms a successful TCP connection. 2. UI Error: The Home Assistant UI shows `unpack requires a buffer of 4 bytes`. 3. No Error in Logs: Even with debug logging enabled for … Excerpt saved from GitHub on 2026-10-23.	Issue #365 · 2025-07

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Local polling

Talks to the device on your network, asking it for updates every so often.

Found automatically over

DHCP

Details

Installs (analytics)	686 (0.1%)
GitHub stars	172
Latest version	2026.10.18 (2026-10-19)
Set up in the UI	Yes
Maintainers	@BenPru, @rhammen, @AJediIAm
License	MIT

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.

Sources

Documentation: https://github.com/BenPru/luxtronik
Source code: https://github.com/BenPru/luxtronik
Issues: https://github.com/BenPru/luxtronik/issues
HACS: https://hacs.xyz