I have a few Tuya TRVs with device ID: _TZE204_ltwbm23f
They have an “Eco Mode” and decide every night at 22:00 to change to their Eco Temperature setting - not the temperature I configured. These are the configuration settings I have to play with and I have no idea how to stop the TRV from reducing the temperature setting. Does anyone have any idea?
I remember I had the same issue with the TRVs I had.
I created an automation that undid that change
Thanks and I appreciate that’s an option but I have many TRV’s and they are at different settings during the day so it would be very complicated to manage that.
I think I may have found an (ugly) solution. When my automation sets the target temperature to e.g. 20, add an Action, Number, Set Number, to set the Eco Temperature to 20 as well. So even it it changes to eco mode, it doesn’t change the target temperature. Hopefully that works.
Perhaps i’m “shooting blanks”, but…
i have sonof trv’s, but they are connected to HA with ZHA, as yours. Since i have one spare trv i played with it on my test HA in Z2M mode, and when connected via Z2M i get way more functions and sensors, and one of them is schedule, which is not visible in ZHA. So, i wonder: perhaps you also have schedule on tuya trv which is active and set to change to eco at set time, but you can’t see it in ZHA. If you manage to disable that schedule this might not happen.
Perhaps check this in tuya app (if you can) .
Yes that is probably correct but by some reason they are shipped with a schedule and there is nothing in the manual about how to remove it.
Tuya app requires you to have a Tuya gateway?
I believe most do not have the gateway but any other Zigbee antenna.
That’s a good question. I also can’t figure out how to add my sonoff’s into sonoff app. Not that i need it to, but just wondering…
I fear that you might be correct: first to add tuya gateway and only then to add tuya trv into app through that tuya gateway… if it’s true then only alternative is to use Z2M, i guess
yes same issue
My proposed solution seems to work reasonably well. I have about 10 Automations, and they all use 2 scripts each (Set Hot - Set Cold) per group (e.g. Living Room Set Hot / Living Room Set Cold) and I updated those scripts to also set the Eco Value to the same value as the Hot/Cold value. That seems to do the trick although I think it’s not a very pretty solution.
No… that was the issue for me too.
I could manage it at times but then at some point our TRVs all of the sudden did something else and it broke my “fix”.
That’s when I got tired of them and just replaced them with actuators instead since they just do as they are told and nothing else.
Another “fix” for people suffering this problem. I figured out that when the “Hysteresis mode” of these devices is set to Eco, the TRV’s switch off when the target temperature reaches the Eco temperature. I have no idea why but that’s the way it is on my TRV’s
I fixed that through an automation which switches it back the moment the Eco Mode kicks in (and yes, I had to do it a few times for it to work)
alias: "TRV: Force Hysteresis to Comfort"
description: "Forces Hysteresis back to Comfort with a delay and retry"
trigger:
- platform: state
entity_id: select.living_room_bay_window_dec_2025_hysteresis_mode
to: "Eco"
action:
# 1. Wait 3 seconds for the device to stop 'talking'
- delay: "00:00:03"
# 2. Send the first command
- service: select.select_option
target:
entity_id: select.living_room_bay_window_dec_2025_hysteresis_mode
data:
option: "Comfort"
# 3. Wait another 2 seconds and send it again just to be sure
- delay: "00:00:02"
- service: select.select_option
target:
entity_id: select.living_room_bay_window_dec_2025_hysteresis_mode
data:
option: "Comfort"
mode: restart
You know you can make one automation that will take care of all your TRVs?
Just list all input selects as triggers and use {{ trigger.entity_id }} as the entity in the actions.