ouman-eh-800-api
Async Python client for communicating with the Ouman EH-800 heating controller.
Installation
pip install ouman-eh-800-api
Usage
import asyncio
import aiohttp
from ouman_eh_800_api import (
OumanEh800Client,
L1BaseEndpoints,
SystemEndpoints,
HomeAwayControl,
OperationMode,
)
async def main():
async with aiohttp.ClientSession() as session:
client = OumanEh800Client(
session=session,
address="http://192.168.1.100",
username="user",
password="password",
)
# Authenticate
await client.login()
# Detect the registries that match the device's current configuration
# (curve type, room sensor, L2, relay mode) and read every endpoint
# in one batch.
registry_set = await client.get_active_registries()
values = await client.get_values(registry_set)
print(f"Outside temp: {values[SystemEndpoints.OUTSIDE_TEMPERATURE]} °C")
print(f"L1 supply temp: {values[L1BaseEndpoints.SUPPLY_WATER_TEMPERATURE]} °C")
# Set home/away mode
await client.set_endpoint_value(
SystemEndpoints.HOME_AWAY_MODE, HomeAwayControl.HOME
)
# Set L1 operation mode
await client.set_endpoint_value(
L1BaseEndpoints.OPERATION_MODE, OperationMode.AUTOMATIC
)
await client.logout()
asyncio.run(main())
Features
- Async API using aiohttp
- Read sensor values (temperatures, valve positions, etc.)
- Control heating circuits (operation mode, temperature curves, etc.)
- Set home/away mode
- Support for L1 and L2 heating circuits
- Support for optional room sensors
- Detect whether the summer function is holding the L1 valve closed
Available Registries
The library splits endpoints into small "fragment" registries. For a given
device configuration only a subset is active; client.get_active_registries()
returns the right composition automatically. Manual composition via
OumanRegistrySet([...]) is also supported.
| Registry | Description |
|---|---|
SystemEndpoints |
System-wide (outside temp, home/away, relay mode, etc.) |
L1BaseEndpoints / L2BaseEndpoints |
Per-circuit endpoints always queryable when the circuit is in use |
L1ThreePointCurve / L1FivePointCurve |
L1 heating-curve setpoints (mutually exclusive) |
L2ThreePointCurve / L2FivePointCurve |
L2 heating-curve setpoints (mutually exclusive) |
L1NoRoomSensor / L1RoomSensor |
L1 endpoints whose IDs differ depending on whether a room sensor is installed |
L2NoRoomSensor / L2RoomSensor |
Same for L2 |
L1ConstantTempMode |
Setpoint exposed when L1 heating mode is constant-temperature controller |
RelayPumpSummerStop, RelayTemperature, RelayTempDifference, RelayL1ValvePosition, RelayTimeProgram |
Relay-control override; one active depending on the configured relay mode. Each fragment also reports the relay state (PUMP_RUNNING or RELAY_ON) |
ReturnWaterSensor, AccumulatorSensor, BoilerSensor |
Optional temperature measurements on channels 3-5; active when a channel is assigned to that measurement |
Requirements
- Python 3.13+
- aiohttp
Contributing
Pull requests for new features or bug fixes are welcome. Please open an issue first to discuss major changes.
License
Metadata
Release files for ouman-eh-800-api 2.0.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 |
|---|---|---|---|---|
| ouman_eh_800_api-2.0.0.tar.gz | 14.3 kB | With provenance | Details for ouman_eh_800_api-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ouman_eh_800_api-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for ouman_eh_800_api-2.0.0-py3-none-any.whl |
Total release size: 30.3 kB
Release files / ouman_eh_800_api-2.0.0.tar.gz
| Download URL | ouman_eh_800_api-2.0.0.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6c2974dd397ea5e40e78f9f6cc6bc9220af3011b3caf315e995cde10f4ab814e
|
|
BLAKE2b-256 checksum How to use checksums |
90d8beae29d43ba33dee01ed2c4f87d9f2360d8dcaacfb08017f1f647dc9420b
|
| 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 Nov 2, 2026.
Transparency logRelease files / ouman_eh_800_api-2.0.0-py3-none-any.whl
| Download URL | ouman_eh_800_api-2.0.0-py3-none-any.whl |
|---|---|
| Size | 16.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
30d720c167bbe8fab47c681a222a2b1a1d0f92251565cfe688c24d4b57804aa6
|
|
BLAKE2b-256 checksum How to use checksums |
2501b4ad28ca5400adeb7cb9f749ae8c079fcb67a491ef0741ed405e8603d121
|
| 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 Nov 2, 2026.
Transparency logSecurity for ouman-eh-800-api 2.0.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
Both files in this release have been uploaded with provenance metadata.
Attestation for ouman_eh_800_api-2.0.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 Nov 2, 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.