python-stiebel-eltron
Python API for interacting with the STIEBEL ELTRON ISG web gateway via modbus for controlling integral ventilation units and heat pumps.
This module is based on the STIEBEL ELTRON modbus user manual, but is not official, developed, supported or endorsed by Stiebel Eltron GmbH & Co. KG. For questions and other inquiries, use the issue tracker in this repo please.
Requirements
You need to have Python installed.
- STIEBEL ELTRON Internet-Service Gateway ISG WEB with enabled modbus module
- You can call the STIEBEL ELTRON support, if your ISG does not have the modbus module enabled. They upgraded mine for free.
- STIEBEL ELTRON heatpumpt (compatible). Successfully used devices:
- LWZ504e
- LWZ304
- Tecalor THZ 7.1 IBC Topline with ISG Connect (reported as
LWZ_R290, WPM register map). Ventilation registers (WpmVentilationValues,WpmVentilationParameters) read only so far; writing the ventilation stages is untested
- Network connection to the ISG WEB
Installation
The package is available in the Python Package Index.
Base install:
$ pip install pystiebeleltron
Install with the optional tmodbus backend used in the example below:
$ pip install "pystiebeleltron[tmodbus]"
Example usage of the module
The examples/ directory contains runnable examples for WPM and LWZ heat pumps. They use the optional tmodbus backend, so install pystiebeleltron[tmodbus] first.
The API takes a ModbusUnit. You own the connection: build it, hand a unit to the API, and close it when done. Building it performs no I/O — the first read establishes the link, and a link that drops later is re-established on the next request, over the same unit handle. Each register block is a component exposed on the API, and values are read as typed attributes (None when the register is unavailable).
Pass the IP address of the ISG gateway to the selected example:
./examples/wpm-example.py 192.168.1.10
./examples/lwz-example.py 192.168.1.10
The WPM example also demonstrates writing and restoring the DHW comfort temperature. The LWZ example reads room and outside temperatures and the current operating mode.
For a read-only WPM library check outside Home Assistant, use examples/wpm-readonly-check.py in a separate virtual environment. Select --family wpm, wpm3 or wpm3i, and pass --confirm-read-only. It performs one poll by default (--polls accepts at most three); --raw exercises raw reads without printing register values. The output contains package versions, a retry-module fingerprint and request outcomes, excluding host addresses and register values. The wrapper permits only input and holding reads and rejects all write operations. This checks the library, not Home Assistant compatibility.
WPM API polls retry an illegal-address input or holding read at most once from a lower start answered directly in the same register space and poll, when the expanded read fits within 125 registers. Healthy reads and writes are unchanged; LWZ does not opt in. A rejected block costs one failed original request and at most one additional read on every poll. A successful retry does not establish that the target registers exist; unavailable words still decode as None.
Errors a caller sees
get_controller_modelraisesStiebelEltronModbusErrorwhen the identification register cannot be read or comes back empty, andUnknownControllerModelError(with.model_id) for an id this library does not know.async_updateandasync_read_rawraise themodbus_connectionerrors unchanged:ModbusErrorand its subclasses such asModbusConnectionError,ModbusTimeoutErroror anIllegalDataAddressErrornaming the refused block. The one exception is an optional block a controller refuses with illegal data address before it ever answered it; that block is dropped and the poll goes on, as described above.writeraisesValueErrorfrom the field's validator for a value outside its documented range,AttributeErrorfor an unknown or read-only field, and themodbus_connectionerrors for a failed transfer.
License
python-stiebel-eltron is licensed under MIT, for more details check LICENSE.
Metadata
Release files for pystiebeleltron 0.10.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pystiebeleltron-0.10.0.tar.gz | 21.6 kB | With provenance | Details for pystiebeleltron-0.10.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pystiebeleltron-0.10.0-py3-none-any.whl | Python 3 | none | any | Details for pystiebeleltron-0.10.0-py3-none-any.whl |
Total release size: 48.1 kB
Release files / pystiebeleltron-0.10.0.tar.gz
| Download URL | pystiebeleltron-0.10.0.tar.gz |
|---|---|
| Size | 21.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
123a613070265bf2ee45c15db4d6fd2f7973538aecc32ca84787969602dfb32d
|
|
BLAKE2b-256 checksum How to use checksums |
979473b1b1c613136a66e4b1a5e369e200bbe07f18d63b0de20fe3f91c4e2872
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logRelease files / pystiebeleltron-0.10.0-py3-none-any.whl
| Download URL | pystiebeleltron-0.10.0-py3-none-any.whl |
|---|---|
| Size | 26.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3671944bd6c8c303691aec988a2bd44976d6fe1d2f771276ab98b817fd684005
|
|
BLAKE2b-256 checksum How to use checksums |
f0bc1218cc6722a32c11f9631513888f912ccf54d13bd1533737d16e460ce6ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logSecurity for pystiebeleltron 0.10.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pystiebeleltron-0.10.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.