Excellent work and such a quick turnaround. Thanks! 
Physical override seems to work at this point - will chime in here if it doesnāt. Thanks for taking my ugly prototype code @bravenel and making it smooth. 
Physical over ride will work great for setting something like, āturning off wake up mode when i just want to sleep in and be late for work!ā
ā¦the physcal override as programmed will suspend the rule if a switch in the rule has been manually turned on. I donāt think itās meaning what you think it meansā¦
That being said, @bravenel, would it be possible to actually have a way (maybe an option page) to actually check off a rule to disable it but not delete it? Maybe in the logic it would force that rule to be false while itās selected? That would meet @bamarayneās example of being able to sleep inā¦
Why not come up with an additional condition? You can use a virtual switch, controlled by a Minimote (or Alexa, or ā¦). Turn on the switch, disables the rule.
Yes, thatās exactly my use caseā¦ or, more appropriately, my wifeās use case - to wit: āIf the I*&%&^%^%&^% light goes off again when Iām in the shower and the motion sensor times out, itās time for a divorceāā¦
My answer with this is simply āturn on the light manually honey, and it will stay on until you turn it offā. Turning it off manually or through the app/automation re-enables the rule evalutation (motion and lux in my case).
I was kinda thinking a checklist might be useful if, say you need to disable rules to test and track down an issue with rules overlapping, etc
Yeah, I was replying to @bamarayne but apparently I hit the wrong Reply button. So much for just getting my āRegularā badge. 
I was doing some testing on my rules, specifically the delayed off feature. So, I have the rule turn on a light when I arrive home and I also want the same light to turn off after 10 minutes, so i added it to the delayed turn off. Do you see an issue with the way I am evaluating the rule? Can I still ātimeā the light if I turned it on as part of the rule?
No problem with that way at all. I have a couple rules that do this.
What you described would work great, but for me, the over ride would be fineā¦ I can just tell Alexa to turn on āSleep Inā and my wake up rule is disabled until I turn off āSleep Ināā¦ then the routine starts and I get up.
added a screenshot to my original post. Does it look like it makes sense?
I just created a test rule with the same conditions and delay; this time it worked. Itās a bit strange that it did not work in my actual rule. I will look into it again. Thanks everyone.
Grrr. It happened again. I was creating a rule and ST app crashed. Now I have another bogus rule after re-doing everything 3 hours ago 
All I can say is thank goodness for Bluestacks! 
I created another thread to try and keep this one about the updates and changes to the app.
The other thread is for dealing with App Logic.
Just for some feedback, I donāt think certain time works for everyone. I have been having trouble running my daily light automation and when I changed it back to 5min time spread, it works correctly. When I left it at 1min and certain time, live logging doesnāt even show the rule even attempt to run.
I too have been seeing issues with time-based rules the last few days. For instance I have a light that I want to turn on at 7:00 PM CST and turn off at 11:00 PM CST with no other conditions. I also have the light turn on at 5:45 AM CST and turn off at 7:15 AM CST with no other conditions. The first rule hasnāt been executing, but the second one has been working. Last night I changed the first rule to turn on at 7:15 PM CST and turn off at 10:45 PM CST, and it worked! I also noticed that one of my mode change rules didnāt execute at 10:30 PM CST, but my evening and morning mode change rules did work, which were based on sunset/sunrise conditions.
Itās just a guess at this point, but perhaps Iām being bit by the hour/half hour bug again. Supposedly it was fixed with a platform update months ago, but Iām going to change any time conditions to be something other than the hour or half hour and find out if things get more stable.
Update posted, Version 1.1.13.
Release notes:
- Added on/off as choices for āSwitches to turn off after a delayā and āSwitches to turn off after a delay, cancellableā. This allows for a delayed On.
- Added Basic and Advanced rule input modes. Basic, which is the default, does not prompt for sub-rules. This makes entering simple rules that donāt have parentheses much cleaner. Advanced allows for sub-rules, and is the app as itās been up until this release. You can find the Advanced option in the More Options section at the bottom of the page.
- Bug fixes for water sensors and valves.
To update: copy code for Rule from Github https://github.com/bravenel/SmartThings/blob/master/Rule
Paste it into Rule in IDE, overwriting previous version, and Save. Do not publish!
@greg and I discovered that the leakSmart valve, which is a zigbee valve, throws on/off events for opening and closing, not open/closed events. I think I will remove Valve as a condition, because it would confuse someone to think their valve could work that way.
It does respond to device.open() and device.close() commands, so choosing a valve for an Action does work.
This is still an issue for meā¦ maybe Iām the only one seeing this? It seems to be confined to mode changes from Night to Home, and it affects rules randomly. I only have one rule that doesnāt have mode restrictions (motion in my master bedroom closet), and this one is never affected, so itās definitely something in the rule evaluation based on modes.
Iāll try to dig into the logs tomorrow morning after switching from Night to Home and before I go into Rule Machine to kick the offending rules and force re-evaluationā¦ sigh