How to Latch a Rule, requiring some additional input to allow retrigger

📐 Rule Machine®
1

I have a contact on my Furnace that closes when the burner does not start properly. I've connected it to a contact sensor.

I wish to send an SMS if this contact ever closes, however if it then opens and re-closes I do not want to send another SMS.
Then when I get to the issue I would activate a virtual button (or something) to release the lock / latch function.

Obviously I wish to eliminate the problem of getting a bunch of SMS messages if the contact is bouncing for some reason. I know there is a limit of 10/day but I do not want to rely on the limit for program function (poor coding form).

I've tried a number of variations but can't seem to find a way to create a latch function.

Thanks
John

2

What's your criteria for the reset that would allow the SMS to be sent again?

**edit got it...virtual button...

On your SMS rule, select the enable/disable with private Boolean option (in the restriction section), then in your actions have the rule set it's own PB to false.

Then create second rule to set PB true for your first rule when you press your button.

1 Like
3

Got it......thanks. Now I'll have to learn about private boolean's. Read about them but never had an opportunity to use one.

1 Like
4

Think of it as a remote control for restricting or unrestricting a rule. There's basic restrictions available within each rule, but using the Enable/Disable PB option allows you to enable and disable based on more complex conditions or triggers, just like any other action you would take.

5

I have made use of private Boolean in several rules to achieve the same effect. Very handy for when you want a rule to run once and then disable itself, with some other set of conditions (i.e. rule) re-enabling it.

1 Like
6

Private Boolean is one of these that is available for every Rule:
15%20PM

It always begin's True (or On like the pic) and when it's True, the Rule will run normally. If you go into ANY Rule you already have and go into Restrictions, you'll see the option of allowing Private Boolean to have an impact BUT you can turn it on (enabled) and nothing will happen!!!

52%20PM

That's because it's True by default meaning allow the Rule to run.

If anything turns the Private Boolean False (off) then the Rule works the same as if it had been removed, gone. Does nothing.. one exception in this metaphor: the Private Boolean remains available. As soon as you turn it back to True, the Rule will behave normally. It does NOT evaluate because of Private Boolean. Evaluation is still and always driven by an event.

1 Like