# Sending MQTT data to a HiveMQ broker using transmission module alone

**URL:** <https://forum.inductiveautomation.com/t/sending-mqtt-data-to-a-hivemq-broker-using-transmission-module-alone/94559>\
**Category:** Ignition\
**Created:** [August 12, 2024, 8:25pm UTC](https://forum.inductiveautomation.com/t/sending-mqtt-data-to-a-hivemq-broker-using-transmission-module-alone/94559 "2024-08-12T20:25:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![USR9000](https://avatars.discourse-cdn.com/v4/letter/u/5f9b8f/32.png) [@USR9000](https://forum.inductiveautomation.com/u/USR9000)\
**Post date:** [August 12, 2024, 8:25pm UTC](https://forum.inductiveautomation.com/t/sending-mqtt-data-to-a-hivemq-broker-using-transmission-module-alone/94559/1 "2024-08-12T20:25:45Z")

</div>

Hello Everyone,

I am looking to send OPC-UA data to a MQTT broker, I want to use HiveMQ, could this work by only using the cirrus Transmission module on ignition? or di I need to use an additional module?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 12, 2024, 8:36pm UTC](https://forum.inductiveautomation.com/t/sending-mqtt-data-to-a-hivemq-broker-using-transmission-module-alone/94559/2 "2024-08-12T20:36:28Z")

</div>

I think just the OPC UA and MQTT Transmission module would be enough.

Be aware that you're locked into the data being transmitted to HiveMQ in Sparkplug format.

---

<div class="post-metadata">

**Author:** ![USR9000](https://avatars.discourse-cdn.com/v4/letter/u/5f9b8f/32.png) [@USR9000](https://forum.inductiveautomation.com/u/USR9000)\
**Post date:** [August 12, 2024, 9:20pm UTC](https://forum.inductiveautomation.com/t/sending-mqtt-data-to-a-hivemq-broker-using-transmission-module-alone/94559/3 "2024-08-12T21:20:24Z")

</div>

Is there a way to transform it in another format using an additional module?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [August 12, 2024, 9:23pm UTC](https://forum.inductiveautomation.com/t/sending-mqtt-data-to-a-hivemq-broker-using-transmission-module-alone/94559/4 "2024-08-12T21:23:01Z")

</div>

Not really.

The MQTT Engine module does provide a scripting function to publish an arbitrary message to an arbitrary topic, but at that point you're basically just rolling your own bridge using tag change scripts on OPC tags or something...

---

<div class="post-metadata">

**Author:** ![Chris\_Murphy](https://avatars.discourse-cdn.com/v4/letter/c/c5a1d2/32.png) [@Chris\_Murphy](https://forum.inductiveautomation.com/u/Chris_Murphy)\
**Post date:** [August 14, 2024, 9:22am UTC](https://forum.inductiveautomation.com/t/sending-mqtt-data-to-a-hivemq-broker-using-transmission-module-alone/94559/5 "2024-08-14T09:22:35Z")

</div>

The same script function exists on the transmission module so you can publish vanilla mqtt to your connected broker with just the transmission module.

[Transmission Python Scripting](https://docs.chariot.io/display/CLD80/MT%3A+Python+Scripting)

I have found though, that transmission seems to disconnect after each publish then reconnect again when you make your next call to that function. Perhaps if the connection was a websocket it might help, I haven't tested it.  
I had a lot better performance and avoided this issue by calling the same function on the engine module instead. It used the same connection to the broker it created to subscribe to the configured topics at startup.