Cirrus Link MQTT Modules

Ignition
1

Maybe I am missing something but it seems to me that the Cirrus Link modules work great in an “All Ignition” environment but can be difficult when other types of clients are involved. BTW, I am running 8.3.

For example, I want to publish plain old MQTT topics that other systems can easily read. When I use the Transmission Module and set up a UNS Transmitter the data published includes a lot more than just the value and prepends a topic called unsAv1.0. I want to completely control the topic name (no unsAv1.0) and just publish a value without all the metadata.

A tag in the root of the selected tag provider (let’s call it Minute) will have two topics published with json data:

  • unsAv1.0/Minute = {"name": "Minute", "dataType": "Int32", "value": 39, "timestamp": 1768498740367, "qualityCode": 192}
  • unsAv1.0/Minute.props = {}

I understand the metadata can be critical but in my use case I am only concerned about the value. I do not/can’t preprocess the data in the subscriber to get the value out of the JSON. Can I do this or am I SOL? And, yes, I know the Cirrus Link forum is a better place to post this but I do not yet have an account and just wanted to hear the experiences or others.

Thanks

2

If memory serves, that module is built specifically for Sparkplug B. But I do think if you use the MQTT Engine module instead, you can use custom MQTT. Otherwise you’ll have to republish with something like Mosquitto, or use some custom tag change script to publish.

Not 100% sure on any of the above…

1 Like
3

There are other free modules that do plain MQTT without predefined namespaces.