Closed Sirse closed 2 years ago
You can trying if its compatible with the normal tuya electrical heating thermostat that is in https://github.com/zigpy/zha-device-handlers/blob/dev/zhaquirks/tuya/electric_heating.py (the cluster looks the same so that is good).
Add your new manufacturer at https://github.com/zigpy/zha-device-handlers/blob/d43df422d103f2bfa5d4cd37c6721f32cdbde984/zhaquirks/tuya/electric_heating.py#L140 and configuring local quirk and testing the new made quirk.
Device uses two different time offsets for UTC and local time payloads: UTC timestamp with time offset 2000 Local timestamp with time offset 1970 Current time sync code supports only one universal offset value for both timestamps via _set_timeoffset https://github.com/zigpy/zha-device-handlers/blob/28bd89a2f34da9a15dd37370734af4e222850316/zhaquirks/tuya/__init__.py#L236
Bug or one more TuYa proto specification?
Its known that tuya TRVs is using 2 different methods setting the time and if some new devices is using the other method then its need doing some changes in the quirk for getting it working OK.
Temporary quirk draft for this device - https://gist.github.com/Sirse/3cf8172935d81c5c00655650854e3160 (almost untested, without schedule support). Works only with https://github.com/zigpy/zha-device-handlers/pull/1021 due to own timesync mechanism
The time fix is merged in dev and is coming in HA 2021.10.
Did you have more time testing it ??
I think its more users that like getting the device supported in ZHA if its possible so its being great if you can making it all the way.
Thanks in advance !!
All basic features (set/get temp, on/off, get state) works fine.
Current problems:
I can create PR with current quirk (https://gist.github.com/Sirse/3cf8172935d81c5c00655650854e3160) and fix these issues later.
I think its much better then not working at all and the "original" Moes is also not having all parts working like the schedule .
I think is only the Moes TRVs that have getting all possible functions implanted and working but i have not betting and feedback from user of all TRVs that is implanted.
My Revolt (Siterwell) is not having all but they is working well for 10 mounts and other users is using them 2 so i think its better little then not at all.
If you like to knowing what DP the thermostat is one dev have saying that if you is disconnecting the power for some minutes and ting it they is sending all possible DP they is supporting (I have trying and finding that my is supporting valve jammed but i cant implanting it then i can not do the coding ;-(( ).
Also if Z2M and deCONZ have implanting it its possible looking what DP they is using.
If you do one PR its being great bit not one must and im sure users is valuing it much then they is getting devices that can working OK in there systems.
Z2M have it but i have not looking how they have doing the DP things in to and from zigbee.
Any updates here ? really waiting for this device support =)
Any updates here ? really waiting for this device support =)
You can use custom quirk :) Now tuya dp can be discovered via their own api (https://www.zigbee2mqtt.io/how_tos/how_to_find_tuya_data_points.html), i'm waiting for my tuya hub shipping :)
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
One of the best cheap chiniese thermostate (internal and external temp sensors, overload/overheat protections, 0.5C settings step with hysteresis, settings restore after powerfail, almost zero network spam) doesn`t have ZHA support (because proprietary TuYa proto).
Support was already implemented in Z2M (via https://github.com/Koenkk/zigbee-herdsman-converters/pull/1694)