-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
TESTERS WANTED! New converter for Tuya TRV _TZE204_ltwbm23f (TRV601Z, TRV602Z, TRV702Z, others?) #8819
Comments
I have the non-OLED TRV601Z and this is worse for me than the current implementation. Some things are null and not working, others have changed name which creates work on the HA side. |
@csutcliff did you remove and repair the device? This is essential because the converter has changed but the state didn't update |
@andreypuhovsky yes I did re-interview and reconfigure |
This is not enough, you have to repair and wait a little bit for device to synchronise |
I wasn't aware that removing and re-adding did anything more than re-interviewing did. I will give it a go tomorrow with a spare. Even if it works it would still be nice to not have to change the names of settings/sensors etc, it would save a lot of time. |
There is a fromZIgbee converter which is called only once after repair |
Main climate attributes' names were not changed, modes/presets are changed intentionally to provide maximum functionality and still be compatible with HA Climate Entity defaults |
Nice work, I'll be testing it during the week. One thing I noticed: The position entity is not reported, can this be added? UPDATE: Forget it, I found it in the file, you it is pi_heating_demand :) |
Hello, thank you for your work, can test it too, I have more versions of "602Z". I'll try and check the power consumption to see if everything is OK. |
One thing I noticed. When the Thermostat is in Auto Mode and I change the target temperature manually, the next schedule does not reset the the target temperature. It stays in "Heat" mode until I revert back to Auto. In the manual of the device it states that the there should be a possibility to temporarily manually override the scheduled temperature. Is there any way to implement this? |
@shajek I didn't notice that for my devices, but still, could you please check with yours? @malwikl I couldn't find this feature for both of my devices neither in app nor in manual nor in api. |
Thanks, and do you know how is this shown in the app? |
No, I don't have a Tuya gateway unfortunately. I'll try to replicate it on the device and send a debug log, but so far did not manage to get the device into that state.... |
I started testing. It is much better with this converter. Thank you @andreypuhovsky! The scheduling settings work now, and it is really great to propose target temperatures mode names (eco / comfort / sleep) in addition to numbers. This simplify TRV's management IMHO. I also checked icons displayed on the TRV itself. Synchronization between Z2M and TRV seems OK (clock when in auto mode, hand when manual, moon and sun when in eco and comfort, two up arrows when in boost, luggage when away). Othe remark on the valve position, which you named "PI heating demand". This leads to IDs like 'sensor.0xa4c1386bc7fed5ff_pi_heating_demand' in HA, and I'm afraid it may be not consistent with other TRV which will expose something like 'sensor.0xa4c1386bc7fed5ff_position' I guess. Screen orientation works. Last remark: Motor thrust still not working (always return to 'middle'), but that's not a big issue. |
Hi @g-chevalier, Regarding system modes and presets. I've tried to use max from predefined settings (which are localized and with icon by default!) from Home Assistant Climate entity, see tables Climate HVAC Modes and Climate Presets. So there's no something more applicable for a configurable mode with the lowest temperature than sleep. (As Away is taken for a Vacation Mode[Tuya]). For the naming of position vs pi_heating_demand.. let me check what are the trends for similar functionality. Don't know what was done first - position expose or pi heating demand expose which is a part of climate expose. That's why I used it in my implementation. Motor thrust seems to be a dummy setting for our devices (because I couldn't find such a setting in an official Tuya App). |
New release! Beta 4 Fixed:
andreypuhovsky--TZE204_ltwbm23f-beta4.txt Waiting for your feedback :) |
Good day! I also have such a TRV and I would also like to test the converter. But since I have just started learning Home Assistance, I don’t know how to get this test converter to work. Please send me instructions on how to make the converter work correctly. I apologize for the lame question and thank you in advance for the answer |
Hi @Aquarius0202, please follow the guide https://www.zigbee2mqtt.io/advanced/more/external_converters.html or search on YouTube how to install external converter. |
Hi everyone,
I've been working on this converter for more than a week to provide the most robust and fully functional one, than we have right now in release version.
This converter supports all the features from the official Tuya application.
Before I spend more time to integrate it in the repo, I would like to get as much feedback as you could provide.
IMPORTANT! You have to remove and repair the device!
Known issues:
Please refer to this comment to get known with Tuya features - Koenkk/zigbee2mqtt#26195 (comment).
This is the functionality in Zigbee2MQTT: TZE204_ltwbm23f-beta3.pdf
HA functionality: Koenkk/zigbee2mqtt#26195 (comment)
Don't forget to rename it to .js after downloading. Please refer to your Zigbee2MQTT version on how to enable it.
[OUTDATED] andreypuhovsky--TZE204_ltwbm23f-beta3.txt
[LATEST] andreypuhovsky--TZE204_ltwbm23f-beta4.txt
If you will see such message as
Please report this issue to the developer with the following data
in the logs, please comment here with the data it provides.This will allow me to investigate into your problem deeply.
The text was updated successfully, but these errors were encountered: