Wavin Sentio Connect

An event-driven Python client for the Wavin Sentio floor heating controller over Modbus TCP, built on modbus_event_connect.

The register map is complete for the location, all 16 rooms and all 64 peripheral slots, modelled from the official Sentio Modbus manual. Connecting finds out which rooms and peripherals your installation actually has; you subscribe to the values you care about and are told when one changes - with its quality, so "offline", "no reading" and a real value never look alike.

Installation

pip install wavin-sentio-connect

Everything you use comes from wavin_sentio_connect: the client and its values, the errors, the connection a controller can share, and, in wavin_sentio_connect.testing, a simulated controller for your own tests. modbus_event_connect is installed with it; nothing needs importing from it.

Enabling Modbus on the controller

Modbus is disabled by default. Enable it from a Sentio Display:

System | Installer settings | Modbus configuration | Modbus TCP

The controller restarts afterwards. It uses DHCP; its hostname is Wavin Sentio CCU#[last four digits of the serial number].

Usage

import asyncio
from wavin_sentio_connect import RoomPointKey, create_client, room_key, rooms

def on_change(key, old, new):
    print(f"{key}: {new.value} ({new.quality.name})")

async def main():
    client = create_client("<device-ip>")
    await client.connect()              # finds the installed rooms and peripherals

    for room in rooms(client):
        print(room.number, room.name, "dummy" if room.is_dummy else "")
        client.subscribe(room_key(room.number, RoomPointKey.TEMP_AIR_CURRENT), on_change)

    while True:                         # you own the clock; the library owns the plan
        await client.poll()      # reads only what is due - free when nothing is
        await asyncio.sleep(1)

asyncio.run(main())

When connect() returns, client.points holds exactly what this installation has - a room that was never set up is not there, so nothing is built for it. Nor is what the controller says a room lacks: a dummy room ("no thermostat or sensor installed") has no temperature, humidity or dew point, and a room not associated with radiators, underfloor heating, drying, thermal integration or ventilation has no state or blocking source for it. Nor has a peripheral what its type is known to lack, as NOT_SUPPORTED lists: the manual's wired RT-201, RS-211 and ET-210, the LCD-200 and the EU-208-A have no signal strength. rooms(client) and peripherals(client) describe the installation from values already read, with no extra requests.

When the installation changes, poll() finds it; nobody needs to connect again. What each scan read is read again at PollRate.SCAN, and where it has changed, only that part is scanned again:

client.subscribe_points(callback) is told the keys gained and lost - a room set up, a peripheral paired or removed.

Every value is a DataValue: value, quality and timestamp (UTC).

How often values are read

Every point has a poll rate, and the library reads it when it is due:

Override any of them, or a single key:

from wavin_sentio_connect import PollRate
client.set_poll_interval(PollRate.FAST, 5)
client.set_poll_interval("room_4_temp_air_current", 2)
await client.refresh(PollRate.STATIC)        # re-read the static values now

Only what something wants is read: a subscriber, or client.set_polling(key).

Writing

await client.write(room_key(1, RoomPointKey.TEMP_AIR_TARGET), 21.5)
await client.write(room_key(1, RoomPointKey.LOCK), RoomLock.HOTEL)   # LOCKED / HOTEL / UNLOCKED

• A value of the wrong type is a type error before the program runs: the lock takes a RoomLock, a temperature a float.
• A value is also checked before anything is sent: its range, its states, and the controller's "no reading" sentinel, which could never be read back.
• Writes are sent in order. Tapping + five times sends the first value and the last, not all five.
• The written point is read back, so subscribers see what the controller holds rather than what was asked for. A write that changes the rooms' regulated targets - vacation, standby, a room's setpoint, mode or preset - reads those targets again too.
• The controller answers SERVER_DEVICE_BUSY (0x06) while it stores a change; the manual says such a request "shall be repeated again", and the library does, with backoff.
• client.status(Status.WRITE_PENDING) - which client.subscribe_status follows - is true from the moment a write is asked for until the last one has finished.

For monitoring only, create the client read-only; every write is then refused before it reaches the controller:

client = create_client("<device-ip>", read_only=True)

Alarms

Every alarm and warning the manual documents for the location, the rooms and the peripherals is a key: system_warning, system_error, and per room and peripheral ..._warning, ..._error, ..._low_battery and room_{n}_peripheral_lost / peripheral_{n}_lost.

The manual describes the location's two bits as covering the whole system ("A problem is pending in whole system"). Those two are always read at the FAST rate; when either changes, every alarm someone subscribes to is read at once. Each alarm is also read by itself at the RARE rate, in case a controller does not reflect it in the system's bits.

Sharing a connection

To put the controller on a connection the host already owns - a gateway shared with other devices - use create_client_on:

from wavin_sentio_connect import ModbusTcpConnection, create_client_on

connection = ModbusTcpConnection("<device-ip>")
client = create_client_on(connection, unit_id=1)

The client is asynchronous end to end - no threads, nothing that blocks the event loop - and owns no timer: the application calls poll() from its own loop.

Keys and addressing

Every point has its key in LocationPointKey, RoomPointKey or PeripheralPointKey, with the type of its value. A location point's is its whole key; a room's or a peripheral's becomes one with the instance:

from wavin_sentio_connect import ROOM, LocationPointKey, RoomPointKey, room_key

client.value(LocationPointKey.VACATION_ENABLE)               # key "vacation_enable"
for n in client.instances(ROOM):                             # the rooms this installation has
    client.value(room_key(n, RoomPointKey.TEMP_AIR_CURRENT))  # key "room_4_temp_air_current"
    client.value(room_key(n, RoomPointKey.STATE))             # a RoomState, such as HEATING

A room point's key is the same in every room, so code that handles RoomPointKey.TEMP_AIR_CURRENT once handles it in all of them; RoomPointKey.all() lists them. UNITS is every unit a Sentio point has. Key strings never change; new points only add keys.

A state reads as its member of the enum the manual's values give: RoomState, BlockingSource, RoomType, RoomMode, RoomModeOverride, TemperaturePreset, RoomLock, HeatingCoolingMode, HeatingCoolingModeOverride, DeviceType, ModbusMode, UpdateMode or PeripheralType, and is written as one. A number the manual does not name reads as NO_DATA, and the value's .raw holds the number the controller sent. Standby, vacation and daylight saving, which the manual gives as 0 and 1, are bool; their "no value", 255, reads as NO_DATA too.

The model is in _model.py; every key is declared there with its address and encoding.

The manual's "Modbus Address" column holds the addresses themselves, so its numbers are used unchanged:

Peripheral slots are not stable identities - the controller reorders them when peripherals are learned or unlearned. Use peripheral_{n}_serial_number to recognise a device, and peripheral_{n}_owner (0 = location, 1–16 = room) to find the room it belongs to.

Two room values are easy to confuse: room_{n}_temp_air_target is the user's setting, and room_{n}_temp_air_target_active is the target the controller is regulating to right now - different under standby, vacation or a schedule.

Documentation

• docs/sentio-modbus-reference.md - the protocol: register tables, data types, error handling, enumerations.
• docs/sentio-registers.csv - all 344 documented registers, one row each.

Known gaps

• Only the location, room and peripheral objects are modelled. Outdoor, DHW, ITC, HCC, buffer tank, ventilation and dehumidifier objects are documented in the CSV but not yet wired.

Disclaimer

Wavin Sentio Connect is provided "as is", without warranty of any kind. The authors and contributors are not responsible for any damage or data loss that may occur from using this library. Users are solely responsible for ensuring the proper and safe operation of their Modbus devices.

This project is not affiliated with or endorsed by Wavin.

License

MIT. See LICENSE.