TRVZB Controlling Wi-Fi Devices within iHost (Reliablity)

eWeLink CUBE
1

I would appreciate any observations about a reliability issue I’ve noticed.
My set up is iHost (firmware 1.13.4), TRVZBs as Masters to control Wi-Fi switches that switch the Central Heating Boiler ON (when the TRVZB status is ‘Heating’) and OFF (when the TRVZB status is 'Keeping). To achieve this I am using very simple smart scenes:

For Heating
If
(Smart Device) TRVZB status = ‘Heating’
Then
(Smart Device) Wi-Fi Switch= ‘ON’

For Keeping
If
(Smart Device) TRVZB status = ‘Keeping’
Then
(Smart Device) Wi-Fi Switch= ‘OFF’

I’ve noticed that on (very) few occasions that the slave Wi-Fi switch will not be in the state as commanded by the TRVZB.

This situation leads me to believe that the scenes I have used only run once each time that the TRVZB changes its status and there is no check that the TRVZB > Wi-Fi Switch command has completed successfully. As I can manually change the state of the slave switch it indicates that there is not any solid sync between the TRVZB as ‘Master’ and the Wi-Fi switch as ‘Slave’. One way I’ve thought about improving the reliability of the scene was to add multiple Then lines to the scene for eg:

For Heating
If
(Smart Device) TRVZB status = ‘Heating’
Then
(Smart Device) Wi-Fi Switch= ‘ON’
Time delay 5 sec
(Smart Device) Wi-Fi Switch= ‘ON’
Time delay 5 sec
(Smart Device) Wi-Fi Switch= ‘ON’

But as this is not a very elegant solution I would appreciate any ideas how fail safe reliability can be achieved preferably using smart scenes. Or is there a way to automatically re-run a scene that failed ?

Thanks

1 Like
2

March 2026 Two years on and there is a solution to this issue: We found that if the ‘Heating’ and ‘Keeping’ scenes are disabled and then re-enabled the slave device and TRVZB will attempt to re-synchronise. A stand-alone wi-fi switch which has inching and loop-timer facilities can be configured to generate a pulse ( eg 0.5sec ON every 60secs) to trigger scenes to disable and enable the ‘Heating’ and ‘Keeping’ scenes ad infinitum.

example scene:

IF (all conditions are met)
Parent Device (eg TRVZB, TH10/16 etc) Status
Pulsing Device = ‘ON’ (eg 0.5 sec ON pulse every 60 secs)

THEN
Child Device > switch to appropriate condition (ON or OFF)
effective period 24 hours

Suitable switches are WiFi - Sonoff Basic or for Zigbee 3.0- BSD17 (eWeLink SWITCH-ZR03-1)

1 Like
3

We also find that using the Sonoff 4CHPRO R3 as ‘slave’ (child device) to TRVZB as ‘master’ (parent device) does not suffer from this issue. The ON or OFF state of individual switches can be included in scene IF and THEN statements. The modified scene structure would be:

For Heating
all conditions met
If
(Smart Device) TRVZB status = ‘Heating’
(Smart Device) 4CH PRO Allocated Channel = ‘Off’
Then
(Smart Device) 4CH PRO Allocated Channel = ‘On’

Effective 24 hours

A similar scene can be written for the ‘Keeping’ function.

We have found that the Sonoff 4CHPRO switch is a better solution as the ‘Child’ device to control a boiler for the following reasons:

  1. It provides clean voltage-free relay contacts.
  2. Individual switch ON/OFF status is available to use in scene IF and THEN statements.
  3. For Central Heating it gives multiple zones and each Channel can be controlled by multiple parent devices.(although in practice we have only allocated a maximum of 2x TRVZBs/ Channel.
  4. Has the ability to be powered by AC mains or low-voltage DC.
4

Thank you so much for sharing your findings and solutions in such detail! You have also summarized clear scene configuration logic and several practical advantages, which are an invaluable reference for us and other users. Thank you again for your selfless sharing and patient support!

1 Like