The Avatto TRV06 properly pairs and returns all of the available configuration. The Exposes are properly updating the device state and the currently pulled states are reflecting real data of the device (temperature, heat mode, etc.)
The problem is that it can't start heat (no flame indicator on the device, running_state is always idle).
With the above state the running_state should not be idle, because the heating setpoint is higher than local temperature reading, even with respect of calibration value.
The problem isn't related to child lock mode (tried turned on and off), it doesn't work in programmable (clock icon on the device) and manual modes. I can only trigger the heat action with the flame indicator by manually operating the device.
Any thermostat actions with a properly set temperature higher than the current one don't change the running_state value to heat and valve remains closed.
What did you expect to happen?
The raised current_heating_setpoint to value higher than local_temperature should trigger the running_state value change to heat.
How to reproduce it (minimal and precise)
Pair the device and try to make the valve work (heat) with a native type: thermostat Lovelace card or any other thermostat add-on. The temperature set update is respected and the sensor reading of the current temperature is proper, but no action is taken to start the heating process.
Zigbee2MQTT version
1.40.2
Adapter firmware version
7.3.1.0 build 0
Adapter
EZSP v12
Setup
Home assistant: Core 2024.10.2 Supervisor 2024.10.0 Operating System 13.1 Frontend 20241002.3
What happened?
The Avatto TRV06 properly pairs and returns all of the available configuration. The
Exposes
are properly updating the device state and the currently pulled states are reflecting real data of the device (temperature, heat mode, etc.)The problem is that it can't start heat (no flame indicator on the device,
running_state
is alwaysidle
).Example state values:
With the above state the
running_state
should not be idle, because the heating setpoint is higher than local temperature reading, even with respect of calibration value.The problem isn't related to child lock mode (tried turned on and off), it doesn't work in programmable (clock icon on the device) and manual modes. I can only trigger the heat action with the flame indicator by manually operating the device.
Any thermostat actions with a properly set temperature higher than the current one don't change the
running_state
value toheat
and valve remains closed.What did you expect to happen?
The raised
current_heating_setpoint
to value higher thanlocal_temperature
should trigger therunning_state
value change toheat
.How to reproduce it (minimal and precise)
Pair the device and try to make the valve work (heat) with a native
type: thermostat
Lovelace card or any other thermostat add-on. The temperature set update is respected and the sensor reading of the current temperature is proper, but no action is taken to start the heating process.Zigbee2MQTT version
1.40.2
Adapter firmware version
7.3.1.0 build 0
Adapter
EZSP v12
Setup
Home assistant: Core 2024.10.2 Supervisor 2024.10.0 Operating System 13.1 Frontend 20241002.3
Debug log
No response