# Creating UDTs with MQTT Devices

**URL:** <https://forum.inductiveautomation.com/t/creating-udts-with-mqtt-devices/51048>\
**Category:** Ignition\
**Created:** [September 16, 2021, 8:37pm UTC](https://forum.inductiveautomation.com/t/creating-udts-with-mqtt-devices/51048 "2021-09-16T20:37:02Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [September 16, 2021, 8:50pm UTC](https://forum.inductiveautomation.com/t/creating-udts-with-mqtt-devices/51048/6 "2021-09-16T20:50:04Z")

</div>

The you won't get backfill data if the comms fails ☹

> [@\[FEATURE\] Allow reference tags to receive backfill data from sources like MQTT tags](https://forum.inductiveautomation.com/t/feature-allow-reference-tags-to-receive-backfill-data-from-sources-like-mqtt-tags/48261):
>
> At the moment, if you have MQTT Engine connected to a device, and Ignition reference tags to reference the MQTT tags with history on, backfill data from MQTT doesn’t transfer to the reference tag if the connection to the MQTT device goes down. If you enable history on the MQTT tag itself, then it backfills fine once connection to the MQTT device is re-established. It would be great if this backfill data was transferred across to the tag(s) that reference it. Idea: [Allow reference tags to rece…](https://ideas.inductiveautomation.com/ignition-features-and-ideas/p/allow-reference-tags-to-receive-backfill-data-from-sources-like-mqtt-tags)

If you care about backfill of course, otherwise just use history on ignition tags. I had no choice as we needed it

---

_[View the full topic](https://forum.inductiveautomation.com/t/creating-udts-with-mqtt-devices/51048)._
