Add Nedis TRV ZBHTR20WT - Tuya _TZE200_ne4pikwm

[prairiesnpr]

Proposed change

Add Nedis TRV ZBHTR20WT, _TZE200_ne4pikwm and _TZE284_ne4pikwm.

Additional information

Closes: #3517
Based on: https://github.com/Koenkk/zigbee-herdsman-converters/blob/09cfce5153d3931c7cc009aa3ae3107d9b394f5c/src/devices/nedis.ts#L10

Checklist

• The changes are tested and work correctly
• pre-commit checks pass / the code has been formatted using Black
• Tests have been added to verify that the new code works

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.96%. Comparing base (bd9ecbb) to head (e3214cb).
Report is 3 commits behind head on dev.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev    #3816   +/-   ##
=======================================
  Coverage   90.96%   90.96%           
=======================================
  Files         327      327           
  Lines       10606    10607    +1     
=======================================
+ Hits         9648     9649    +1     
  Misses        958      958           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[checkiecheck]

hello, any chance this change gets merged for a HA 2025.2 release?

[prairiesnpr]

hello, any chance this change gets merged for a HA 2025.2 release?

Can you confirm it's working for you?

[jonas-bork]

Thank you for making this! It allowed me to get my thermostat working in Home Assistant :)

However, I had to make some changes to make it fully work. Firstly, though, I want to mention that I'm new to Home Assistant and this repo so maybe my changes are not correct - but they seem to be working for me. Also, I have the _TZE200_ne4pikwm thermostat and have only tested my changes on that one.

I think you forgot to add the frost protection switch. Here's my proposed code for it:

    .tuya_switch(
        dp_id=10,
        attribute_name="frost_protection",
        translation_key="frost_protection",
        fallback_name="Frost protection",
    )

[prairiesnpr]

Thanks for the feedback, I'm focused on fixing the saswell TRVs that broke during the last release, but when that's complete I'll update this and let you test again.

[checkiecheck]

hello, any chance this change gets merged for a HA 2025.2 release?

Can you confirm it's working for you?

to be honest, it was a decision making question. I tried to use it as custom quirck , but cant seem to activate that. So if this is possible in next release, i'll stop trying custom quirk. activation If it takes more time, i'll invest a bit more to get custom quirk working.

[sonikki789]

I could put this up to a test if somebody can tell me what file I should use as custom quirk?

[prairiesnpr]

I could put this up to a test if somebody can tell me what file I should use as custom quirk?

You need tuya_trv.py https://github.com/zigpy/zha-device-handlers/blob/6872b635a87bd5dfb9567086aad2e143c1dbe378/zhaquirks/tuya/tuya_trv.py

[sonikki789]

I could put this up to a test if somebody can tell me what file I should use as custom quirk?

You need tuya_trv.py https://github.com/zigpy/zha-device-handlers/blob/6872b635a87bd5dfb9567086aad2e143c1dbe378/zhaquirks/tuya/tuya_trv.py

Thanks, got it running :)

[checkiecheck]

hello, any chance this change gets merged for a HA 2025.2 release?

Can you confirm it's working for you?

got it up now. Just the firmware sensor isnt populating, while it did show something when just paired without the quirk.

oh, another item i spotted. I cant set the max heat value
[0xFC3C:1:0xef00] No cluster_dp found for 1, max_heat_setpoint_limit
[0xFC3C:1:0xef00] no MCU command for data TuyaClusterData(endpoint_id=1, cluster_name='thermostat', cluster_attr='max_heat_setpoint_limit', attr_value=2300, expect_reply=False, manufacturer=-1)
[0xFC3C:1:0xef00] no MCU command for data TuyaClusterData(endpoint_id=1, cluster_name='thermostat', cluster_attr='max_heat_setpoint_limit', attr_value=2100, expect_reply=False, manufacturer=-1)

[prairiesnpr]

oh, another item i spotted. I cant set the max heat value

I didn't expose a max heat DP since it wasn't exposed in z2m. Are you getting a slider for it or just trying to write the attribute directly? If the Tuya app exposes it, we can add it but would need someone to identify the DP, assuming it exists.

[checkiecheck]

oh, another item i spotted. I cant set the max heat value

I didn't expose a max heat DP since it wasn't exposed in z2m. Are you getting a slider for it or just trying to write the attribute directly? If the Tuya app exposes it, we can add it but would need someone to identify the DP, assuming it exists.

it did expose in device as entity:

if it doesnt have info on setting DP, then better not have it at all i suppose (i dont need it)

[prairiesnpr]

if it doesnt have info on setting DP, then better not have it at all i suppose (i dont need it)

Thanks for pointing that out, we do set them as constant attributes, but I wasn't aware that we generated entities for constant attributes, we shouldn't, they are after all constant.

[checkiecheck]

if it doesnt have info on setting DP, then better not have it at all i suppose (i dont need it)

Thanks for pointing that out, we do set them as constant attributes, but I wasn't aware that we generated entities for constant attributes, we shouldn't, they are after all constant.

agree with that :)

[alexanderwwagner]

I tested your PR and found an issue with the custom quirk.
If the trv is on state heating, homeassistant always shows the state idle:

On my other trv from sonoff the state is shown correctly:

Unfortunately i don't know how to fix it, otherwise i would have made a suggestion right away!

[prairiesnpr]

Is the running state correct or is it inverted?

[checkiecheck]

Seems inverted, my schedule starts and turns off, and state is the other way around

[prairiesnpr]

See if changing converter=lambda x: RunningState.Heat_State_On if not x else RunningState.Idle, to converter=lambda x: RunningState.Heat_State_On if x else RunningState.Idle, does it.

[checkiecheck]

Heat_State_On if not x

doenst seem to. Looking at the lines before it wants an attribute running_state. But if i look at attributes in the states screen, i see system mode that gives the info

[prairiesnpr]

They are actually different, system mode is the mode the thermostat is set to, where running state is the actual current state. So we would expect to see system mode on heat then running state in idle or heat depending on if the thermostat is calling for heat. The heating action is then calculated in ZHA based on system mode and running state, sometimes some other attributes, but mostly those two.

[checkiecheck]

They are actually different, system mode is the mode the thermostat is set to, where running state is the actual current state. So we would expect to see system mode on heat then running state in idle or heat depending on if the thermostat is calling for heat. The heating action is then calculated in ZHA based on system mode and running state, sometimes some other attributes, but mostly those two.

got it.. i was impatient seemingly, running state is little behind in reporting. The change you proposed does work.

[alexanderwwagner]

See if changing converter=lambda x: RunningState.Heat_State_On if not x else RunningState.Idle, to converter=lambda x: RunningState.Heat_State_On if x else RunningState.Idle, does it.

Should I change both lines: 131 and 262?
I tried it but now the state is always "heating".

[prairiesnpr]

Should I change both lines: 131 and 262? I tried it but now the state is always "heating".

Try the latest version

[checkiecheck]

History Looks much better now

Heat and idle corrected. Messy yellow lines was me testing

[TheJulianJES]

Is this something like "Away mode" for the thermostat? If so, I'd probably call it that. It's similar to "schedule mode".