Have an outdoor positioned Sengled bulb that is dimmable. Set up the following two Simple Automation Rules.
Rule #1 - Turn on & set to 30% at Sunset, off at Sunrise.
Rule #2 - Triggered by Motion Sensor , Turn on & set to 100% then Turn off after 8 minutes (per the available options). Don't really want it off after being triggered to brighten but don't want it on at 100% all night either.
Desired outcome would be for rule #2 to either put the bulb back to the setting it was at
(which might be what toggle would do but I want the 100% setting to last a few min)
OR
have an additional setting allowing to leave the bulb on but at a specified setting.
Probably a Rule Machine task I'm asking to be integral to SAR.
Problem is with a request like this is that feature creap turns SAR into RM quite quickly. This is easy to do in RM for the second rule. Leave the first one in SAR, do the bright for a few minutes rule in RM. RM has capture and restore as one way to do it, so it's completely independent should you change the level in the SAR rule. Now, consider how much logic is in this rule that you think should be added to SAR. Makes no sense to do that!
I will say this, if you already had that rule set up and others like me have come upon the same need for that functionality...it begs the question should we build a library of common use / common functionality rule examples.
Ya know, thinking more about what you said here....this is exactly why, ...as someone not wanting HA "system maintance" to become a hobby, I have raised a few feature requests that I've thought were reasonably logical & broadly useful (OK, maybe not all).
I get that a small cadre of sharp, hard working, and dedicated Hubitat crew has developed a complexly flexible platform upon which we can do just about anything. My respect for that achievement grows every time I add a new device and work to achieve some collection of new functionality from it.
But the question remains....how many more people are out there yet to adopt the Hubitat platform, what are there needs, abilities, and time constraints? If the remaining market is less apt to expand on the basic App hand holding provided in HE ...then we may not get or keep them.
I'm grateful Bruce put up that example. It was another nudge to get me under the RM hood ...and I had another "holy sh-t they've built a lot into this system" moment as I built another rule.
But as I closed it ...I thought "now I have to maintain it and how many more of these basic adds will add up to complexity in maintaining my HE environment going forward" .
It wasn't like this was some overly-custom-unique-to-my-needs feature. 1000s of other folk would likely want exactly what I was looking for in exactly the spot I was wishing for it within Simple Automations, or even HSM for that matter.
But that said, I do get that Simple Automation is more helpful hand holding than it was under another name.....and I do get the risk of creeping scope. And if I were in Bruce's shoes having put so much work into the "make it yourself'" flexibility I would react the same cautious way about investing too much time in HE "spoon feeding features".
Why do you have to maintain it at all? If it works, it works and will continue to work. Many of my rules are from the original Rule release, never updated -- no reason to. You don't have to do platform updates unless there is some new feature you want, or a bug that was a problem is fixed. But, if your system works, it will continue to.
Most people here do turn HA into a hobby that they tinker at constantly. It's a stimulating hobby. But for those who just want it to work and go on working without maintenance, that is very possible.
I got a lifetime of "stimulation" (frustration) during the X10 years. Then stepped away from HA as other new & improved proprietary systems became the next evolution in the HA hobby.
Industrial SCADA was great fun because you could earn a salary taking care of what the vendors didn't supply or otherwise broke with unsuspecting upgrades.
I'm just in a different place now with lots of other things to do and learn. Never doubted the value of HA, Just was always a bit skeptical about when it was going to be ready for prime time and more importantly, mass adoption.
The latter is what I wish for Hubitat because I believe you've gotten so very much right at a low level. But don't discount the input of newbees at this point in your product maturity because the late adoptors represent the next and far larger tier.
Once I've become conversant enough in RM I won't care about some of this as much. In a way that's bad because for every one like that there might be two others that buy one unit and then only modestly put it to use. I know with HEs flying off your shelves that probably sounds disconnected from your reality...but my IT experience (albeit ancient) suggests it's not. I'm guessing you already get this, otherwise SAR wouldn't exist
