@obober
Something else to note, as I change the tag value to test the dynamic enabling and disabling of the alarms I see inconsistent behavior of the H enable value and HH enable value. Sometime the bit is true with tag value that should activate the alarm but doesn’t. Sometimes the value is false when it shouldn’t be and sometime the value is null.
I think there is more going on here than just the H alarm (original issue) not entering the pipeline.
Have a look at [Bug-6178] Alarm {state} value isn't clear after clearing an alarm that was acknowledged
I believe they’re probably related.
Regards,
Ted.