Viessmann ZK03840 - Target Temp not considered for valve

[FranzToepfer]

describe the problem in Detail. What do you expect to happen ? What does happen ?

To control radiators/heating via existing smart home solution, for each radiator high quality Viessmann ZK03840 device has been selected. As per documentation of iobroker zigbee adapter, this device has already been integrated and should work.

Therefore for each radiator the corresponding thermostat has been paired via Zigbee adapter, which basically worked as expected. Resulting from this, several states appear in Object browser, such as:

1. Battery state
2. Local Temp
3. Target Temp

So far so good. Anyhow, setting target temperature does not work as expected:

• Setting the target temp e.g. to 30 °C, the device is expected to open the valve.
• Doing so, means setting target=30 in object browser, this information gets sent to the device, and obviously also will be accepted, as the On-device display next shows this new target temp of 30 °C
• But no further action, valve does not move.

Also the other way around, setting very low value of target=8 does not close the valve. In any case, after waiting for several minutes without and move of the valve, when manually changing the target temp directly at the physical device, the valve immediately follows in expected direction, opening or closing.

So the basic communication from/to the device seems to work. Temp/Battery from device correctly appears in iob.
But changing the target temp does not have the expected effect, only on display new target temp gets shown, but valve is not controlled by that.

Am I missing something, or is there a bug in the device settings?

Adapter version

2.0.4

Coordinator firmware version

?

Coordinator

CONBEE II, CONBEE III both having same issue

Setup

Docker on RPI4

Protocol of the error (as text, encapsulated in multiline code tags <>). Separate different occurrances into clearly split log sections

No response

[asgothian]

If the device shows the changed value, the data is sent, received and acknowledged on the device. The reason for this behaviour must lie in the device.

Please check the device manual for operation modes and the like.

A.

[FranzToepfer]

Thanks to @asgothian for quick response. Basically, I see your point, agreed. Anyhow, this is not a solution to the issue, thermostat still not working.

For reference, same issue [Koenkk/zigbee-herdsman-converters/issues/2275] and as per my understanding not final solution.

So might be caused by the vendor and some propitiatory interface implementations, but internally (in the Viessmann eco system) devices are working as expected. So as per my understanding, there is something missing here in the Zigbee converters?

[asgothian]

As far as I understand the issue you linked - yes. It may be fixed with a firmware upgrade of the device - if a new firmware is offered.

Other than that - given that the thread is 3 yrs old, it is safe to assume that any takeaway from that thread has been integrated into the zigbee-herdsman-converters and is active with the zigbee Adapter.