Sticky Trigger

I am trying to use a new RM using a Sticky Trigger for the first time. Not getting the results I was expecting.

I have an exterior gate with a Ring Contact Sensor (V1). I want the Rule to send me a text when the gate is opened, and also if the gate is left open for an hour. So my Trigger is:

Gate contact open
Or
Gate contact open and remains open for 1 hour (sticky trigger)

From my Device log, when I open the gate it triggers once.
From the Rule log, it seems to trigger twice, and performs the action of the Rule twice. That is, I immediately receive 2 text messages.

Both triggers seem to be firing even though I just opened the gate (has not been left open for more than an hour).

What am I not understanding about Sticky Triggers? If I separate the Triggers into 2 separate Rules, they work fine. Why can't this be 1 Rule with the 2 Triggers?

Possibly a bug in RM. I dont think it should trigger twice. @bravenel

But in the meantime you can also use just the one trigger for the contact open. And there are multiple ways to build a rule for what you want.
In the rule
Send Alert
Send Alert Again > Delayed for 1 hour
Wait for Evets (Gate Closed)
Could send another Alert Gate Closed if you want.
Cancel Delayed actions (this will cancel the delayed second alert from above if the gate is closed before the 1 hr delay)

If you want me to look into this I need you to post a screenshot of the rule, and to turn on all logging for the rule, and post a screenshot of those logs for when this happens,

I think it's a problem to have both a regular trigger and a stays trigger for the same event. That's a contradiction, and I wouldn't expect it to work. There should be only a single trigger.

Here is the additional information...

I have since tried multiple variations of the Rule. But the only version that does not act as I expected is when a single Rule contains a Sticky Trigger, and another Trigger, for the same Device. It appears to trigger twice, immediately. And then it does not trigger again at the Sticky Trigger time interval. This does not seem like a contradiction to me as these are different "events" that are not mutually exclusive.

Here is the Rule:

Here is the Log from the Device:
2022-04-29 10:05:56.670 am debugparse:zw device: B9, command: 7105, payload: 00 00 00 FF 09 04 01 AD , isMulticast: false

dev:14442022-04-29 10:05:56.661 am infoBackyard Side Gate contact became closed

dev:14442022-04-29 10:05:56.659 am debugNotification - Type: Home Security, Event: 0, EventParameters: [2]

dev:14442022-04-29 10:05:56.657 am debugparse:zw device: B9, command: 7105, payload: 00 00 00 FF 07 00 01 02 , isMulticast: false

dev:14442022-04-29 10:05:50.000 am debugNotification - Type: Home Security, Event: 0, EventParameters: []

dev:14442022-04-29 10:05:49.997 am debugparse:zw device: B9, command: 7105, payload: 00 00 00 FF 07 00 00 , isMulticast: false

dev:14442022-04-29 10:05:49.682 am infoBackyard Side Gate battery is 100%

dev:14442022-04-29 10:05:49.680 am debugparse:zw device: B9, command: 8003, payload: 64 00 00 , isMulticast: false

dev:14442022-04-29 10:05:49.641 am debugBackyard Side Gate Device wakeup notification

dev:14442022-04-29 10:05:49.639 am debugparse:zw device: B9, command: 8407, payload: , isMulticast: false

dev:14442022-04-29 10:05:39.132 am debugNotification - Type: Home Security, Event: 0, EventParameters: []

dev:14442022-04-29 10:05:39.129 am debugparse:zw device: B9, command: 7105, payload: 00 00 00 FF 07 00 00 , isMulticast: false

dev:14442022-04-29 10:05:38.811 am infoBackyard Side Gate battery is 100%

dev:14442022-04-29 10:05:38.808 am debugparse:zw device: B9, command: 8003, payload: 64 00 00 , isMulticast: false

dev:14442022-04-29 10:05:38.771 am debugBackyard Side Gate Device wakeup notification

dev:14442022-04-29 10:05:38.769 am debugparse:zw device: B9, command: 8407, payload: , isMulticast: false

dev:14442022-04-29 10:05:38.757 am debugNotification - Type: System, Event: 4, EventParameters: [173]

dev:14442022-04-29 10:05:38.753 am debugparse:zw device: B9, command: 7105, payload: 00 00 00 FF 09 04 01 AD , isMulticast: false

dev:14442022-04-29 10:05:38.740 am infoBackyard Side Gate battery is 100%

dev:14442022-04-29 10:05:38.738 am debugparse:zw device: B9, command: 8003, payload: 64 00 00 , isMulticast: false

dev:14442022-04-29 10:04:47.352 am debugNotification - Type: Home Security, Event: 0, EventParameters: []

dev:14442022-04-29 10:04:47.348 am debugparse:zw device: B9, command: 7105, payload: 00 00 00 FF 07 00 00 , isMulticast: false

dev:14442022-04-29 10:04:47.050 am infoBackyard Side Gate battery is 100%

dev:14442022-04-29 10:04:47.048 am debugparse:zw device: B9, command: 8003, payload: 64 00 00 , isMulticast: false

dev:14442022-04-29 10:04:47.010 am debugBackyard Side Gate Device wakeup notification

dev:14442022-04-29 10:04:47.008 am debugparse:zw device: B9, command: 8407, payload: , isMulticast: false

dev:14442022-04-29 10:04:36.945 am debugNotification - Type: Home Security, Event: 0, EventParameters: []

dev:14442022-04-29 10:04:36.942 am debugparse:zw device: B9, command: 7105, payload: 00 00 00 FF 07 00 00 , isMulticast: false

dev:14442022-04-29 10:04:36.583 am infoBackyard Side Gate battery is 100%

dev:14442022-04-29 10:04:36.580 am debugparse:zw device: B9, command: 8003, payload: 64 00 00 , isMulticast: false

dev:14442022-04-29 10:04:36.539 am debugBackyard Side Gate Device wakeup notification

dev:14442022-04-29 10:04:36.536 am debugparse:zw device: B9, command: 8407, payload: , isMulticast: false

dev:14442022-04-29 10:04:36.514 am debugNotification - Type: System, Event: 4, EventParameters: [173]

dev:14442022-04-29 10:04:36.511 am debugparse:zw device: B9, command: 7105, payload: 00 00 00 FF 09 04 01 AD , isMulticast: false

dev:14442022-04-29 10:04:36.502 am infoBackyard Side Gate contact became open

Here is the Log from the Rule:

app:13962022-04-29 10:05:56.700 am infoEvent: Backyard Side Gate contact closed

app:13962022-04-29 10:04:36.632 am infoAction: Notify Twilio-Text-Device: 'Backyard Back Gate TEST. %date% %time%(Backyard Back Gate TEST. 2022-04-29 10:04)'

app:13962022-04-29 10:04:36.607 am infoAction: Notify Twilio-Text-Device: 'Backyard Back Gate TEST. %date% %time%(Backyard Back Gate TEST. 2022-04-29 10:04)'

app:13962022-04-29 10:04:36.572 am infoTriggered

app:13962022-04-29 10:04:36.553 am infoTriggered

app:13962022-04-29 10:04:36.551 am infoEvent: Backyard Side Gate contact open

app:13962022-04-29 10:04:36.545 am infoEvent: Backyard Side Gate contact open

I can't work with pasted logs. Screenshots only.

Okay, you win.

Please disregard my post and i will work around this issue.

I re-created this using a virtual contact sensor. It does trigger twice immediately. It does not trigger after being left open for 1 minute.

image

Like I said above, I don't expect this to work. I will take a look at it, but not promising anything. This may be a documentation thing: don't try this.... because it won't work. There are other ways to accomplish the same thing.

1 Like

Thats sort of what I thought but good to know its just outside the limits of what it can handle.

All I know is that it doesn't work... Don't know why, and haven't looked at it. Clearly it is beyond the intended design. Did you try flipping the order of the two triggers (in a new rule)?

Then it triggers once, but not the second time after waiting. If I set either one of the contact sensors to another sensor it works properly so it just because two triggers have the same device.

Worked for me:

Download the Hubitat app