Delay trigger in case state changes for door sensor

[mgilbert]

I did not realize that it shows the current status when creating the rule!

[mgilbert]

So now that I have this I now see 4.0 is here and since I am just starting out I would prefer to move directly to 4.0. Could someone provide me with an example of this rul in 4.0 and also any places that have in depth tutorials on 4.0 for rules?

[ogiewon]

@mgilbert

and also any places that have in depth tutorials on 4.0 for rules?

Sorry, but I actually laughed out loud... RM 4.0 was literally released about 24 hours ago. There are no in depth tutorials yet. There is a thread dedicated to RM 4.0, where you might want to post your old rule and ask for RM 4.0 advice. Most users are somewhat cautious and haven’t even upgraded their hub firmware yet, as usually numerous hot fixes are in order to address bugs that are found.

Here’s the RM 4.0 documentation

https://docs.hubitat.com/index.php?title=Rule-4.0

And the thread..

[Released] Rule 4.0

Rule 4.0 -- The new Rule Machine Rule 4.0 is the culmination of a journey in the transformation of Rule Machine. At once it simplifies and adds power, resulting in a fully generalized automation engine. The prior top-level organization of RM is thrown out, replaced by a simpler interface. The changes are described below, and how what was done in prior versions is now accomplished. Gone are Rules, Triggers, Triggered Rules, Actions and Schedules. Instead, you define what causes a rule to run…

[mgilbert]

Ok I was assuming that documentation would be released before going live with it but I understand that is also a huge task and would have probably delayed the 4.0.

I am only now deploying Hubitat at my home so I have not really created any rules. Just this one. I will repost in the rules engine.

Thanks

[bravenel]

@mgilbert

Could someone provide me with an example of this rul in 4.0

This rule would be tricky due to cancel on both sides of it. Easiest way to do this would be to split into two rules, one for open and one for closed. It's possible to do using Private Boolean to control the cancels, but not worth the effort imo.

@mgilbert

I was assuming that documentation would be released before going live with it

The documentation at release was the post that @ogiewon referenced, which includes tutorial on converting from Rule-3.0 forms to 4.0. The app documentation was posted a few hours later, also linked by @ogiewon.