Repository navigation
Changing settings safely
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.
A write has to pass two separate layers:
- Home Assistant Write access - the controller-level safety switch in this integration.
-
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.
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.
When Write access is enabled, the writable entities become usable according to the controller model and current configuration.
The TROVIS access code is entered during integration setup. The factory default is normally 1732, unless it has been changed on the controller.
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.
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:
- note the current value,
- make one small change,
- give the controller time to react,
- watch the relevant temperatures and operating state,
- 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.
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.
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.
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.
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, ortmodbus.
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.
The Home Assistant safety gate and the controller-side write logic intentionally live in different layers.
The technical write path is documented here:
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