Failed to handle write to Metric Device Control/Rebirth

Ignition Modules MQTT Modules
1

Hello all,

May I have some assistance narrowing down what is causing the following issue?
Failed to handle write to Metric Device Control/Rebirth

java.lang.NullPointerException: null
at com.cirruslink.common.gateway.MetricManager.getTagProviderName(MetricManager.java:320)
at com.cirruslink.mqtt.common.gateway.agent.Agent.handleMetricWrite(Agent.java:707)
at com.cirruslink.mqtt.common.gateway.agent.Agent.handleDeviceMetricWrites(Agent.java:627)
at com.cirruslink.mqtt.transmission.gateway.sparkplug.SparkplugMqttCallback$MessageArrivedWorker.run(SparkplugMqttCallback.java:234)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)

image
image1168×247 31.7 KB

2

What version of MQTT Transmission are you using?

3

I am using version 4.0.7

I changed my MQTT broker to one that only I was connected to and I didn’t have any errors.

4

So - something appears to be writing to the ‘Device Control/Rebirth’ tag on the Engine/Host side. This is failing because that tag is no longer supported in MQTT Transmission. You should delete the ‘Device Control’ folder on the MQTT Engine side and do a Refresh on the Transmission side. This should make it so only valid tags are shown on the MQTT Engine side.

5

Thanks, I will test that out tonight.