Haven't been under the hood of my early day HSM configurations in awhile but here I am with the mindset to maybe do less stuff in RM that COULD and probably SHOULD be consolidated under the HSM umbrella .
Opening stuff up again I'm prompted to comment right off with a complaint I had waaaaay back when.
Yes HE is not a Security System BUT....to the degree that HSM serves some interlinked function(s) that are allied to that Use Case (and can appear to folk "like it" in a number of respects)....let me say this:
If you are going to hold a user's hand through a boatload of handy constructs to aid them in configuring all the things HSM can configure & act upon...then you OUGHT to have a "TURN OFF/STOP/UNDO upon/after/If/when" every place that there is an option to take
action turning on a switch/siren/strobe/pump/valve/electric fence/moat drawbridge/ etc.
And to allow the AUTOMATIC RESET OF THE STATE OF THINGS TO NORMAL & ARMED AGAIN after a period.
This is basic Security/Safety System Response procedure; the perfect example of which is the standard function to turn off a security alarm after X amount of time so the neighborhood doesn't have to listen to it all night. The presumption being, you are away from home and whatever caused the trigger is long gone ...or it's a faulty sensor. The latter brings up another nice feature, that being, "if this is the third time tonight that this sensor has triggered I want you to ignore it until I physically reset the condition/rule/environment.
There is a big rabbit hole you can go down trying to replicate the best of the certified alarm systems out there...and that's not the ask here. But when new users are tempted to get into HSM for a consolidated solution under one App...at least help them prevent nuisances with their trigger condition responses by putting stuff in like "turn off after x" or "upon y".
Thanks.
