What’s the plan for TRVZB?

Will it be possible to pair them with ihost?
Will it be possible to show them on a Cast dashboard? (Cloud or local one)?
Will it be possible to add them as a widget in NSPanel?
Will it be possible to use a different sensor as temperature sensor for the TRV?
Will it be possibile to use a TRV as a temperature sensor for NSPanel?

These are a lot of questions but it’s the kind of integration I’m expecting from the system.

Any ETA on any of previous question?

Thanks to anyone can answer :blush:

Will it be possible to pair them with ihost?

  • Yes, Currently expected in November version

Will it be possible to show them on a Cast dashboard? (Cloud or local one)?

  • A November or December release is currently expected (cloud and local both)

Will it be possible to add them as a widget in NSPanel?

  • Currently there are plans, but the specific release has not been confirmed. The target is December.

Will it be possible to use a different sensor as temperature sensor for the TRV?

  • There are no plans for that at the moment

Will it be possibile to use a TRV as a temperature sensor for NSPanel?

  • There are no plans for that at the moment

Thanks @Alexie for all the answers :smiling_face:

Any news about it?
Without this possibility the TRVs do not work very well, even after calibration.

Will there be the possibility to open the valve proportionally?
Is it possible to develop software for TRVs?

Isn’t that on schedule? You can now update to the latest version and pair the TRV to the ihost control. CAST support in December - it’s all going according to plan.

Thanks so much for the answer… but my question was this:
Will it be possible to use a different sensor as temperature sensor for the TRV?

already replied earlier: There are no plans for that at the moment

If you have a minute to answer…

Will/When will TRV be fully supported in ewelink scenes (web/app). Currently, users complain about a significant lack of functionality in terms of automation for TRV.

There are problems with the inability to use TRV as a trigger in a scene. So that it is possible to perform actions for other devices based on the TRV status, whether it is open/closed, and to read the temperature.

Currently it is not possible to use TRV and its condition as a trigger.

TRV in “If”, and the valve status is open
“Then” smart device, status On.

TRV in “If”, and the temperature reaches the set value.
“Then” smart device, status On.

Currently, users report that it is impossible to use TRV in a scene in this way, which severely limits its functionality in automation.


I’ve watched the Node Red debugging on an iHost for a while. They don’t update temperature anywhere near enough. Maybe opening/closing triggers sending data, but temperature I doubt that a temp/humidity sensor isn’t much better. The other trigger I can think of that would be a useful trigger is the onset of window mode.

It seems to me that this is not about using TRV as another temperature sensor…

Here, people are probably more interested in performing an action using such a trigger.
Therefore, such high speed and precision of temperature indication is not necessary.

A good example of the problem is @cnt.luc post, yes, his situation is from a minority group, but…

If the TRV notices that its temperature is xyz, turn on or close the valve, which is exactly what it does locally as a stand-alone device. It’s just missing from the scene as a trigger. If it is not possible to implement a variable for temperature, at least read the valve’s closed or open position and perform the trigger based on it. This still seems like a useful feature to implement imho.

Yes, it can be done using a separate temperature sensor as a trigger, but if someone has, say, 10 TRVs, they must buy 10 sensors to have the functionality that is theoretically already in the device.

There are also other ways to extract live information about the device without interfering with it. I did it in two ways: Reading the value in ewelink and PageProbe in the web browser + webhook or ewelink app and macrodroid observing the application for the keyword and reacting accordingly. Both work but are not convenient for the average user to implement and require a dedicated device.

Apparently the TRV trigger will be available later this year… time will tell.

You could already use temperature as a trigger in Node Red if you wanted. The other options are manual/auto/off status, battery and signal strength, but not open.closed. Given how infrequently the temperature updates I don’t think they have the hardware to have temperature triggers. Same is true of the other two types of smart valve I have though. Suspect it’s to do with saving battery power.
The valve can check temperature for itself without transmitting a lot more efficiently than if it also has to update a coordinator. Open/closed though I’d bet can get induce an update and might be useful.

I welcome the feature to use an alternative temperature sensor to control the TRV; assuming this could be done with a scene. If room temp below X degrees then open TRV and turn boiler on. If room temp over Y degrees then close TRV and turn boiler off. This is quite basic functionality.

Are there plans for a boiler control to work with the TRV’s? Something a bit more fancy than a basic switch or that works with a bigger wiring centre?

Node Red or any other solution is always an alternative when it comes to the Sonoff product, but there is probably a huge group of users who would prefer to stay with the ewelink ecosystem and not have to add blocks to this game. :slight_smile:

I think it’s something a little different… Using a different temperature sensor to pair with the TRV to replace the built-in sensor.
However, controlling via the scene and an additional sensor is a slightly different concept that can probably be implemented today.

For example, SNZB-02P as a trigger, when it indicates temperature X, in action, TRV open.
Of course, provided that the SNZB-02P can be used as a trigger with a specific value.

Instead of Fan, TRV…

The question was:

The answer was:

What do you use to control the boiler currently?

Sticking within EWeLink is the key element here. The solution needs to be simple and not reliant of external components and what is available at present is not a working solution.

Currently, I’ve got boilers being controlled by traditional Honeywell controls and I want to replace that and the standard TRV’s but Sonoff is not ready yet.

In another instance I have a Google Nest with traditional TRV’s that’s also switched with a Sonoff Mini, and another instance I have Tado throughout which generally works well but to upgrade to a larger deployment would require multiple instances as they only support one router/gateway. With Sonoff, if there’s a Zigbee black spot, I can put another Zigbee gateway or router such as an S26.

I hear you and I generally agree.
There is supposed to be another ewelink update in December and trv is supposed to appear as a trigger, so let’s wait a little longer.

Ok… but you have this boiler with a valve and you want to install a TRV next to it?

I don’t have a boiler, I only have an electric water pump that circulates hot water in the pipes, and I only have thermostats on the radiators.
What function would the TRV need to have for you to be able to control your boiler?
When TRV support appears in scenes as a trigger, you will be able to control other sonoff devices with it.

What else do you need from TRV to be fully functional in your situation?

In the UK, central heating is common, where either a gas-fired (in most cases), wood or oil-fired (in remote parts where there is no piped/mains LNG exists) heats radiators around the home to about 60 degrees Celsius, or underfloor heating where there is a mixing manifold which delivers heat at an average 21 degrees Celsius.

The boiler is generally in two formats, a system boiler or combi boiler.

The system boiler heats a tank of hot water (thermal heat store) and hot water for outlets or radiators generally circulates through the tank. Hence there can be hot water without the need for the boiler to come on. In this case, the tank would have a connected thermostat which switches the boiler on when the tank temperature drops. In this scenario, the tank has an electric immersion heater (usually 3-6Kw) which acts as a backup if the boiler fails.

The other format, combi (combination) is where the boiler provides instant hot water to outlets or circulates through radiators.

In the case of the system setup, a TRV on a radiator should switch on the boiler if tank temperature is low (unless the radiator flow/return circuit goes direct to the boiler) and there is demand (radiator is below desired temp). When radiator is hot (above desired temperature) and tank is hot, boiler should be turned off. In the combi setup, the TRV should control the boiler switch directly. In both system and combi setups a single thermostat would control when the heating comes on; this isn’t great because houses should be zoned with more thermostats but that’s where smart TRV’s and smart temperature sensors can help drive efficiency and automation.

It’s worth adding that the heating controller is used as a time switch for separate programmes for hot water (system boiler setup only) and central heating. To control whether heating is on / off or hot water is on / off, a Sonoff Dual Lite can be used with a programmer like the Honeywell model shown so switching is 2-way.

More modern houses or passive houses would rely on electricity to heat electric underfloor heating with each room being a zone and an immersion heater would heat a thermal store for water outlets but these are less than 1% of the housing stock.

Where there are apartment blocks, larger ones would be solely electric heated as they don’t have boilers and smaller blocks are normally with gas boilers.

Of course there are a wide variety of homes but the majority rely on main gas boilers.

In my instances, all radiators except one (emergency heat dump for boiler if all TRV’s are closed) would have smart TRV’s and either the TRV thermostat or a separate smart thermostat will control when the boiler needs to fire.

I need the TRV (or separate smart thermostat) to trigger the boiler, but there needs to be intelligence. For example, if I have two TRV’s both needing heat, an on trigger is sent to the boiler but the off trigger can only be sent when all TRV’s are sending off. It’s not complicated logic. Until this is here, I can’t use my TRV’s as they would just be left in the manual on mode wasting battery power!

Ideally, the groupings could help control this functionality but if there was a separate heating function, designed specifically for this purpose, the setup could be easier for less savvy users.

Less essential, is the adding of TRV’s to cast with simple override functions or controlling groups of TRV’s with the same schedule. By example, my Tado setup in a property that I have multiple rooms on Airbnb has a schedule with a different target temperature set every hour of the day. This way, if a guest cranks up the temperature, at most, it will heat the individual room for an hour until the new target temperature takes effect. The same schedule is applied to all bedrooms (one group), another group is for the living room, hallways and kitchen; and a third group for the bathrooms. This way, I only have to configure three groups and the fifteen radiators rely on those group settings.

Here an example of a radiator with a Sonoff TRV compare to a traditional TRV, a very old (but still working) thermostat and the heating controls for a system boiler. The thermostat and heating controls all switch at 240V.