Repository navigation
Coordinator and runtime updates
Once a TROVIS config entry has been set up, normal operation is intentionally simple: one coordinator refreshes the shared controller state and all entities use that result.
This page is the single reference for polling, availability, communication errors and runtime recovery.
The Home Assistant integration uses one DataUpdateCoordinator per TROVIS
config entry.
The current integration polls the controller at a fixed interval of 60 seconds.
The coordinator:
- calls the shared
Trovis557xinstance, - lets the library perform the planned grouped reads,
- publishes the refreshed device state to all entity platforms.
Entities do not poll independently.
DataUpdateCoordinator
│
▼
Trovis557x.async_update()
│
▼
library components / grouped reads
│
▼
ModbusUnit
│
▼
connection
This keeps controller I/O serialized and predictable.
Transport and protocol errors are represented through the
modbus-connection exception hierarchy.
At the Home Assistant boundary, normal communication failures are converted to
UpdateFailed.
Conceptually:
try:
await device.async_update()
except ModbusError as err:
raise UpdateFailed(...) from errThe result is normal Home Assistant coordinator behavior:
- the update fails,
- affected entities become unavailable,
- the config entry remains loaded,
- a later coordinator refresh tries communication again.
The integration does not reload the complete config entry for every temporary Modbus failure.
This is intentional. A transient socket loss should not recreate the full controller model, device tree, and entity platforms.
The connection is closed when the config entry is actually unloaded.
Temporary transport errors are normal runtime failures.
The coordinator reports a failed refresh and lets the existing connection try again on a later update. Reloading the complete config entry for every dropped socket would unnecessarily recreate the controller model, device tree and entity platforms.
A config-entry reload is therefore a lifecycle action, not the normal reconnect strategy.
Entities do not communicate with the TROVIS independently. They consume the state refreshed by the shared coordinator.
That means a communication problem affects the shared controller update rather than causing individual entities to open their own Modbus connections.
Entity creation and identity rules are 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