@bravenel I've started using the new RM 4.1/HSM rules and have discovered what I believe is unintended.
If I use HSM Alert Rule XX as a trigger in RM 4.1 and use arm/disarm the associated HSM rule it triggers the rule. I would assume the HSM Alert trigger would only trigger when the HSM custom rule is actually triggered?
Show the System Events log. Only the rule Alerting sends an "hsmAlert" event. Which isn't to say that the rule didn't alert when it shouldn't have. But arming/disarming sends "hsmRule" events.
RM subscribes to "hsmAlert" events. Show the Event Subscriptions for the rule.
These are the most recent for this rule. I can run some tests to show more detail if necessary.
Well, the disarm cancels alerts, and that sends the hsmAlert event. HSM Rule shouldn't use hsmAlert for canceling alerts.
Does this mean I am using the trigger incorrectly or is there something occuring not intended? Sorry for not understanding your statement.
Excellent, for now I can workaround this by using a simple condition restricting the action if the HSM trigger isn't true.
You can look at %value% to know what happened.
1 Like