I might be missing something simple, but in an alarm pipeline is there a way to get the current value (not initial eventValue) of the tag that caused the alarm pipeline to start?
I figured out from {source} or {displayPathOrSource} how to store the original tag path to a local property, (which in my case is currentValue)
If I then use tag({currentValue}), I just get null?
use case: I have a tag alarm with multiple e-mail updates if temperature is above a certain limit but I want to update the value with whatever the current tag value is.
Figured it out by doing it in a script but I still feel like I am missing something more straightforward, like in the expression syntax - ie: why did tag() not work..
|
path = event[currentPath] |
|
t = system.tag.readBlocking([path])[0].value |
|
event[currentValue] = t |
You can use {eventValue} to get the value that triggered the alarm
1 Like
Sorry could have been more clear, I meant getting the current value. {eventValue} is straight forward but I'm trying to send status notifications for an alarm, like "Yep, the room is still hot, it's currently __F"
Maybe I'm using the alarm pipeline wrong and I should be triggering the alarm again? I'm not expecting the alarm to go to a cleared/dropout state first
1 Like
Alarm pipelines get a very limited, not-a-real expression context. A script is the best way to go here.
2 Likes
Rgr that - in the same token, I'm looking to re-use the same alarm pipeline but change the roster depending on what tag is calling the pipeline, again script best friend?