MQTT payloads incomplete 16 bytes instead of 18 or 19 bytes

Using MQTT.fx I have verified connection to the Cirrus MQTT broker running ont the ignition server that the payloads for sensor value have their full payloads. Looking at HEX they are the full 18 and/or 19 bytes. However, when brought into Ignition, the payloads at 16 bytes. Essentially missing between 2 and 3 bytes depending on the sensor. Some are 18 bytes and some are 19 bytes.

The payloads are datatype: "string" in the tag browser. I'm converting them to bytes for HEX to parse. Perhaps that is related?

Could not locate any settings where 16 would be the limit. Any thoughts as to what could cause such behavior?

In particular, the device connected broadcasting the MQTT is a Broadsens Gateway with wireless vibration sensors.

Again, the data is entirely complete when subscribing to the MQTT topics that are on the Cirrus Broker. Just for some reason when looking at the tags coming from the connection within igntion are never larger than 16 bytes.

Example full payload: 01 00 D9 01 C2 00 0B 00 10 00 0D 00 06 00 06 00 05 AA 0A

If anyone has some ideas, that would be much appreciated.
Thanks,
Casey

Yes, this is a lossy conversion, it's not going to work.

You'll need to encode your payloads in a format that can survive a binary to string to binary conversion. Base64 or just hex encoded should work.