Skip to content
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

Open
andreypuhovsky opened this issue Feb 16, 2025 · 19 comments

Comments

@andreypuhovsky
Copy link
Contributor

andreypuhovsky commented Feb 16, 2025

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:

  • [FIXED] When changing mode from Off to Auto, the temperature doesn't update
  • [FIXED] If while the Boost Mode lasts the next Auto Mode transition will happen, the temperature will not be updated to the new one after Boost Mode ends (will show previous temperature until next temperature update).

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.

@csutcliff
Copy link

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.

@andreypuhovsky
Copy link
Contributor Author

@csutcliff did you remove and repair the device? This is essential because the converter has changed but the state didn't update

@csutcliff
Copy link

@andreypuhovsky yes I did re-interview and reconfigure

@andreypuhovsky
Copy link
Contributor Author

andreypuhovsky commented Feb 16, 2025

This is not enough, you have to repair and wait a little bit for device to synchronise

@csutcliff
Copy link

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.

@andreypuhovsky
Copy link
Contributor Author

There is a fromZIgbee converter which is called only once after repair

@andreypuhovsky
Copy link
Contributor Author

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

@malwikl
Copy link

malwikl commented Feb 17, 2025

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 :)

@shajek
Copy link

shajek commented Feb 17, 2025

Hello, thank you for your work, can test it too, I have more versions of "602Z".
If i can ask, have you this problem too ?
Koenkk/zigbee2mqtt#25833
I was trying to solve it, but ...

I'll try and check the power consumption to see if everything is OK.

@malwikl
Copy link

malwikl commented Feb 17, 2025

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?

@andreypuhovsky
Copy link
Contributor Author

andreypuhovsky commented Feb 17, 2025

@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.
When I change the temperature in app the device goes to custom mode. The only possibility to temporary change the temp is boost mode.
Could you please provide photos of manual, and screenshots/screencasts from tuya app if you have their gateway?

@malwikl
Copy link

malwikl commented Feb 18, 2025

Sure, this is what I found in the manual:

Image

@andreypuhovsky
Copy link
Contributor Author

Thanks, and do you know how is this shown in the app?
Also as I don't have such a device, to understand how it works I will need raw debug data for all datapoints when this mode is set.
This can be done by you or anyone else with the same device.

@malwikl
Copy link

malwikl commented Feb 18, 2025

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....

@g-chevalier
Copy link

I started testing. It is much better with this converter. Thank you @andreypuhovsky!
Up to now, I did not test every scenario as this is the first time I deal with TRV and HA Climate GUI, and I was disappointed at the beginning with the notion of System modes and modes (presets 'sleep', 'eco', 'comfort', '100%', 'away', 'boost'), mainly by the interactions between them, that is not every time straightforward.

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).
One remark: the Froze icon is used for night / sleep, which may be is not consistent with other TRV in Z2M? Not sure about that…

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.
Display brightness works.
Regulation mode works (I have 0 or 100% in hysteresis mode, and intermediate values in pid mode).

Last remark: Motor thrust still not working (always return to 'middle'), but that's not a big issue.

@andreypuhovsky
Copy link
Contributor Author

andreypuhovsky commented Feb 18, 2025

Hi @g-chevalier,
Highly appreciate your feedback, thank you!

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).

@andreypuhovsky
Copy link
Contributor Author

andreypuhovsky commented Feb 19, 2025

New release! Beta 4

Fixed:

  • known issue with auto -> off -> auto not returning back to auto temperature - the temp now will not be overridden with min temp when turning off = no need to set correct temp back.
  • issue with changing auto mode temp while in boost mode now handled properly - the temp after boost mode will be for the correct transition now.
  • renamed pi_heating_demand back to position (I don't like the naming but the trend shown it's value..)

andreypuhovsky--TZE204_ltwbm23f-beta4.txt

Waiting for your feedback :)

@Aquarius0202
Copy link

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

@andreypuhovsky
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants