Hometronic setpoint adjustment broken in 0.11.0

[skundrik]

Hometronic does not react to W:2349 but rather requies W:2309. This is something that used to work before but looks like some structural changes may have broken it. I was able to fix it temporarily on my system by adapting climate.py from this

    def svc_set_zone_mode(
        self, mode=None, setpoint=None, duration=None, until=None
    ) -> None:
        """Set the (native) operating mode of the Zone."""
        if until is None and duration is not None:
            until = dt.now() + duration
        self._device.set_mode(mode=mode, setpoint=setpoint, until=until)
        self._req_ha_state_update()

to this

    def svc_set_zone_mode(
        self, mode=None, setpoint=None, duration=None, until=None
    ) -> None:
        """Set the (native) operating mode of the Zone."""
        if until is None and duration is not None:
            until = dt.now() + duration
        self._device.setpoint=setpoint
        self._req_ha_state_update()

As per the comment on the forum it's not really suitable as is because it would limit functionality for others.

Packet info
In the current system when I adjusted the zone setpoint to 8.5 deg. I can see it's sending the requests to zone 5 for 0352 but getting no reply

2021-07-18T15:32:28.499339 000  W --- 18:138267 01:020766 --:------ 2349 007 05035202FFFFFF
2021-07-18T15:32:28.586291 000  W --- 18:138267 01:020766 --:------ 2349 007 05035202FFFFFF
2021-07-18T15:32:28.723146 000  W --- 18:138267 01:020766 --:------ 2349 007 05035202FFFFFF
2021-07-18T15:32:30.444316 075  I --- 00:000951 --:------ 00:000951 30C9 003 000A54
2021-07-18T15:32:35.444890 067  I --- 00:000494 --:------ 01:020766 2309 003 050320
2021-07-18T15:32:41.944937 075  I --- 00:000606 --:------ 01:020766 3150 002 0800

However after the fix the following sequence works fine and W:2309 is immediately confirmed by I:2309 and the new zone temp could be seen later on I:2309 broadcast by the controller.

2021-07-18T18:32:29.951767 000  W --- 18:138267 01:020766 --:------ 2309 003 0308FC
2021-07-18T18:32:29.994800 070  I --- 01:020766 18:138267 --:------ 2309 003 0308FC
2021-07-18T18:32:35.412075 061  I --- 00:000599 --:------ 01:020766 2309 003 0D0320
2021-07-18T18:32:37.413208 068  I --- 00:000567 --:------ 01:020766 2309 003 0A0320
2021-07-18T18:32:40.911535 065  I --- 00:000595 --:------ 01:020766 3150 002 0C00
2021-07-18T18:32:47.913285 076  I --- 00:000606 --:------ 00:000606 30C9 003 000942
2021-07-18T18:32:49.413565 076  I --- 00:000606 --:------ 01:020766 1060 003 08FF01
2021-07-18T18:32:49.425550 075  I --- 00:000606 --:------ 00:000606 1060 003 00FF01
2021-07-18T18:32:50.411372 071  I --- 04:017575 --:------ 01:020766 2309 003 060320
2021-07-18T18:32:53.414567 068  I --- 00:000498 --:------ 01:020766 1060 003 00FF01
2021-07-18T18:32:53.425560 068  I --- 00:000498 --:------ 00:000498 1060 003 00FF01
2021-07-18T18:32:58.911055 081  I --- 00:000392 --:------ 00:000392 30C9 003 000921
2021-07-18T18:33:00.411387 048  I --- 04:024117 --:------ 04:024117 30C9 003 000960
2021-07-18T18:33:02.912131 075  I --- 00:000951 --:------ 01:020766 1060 003 07FF01
2021-07-18T18:33:02.924132 075  I --- 00:000951 --:------ 00:000951 1060 003 00FF01
2021-07-18T18:33:05.912701 073  I --- 00:000606 --:------ 01:020766 3150 002 0800
2021-07-18T18:33:08.413592 062  I --- 00:000599 --:------ 01:020766 1060 003 0DFF01
2021-07-18T18:33:08.424613 061  I --- 00:000599 --:------ 00:000599 1060 003 00FF01
2021-07-18T18:33:08.912324 070  I --- 00:000567 --:------ 01:020766 3150 002 0A00
2021-07-18T18:33:09.482978 066  I --- 01:020766 --:------ 01:020766 1F09 003 FF04CE
2021-07-18T18:33:09.525971 065  I --- 01:020766 --:------ 01:020766 2309 042 0002DA0103200203200308FC0403200503200603200703200803200903200A03200B03200C03200D0320
2021-07-18T18:33:09.558959 066  I --- 01:020766 --:------ 01:020766 30C9 042 000AAA010E7C02095003085004090D0508B8060A0B0709F40809420909600A09420B09210C09140D092E

I can provide daily logs if necessary for your collection.

[zxdavb]

OK, I believe I has addressed this, so it now uses 2309 again - this will be in the next release of the code, 0.14.15.

[zxdavb]

Closing, as I believe I have fixed.