Hello,
I have a device based on a RAK3172 that sends data using fragmented uplinks.
My question is about the ChirpStack payload codec behavior. Is it possible for the codec to somehow keep received fragments in memory, wait until all fragments of a message have been received, reassemble the complete payload, and only then forward the decoded data to the MQTT topic?
Or does ChirpStack execute the codec independently for each uplink and immediately publish every received fragment to MQTT, making message reassembly impossible within the codec itself?
Thank you.
