Repository navigation
Troubleshooting
Check that:
-
SAMSON TROVIS 557x is installed in HACS or under
custom_components/trovis557x, - Home Assistant has been restarted after installing or replacing the integration,
- the integration is visible under Settings → Devices & services → Add integration.
You do not need a separate Home Assistant modbus_connection integration or
Modbus YAML configuration. The TROVIS integration manages its own connection.
A successful TCP connection only proves that the port is reachable. It does not prove that the Modbus framing matches.
Check which mode your adapter actually provides:
- Modbus TCP / gateway mode: use the Network setup path with Modbus TCP framing,
-
raw Modbus RTU over a TCP socket: use RTU-over-TCP framing or a Remote Serial
socket://...target, depending on how the adapter is configured.
If a socket://IP:PORT serial connection works while native Modbus TCP does not,
this usually means the adapter is transparently forwarding RTU bytes rather than
translating Modbus TCP to RTU.
Check:
- controller power and wiring,
- RS-485 polarity and termination,
- the configured unit ID,
- baud rate, parity, stop bits and data bits,
- whether another bus master is interfering,
- whether the gateway uses the expected protocol mode,
- firewall and TCP port settings for network connections.
The factory TROVIS unit ID is 255. This integration normally uses 246, so
make sure the controller and the integration are configured to the same value.
Verify the model identity reported by the controller and update both
trovis-modbus-hass and its required trovis-modbus version together. OEM
controllers are mapped through the corresponding TROVIS model identity and
profile.
Include the detected identification registers and controller model in a bug report. Do not override the model manually unless a development build explicitly provides such a diagnostic option.
Only technical slots and hydronic roles supported by the detected model and system code number are instantiated.
Examples:
- Rk3 is not available on two-slot controller models,
- Rk4 is created only when the hydronic system contains domestic hot water,
- a
climateentity is created only for a heating circuit running in heating-curve mode, - Solar is created only for a supported solar configuration,
- buffer-tank extensions are added only when Rk1 has the buffer-tank role.
Unsupported areas are intentionally not polled.
Physical sensor entities are created from the sensor set detected during setup or a later reconfiguration.
Check the controller's sensor and input configuration, then open the TROVIS integration menu and run Reconfigure to probe the controller again. Newly detected sensors are added while previously known sensor entities are retained.
An electrically connected sensor can still be absent when its input role is not configured or its value is invalid during probing.
This is intentional. Physical inputs remain under the Measurements sub-device because their hydronic meaning depends on the model, system code, terminal assignment, functions and parameters. The same physical sensor identity should stay stable when an Rk role changes.
Check:
- the controller-level Write access switch,
- the configured TROVIS access code,
- whether the entity is writable for the detected model and configuration,
- the entity's valid range, step, or option set,
- the controller's current operating state,
- TROVIS-specific write preconditions.
Review the Home Assistant log for errors from custom_components.trovis557x,
trovis_modbus, modbus_connection, and tmodbus.
climate and water_heater are convenience views. They expose only the values
that can be mapped meaningfully for the detected controller role. The complete
set of available TROVIS datapoints remains available through the normal sensor,
number, select, switch, date, and time entities.
A temporary communication failure is handled as a failed coordinator update. The
TROVIS config entry stays loaded, and the same modbus-connection object can
reconnect on a later request.
If entities keep going unavailable, look for the underlying cause instead of recreating the integration entry: transport, framing, gateway mode, wiring, unit ID, or controller availability are the usual suspects.
Earlier beta versions used hk1 through hk3, ww, and different physical
sensor IDs. The current structure uses rk1 through rk4 and the documented
sensor abbreviations.
This was an older beta migration and is not part of the current setup flow.
Please include:
- Home Assistant version,
-
trovis-modbus-hassversion, -
trovis-modbusversion, -
modbus-connectionandtmodbusversions, - controller or OEM model and firmware,
- system code number,
- connection type and framing,
- unit ID and serial parameters where relevant,
- relevant log excerpts,
- whether reading, writing, or only one entity is affected.
Remove passwords, access codes, public addresses, and other secrets before posting logs.
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