Rule machine - as per the app developer, this app is no longer available for new installs, distribution, or support

There are several ways to do it.

One is to use a rule like this:

Conditions: motion inactive [any], presence sensors not present [all]
Rule: motion inactive AND presence sensors not present [all]
Action for true: delay these actions 60 minutes: [whatever] with cancel
Action for false: [none]

Each time motion goes inactive the rule is evaluated, and if all of the presence sensors are gone, it starts the 60 minute timer. Should a presence return, or motion occur prior to the clock running out, it is cancelled. Repeats until no motion and no presence for 60 minutes.

1 Like

Make a new Conditional Rule

Condition 1: Presence Sensor(s) not present
Condition 2: Motion {your sensor} inactive
Define the Rule: Condition 1 AND Condition 2
Select Actions for True: Turn On Or Off These Switches After a Delay, Pending Cancellation: select your switch {Tie arming your Fire Alarm to a virtual switch for this}, Turn ON after the delay, Minutes of delay: 60

1 Like

Great!!!

Thanks to both!!!

Strange thing happening. I created three rules for three pairs of lights to track dimmer events.

The two pair of GE bulbs work great, almost no lag between the master and slave. The third pair is cree and won’t follow unless I hit refresh on the master.

I’ve recreated the rule twice as well as creating the same thing with a conditional trigger and it just won’t work.

Any ideas? Haven’t done anything in the IDE yet but this seemed so simple…

Most likely the bulb isn’t updating its state to the cloud. Not too surprising.

I have similar problems with the AEON RGBW lights. I use Expert Commands, and force a refresh, after a couple of minutes.

This custom dimmer looks like a good framework to store color information. If I have time I woll play around with it. On a side note all my rules with an enerwave sc7 give me the dreaded “You are not authorized…” error. Happened literally overnight. Everything else works, including the sc7 smartapp. Weird!

[quote=“sgnihttrams, post:3293, topic:28730, full:true”]

[quote=“sgnihttrams, post:3290, topic:28730, full:true”]
For the water heater rule, I think the answer is Yes (for the wake Android screen rule that was also failing earlier today, there is no time of day involved).

I have three rules for my water heater (I’ll merge them someday if possible)…

HomeDay
Set to ### if any of these people are present between this time in the morning and that time at night

HomeNight
Set to ### if any of these people are present between this time at night and that time in the morning

Away
Set to ### if nobody is present (regardless of time of day), and delay this one by x-minutes.

@bravenel
Do you think the reason this one didn’t fire is because I have it configured to use a ‘time of day’ trigger?
[/quote]…[/quote]

@bravenel
I’m trying something a little different…

No, you are having the general ST schedule issues. Sunset / Sunrise is no better or worse than Certain Time (actually, it’s worse).

If you have schedules on the hour or half hour, that could be your problem. Move them to a few minutes off that.

Lots of people have been having schedule failures recently.

[quote=“bravenel, post:3322, topic:28730, full:true”]
No, you are having the general ST schedule issues…
…Lots of people have been having schedule failures recently.[/quote]

@bravenel
OK. Ya, I knew of this and have seen the discussions. It’s sort of what I thought may be going on. :expressionless:

[quote=“bravenel, post:3322, topic:28730, full:true”]
…Sunset / Sunrise is no better or worse than Certain Time (actually, it’s worse).[/quote]

My other rules that use sunrise/sunset for conditions seem to work fine. It’s just things that need to happen at a certain time that are getting skipped.

[quote=“bravenel, post:3322, topic:28730, full:true”]
…If you have schedules on the hour or half hour, that could be your problem. Move them to a few minutes off that.[/quote]

OK. None of mine for the water heater were on hour or half hour. I think they were either on the :45 or :50 minute marks.

I had the same problem. Bruce had me change the time a few minutes after the hour and have not had a problem since.

1 Like

Bruce, I found some funny stuff with the new interface changes.

  1. For old rules created before you started grouping the actions into pages of similar actions, the actions I’ve set don’t populate correctly on the “main” action page until I go into the subpage and click “ok”. The rules still appear to function fine, however.

  2. I noticed for setting color on bulbs, if I set color then choose to dim to “0”, the action that’s created does not reflect “level:0”; instead it just shows that no level is set. Again, these rules still function properly.

I too have noticed some niggles but nothing concrete to allow debugging. I did have issues with the delay rule value not migrating on 3 rules, fixed that by finding and re-saving them once I put the value back in.
Last few days some other rules seem to have not migrated the mode/lock value, I have manually changed those and saved them but it was not saving the value. I had to do it 2 or 3 times to get the mode value and lock select to “stick”.
Maybe just an ST thing, who knows.

These are simple display of descriptive text issues. Old rules opened don’t have their actions descriptive text on the intermediate page until you go all the way into the actions and back out. This was an unintended consequence of introducing the intermediate page for Actions. The rules are fine; it’s only the descriptive text that is omitted at first.

Just to clarify, I realize the Rule display issues exist and how they update, not a biggee. My input was based on observations that the rules were actually failing due to missing values and the values not being saved even after multiple attempts at re-entry.

Can we get support for the plantlink sensors, specifically when we use the default Smarthings/plantlink device handler?

Thanks

How do you know the values weren’t saved? Did you look in the IDE. Not seeing the text doesn’t mean they weren’t saved (it might or might not). Are you on Android?

Yes, as stated a wholly unscientific observation :wink:
I can only “assume” the values weren’t saved as the errant rules (that used to work) were now either ignoring the mode limitations or not setting the mode as specified in the rule. I also had one door that stopped locking and I found it’s value unchecked in the rule whereas it was checked and executing previously.
Sorry for the lack of proof. If I find another rule the acts in this manner I’ll have a check first before I go bludgeoning the rule with keystrokes :slightly_smiling:

I just did a first time installation of the Rule Machine as per the instructions and everything seemed to be working great. After I created my first rule it appeared (for a while) after “saving” it. I could exit that SmartApp (test the rule) and go back in and see it for a while but then all of a sudden - POOF it disappeared! Just vanished… I then tried to create a couple of other rules and they also disappeared. Rules even seem to disappear just after I hit Done and expect it to show up on my list within the app. I am running an iPhone 6. Only coincidental thing is it looks like today the ST app got updated with a UI face lift. Coincidence? Am I seeing things?

Also apologize for missing this in the 3K posts above - how do I shut lights off after xx minutes of motion inactivity? Since my rules keep disappearing I can’t figure it out for myself at the moment :).

Thanks,

DOM

You may have failed to hit Done in Rule Machine when you first opened it in the Marketplace. It seems to work, but hasn’t been installed yet, so it actually doesn’t work.

Steps:

  • Marketplace / SmartApps / My Apps / Rule Machine
  • Hit Done, upper right corner
  • Then Rule Machine can be found in SmartApps in the “hamburger” menu