I have a Danfoss Zigbee radiator valve, model 014G2460 (eTRV0100), with firmware version 0120.
The TRV is controlled by Home Assistant with ZHA, which sends a Zigbee command every day at 5:00 a.m. to set the temperature to 35 °C, and another command at 9:00 a.m. to set it back to 20 °C.
However, when the heating system starts at 7:00 a.m., the radiator remains cold.
If I then manually turn the TRV knob from 35 °C down to 34 °C, I can hear the valve motor move, and the radiator starts to heat up.
So the temperature setting of 35 °C is accepted but not actually used to open the valve.
I’ve already removed the batteries and reinserted them while holding the button, and I’ve also performed an adaptation run — neither made any difference.
Hardware-wise the TRV appears to be completely fine, and a firmware bug seems unlikely. Window detection is off and load balancing is off.
Could it be that Home Assistant is sending the Zigbee command incorrectly?
Maybe the TRV is in valve mode - if this mode exists?
I have also a eTRV0103 which works fine.
Are you using ZHA or Zigbee2MQTT for integrating the TRVs? For Danfoss Ally I highly recommend using Zigbee2MQTT, as this exposes all entites you might need to configure the TRV and investigate what might be wrong.
ZHA also exposes all entities since an update a while ago, so I don’t think it matters much in that respect.
To the op, can you see in the logs what happens when you send the command to your TRV? And can you post a screenshot of the device page with all the settings for the TRV?
That looks pretty much the same as mine (that work as expected). So no clues in there for me. I was thinking maybe the response time was very slow or something but no.
There may still be a clue in the log file? Check around the time you send the command to the TRV.
I didn’t ask yet, but does this happen only in the morning when you send the automated command. Or every time you send a command that should set the motor in motion?
Especially the PI heating demand value should be interesting to watch in logs or history. This parameter should more or less correspond to the motor position. Generally it should start moving relatively soon (tens of seconds tonminutes) after you change the setpoint.
The problem exists not only in the morning.
PI heating demand does not change also.
As soon as I turn the knob, in the display I see that the new set point was accepted. And after turning the knob, the motor turns and PI heating demand changes.
