Skip to content

Current Limits and Migration

Tom-Bom-badil edited this page Sep 15, 2026 · 1 revision

Deliberate scope

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.

Static entity discovery

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.

Fixed polling interval

The integration polls the controller every 60 seconds. It does not currently provide a user-configurable scan interval per controller or entity.

Convenience entities

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.

Connection-provider dependency

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.

Migration from earlier beta entity identities

Earlier beta versions used technical identities that no longer match the role-aware Rk and physical-sensor model:

  • former hk1 through hk3 identities were replaced by rk1 through rk3,
  • former ww identities were replaced by rk4,
  • 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:

  1. remove the existing SAMSON TROVIS 557x config entries,
  2. keep the existing modbus_connection entries,
  3. update trovis-modbus-hass and its required trovis-modbus version together,
  4. restart Home Assistant,
  5. add each TROVIS controller again through the config flow,
  6. verify the detected model, hydronic system, Rk roles, and physical sensors,
  7. update dashboards and automations that reference former entity IDs.

An automatic migration from the former beta identities is intentionally not provided.

Stable identities after setup

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.

OEM controller status

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.

german Wiki - Start english


english Bauanleitungen

Schritt 1 - Kabel

Schritt 2 - Adapter

Schritt 3 - Schnittstelle

Schritt 4 - Regler

Schritt 5 - Erster Test

🔥 Update: Weitere Adapter


english Home Assistant Integration

🚀 Getting started

🔌 Using the integration

🧑‍💻 Technical reference

🔢 Related projects


english SmartHomeNG Plugin


german2 Anhang: Info-Sammlung

Clone this wiki locally