[Device Support Request] _TZE200_cwnjrr72 TS0601

[mhombach]

Is your feature request related to a problem? Please describe. My TuYa valve seems to have a lot of properties/entities missing when connected over ZHA instead of e.g. zigbee2mqtt. I was following youtube video (with timestamp: https://www.youtube.com/watch?v=iD1U6Q47yLU&t=502s) and also bought exactly the same devices as he did (followed his link). As you can see in the attached screenshot, my HA only recognizes 2/3 entities while in the youtube video there are a lot more. Also, in the product page (where I bought them) it's stated that those devices have switches for child-lock and open-window-detection. So at least there should be 2 switch-entities be available. Not talking about the rest like schedlue-switching etc. And btw, I'm using a zigbee ethernet coordinator.

Describe the solution you'd like Since the id cwnjrr72 is already in the code, the problem must lie somewhere else. I would love to have this fixed somehow, so I can start using my newly bought 6 tuya valves :)

Device signature

{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0301",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0201",
        "0x0204",
        "0xef00"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    }
  },
  "manufacturer": "_TZE200_cwnjrr72",
  "model": "TS0601",
  "class": "zhaquirks.tuya.ts0601_trv.MoesHY368_Type1"
}

Additional context

[MattWestb]

The "Moes" type have all working on cluster also setting and reading the weekly schedules but its not so easy using in automations. Only window detection is on one switch in the GUI.

One user have making one with most functions in ZHA GUI but its not well tested and need more brave user testing it. Look in this issue and trying it out if you like and give feedback for getting all things in place. https://github.com/zigpy/zha-device-handlers/issues/1178#issuecomment-980294492

[jacekk015]

@mhombach Add to configuration.yaml

zha:
  custom_quirks_path: /config/zha_custom_quirks/

Create that directory "zha_custom_quirks" under config. Download, unzip, and place that file below into that folder. Restart HA ts0601_trv_moes.py.zip

[edit] @MattWestb That's a bit new, refactored version.

[mhombach]

@mhombach Add to configuration.yaml

zha:
  custom_quirks_path: /config/zha_custom_quirks/

Create that directory "zha_custom_quirks" under config. Download, unzip, and place that file below into that folder. Restart HA ts0601_trv_moes.py.zip

[edit] @MattWestb That's a bit new, refactored version.

Edit: Nvm, got confused for a sec. Dfter the restart, do I need to re-discover the valves or should it directly work?

[MattWestb]

ZHA shall loading the new quirk if all is OK but it can being good deleting it so the old data is deleted and then adding it after one minute or more or best restarting HA.

@jacekk015 The ForceValveState is one good name but i think many user is not understanding the meaning of Normal = 0x00, Open = 0x01 and Close = 0x02 Perhaps: Automatic_mode= 0x00 (or PID_mode) Force_Open = 0x01 Force_Close = 0x02

? ? ?

[MattWestb]

By the was in both "ZHA Native" and the new quirk is scheduled supported but on zigbee cluster (from the device card and manage cluster and the MoesThermostat and attributes get and setting).

[mhombach]

ZHA shall loading the new quirk if all is OK but it can being good deleting it so the old data is deleted and then adding it after one minute or more or best restarting HA.

@jacekk015 The ForceValveState is one good name but i think many user is not understanding the meaning of Normal = 0x00, Open = 0x01 and Close = 0x02 Perhaps: Automatic_mode= 0x00 (or PID_mode) Force_Open = 0x01 Force_Close = 0x02

? ? ?

I did as you told me, but that didn't change anything, sadly. I put the config there, restarted the server, even removed and re-discovered the valve. Not 1 additional setting/entity on that device.

[jacekk015]

@mhombach Did you add it to configuration.yaml??

zha:
  custom_quirks_path: /config/zha_custom_quirks/

Did you create a folder "zha_custom_quirks" in HA config folder?? Did you unzip and put a file inside "zha_custom_quirks" folder? Did you then restart HA???

If all yes, then put again a TRV card screenshot. Best would be to enable DEBUG logging in configuration.yaml and restart HA again:

logger:
  default: info
  logs:
    homeassistant.components.zha: debug
    zigpy: debug
    zhaquirks: debug

Then put ALL logs here as a file. A time of minimum 5 minutes of logs is a min, best is 10 minutes.

[mhombach]

@jacekk015 I'm 1000% sorry, I missed the line in the config yaml. After I restarted HA many entities were added ! See my valve's signature now:

{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0301",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0201",
        "0x0204",
        "0xef00"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    },
    "2": {
      "profile_id": 260,
      "device_type": "0x0000",
      "in_clusters": [
        "0x0006"
      ],
      "out_clusters": []
    },
    "3": {
      "profile_id": 260,
      "device_type": "0x000d",
      "in_clusters": [
        "0x000d"
      ],
      "out_clusters": []
    },
    "4": {
      "profile_id": 260,
      "device_type": "0x000d",
      "in_clusters": [
        "0x000d"
      ],
      "out_clusters": []
    },
    "5": {
      "profile_id": 260,
      "device_type": "0x000d",
      "in_clusters": [
        "0x000d"
      ],
      "out_clusters": []
    },
    "6": {
      "profile_id": 260,
      "device_type": "0x0000",
      "in_clusters": [
        "0x0006"
      ],
      "out_clusters": []
    },
    "7": {
      "profile_id": 260,
      "device_type": "0x000d",
      "in_clusters": [
        "0x000d"
      ],
      "out_clusters": []
    },
    "8": {
      "profile_id": 260,
      "device_type": "0x000d",
      "in_clusters": [
        "0x000d"
      ],
      "out_clusters": []
    },
    "9": {
      "profile_id": 260,
      "device_type": "0x000d",
      "in_clusters": [
        "0x000d"
      ],
      "out_clusters": []
    },
    "10": {
      "profile_id": 260,
      "device_type": "0x000d",
      "in_clusters": [
        "0x000d"
      ],
      "out_clusters": []
    },
    "11": {
      "profile_id": 260,
      "device_type": "0x000d",
      "in_clusters": [
        "0x000d"
      ],
      "out_clusters": []
    }
  },
  "manufacturer": "_TZE200_cwnjrr72",
  "model": "TS0601",
  "class": "ts0601_trv_moes.MoesHY368_Type1"
}

A few followup questions:

• analog_output_valve_state is this correct? The valve itself does not have a physical turnable knob. Or I'm misinterpreting this
• switch.tze200_cwnjrr72_ts0601_37054afe_on_off_2, switch.tze200_cwnjrr72_ts0601_37054afe_on_off and switch.thermostat_esszimmer_37054afe_on_off (that one was renamed before from me) all are switches, but i have no idea what they mean. I guess that one is the child lock, one is the open-window-recognition and the 3rd is... ?
• see below screenshot, the value sliders all give me a "not a number" and so they can't be changed.
• Is _TZE200_cwnjrr72 TS0601 37054afe analog_output Temperature Calibration the entry that would let me set the offset for the valve's turning? Because my valves are all like 4 °C off the real temperature

[MattWestb]

switch.thermostat_esszimmer_37054afe_on_off = WindowDetectionswitch.tze200_cwnjrr72_ts0601_37054afe_on_off = ChildLock switch.tze200_cwnjrr72_ts0601_37054afe_on_off_2 = ValveDetect

MOES_VALVE_STATE_ATTR = 0x026D # opening percentage

and calibration is the offset of the device local temperature 👍

[mhombach]

@MattWestb Hmm, is that duplicated entity caused by the device beeing in HA before that additional config? Then I would just remove and re-discover them. I have 6 valves but only installed 2 until now because i want to get them working 100% first.And what doesValveDetectmean? And the problem withNaN` still needs to be fixed then. Is it possible, by the quirk config, to configure the entity names a little bit?

[MattWestb]

I think it was only WindowDetection you was having before with the "old quirk" but you can deleting it waiting one minute and adding it. Edit: The device

Sorry i was missing putting the function on the first one !! switch.thermostat_esszimmer_37054afe_on_off = WindowDetection.

Valve detect is anti calke / valve jamming detection.

Im not 100% sure then i dont have the devices and only some Siterwells and all things is not the same then all is zuya devices.

[MattWestb]

The first temperature is window detection (how much temperature is falling for triggering) and the time is how long it shall stop heating then window open is detected. Both must being sett for the switch is working if the device is not having it configured.

And i was forgetting the valve state is one read only function but we have not getting it working so its possible changing but its not doing anything but shall reporting valve state OK.

[mhombach]

Aaaah. About the NaN btw, I figured I just have to click inside the slider somewhere to set a value. I just jas no number as initial value. Weird UI though^^° So, if I leave all toggle switched in the default OFF position, does that mean that window detection is active or inactive?

[mhombach]

And another discovery: I think it's recommended to remove devices before using the new config. I just now removed my valves from HA and discovered one again and now all entities have initial values that make sense.

[jacekk015]

When device is paired again it sends all data to HA. So that's why values were updated on pairing. For device functions - see manual. We didn't add anything more than you have.

[mhombach]

Makes sense, goot to know :) I'm 99% done now. I'm just trying to calibrate my valves, because the temperature is off. But for some reason I'm having trouble understanding thr workings of those 2 sliders. top slider is the calibration one, bottom one is the valve state. From what I realized now I think, the valve state is basically showing how far the valve's pin is physically pushed in (or to be more precise, how far the valve's motor has pushed the pin out). The calibration slider is mysterious to me. It ranges from -9 to 9. I attached a sketch for my current situation. My valve is measuring 20°C and when the vale is set to 18°C, it's closed (from listening with my ear on the valve/waterflow). When I set it to 19°C, the valve will open. So my valve is off by 2°C. But most of the time when I use the calibration slider and set it to e.g. 4, it will stay on 4 for a few secs, then it will revert to 0. Then the valve state slider will change a little bit, as if the calibration is meant to increase/decrease the valve state without keeping a state itself. But that didn't fully work. At some point my calibration slider got "stuck" at position -9 or 9. What is the proposed way how to calibrate in my current case?

[jacekk015]

All sliders have representation on the TRV itself. If you change calibration to +2 then you should see same when you click the TRV physically. We just read/write data HA<->TRV - nothing more. What TRV allow - it works. Like Valve state - if it's read-only on TRV then there's no real possibility to change it from HA UI.

[mhombach]

Hmm... I might be missing some information here... I was now calibrating the temperature on the valve itself and it seems that I can change not the temperature that I set but instead the measured temperature? I was thinking that

• the valve has a temperature sensor that measures to some extend reliable the temperature around the valve
• the valve is pushing in the pin on the radiator and that can be a little bit off. So I would think that I need to adjust that number (the temp I set)? Because when I set the temp to 21°C and the TRV pushed the pin in an arbitrary amount, how should it be sure that this position is 21°C?

[MattWestb]

One thing is that the TRVs Zigbee module is one sleeping end device and it can taking some seconds for one command being received of it from you is doing changes in ZHA. Then doing changes on the TRV is nearly immediately changes in ZHA and we cant do anything for foxing it without keeping the device alyas awake then then your batteries is dead in some weeks.

The local temperature calibrating -9 - +9 shall being sent to the TRV and its sending the "new" local temperature back with the corrected temperature to ZHA and is using it until you is sending one new value for calibration. The TRV have one very pore (not good calibrated) temperature sensor but then calibrated its working OK. That is not problem then the TRV is only comparing the setpoint and if need heating more or less and the calibration is more or less "cosmetic" for presentation in the host system.

[teklabania]

@jacekk015, I have _TZE200_cwnjrr72. My findings on the quirk you prepared:

• Calibration slider doesn't work correctly. When I set the value to +/-5, the temperature is adjusted of 0,5C and the value displayed next to slider shows +/-50C: Setting other values makes slider return to the previous value.
• Valve state percentage slider makes no change (the valve's display indicates another value).
• There's no power button for disabling the thermostat:

There are 3 switches, but have no idea what they are. My guess:

• window detection
• children lock
• ???

Do you think there's a way to set up hysteresis for this valve? Is the quirk you made going to be merged into master branch?

[jacekk015]

@teklabania Was the device re-paired?? Enable debug logs and put here as a file whole logs. The logs need to include action you take. Without it I can say nothing.

Valve state percentage slider makes no change

Read-only

There's no power button for disabling the thermostat:

Yes. How do you disable thermostat? There's no kind of function on the device.

There are 3 switches, but have no idea what they are.

• MoesValveDetect
• MoesWindowDetection
• MoesChildLock

Do you think there's a way to set up hysteresis for this valve?

You do have Temperature Calibration. If the valve manual says nothing about functions there's no possibility.

Is the quirk you made going to be merged into master branch?

Don't know. PR needs working Python tests - I can't/won't do this.

[teklabania]

@jacekk015, thank you for quick response.

@teklabania Was the device re-paired?? Enable debug logs and put here as a file whole logs. The logs need to include action you take. Without it I can say nothing.

No, the device wasn't re-paired. I just put a quirk on place and restarted HA. New switches/sliders appeared after restarting. Should I delete and pair the device again?

Yes. How do you disable thermostat? There's no kind of function on the device.

Hmm... Generic thermostat has the option:

• MoesValveDetect

What might that be?

You do have Temperature Calibration. If the valve manual says nothing about functions there's no possibility.

So it seems there's no option for setting up hysteresis. I didn't find it in manual.

Don't know. PR needs working Python tests - I can't/won't do this.

I'm keeping fingers crossed for adding this device to official support.

[teklabania]

Current temperature shows 24C. I set calibration to -5 with the slider. After that current temperature is set to 23,5C, but the slider shows -50. Logs:

2021-12-10 16:10:33 DEBUG (MainThread) [zigpy.zcl] [0xc6a9:1:0xef00] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=True is_reply=True disable_default_response=False> manufacturer=4098 tsn=124 command_id=Command.Default_Response>
2021-12-10 16:10:33 DEBUG (MainThread) [zigpy.zcl] [0xc6a9:1:0xef00] ZCL request 0x000b: [0, <Status.SUCCESS: 0>]
2021-12-10 16:10:35 DEBUG (MainThread) [zigpy.zcl] [0xc6a9:1:0xef00] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=106 command_id=1>
2021-12-10 16:10:35 DEBUG (MainThread) [zigpy.zcl] [0xc6a9:1:0xef00] ZCL request 0x0001: [Command(status=1, tsn=255, command_id=515, function=0, data=[4, 0, 0, 0, 235])]
2021-12-10 16:10:35 DEBUG (MainThread) [zhaquirks.tuya] [0xc6a9:1:0xef00] Received value [0, 0, 0, 235] for attribute 0x0203 (command 0x0001)
2021-12-10 16:10:35 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0xC6A9:1:0x0201]: Attribute report 'MoesThermostat'[local_temp] = 2350
2021-12-10 16:10:35 DEBUG (MainThread) [homeassistant.components.zha.entity] climate.termostat_sypialnia: Attribute 'local_temp' = 2350 update
2021-12-10 16:10:36 DEBUG (MainThread) [zigpy.zcl] [0xc6a9:1:0xef00] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=CLUSTER_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=107 command_id=1>
2021-12-10 16:10:36 DEBUG (MainThread) [zigpy.zcl] [0xc6a9:1:0xef00] ZCL request 0x0001: [Command(status=2, tsn=0, command_id=556, function=0, data=[4, 255, 255, 255, 251])]
2021-12-10 16:10:36 DEBUG (MainThread) [zhaquirks.tuya] [0xc6a9:1:0xef00] Received value [255, 255, 255, 251] for attribute 0x022c (command 0x0001)
2021-12-10 16:10:36 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0xC6A9:1:0x0201]: Attribute report 'MoesThermostat'[local_temperature_calibration] = -50
2021-12-10 16:10:36 DEBUG (MainThread) [homeassistant.components.zha.entity] climate.termostat_sypialnia: Attribute 'local_temperature_calibration' = -50 update
2021-12-10 16:10:36 DEBUG (MainThread) [zigpy.zcl] [0x37a8:1:0x0006] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=33 command_id=Command.Report_Attributes>
2021-12-10 16:10:36 DEBUG (MainThread) [zigpy.zcl] [0x37a8:1:0x0006] ZCL request 0x000a: [[Attribute(attrid=0, value=<TypeValue type=int8s, value=0>)]]
2021-12-10 16:10:36 DEBUG (MainThread) [zigpy.zcl] [0x37a8:1:0x0006] Attribute report received: on_off=0
2021-12-10 16:10:40 DEBUG (MainThread) [zigpy.zcl] [0xba87:1:0x0006] ZCL deserialize: <ZCLHeader frame_control=<FrameControl frame_type=GLOBAL_COMMAND manufacturer_specific=False is_reply=True disable_default_response=False> manufacturer=None tsn=5 command_id=Command.Report_Attributes>
2021-12-10 16:10:40 DEBUG (MainThread) [zigpy.zcl] [0xba87:1:0x0006] ZCL request 0x000a: [[Attribute(attrid=0, value=<TypeValue type=int8s, value=0>)]]
2021-12-10 16:10:40 DEBUG (MainThread) [zigpy.zcl] [0xba87:1:0x0006] Attribute report received: on_off=0

[mhombach]

I can confirm that the slider for temperature calubration doesn't work as excepted. Maybe there some number-format wrong or so (int/float/whatever)? I manually set the offset on my valve to +2°C (by the menu on the valve itself). Then I paired it with HA (over ZHA). And the slider for temperature calibration shows 100°C :/

[jacekk015]

You didn't read whole topic: https://github.com/zigpy/zha-device-handlers/issues/1212#issuecomment-990213781

Should I delete and pair the device again?

Yes - then all default values will be set according to what TRV sends to HA.

Hmm... Generic thermostat has the option:

Does the TRV has this function in manual? Do you really can OFF that device? Like totally OFF???

What might that be?

Don't know. You have the device in your hand - switch and look what changed. Probably manual says something about it. We only implement that what users provide. Quirk was originally written by other user - didn't analyse functions and I don't have this device.

Current temperature shows 24C. I set calibration to -5 with the slider. After that current temperature is set to 23,5C, but the slider shows -50. Logs:

Re-pair device. Then check again. Other users would need to confirm that also.

[jacekk015]

@mhombach No logs, no talks. Logs show everything what happens in communication. Do changes on TRV physically and then put logs here.

[teklabania]

You didn't read whole topic: #1212 (comment)

I did. The comment recommends re-pairing in case of issues with initial values. I had no problem with that.

Should I delete and pair the device again?

Yes - then all default values will be set according to what TRV sends to HA.

Didn't help.

Hmm... Generic thermostat has the option:

Does the TRV has this function in manual? Do you really can OFF that device? Like totally OFF???

Well, thermostat in HA is virtual representation of a physical device. It could be turned off programmatically.

What might that be?

Don't know. You have the device in your hand - switch and look what changed. Probably manual says something about it. We only implement that what users provide. Quirk was originally written by other user - didn't analyse functions and I don't have this device.

I wouldn't ask if the option were described in manual. Toggling the switch changes nothing. Some people may have this knowledge, the question was public. Don't get too excited.

Current temperature shows 24C. I set calibration to -5 with the slider. After that current temperature is set to 23,5C, but the slider shows -50. Logs:

Re-pair device. Then check again. Other users would need to confirm that also.

Nothing changes after re-pairing.

[MattWestb]

@teklabania

Hmm... Generic thermostat has the option:

Does the TRV has this function in manual? Do you really can OFF that device? Like totally OFF???

The HA clima generic card have many functions for all kind of clima component. If you have one heating thermostat you can shutting it off completely (the device is DEAD) and shall using off mode in clima component.

TRV is normally always living and cant being shutted off so ZHA is not enabling this function then most TRVs is having antifreeze function that cant being suted off.

Also some TRV have off mode but its not recommending using one TRV for open and closing the valve then you is losing all algorithms in the TRV for adjusting the heat demand to the room is shall keeping heated at one setpoint. Its takes days for one TRV for adjusting it so it not doing over and undersutting the heating and if you is turning it off and on its starts from zero.

If your TRV can being sutted off with commands and you like to using it its up to you but if its not have it as mode we cant implanting it in ZHA and cant getting the code accepted of HA maintainer then its not one real working mode of the device.

If like gettin all function working with GUI elements in ZHA we need testing the devices for knowing how the funktions is working or perhaps is not working at all but we dont have all device so we need help of users that can do the testing and reporting back and also providing logs so we can getting all function that is possible on the device working OK in our system.

Also we cant doing great magic thins with devices then all is locked in the firmware but with good feedback we can making the device working great in ZHA and also putting in little extras then its possible.

[teklabania]

That's great explanation. Thank you @MattWestb.

[MattWestb]

One very good example:

Calibration slider doesn't work correctly. When I set the value to +/-5, the temperature is adjusted of 0,5C and the value displayed next to slider shows +/-50C:

If providing logs then changing the calibrating in ZHA and reporting it is very likely getting one updated quirk in some hours but with no feedback its not possible doing anything and its better using the standard quirk in ZHA without GUI element and doing all on the Zigbee cluster.

Edit: For logging pleas use this setting in HA https://github.com/zigpy/zha-device-handlers/issues/1212#issuecomment-990123605