-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tuya TRV602Z not so well supported #26195
Comments
Got 10 of these TRVs, investigating how to implement some features. This is my device btw |
I guess I've found how their engineers have done the schedule to support all the features they provide. @Koenkk I know we are not in the right place (should we probably move to converters repo?), but are there any converters with complex functionality like composite groups? I've found some semi-complex one for the following device https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/src/devices/tuya.ts#L4598. |
Nobody wanting to capitalize on discussions/25269 work? As said, the converter prototype that can be found here is working with schedules. |
fyi @g-chevalier I've finished my work, but this is still considered as beta :)
However these are identical without cover and "screen". I guess I will share the implementation as external converter tomorrow in z2m-converters repo discussions (and mention it here), because it will take a while to get it in a release version. Functionality as below ![]() |
Thank's @andreypuhovsky you for your hard work! |
@g-chevalier here you go Koenkk/zigbee-herdsman-converters#8819 |
@andreypuhovsky, I just posted some feedback into your request to comments. Thank you again. |
What happened?
This TRV listed as supported in the devices pages is in fact partially supported.
Before going into details, as there is a lot of confusion on Tuya's devices identification, here is the exact data I have from Zigbee pairing:
Moreover, "TRV602Z" is indeed written on the device itself, and the picture correspond (the new OLED display).
Auto mode and schedules problem:
In "manual" modes, presets are working well. If I set Preset to "Eco" or "Comfort", the target temperature displayed on the valve itself corresponds to the respective temp settings and the mode icon follows the Preset.
The "Auto" mode doesn't work as intended.
First, when the valve is set to "Auto" mode, the icon on the valve is OK (the one with a clock), but the target temperature displayed is not the one that is in the schedule (here 20.0 as per the factory default "06:00/20.0 08:00/15.0 12:00/20.0 14:00/15.0 18:00/20.0 22:00/15.0"), but stay on the "Eco" setting.
And, here is the worst problem, as soon as we update a schedule in the GUI, this scrambles the device settings.
I did a simple test. Factory default schedule is "06:00/20.0 08:00/15.0 12:00/20.0 14:00/15.0 18:00/20.0 22:00/15.0" for all days. I just changed the schedule for the current day to "06:00/19.0 08:00/17.0 12:00/19.0 14:00/17.0 18:00/19.0 22:00/17.0" (without touching hours, just the target temperatures to be sure that I was not wrong on the time periods syntax).
After applying this new schedule, the TRV displays the antifreeze icon and target temperature is 5°C. For other untouched days, it's OK, it works according to schedules.
While googling for support of this _TZE204_ltwbm23f particular model, I found this discussion where the proposed converter works for the daily schedules (file trv601z_trv602z.txt, renamed into .js): discussions 25269
Motor thrust problem:
This setting seems to just be silently ignored, and always stays to "middle".
If I click on "Weak", I can see in the logs that it immediately returns to "Middle". Same on the GUI as soon as it is refreshed.
Display orientation problem:
If I change screen orientation on the device itself using the push button, over the 4 possibilities, the following errors are triggered in the logs for positions right and left:
The relevant frames I found in debug mode for this setting are:
So, it seems that dp 113 with values 2 and 3 holds left and right orientation.
What did you expect to happen?
No errors and full support of all cases.
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
2.1.0-1
Adapter firmware version
Not relevant
Adapter
Not relevant
Setup
Home Assistant OS
Debug log
No response
The text was updated successfully, but these errors were encountered: