Time is always "0001-01-01T00:00:00Z" in MQTT messages (using a LORANK8)

[chirpstack]

Time is always "0001-01-01T00:00:00Z" in MQTT messages (using a LORANK8)

[brocaar]

This is because the time field is only filled in the UDP packet when the gateway has an accurate time source (GPS). Since an empty time in Go is equal to 0001-01-01T00:00:00Z, the JSON published to MQTT is filled with this value. This has been brought up before and I agree it is confusing. I'll look into a proper solution soon.

[lg007]

Thanks for your reply. Don't worry too much about it, it is really not a big issue.

[jpmeijers]

How about setting the time field to 1970-01-01 00:00 (unix epoch)?

On the other hand, if the time is not set because the gateway is not aware of the current time, how about setting it to the current timestamp of the server. If the server is NTP sync'ed this will at least give a good representation of when the packet was passed through the bridge.

[tftelkamp]

Please don't set it to current time in the server, because then we don't know anymore of this is GPS synced time from the gateway or not.

Server time is useful though, but then better add a field for it.

[brocaar]

I don't thing it would be a good idea to let LoRa Gateway Bridge add a time-field to the JSON. As the instance might not run on the gateway itself, there might be quite a difference between when it was received by the gateway and when it was received by the gw bridge (as in seconds in some setups using 3G connection).

[sslupsky]

I have seen this issue when using the Microchip gateway as well so I do not think this is specific to the LORANK8.

Here is the output when subscribed to "gateway/#/#":

gateway/1234567887654321/rx {"rxInfo":{"mac":"1234567887654321","time":"0001-01-01T00:00:00Z","timestamp":1433980587,"frequency":903100000,"channel":4,"rfChain":1,"crcStatus":1,"codeRate":"4/5","rssi":-39,"loRaSNR":9.8,"size":21,"dataRate":{"modulation":"LORA","spreadFactor":7,"bandwidth":125}},"phyPayload":"QHC9cwcAIgI8qBIoYzAPfh8iXsvN"}

[brocaar]

This will be fixed soon :-)