logo elektroda
logo elektroda
X
logo elektroda

TRV Smart Head for Heater - External Sensor Control Issues with Zigbee Scenes

Janeo 3423 12
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 20912069
    Janeo
    Level 12  
    Posts: 232
    Rate: 32
    Board Language: polish
    I connected in Scenes a gate, a head (modern, 3xAA) and an external temperature sensor. I have set in these Scenes the times of the relevant operation of the head (heating, pause) depending on the ambient temperature indicated by this EXTERNAL sensor. Thus, the scenes are and are active.
    By way of explanation I would like to add that the Tuja programme (Smart Life) has in the settings an option called "Heating Sequences" permanently switched on (I presume so, because there is no option to switch it off) where the desired temperature and ambient temperature, which comes from the head sensor at the radiator, are set for the week - hours.

    Well, my head as I can see from the behaviour of the % tightening/un-tightening graph works according to the "Heating Sequence" and not according to the active Scenes. The conclusion is that the head cannot be controlled by external temperature sensors, e.g. in my case a sensor lying on a table in the middle of the room.

    Has anyone tried connecting the head to an external temperature sensor, and if so, with what results?
  • ADVERTISEMENT
  • #2 20912114
    freebsd
    Level 42  
    Posts: 6790
    Help: 766
    Rate: 2025
    Board Language: polish
    Janeo wrote:
    I have set in these Scenes the hours of relevant head operation
    What time ranges did you select?
  • ADVERTISEMENT
  • #3 20912122
    Janeo
    Level 12  
    Posts: 232
    Rate: 32
    Board Language: polish
    As it is according to you a matter of importance, I can of course inform :-) .
    I would add that the hours from the Scenes overlap with the hours from the "Heating Sequence" because, as you know, a day is one.
  • ADVERTISEMENT
  • #4 20912134
    freebsd
    Level 42  
    Posts: 6790
    Help: 766
    Rate: 2025
    Board Language: polish
    Janeo wrote:
    If it's a matter of importance according to you, then of course I can inform you .
    You've just set up a thread asking for help with setting up scenes in Tuya with a time schedule. To answer your question, for me this information is not relevant.
  • ADVERTISEMENT
  • #5 20912143
    Janeo
    Level 12  
    Posts: 232
    Rate: 32
    Board Language: polish
    I didn't start a thread asking for help with scene configurations because I know such configurations like the trowel. Nonetheless, thank you for your interest :-)
    I have started a thread about the head working with scenes, has anyone had similar problems that the head does not work in scenes but chooses to act according to the "Heating Sequence".
  • #6 21270759
    grzmeh
    Level 3  
    Posts: 6
    Board Language: polish
    I have a question, have you already solved the problem with the head and scenes, because I have the same situation and don't really know how to solve it.
  • #7 21271062
    Janeo
    Level 12  
    Posts: 232
    Rate: 32
    Board Language: polish
    Specifically what is the problem, can you describe?
    What model of TRV and what communication protocol?
  • #8 21271664
    grzmeh
    Level 3  
    Posts: 6
    Board Language: polish
    I'm just gaining experience in this topic, I wanted to prepare a scene: if the temperature on the external sensor drops, the head is supposed to switch to heating mode. The scene turns on, but the head does not react, as if it is under the control of the application. I'm probably doing something wrong, but what, I don't know at the moment.

    Added after 2 [minutes]: .

    Moes head - type not found 3 AA batteries, ZigBee protocol.
  • #9 21271677
    Janeo
    Level 12  
    Posts: 232
    Rate: 32
    Board Language: polish
    grzmeh wrote:
    Scene comes on but head does not respond as if under application control.


    Firstly you need a zigbee gateway for the set (I assume you have one), secondly if the head does not respond, it IS NOT (not - IS) under application control.
    ps: set the head to Manual mode, and only ON<->OFF in scenes(possibly Pause).
    Also put Notifications in scenes to make sure the scene is on. Take note that the whole thing may work with a 25-minute delay.
  • #10 21271716
    grzmeh
    Level 3  
    Posts: 6
    Board Language: polish
    Thank you, I will test it right away
  • #11 21291447
    Jericho24
    Level 20  
    Posts: 505
    Help: 4
    Rate: 162
    Board Language: polish
    grzmeh wrote:
    Thanks, I'll test it soon
    .
    And what came out of the tests?
  • #12 21293436
    grzmeh
    Level 3  
    Posts: 6
    Board Language: polish
    Thanks again for the tips, the one about the scene delay was particularly valuable, as I had previously defined a scene and was waiting for the effect. As for the head itself, as I mentioned earlier, the application of the head itself has power over most of the parameters. From the scenes I was able to run the target temperature setting function, thus I can adjust the opening and closing of the head - which is really what it was all about. I bought more heads and temperature sensors and will try to configure the system for the whole house, the idea is to check the temperature with the sensor, and if it is too high or too low, I turn on the heating, I don't know if this is the most efficient, because I plan to install 5-6 sensors. The subject is probably more complex, because you can, for example, control the heads (a lot of freedom points, which can be controlled). How did you solve the control of the heating in the whole house at your place?
  • #13 21316868
    Janeo
    Level 12  
    Posts: 232
    Rate: 32
    Board Language: polish
    grzmeh wrote:
    Thank you again for the tips, especially valuable was the one talking about the delay in the effect of scenes, as I had previously defined a scene and was waiting for the effect. As for the head itself, as I mentioned earlier, over most parameters the application of the head itself has power.
    .


    You're welcome.
    As for the functions it is not you, rather I have been telling you from the beginning that you should set only on one - ON<->OFF - and not on any part of the parameters, because any setting of scenes to other actions of the automation which is based on its own (internal) sensor in the head causes the TRV to take complete control of the situation ignoring external data.

Topic summary

✨ The discussion addresses issues with controlling a TRV smart radiator valve (head) using external temperature sensors within Zigbee scenes configured in the Tuya Smart Life app. The user observes that the TRV head operates according to the app's built-in "Heating Sequence" based on its internal sensor rather than responding to external sensor data or scene triggers. It is clarified that the TRV head prioritizes its internal temperature sensor and heating schedule, overriding external scene controls. To enable scene-based control, the head should be set to Manual mode with simple ON/OFF or Pause commands in scenes, avoiding parameter adjustments that conflict with the internal heating sequence. A delay of up to 25 minutes in scene execution is noted. The model discussed is a Moes Zigbee TRV head powered by 3 AA batteries. The conversation highlights the complexity of integrating multiple external sensors for whole-house temperature management and the limitations imposed by the TRV's internal automation logic.
Generated by the language model.

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

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.
  1. Set the TRV to Manual mode.
  2. In scenes, toggle ON/OFF (or Pause) based on the external sensor.
  3. 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]
Generated by the language model.
ADVERTISEMENT