Would it be possible to run the Gateway metadata through the device codec like Helium does? It would be very convenient, especially when formatting data for the InfluxDB or http integrations.
Like this:
function Decode(fPort, bytes, metadata)
{
(where metadata is a JSON object)
}
Would you be able to share an example use-case? I’m just wondering if this is related to the payload decoding or if the InfluxDB integration should write more data to the database. Note that all gateway meta-data is already exposed in the http integration.
Thank you for responding.
Let me begin by saying that if I understood my options better I probably wouldn’t be asking this. ChirpStack is powerful and flexible, but I just don’t know enough about how to use it, so I’m asking for something that would make it easier for me. 
I am in the final testing phase of a LoRaWAN device that we will bring to market soon. I’ve built an automated test, and am using ChirpStack on an RAK Wireless gateway to log test data. The data I need includes the application payload plus some metadata like the rssi, snr, frequency and so forth. It would be convenient if I could combine this data in the CODEC to forward it on to InfluxDB Cloud. Also, in the final product I will be logging some metadata.
I got around this for now by subscribing to the MQTT flow, parsing the parts I want, and writing it to a local file. I’m sure there are a dozen ways to do this better that I just don’t know.
Anyway, have I made a case for metadata in the CODEC, or am I just missing an obvious better solution?
Keith
Could it be that you’re looking for this: InfluxDB - ChirpStack open-source LoRaWAN<sup>®</sup> Network Server?