The event is triggered with event.enum = 109, and the corresponding description is expected in custom.param.109.
From the device side, the AVL ID 109 is indeed being sent with the data payload.
We suspect that Flespi is receiving the data but not parsing it correctly — possibly due to the need for converting the hexadecimal data to ASCII in order to interpret the payload.
We’ve confirmed that selecting View Traffic for a specific timestamp shows the data, but in the parsed view, the field remains blank.
