ZHA - device TS0601 reports opposite hvac action

Configuration Zigbee
1

I have purchased 8 valves TS0601 _TZE204_qyr2m29i and every one of them reports opposite hvac action. They work well, but they report opposite.

Screenshot 2025-03-16 20.43.55
Screenshot 2025-03-16 20.43.55691×1171 51.7 KB

2

Screenshot 2025-03-16 20.42.33
Screenshot 2025-03-16 20.42.33715×1294 87.2 KB

3

assuming you’re using zha , pls report that on the zha device handler git

thats where the magic happens

line 661 can even be modified and then load the quirk as ‘custom’ to see if that fixes your issue.

4

I have reported: ZHA - device TS0601 reports opposite hvac action · Issue #140797 · home-assistant/core · GitHub

5

@checking12 thank you for digging in code, could you please advice me how to get to the code since I’m running supervised home assistant OS on rassberry pi

6

try this one

please note the post How to setup local ZHA quirks - #43 by dhavaldesai-HA
with this you should be able to fix it in your installation

7

thank you very much it helped, I have only copied required part.
Since you seem to be a proffessional I have another question.
There are only two HVAC Actions the valve accepts: Off & Heat, but when I send “Off” it goes in Eco mode, “Heat” action makes it Comfort mode. What I would need is ability to Off the thermostat. I tried to manipulate the:

class TuyaPresetMode(t.enum8):
    """Tuya preset mode."""

    Eco = 0x00
    Auto = 0x01
    Off = 0x02
    Heat = 0x03

with no success

8

Futhermore when I want to set preset mode HA sais:

Entity climate.xxx does not support action climate.set_preset_mode

The configuration enables to choose Preset mode

Screenshot 2025-03-19 07.00.09
Screenshot 2025-03-19 07.00.09505×1252 53.1 KB

9

now you hit the ‘tuya datapoints’ conundrum. Tuya doesnt do proper zigbee protocolling, but datapoints handling. All features are handled by datapoints reading and setting. If it’s unkown what datapoint do what feature, you’ll end up diving into ‘spec search’.
See a bit more at GitHub - zigpy/zha-device-handlers: ZHA device handlers bridge the functionality gap created when manufacturers deviate from the ZCL specification, handling deviations and exceptions by parsing custom messages to and from Zigbee devices.

10

I have taken one of the valves away from ZHA and paired it via Tuya Hub. I’ve account on tuya platform and I can talk to the device by sending DPs, but the DPs are strings (like temp_current), so what dp_id=INTEGER in zha-device-handlers/zhaquirks/tuya/tuya_trv.py at 62765a43b32bce6cf21236f4a705759b7cfac50a · zigpy/zha-device-handlers · GitHub stand for? What is the meaning of those integers, since authors don’t use constatns?

and what should be changed in the quirk for Home Assiatnt to be able to use climate.set_preset_mode

I have also in my house _TZE200_bvu2wnxz and _TZE200_kds0pmmv. _TZE200_kds0pmmv is the only one Home Assitant can climate.set_preset_mode. I’ve pulled all GitHub - zigpy/zha-device-handlers: ZHA device handlers bridge the functionality gap created when manufacturers deviate from the ZCL specification, handling deviations and exceptions by parsing custom messages to and from Zigbee devices. and figured out _TZE200_kds0pmmv is the only one (of my 3 kinds) that is not treated by TuyaQuirkBuilder

11

This isn’t possible yet. We need to add v2 climate entities to zigpy, for now we expose the preset mode separately so it’s not actually part of the climate entity.

12

Thanks, let me know when v2 climate entities are in zigpy

13

I don’t think anyones actively working on it. Going to be awhile.