We have an active alarm with priority 3,
Tag1 = 0 instead of 1 as expected
Tag2 = 1
Can we use "…[.] " or these kinds of widcards for relative tagPaths in isAlarmActiveFiltered ???
It seem to be mandatory to have a path with an explicit tag provider (as for example “[default]”) in isAlarmActiveFiltered
Hey @mazeyrat,
The provider name is only required in the tagPath on gateway-scoped expressions, otherwise the function assumes the default provider.
The isAlarmActiveFiltered function uses the same tagPathParser that isAlarmActive uses, so wildcards should all work the same way . However, I think the syntax in your example is a bit off. If you’re specifying a provider, it should be the first item in the string.
Hi, I know this is an old converstation, but I have the same problem with realtive paths for isAlarmActiveFiltered in UDT´s. Did anyone of you find a solution for this?