Skip to content

Understanding your TROVIS

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

TROVIS controllers can look complicated at first because one controller can be used for many different heating and district-heating systems. The good news is that the integration already reads most of that structure for you.

This page explains the terms you will see in Home Assistant without diving into register addresses or controller internals.


🧠 The three things that define your installation

A TROVIS installation is mainly shaped by:

  1. Controller model - for example TROVIS 5576, 5578 or 5579.
  2. System code / Anlagenkennziffer - the hydronic system selected in the TROVIS.
  3. Functions and connected inputs - which sensors and optional functions are actually configured.

The integration probes these automatically and creates only the Home Assistant devices and entities that make sense for the detected installation.


🔢 What is an Anlagenkennziffer?

The Anlagenkennziffer (system code) tells the TROVIS what kind of hydronic system it is controlling.

Examples can describe systems with:

  • one or more heating circuits,
  • a primary/pre-control circuit,
  • domestic hot water,
  • a buffer tank,
  • solar support,
  • combinations of these functions.

Two identical TROVIS 5578 controllers can therefore look quite different in Home Assistant when they use different system codes.

You normally do not need to enter this number in Home Assistant. The integration reads it from the controller.


🔄 What does Rk mean?

Rk is the TROVIS technical control-circuit slot.

The important point is that an Rk number is an identity, not automatically a heating-circuit number.

Technical slot Possible meaning
Rk1 heating circuit, primary/pre-control circuit, buffer-tank circuit, or unused
Rk2 heating circuit, primary/pre-control circuit, or unused
Rk3 heating circuit, primary/pre-control circuit, or unused
Rk4 domestic hot water, when the selected hydronic system includes it

Home Assistant keeps the Rk number stable and uses the detected role to decide the visible name and useful entity set.

So a device named Rk1 - Pre-control circuit is not a renamed heating circuit. It really is the controller's Rk1 slot operating in a different hydronic role.


♨️ Heating circuit

A heating-circuit Rk controls a flow temperature for a room-heating circuit.

The integration currently understands three basic ways the TROVIS can calculate that target:

Heating curve

The controller uses outdoor temperature together with room setpoint, gradient and level to calculate the required flow temperature.

This is the normal weather-compensated mode and is the mode used by the Home Assistant climate convenience entity.

Fixed setpoint

The controller uses fixed flow temperatures for day and night operation instead of calculating them from outdoor temperature.

4-point curve

Four outdoor-temperature points define the heating curve explicitly. Separate day and night flow temperatures can be configured, together with the corresponding return-temperature limits.

Only one of these three basic modes is active for a heating circuit at a time.


↩️ Return-temperature limitation

Return-temperature limitation is not a fourth heating mode.

It is an additional limit applied on top of the selected heating-circuit mode. If the return temperature becomes too high, the TROVIS can reduce the flow-temperature demand and close the control valve further.

This is particularly important in many district-heating systems where a maximum return temperature is required.


🌤️ Outdoor-temperature cutoff and summer operation are different things

The integration distinguishes between:

  • the immediate, circuit-specific Outdoor temp cutoff active state, and
  • the controller's broader summer-operation behavior.

The outdoor-temperature cutoff belongs to an individual Rk and reacts to its effective outdoor-temperature shutdown threshold. It should not be confused with a multi-day or controller-wide summer mode.


🚿 Rk4 - Domestic hot water

When the selected hydronic system contains domestic hot water, the integration creates Rk4 - Domestic hot water.

Rk4 can contain supported values and controls for the DHW function, and a water_heater convenience entity can be added where the available TROVIS data maps cleanly to Home Assistant.

If your hydronic system has no DHW function, Rk4 is not created.


🛢️ Buffer tank

In actual buffer-tank systems, the buffer-tank circuit uses Rk1.

The integration therefore does not create a second duplicate buffer device. Instead, Rk1 keeps its technical identity and receives the additional buffer-tank values that are valid for the detected controller and system code.


☀️ Solar

Solar is not Rk1 through Rk4.

When the hydronic configuration contains a supported solar circuit, Home Assistant creates a separate Solar device.

The solar circuit may interact with domestic hot water or a buffer tank, but it remains its own functional part of the integration.


🌡️ Measurements and sensor names

Physical sensor inputs are kept together under the Measurements device.

Common TROVIS abbreviations include:

Abbreviation Meaning
AF outdoor temperature sensor
VF flow temperature sensor
RüF return temperature sensor
RF room temperature sensor
SF storage temperature sensor
FG remote sensor / remote setpoint input
IMP pulse-rate input

The number identifies the physical/logical input, for example VF1, VF2 or SF2.

Why keep these under Measurements instead of moving every sensor into an Rk device? Because the same physical input can have a different role depending on model, wiring, system code and enabled functions. Keeping the sensor identity stable avoids confusing entity changes when the controller configuration changes.


🧩 Why do some entities appear only sometimes?

The integration intentionally avoids exposing every possible TROVIS datapoint on every controller.

An entity can depend on:

  • controller model,
  • system code,
  • Rk role,
  • configured functions,
  • detected sensor inputs,
  • active heating-circuit mode,
  • whether the datapoint is safe and useful to expose in Home Assistant.

That is why two users with the same controller model can still see different devices and entities.

➡️ Devices-and-entities


🔧 Changed the TROVIS configuration?

Normal polling updates values, but it does not rebuild the Home Assistant device structure every minute.

If you change something on the TROVIS that affects the system structure - for example the hydronic system, sensor assignments or important function settings - run Reconfigure on the integration so that the controller is probed again.

➡️ Config-flow-and-reconfiguration


📚 Want the controller-level details?

This Wiki stays focused on the Home Assistant integration. Register/coil definitions, hydronic matrices, sensor resolvers and controller-side rules are maintained in the trovis-modbus documentation so that the same information does not need to be maintained twice.

➡️ trovis-modbus Wiki

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