Hi, I’m testing the recently added feature to the MQTT-transmitter module to propagate Alarm Events.
It would be very useful if the “Display Path” and “Ack Notes” properties were also propagated since they are widely used in the Alarm Status Table.
Otherwise the EDGE Panel Alarm Status shows one Display Path while the Central Gateway Alarmer shows another.
Is there any information regarding when this will be implemented?
Regards, Andres
Hi Andres,
Currently the alarm properties that are propagated are: Name, Priority and Notes. We do have an item in our backlog to address the propagation of all alarm properties and anticipate this will be completed by the end of Q1.
Regards, Gill
Hi Gill,
Continuing with this topic of alarm property propagation via MQTT, I saw that yesterday that you released version 4.0.27 of the MQTT modules for Ignition.
From what I understand, you added support for "Added Sparkplug IDs to the source and display path of alarms at MQTT Engine." Does this mean the Display Path property is now propagated via MQTT? Because I tested it, and it’s not working. In fact, it works worse than before, as it duplicates part of the path in the Alarm Status on the MQTT Engine side.
Regards, Andrés
Hi Andres,
We still have the task in our backlog to fully support the propagation of alarm properties.
The adding of the Sparkplug IDs to the source and display path of alarms at MQTT Engine was to allow customers to filter alarms to specific Sparkplug IDs using the Alarm Status Table filtering.
Thanks
Gill
Hi Gill thanks for the answer.
And were you able to take a look at how the alarm Display Path is now displayed on the Alarm Status on the MQTT Engine side?, as it appears to be a downgrade from version 4.0.25.
Before version 4.0.26, at least it showed the correct Display Path for the EDGE Panel, but now it seems there’s a bug or something because it repeats part of the TAG Path incorrectly.
Regards, Andrés
Hi again Gill,
I saw that there’s a new version of the MQTT modules for Ignition.
Unfortunately, I found that the Display Path issue persists; that is, part of the path appears duplicated in the Alarm Status on the Gateway side with the MQTT engine.
Note: I’m leaving in blank the Alarm Display Path property and using the full Display Path for the alarm (the default configuration)
Regards, Andrés
Hi Andres,
We still have the task in our backlog to fully support the propagation of alarm properties.
The recent release of the 4.0.28 modules was to resolve a severe Transmission bug.
Thanks
Gill
