I have an application where I am communicating to Ignition via MQTT.
At Ignition I’m referencing the MQTT tag to a UDT (using a reference tag) to apply additional data and then historicize it in Ignition.
My question, with MQTT buffering, will it still buffer data into the historian if I do the referencing to another tag? Or will the buffering break and I’ll see a gap in data?
I think this thread discusses your specific question: [FEATURE] Allow reference tags to receive backfill data from sources like MQTT tags
I’ve not had a chance to check in on this behavior, but there I’m pretty sure there was a point in time in the past where the history was only on the base MQTT tag, requiring some custom functionality to indirect over to it for history queries (associated with your UDT). Last time I worked with this specific scenario was back in the 8.0.x days (and associated MQTT module versions of that time).
EDIT: just for clarity, the situation I mentioned above had History enabled on the MQTT Engine tag (and not the reference tags in the UDT). That used to be the only way I could get the backfill working properly.
Yep, this is what we're using as well, since backfill data does not get forwarded onto the reference tags. It's a bit of an ugly setup.