1.1 Timestamp Handling

1.1.1 When saving telemetry data, it is recommended to save both the UNIX timestamp (reported by the device) and the time at which the data record was created in the database. This is valuable to evaluate delays in data reporting between the device and online server.

1.1.2 Alternatively, if the above is not possible - it is recommended to assign the UNIX timestamp reported by the device to the telemetry data and then record the last communication time of the device.

1.2 Data Assignment

1.2.1 A key should only hold 1 value.

1.2.2 Parameter (param) field has telemetry data only whilst a setting (set) can be considered as telemetry data and attributes i.e. history of settings and the current settings.

1.3 Data forwarding JSON structure

1.3.1 The following JSON structure is sent for each timestamp or event reported by the device.

device_id: {imei, dev_eui, sigfox_id} string
network_id: {cellular, lora, sigfox} string
device_param_application_id: {based on fields} string
last_seen_by parser: {unix time} decimal
time_param_unix_absolute: {unix time} decimal
field_x: {value_x}