TagoIO integration sends different downlink

Hello,

I have recently added a TagoIO integration to one of my devices. When trying to send a downlink payload from Tago to the device I noticed that the raw payload is different. Anyone know why?

Down_Combined

The value 00073C00A00501 is sent as text, so: the downlink holds the ASCII values for the characters 0 (wich is hexadecimal 0x30), 0, 0, 7 (ASCII 0x37), 3 (ASCII 0x33), and so on.

As for why, I don’t know.