Is there any way to enforce millisecond accurate timestamps in the metadata of messages from LoRaWan devices?
I have verified that the timestamp generated by my gateway is a unix timestamp in millisecond (eg 1667406503931), but the JSON timestamp in the metadata I am getting from IoT Core is a string timestamp that only goes to seconds (eg. 2022-11-02T16:23:15Z).
The example with gateway metadata off on this page of the documentation has an example of a message with milliseconds in the timestamp, and I am curious how accurate that example is. Currently if I disable gateway metadata in the service profile it will remove the timestamp all-together (the only metadata I get is fcount and fport) so I am wondering if I am missing something or if that example is just wrong.
Truncating the milliseconds like this also makes it unclear if the timestamp in the metadata is the time that the Gateway received the message, or if it is the time that the LNS server received the message, is this information also available anywhere?
I poked around in the settings and documentation for the Devices, Gateways, Device profiles and Service profiles and was unable to find much regarding timestamps or metadata formatting.
Is anyone able to provide any insight into this, or otherwise point me in the right direction?
AWS OFFICIALUpdated 7 months ago
Hey Greg, I was under the impression that the timestamp field in the metadata was the timestamp from gateway (on the edge). Can you confirm that this timestamp is actually the time that AWS LNS receives the message?
This is a follow-up to my last question. In a separate AWS Support ticket, we've confirmed that the timestamp field is the time AWS LNS receives the message and not the timestamp from the edge