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
- Network connection to the ISG WEB
Installation
The package is available in the Python Package Index.
$ pip install pystiebeleltron
Example usage of the module
The sample below shows how to use this Python module (api for wpm heat pumps).
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).
import asyncio
from modbus_connection import ModbusTcpParams
from modbus_connection.pymodbus import ModbusConnection
from pystiebeleltron.wpm import WpmStiebelEltronAPI
async def main():
connection = ModbusConnection(ModbusTcpParams(host='IP_ADDRESS_ISG', port=502))
api = WpmStiebelEltronAPI(connection.for_unit(1))
await api.async_update()
print(f"outside temperature: {api.system_values.outside_temperature}")
print(f"water comfort target temperature: {api.system_parameters.comfort_temperature_dhw}")
# Writing a register:
await api.system_parameters.write("comfort_temperature_dhw", 50)
await connection.close()
asyncio.run(main())
License
python-stiebel-eltron is licensed under MIT, for more details check LICENSE.
Release files for pystiebeleltron 0.7.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pystiebeleltron-0.7.2.tar.gz | 18.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pystiebeleltron-0.7.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 40.8 kB
Release files / pystiebeleltron-0.7.2.tar.gz
| Download URL | pystiebeleltron-0.7.2.tar.gz |
|---|---|
| Size | 18.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1cbcdffdd4bf8234c139f311934e1f5cafef061f71013e00d6dade701f53549e
|
|
BLAKE2b-256 checksum How to use checksums |
07fcbabcd9d069481b82ed3153e2d459c09849096511820059bbf31ab21110ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 18, 2026.
Transparency logRelease files / pystiebeleltron-0.7.2-py3-none-any.whl
| Download URL | pystiebeleltron-0.7.2-py3-none-any.whl |
|---|---|
| Size | 22.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
da38256606d2048d3d663b48ef4470a877a020ed4ebb89ac74a324290b7b2dfa
|
|
BLAKE2b-256 checksum How to use checksums |
3fe6644b7ff3e7799f537a6bdde9b69a2407aac80e86750628ffae630662ff66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 18, 2026.
Transparency log
