Open sorru94 opened 7 months ago
Server-owned datastreams are transmitted to devices with no timestamp in the BSON file even when the explicit_timestamp is set in the interface definition.
explicit_timestamp
Replicate transmitting a boolean type using CURL:
curl -v -X PUT -H "Accept: application/json" -H "Content-Type: application/json" \ -H "Authorization: Bearer $APPENGINE_TOKEN" \ https://$APPENGINE_URL/v1/$REALM/devices/$DEVICE_ID/interfaces/$INTERFACE/boolean_endpoint \ --data '{"data" :true}'
The received BSON is the following:
09 00 00 00 08 76 00 00 00
Which in human readable form is:
{ "v": false }
Interface definition to use to replicate this issue: datastream_individual_interface.json
Tested with Astarte v1.1.1.
v1.1.1
See also #785 (TL;DR: does explicit_timestamp make sense on server-owned interfaces, as AppEngine API do not provide a way to set it?)
Server-owned datastreams are transmitted to devices with no timestamp in the BSON file even when the
explicit_timestamp
is set in the interface definition.Replicate transmitting a boolean type using CURL:
The received BSON is the following:
Which in human readable form is:
Interface definition to use to replicate this issue: datastream_individual_interface.json
Tested with Astarte
v1.1.1
.