FAQ
TL;DR: 25-minute delays are normal; "Set the head to Manual mode, and only ON↔OFF in scenes" to make external sensors work. Most Tuya/Moes Zigbee TRVs will otherwise follow Heating Sequence from the valve’s own sensor. [Elektroda, Janeo, post #21271677]
Why it matters: This helps Tuya Smart Life users fix TRVs that ignore Zigbee scenes driven by external temperature sensors.
Quick Facts
- Expect up to ~25 minutes latency between a scene trigger and the TRV’s actuation; design scenes accordingly. [Elektroda, Janeo, post #21271677]
- For reliable control via external sensors, use Manual mode and toggle only ON/OFF (or Pause) in scenes. [Elektroda, Janeo, post #21271677]
- Tuya Heating Sequence reads the TRV’s internal sensor and can override overlapping scene logic. [Elektroda, Janeo, post #20912069]
- A Zigbee gateway is required for the TRV and scenes to communicate. [Elektroda, Janeo, post #21271677]
- Moes Zigbee TRV uses 3×AA batteries and communicates over Zigbee. [Elektroda, grzmeh, post #21271664]
Why is my TRV ignoring the external sensor and following Heating Sequence?
Because Heating Sequence uses the valve’s own onboard temperature sensor and schedule. If your scene schedule overlaps, the TRV follows Heating Sequence instead of your external-sensor logic. Users observed scenes active, yet the head acted per the weekly Heating Sequence. Avoid overlap if you rely on the external sensor. [Elektroda, Janeo, post #20912069]
How do I make Zigbee scenes control the TRV reliably with an external sensor?
Use this setup: “Set the head to Manual mode, and only ON↔OFF in scenes.” Then allow for latency.
- Set the TRV to Manual mode.
- In scenes, toggle ON/OFF (or Pause) based on the external sensor.
- Add a Notification action and wait up to 25 minutes for the change.
This pattern avoids internal overrides and confirms triggers. [Elektroda, Janeo, post #21271677]
Do I need a Zigbee gateway for scenes to control the TRV?
Yes. A Zigbee gateway is required for the TRV, external sensor, and scenes to communicate and function as a set. Without the gateway, the head will not respond to scene commands from Smart Life/Tuya. Confirm the gateway is online before testing automations. [Elektroda, Janeo, post #21271677]
Can scenes change the target temperature instead of switching ON/OFF?
A user succeeded in setting target temperature via scenes and thus influenced valve opening/closing. However, the head’s application still controls most parameters, limiting scene authority. If you need deterministic external-sensor control, prefer ON/OFF toggling in Manual mode. This balances simplicity and predictability. [Elektroda, grzmeh, post #21293436]
Why does the valve react so slowly after a scene fires?
This system exhibits noticeable latency. Expect up to 25 minutes between a scene firing and the TRV changing state. Add a Notification step in the scene to verify the trigger, then wait for the valve to catch up. Plan scene timing with this delay in mind. [Elektroda, Janeo, post #21271677]
Does Heating Sequence use the internal or external temperature?
Heating Sequence uses the temperature from the head’s own sensor at the radiator. It does not use the external sensor’s reading. If both are configured, the valve tends to follow the internal-sensor schedule. This explains the apparent override behavior. [Elektroda, Janeo, post #20912069]
How do I prevent Heating Sequence from overriding my scenes?
Keep scenes minimal and state-based. “Set only on one — ON↔OFF,” and avoid changing parameters like target temperature via scenes. When scenes adjust internal-sensor-driven functions, the TRV assumes full control and ignores external data. Limiting scenes to ON/OFF prevents this conflict. [Elektroda, Janeo, post #21316868]
My scene says it ran, but the head didn’t move. What should I check?
First, ensure a Zigbee gateway is present and online. Set the TRV to Manual mode so scenes can control it. Add a Notification to confirm the scene trigger. Then wait up to 25 minutes for the valve to respond. If it still doesn’t move, reconsider the scene’s actions. [Elektroda, Janeo, post #21271677]
Can I scale this to multiple rooms with several sensors and TRVs?
Yes. One user expanded to house-wide control by adding more heads and sensors, planning 5–6 sensors total. Their approach uses scene thresholds to switch heating when temperature is too high or too low. Start room-by-room and keep scenes simple for reliability. [Elektroda, grzmeh, post #21293436]
Which TRV model and protocol are discussed here?
The thread covers a Moes smart TRV using the Zigbee protocol and powered by 3×AA batteries. This aligns with common Tuya Smart Life integrations for scene-based control. Verify your specific model’s manual for any differences. [Elektroda, grzmeh, post #21271664]
What does Manual mode accomplish in this setup?
Manual mode prevents the internal schedule from dictating behavior, allowing scenes to switch the valve’s state. As recommended: “Set the head to Manual mode, and only ON↔OFF in scenes.” This combination enables external-sensor-driven control to take effect. [Elektroda, Janeo, post #21271677]
How do I confirm that a scene really executed?
Add a Notification action inside the scene. When it triggers, you’ll get an alert confirming the scene ran. Then wait for the TRV to enact the change, considering the typical delay window before movement occurs. [Elektroda, Janeo, post #21271677]
Has anyone resolved this issue and what was the outcome?
Yes. After applying the delay insight, a user achieved control by setting target temperature via scenes, while noting the app still governs most parameters. They proceeded to scale with more TRVs and sensors. This confirms the method works with care. [Elektroda, grzmeh, post #21293436]
Edge case: I set parameters in scenes and the TRV ignores the external sensor. Why?
When scenes manipulate internal-automation parameters, the TRV takes full control and disregards external data. Keep scene actions to ON/OFF in Manual mode to avoid this failure mode. This prevents conflicts with the valve’s internal logic. [Elektroda, Janeo, post #21316868]
.
