# Best way to publish non-SparkplugB MQTT data?

**URL:** <https://forum.inductiveautomation.com/t/best-way-to-publish-non-sparkplugb-mqtt-data/74208>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [May 26, 2023, 5:27am UTC](https://forum.inductiveautomation.com/t/best-way-to-publish-non-sparkplugb-mqtt-data/74208 "2023-05-26T05:27:03Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joe\_Bonhage](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/joe_bonhage/32/45543_2.png) [@Joe\_Bonhage](https://forum.inductiveautomation.com/u/Joe_Bonhage)\
**Post date:** [May 26, 2023, 5:27am UTC](https://forum.inductiveautomation.com/t/best-way-to-publish-non-sparkplugb-mqtt-data/74208/1 "2023-05-26T05:27:04Z")

</div>

Hi all,  
I'm looking for the best approach to put an entire tag provider (or a certain folders) to publish plain MQTT (non-SpB) on change. I currently have an on-change tag event working (script below) but I'd like to design something more scalable instead of putting scripts on each tag. I"m thinking a gateway event could do this?

Basically I'd like all the functionality of the MQTT transmitter but not have it in SparkplugB format.

Script -----  
tagvalue = tag.value  
system.cirruslink.transmission.publish("Chariot SCADA", tagPath, str(tagvalue.value).encode(), 0, 0)

---

<div class="post-metadata">

**Author:** ![Joe\_Bonhage](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/joe_bonhage/32/45543_2.png) [@Joe\_Bonhage](https://forum.inductiveautomation.com/u/Joe_Bonhage)\
**Post date:** [May 26, 2023, 7:47pm UTC](https://forum.inductiveautomation.com/t/best-way-to-publish-non-sparkplugb-mqtt-data/74208/2 "2023-05-26T19:47:19Z")

</div>

Hi all,  
Referencing [this post](https://forum.inductiveautomation.com/t/mqtt-engine-error-processing-edit-for-tag-path-cannot-accept-children-tags/69578) on IA forum, and [here](https://docs.chariot.io/display/CLD80/MQTT+Engine+Custom+Namespace) on Cirrus Link forum, looks like if I use a custom namespace, it may be a work-around for SpB

---

<div class="post-metadata">

**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\
**Post date:** [May 3, 2025, 1:23am UTC](https://forum.inductiveautomation.com/t/best-way-to-publish-non-sparkplugb-mqtt-data/74208/3 "2025-05-03T01:23:46Z")

</div>

what did you end up doing here?

---

<div class="post-metadata">

**Author:** ![Kevin.Collins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.collins/32/13497_2.png) [@Kevin.Collins](https://forum.inductiveautomation.com/u/Kevin.Collins)\
**Post date:** [May 4, 2025, 7:04pm UTC](https://forum.inductiveautomation.com/t/best-way-to-publish-non-sparkplugb-mqtt-data/74208/4 "2025-05-04T19:04:12Z")

</div>

Probably worth mentioning the new[ish] UNS Transmitter in MQTT Transmission, as this wasn't available at the time of this original post.

- [https://docs.chariot.io/display/CLD80/MT%3A+Configuration#MT:Configuration-unstransmitter](https://docs.chariot.io/display/CLD80/MT%3A+Configuration#MT:Configuration-unstransmitter)
- [Which MQTT Transmission Transmitter should I use - MQTT Modules for Ignition 8.x - Confluence](https://docs.chariot.io/display/CLD80/Which+MQTT+Transmission+Transmitter+should+I+use)

---

<div class="post-metadata">

**Author:** ![Joe\_Bonhage](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/joe_bonhage/32/45543_2.png) [@Joe\_Bonhage](https://forum.inductiveautomation.com/u/Joe_Bonhage)\
**Post date:** [May 5, 2025, 6:04am UTC](https://forum.inductiveautomation.com/t/best-way-to-publish-non-sparkplugb-mqtt-data/74208/5 "2025-05-05T06:04:24Z")

</div>

Ended up not using MQTT, MES vendor bypassed Ignition to go direct to the equipment controller with their native edge connectors. Ugh....

---

<div class="post-metadata">

**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\
**Post date:** [May 5, 2025, 12:37pm UTC](https://forum.inductiveautomation.com/t/best-way-to-publish-non-sparkplugb-mqtt-data/74208/6 "2025-05-05T12:37:40Z")

</div>

Thanks for the reply!

---

<div class="post-metadata">

**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\
**Post date:** [May 5, 2025, 12:39pm UTC](https://forum.inductiveautomation.com/t/best-way-to-publish-non-sparkplugb-mqtt-data/74208/7 "2025-05-05T12:39:09Z")

</div>

Hi @Kevin.Collins I got it working and thanks for the links.

I do have another question, I noticed in the broker when i send a temperature for example, there are two topics, Temperature.props = {} and temperature = {value:mysuff}.

Any idea what the temperature.props = {} is used for and if I need it or can remove it?

Thanks again!
