Skip to content

Changing settings safely

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

The TROVIS controller remains responsible for the actual heating control. Home Assistant is mainly intended for monitoring and for occasional, deliberate fine adjustment of settings that the integration can interpret safely.

For that reason, writing is disabled by default.

Important

Do not use Home Assistant as a substitute for commissioning the heating system. If you are unsure what a controller parameter does, leave it unchanged and check the TROVIS manual or ask your heating professional.


🔐 Two things protect writes

A write has to pass two separate layers:

  1. Home Assistant Write access - the controller-level safety switch in this integration.
  2. TROVIS write rules - access code, valid value range and controller-specific write handling in trovis-modbus.

So simply having a number, select or switch entity does not bypass the controller's own rules.


🔓 Enabling Write access

Open the main TROVIS controller device in Home Assistant and find the Write access switch.

With Write access disabled, the integration can still read and monitor the controller normally, but supported settings cannot be changed.

TROVIS controller settings with write access disabled

When Write access is enabled, the writable entities become usable according to the controller model and current configuration.

TROVIS controller settings with write access enabled

The TROVIS access code is entered during integration setup. The factory default is normally 1732, unless it has been changed on the controller.


✅ Good candidates for occasional adjustment

Depending on the detected model and hydronic configuration, the integration can expose settings such as:

  • operating mode,
  • day and night room setpoints,
  • heating-curve gradient and level,
  • fixed flow-temperature setpoints,
  • minimum and maximum flow-temperature limits,
  • selected return-temperature limits,
  • domestic-hot-water setpoints,
  • selected buffer-tank charging parameters,
  • controller date and time.

Not every controller or system shows all of these settings.

The integration deliberately exposes a useful subset, not every technically writable register or coil in the controller.


🐢 Change one thing at a time

Heating systems react slowly. A change may take many minutes - sometimes much longer - before the effect is visible in room temperature or return temperature.

A good workflow is:

  1. note the current value,
  2. make one small change,
  3. give the controller time to react,
  4. watch the relevant temperatures and operating state,
  5. revert the change if the result is not what you expected.

Avoid changing several related settings at once unless you already understand the TROVIS control strategy.


🌡️ Heating-circuit settings depend on the control mode

A TROVIS heating circuit can use one of three basic control modes:

Mode What Home Assistant shows
Heating curve room setpoints, gradient, level and flow limits
Fixed setpoint fixed day/night flow temperatures and flow limits
4-point curve the 4-point outdoor/flow/return values and flow limits

Only the settings that belong to the active mode are shown. This is intentional: the integration avoids presenting controls that would currently have no useful effect.

The climate convenience entity is currently created only for a normal heating circuit using the gradient heating-curve mode, because that is the mode in which its room-setpoint control has the intended meaning.

➡️ Understanding-your-TROVIS


♨️ Domestic hot water, buffer tank and solar

These functions are only shown when the detected hydronic system actually uses them.

  • Rk4 - Domestic hot water contains supported DHW settings.
  • Buffer-tank settings are added to Rk1 when Rk1 is the buffer-tank circuit.
  • Solar is a separate functional device and is not part of Rk4.

A missing setting therefore does not automatically mean that something is broken - it may simply not apply to your controller or system configuration.


⚠️ Special values

Some TROVIS parameters use special numeric values with a non-numeric meaning. For example, selected buffer-tank parameters can use 0 for an automatic/outdoor-temperature-dependent mode.

The integration tries to preserve these controller semantics instead of pretending that every parameter is just a normal number.

If a value looks surprising, check its description before changing it.


🧯 If a write fails

Check:

  • Write access is enabled,
  • the configured TROVIS access code is correct,
  • the selected value is inside the allowed range,
  • the entity is actually writable for this controller and configuration,
  • the controller is reachable,
  • Home Assistant logs for trovis557x, trovis_modbus, modbus_connection, or tmodbus.

A failed write should not be worked around by writing raw Modbus addresses manually from Home Assistant. If the integration refuses a write that should be supported, please report it so that the controller-side rules can be fixed in the library.

➡️ Troubleshooting


🧑‍💻 For developers

The Home Assistant safety gate and the controller-side write logic intentionally live in different layers.

The technical write path is documented here:

➡️ Writing-and-write-access

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