How to interpret gateway timestamp

1

Hi,

When collecting my node data, there is a field in the JSON object called gateway timestamp. I guess this is the closest time to when the node transmitted a message. But I’m unsure how to interpret it. If converting as a UNIX timestamp it does not make sense (gives me a date in 2064).

Thanks in advance,

Mathies

2

You also can find “server_time” in the JSON object which might make more sense to you.

3

Hi jdelaet,

Thanks. However I guess that the gateway timestamp is closer to the actual time the message was sent from the Node? I know it is probably pretty close, but I would like to get the time that represents the send time the best. So if the gateway forwards its time in the header, I guess I should be able to use it? The number seems arbitrary though?

4

Gateway_timestamp values didn’t make sense to me so far. Server_time was accurate enough for me.
But as you say, there might be a difference in their meaning.

I hope others can help.

5

Yeah, It might be accurate enough for me as well… But if anybody knows how to interpret the gateway_timestamp please let me know. :slight_smile:

6

You could always take a look at the packet forwarder source to see where/how it is used… (count_us) The time stamp is used to schedule transmissions. For GPS equipped gateways it should be based on the real time, it is millisecond based, not second based like the UNIX timestamp.
The other time included in the packet is based on the same time stamp when a gateway is GPS enabled and the time the packet is received on the back-end for other gateways. Not millisecond accurate, but usually within a few seconds.