One scene triggered by another unconnected scene

[Keithlambley 3]

I have a Universal Sensor device connected to an output on my conventional house alarm panel so my HC3 knows when the alarm is armed, this has worked reliably for several years.

 

I use this to trigger various scenes.

 

1) A scene to close an actuated valve on my main water supply after 3 hours from when the alarm is armed, as the alarm is armed, I am not at home therefore the water can be turned off, delayed by 3 hours to allow the dishwasher or washing machine to complete their cycles. This has worked reliable for several years.

 

2) A scene to check if the actuated valve on my main water supply has closed after 3 hours and 1 minute of the alarm being armed, if not generate a warning message. This has worked reliable for several years.

 

3) I have recently created a new scene, when the alarm is armed and a variable is set to "Holiday mode ON" I will be sent a message. This is also working.

 

BUT

 

I am experiencing a very strange phenomenon which I cant explain, when the alarm is armed scene 3 sends a message, 3 hours later scene 1 closes the water valve but scene 3 runs again ! and 3 hours and 1 minute after the alarm is armed scene 2 runs but scene 3 runs again.

 

I don’t understand why scene 3 runs when again when scenes 1 and 2 run ? the trigger, the Universal Sensor has not changed state.

 

Any ideas ?

[Stycx 9]

Hi @Keithlambley,

perhaps you can provide more information.

Especially the trigger of each of the scenes (or how they are called) to get a better understanding and look into the problem.

 

[Keithlambley 3]

4 hours ago, Stycx said:

Hi @Keithlambley,

perhaps you can provide more information.

Especially the trigger of each of the scenes (or how they are called) to get a better understanding and look into the problem.

 

The trigger for all 3 scenes is a Fibaro Universal Binary Sensor FGBS-001 changing state when my conventional house alarm is armed. The IN1 of the Universal Binary Sensor is connected to GND by the NO contacts of an output relay on the alarm PCB.

 

For scene 1 the change of state has to be true for 3 hours, for scene 2 the change of state has to be true for 3 hours and 1 minute and scene 3 is instant and indeed does run immediately.

 

The problem is that when scene 1 eventually runs after its "true" time scene 3 runs again. And when scene 2 eventually runs after its "true" time scene 1 and 3 both run again.

 

I don’t understand this as the trigger, the Universal Binary Sensor does not change state.

 

See attached scans of the history

 

You can see that the alarm was disarmed at 10:29:59 then armed again at 10:30:48 then there is no other change if state until 17:56:35.

 

Arming the alarm triggered the scene "Alarm Armed Text" (scene 3) at 10:30:48 then exactly 3 hours later at 13:30:48 the scene "Water Valve AWAY" (scene 1) is triggered and also the scene "Alarm Armed Text" for the second time, a minute later at 13:31:48 another scene is triggered, scene 2, it does not run as an additional condition is not met, but it causes "Water Valve AWAY" (scene 1) to run for a second time and "Alarm Armed Text" (scene 3) to run for a third time.

 

I suspect that "Water Valve AWAY" (scene 1) has always been running for a second time but I did not notice as it just tried to close a valve which was already closed, its only now that "Alarm Armed Text" (scene 3) is sending me text (SMS) messages that I have noticed this behaviour.

 

Please login or register to see this attachment.

Please login or register to see this attachment.

 

[Keithlambley 3]

Anyone got and answer to this query ?