HSM nicely allows for non-persisting actions upon a condition triggering, and allows for repeating actions. Clearing the condition returns some of the behaviors to normal.
There are 2 specific use cases that are areas for enhancement. The first is "acknowledging" the action so we stop the repeating conditions, but we don't want to reset all conditions to normal.
Example:
Water leak is detected. Valve is closed, siren and strobe go off, lamp bulbs turn to blue in the master bedroom, text messages go out every 5 minutes. In this case, it may be necessary to acknowledge the problem, leave the valve closed but still silence the siren/strobe, stop sending the continual alerts and reset the lamp bulbs to white and turn them off. Perhaps we also log the user who ack'ed the problem and send a SMS with that info too for an audit trail. Ultimately, this mode allows us to resume a "sane moment" while the underlying problem is resolved without going in and mucking with rules or devices instead of addressing the actual water condition and mess on the floor.
The second area for enhacement is Cancel the Alert. Today we can cancel the condition which may turn off sirens/strobes etc and return to a monitored condition, but there are still other actions that may have been triggered that need to be returned to normal.
In the scenario above, Cancel still leaves me with resetting the blue lamp bulbs, and turning on the water valve. Maybe we should send out a new message to everybody and say it's handled and have a record of the user who "cleared" the condition. Today it's awesome that we go back to a monitored state, but perhaps it's appropriate to have a check box that says "don't resume monitoring" when things are cleared until someone chooses to resume water monitoring too.
This of course extrapolates to all the intrustion modes and probably custom monitors too. Any condition we can watch for should have triggers, tripped actions, acknowledge actions, clear actions, and monitor-arm/disarm modes.
< Unsolicited thoughts on implementation >
Don't let this section cloud the enhancement request - how ya go about doing this isn't my business really 
The request really muddles the UI even more than it is -- Perhaps handling this via a wizard with an "advanced" button that launches a specific instance of rule machine covers the advance cases... I would imagine the rules storage under the cover for most of the apps are getting more similar?? and having the "state" of the HSM object set as the trigger in advance mode might give the best of all worlds, particularly if the conditions and actions are stored similarly. Either ya can have basic wizard mode or advanced once set so adjusting the rule set in 2 modes is not needed.
< /Unsolicited thoughts on implementation aka stop suggesting implementation >
