Repository navigation
Writing and write access
Reading a controller is relatively harmless. Writing to a heating controller is different, so the integration deliberately keeps the Home Assistant safety gate separate from the controller-side write logic.
This page documents the technical write path. For normal users, see Changing-settings-safely.
Writing is part of the integration architecture because it crosses the boundary between Home Assistant and the controller model.
Writes pass through two different safety layers:
flowchart TD
ENTITY["Home Assistant entity write"]
GATE["Write access switch"]
LIB["trovis-modbus write API"]
MODBUS["Modbus write"]
CTRL["Controller"]
ENTITY --> GATE
GATE --> LIB
LIB --> MODBUS
MODBUS --> CTRL
The controller-level Write access switch is the Home Assistant safety gate.
After that gate has allowed a write, trovis-modbus remains authoritative for
the controller-side write semantics and validation.
The integration should therefore use the library's public write API instead of writing raw Modbus addresses from an entity.
The exact Home Assistant entity platforms used for writable datapoints are documented in Devices-and-entities.
For user-facing information about enabling and using writes, see Changing-settings-safely.
For the library-side write model, see Datapoints, reading, and writing.
A Home Assistant entity should never contain its own TROVIS register or coil write such as:
await unit.write_register(123, value)The datapoint, its valid range, encoding, access requirements and write
preconditions belong in trovis-modbus.
The integration should only decide how that writable datapoint is represented in Home Assistant and whether the Home Assistant Write access gate currently allows the request.
This keeps the same controller-side write rules usable by Home Assistant, the library CLI, tests and other future consumers.
Depending on the datapoint, writable values can appear as normal Home Assistant platforms such as:
-
number, -
select, -
switch, -
date, -
time, -
climate, -
water_heater.
The entity structure itself is documented in Devices-and-entities.
Disclaimer: Any information on this wiki is informal advice only. It is not supported nor endorsed by Samson, Sauter, YADOS, Pewo or any other equipment maker or OEM. There is no warranty expressed or implied: you take sole responsibility for everything you do with your heating controller.
-
Wozu dieses Projekt?
What is this project about?
-
Wie funktioniert das?
How does it work?
- Was wird benötigt? Kosten?
What's required? Costs?
- Supported controllers
- Connecting your TROVIS
- Installation and setup
- Current limits and migration
- Troubleshooting
- Architecture and internals
- Connections and transports
- Config flow and reconfiguration
- Coordinator and runtime updates
- Devices and entities
- Writing and write access
- Development and testing
- LAN/WLAN
USR-TCP232-T2, USR-TCP232-410S, USR-K7, USR-DR301 (Hutschiene), Elfin-EE10 (WLAN) - USB
AZDelivery FT232RL, Waveshare USB 2 RS232/485/TTL - ESP
ESP-01, Wemos D1 - SPS
S7 1200, Wago 750-889 - KNX
Masifi Modbus Gateway
- Edomi
- espHome/HomeAssitant
- FHEM
- HomeAssistant
- ioBroker
- KNX
- Loxone
- NodeRed
- openHAB
- SIMATIC Step7
- smarthomeNG
- Tasmota/MQTT
- Wago CODESYS
Wiki - Start