After noticing on several occasions that switching devices tied by scenes as ‘Child’ devices to Sonoff TRVZB Valves as ‘Parents’ were not properly in syncronisation e,g. TRVZB showing status as ‘Heating’ and the ‘Child’ device showing ‘Off’ when it should have been showing ‘On’ we conducted the attached experiment to determine if synchronisation after a change of status is ongoing.
SONOFF TRVZB ONGOING STATUS SYNCHRONISATION EXPERIMENT.pdf (86.9 KB)
As a sequel to the detailed experiment we found that this phenomenon does not effect the individual switches of the Sonoff Wi-Fi 4CH PROR3 (Software ver 3.8,2) as ‘Childs’ linked to TRVZBs as ‘Parents’. Unlike single channel switches each channel of a Sonoff Wi-Fi 4CH PROR3 can be included in iHost Scene ‘IF’ and ‘THEN’ Statements. All of the Sonoff TRVZB heating systems we design use the 4CHPROR3 channels as ‘Childs’ to 1 or 2 (max) TRVZBs.
Additionally, in iHost using a Node- Red virtual switch and 2 scenes we constructed a pulse timer giving a 1 second pulse every 60 seconds to trigger a scene to disable and then re-enable the Heating and Keeping scenes but found that this solution used a considerable amount of the iHost processing power.
What we would suggest to anyone who is using 1 switch as a ‘Child’ device to turn a boiler ON and OFF under the control of one or more TRVZBs as ‘Parent(s)’ is to use a separate hardware device to generate a regular time pulse to trigger the scenes that disable then re-enable the Heating and Keeping scenes to ensure that the state of the ‘Child’ switch is checked against its ‘Parent(s)’ Status. A simple solution is to have a dedicated switch (for example a Basic Switch) with its ‘loop’ and ‘inching’ settings set to give a pulse of the desired duration at the desired interval.