Strange one. I've just created an RM 5.1 (hub version 2.3.1.134) for Fridge door left open that should trigger if the door opens and stays that way for 1 minute - action notify phone. As below:
I've opened the door and held it for 1 minute and it works. However as can be seen in the log below, the rule triggered again on the close event, so sent a further notification 1 minute after the door was closed.
Any ideas why? Thanks
The contact event comes from a child device of an LG ThinQ integration rather than an actual contact, but the device events do correctly reflect open and close correctly as does the current state. I'd have though that should work like any other contact? Open > start wait > 1 minute > rule triggered. I can't see why it would wait for the door to be closed for 1 minute when the only trigger is open.
The major difference is that you were opening and closing yours rapidly, presumably to test whether the rule works, whereas I was using the fridge in my normal way. I wonder if that makes a difference. I shall try that with mine
A little later: Have to do it with contact sensor, my Sensative Strip doesn't report frequently enough!
Hmmm very strange. So I've just opened the fridge door once, for a few moments and closed it (rather than repeatedly opening/closing). The device events show the open and close correctly with no duplicate events:
The logs also show the door is opened, the wait begins, the door closes. Yet I get "still waiting" and the door close that is present in both the device events and rule log seems to be ignored.
The trigger occurs even though the logs show that the close should have prevented it.
Is your hub on 2.3.1.134 ? Oh you already said so. Ok I am out of ideas lol. Perhaps try it on your system with a more basic contact sensor so it might point up whether it's a problem with the device or your rules/system
And/or try the dumber things like restarting the hub or rewriting the rule.
Yeah good idea - I put a regular contact on the washer cupboard door the other day. I'll start by creating an identical rule using that device and if it works as expected I'll delete and rewrite the one for the fridge. It's a pain because I've spent a number of hours trying to get the LG integration working. I was hoping it might send an event when the door is left open and the chime starts but it is very basic.
@Inge_Jones I think I've solved it. I'm not sure if this is expected behaviour so I'm tagging the rulemeister @bravenel
If I use as the trigger - capability > custom attribute > fridge (device) > contact (attribute) I get the problem. The door closing does not cancel the remaining time and the actions are executed.
However if I use as the trigger - capability > contact > fridge (contact sensor). The door closing correctly cancels the remaining time and everything works as it should as shown below with the door being opened and closed twice:
As the "contact" is not a physical contact but an event generated by an app I thought choosing custom attribute was the way to go but this causes an issue.
Is that behaviour expected when using custom attribute in a sticky trigger? Thanks
Please show the rule, the one with custom attribute that fails.
Here you go. I rewrote it using contact in one and custom attribute in the other so I could pause one of them at a time, while testing each.
I will look into it.
Found the bug. This will be fixed in the next release. Thanks for helping.
Cool - no problem.
Download the Hubitat app
