Repository navigation
Current Limits and Migration
The integration is designed primarily for:
- monitoring temperatures, pumps, valves, operating modes, faults, and other controller state,
- representing the detected controller and hydronic subsystems as normal Home Assistant devices and entities,
- changing selected operating modes, setpoints, heating-curve values, temperature limits, controller date/time, and supported subsystem parameters,
- integrating an already commissioned TROVIS installation into automations and dashboards.
It deliberately does not attempt to:
- replace the TROVIS controller's internal heating logic,
- reproduce the complete physical controller user interface,
- expose every possible CO/PA parameter, time program, service function, and firmware-specific special case,
- infer arbitrary electrical wiring that is not represented by the controller's model and configuration,
- own or configure the physical Modbus transport.
The exact entity set remains model-, hydronic-system-, function-, parameter-, and sensor-assignment dependent.
The entity structure is determined during initial setup and reconfiguration. Physical sensors or optional functions that become available later are not added dynamically during normal polling.
Run Reconfigure after changing the controller's system code, sensor/input assignments, or relevant functions. Newly detected sensors are added to the stored set; previously known sensor entities are retained to avoid unnecessary removal after a temporary invalid reading.
The integration polls the controller every 60 seconds. It does not currently provide a user-configurable scan interval per controller or entity.
climate and water_heater are convenience views over the normal library-backed
entities. They intentionally expose only the subset that maps cleanly to the
Home Assistant platform model. Their absence or limited feature set does not
mean that the corresponding readable values are unavailable as normal entities.
The current implementation depends on the separate Home Assistant
modbus_connection integration for the shared physical connection. The TROVIS
controller model and entity implementation are kept independent of that provider
so a future shared Home Assistant Modbus API can be adopted without redesigning
the hydronic model.
Earlier beta versions used technical identities that no longer match the role-aware Rk and physical-sensor model:
- former
hk1throughhk3identities were replaced byrk1throughrk3, - former
wwidentities were replaced byrk4, - physical sensor IDs now include their documented TROVIS abbreviation,
- visible and technical sensor identities were made consistent across models.
Existing dashboards, automations, scripts, statistics, and history references created with those earlier beta IDs may require manual adjustment.
For a clean migration from such an early beta:
- remove the existing SAMSON TROVIS 557x config entries,
- keep the existing
modbus_connectionentries, - update
trovis-modbus-hassand its requiredtrovis-modbusversion together, - restart Home Assistant,
- add each TROVIS controller again through the config flow,
- verify the detected model, hydronic system, Rk roles, and physical sensors,
- update dashboards and automations that reference former entity IDs.
An automatic migration from the former beta identities is intentionally not provided.
The user-defined device slug is retained during normal reconfiguration. Changing the selected provider connection, Modbus unit ID, display name, or write-access code therefore does not intentionally change existing entity IDs.
Rk numbers remain tied to the technical controller slots and are not renumbered according to their role. Physical sensors retain their manufacturer abbreviations and remain under Measurements even when the hydronic role using the value changes.
Compatible OEM controllers use the corresponding TROVIS profile supplied by
trovis-modbus. Their behavior depends on the identity and feature set reported
by the device. Not every documented OEM variant has been verified on physical
hardware; consult the trovis-modbus documentation for the current model mapping
and test status.
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