I am polling SNMP data from DPS equipment which contains alarm points consisting of point description and point state (Alarm/Clear). Point description and point state are two different OIDs. My trigger uses {ITEM.VALUE1} in the trigger name to display the point description as the trigger issue.

When I add my template to a DPS host that has alarm points already in alarm the trigger issue displayes "POINT##: *UNKNOWN*". The latest data shows correct values for both OIDs retrieved. To get this issue to resolve, within the DPS equipment settings, I had to manually flip the alarm polarity so the point state value becomes "Clear" instead of "Alarm". This of course clears the event and the trigger issue disappears. After a few polls I then flipped the alarm point polarity back to the original setting and the alarm returned displaying the expected point description data in the trigger name/issue field. So, if the trigger has never evaluated to true, the {ITEM.VALUE1} macro does not return a proper value in the trigger name/issue field.

I have attached a few screenshots showing my trigger logic, the latest data the trigger evaluates and the trigger error displayed.