When Iot Agent sends data within milliseconds, the values are not notified to Draco subscription - fiware-orion

Question

Our device sends millisecond level telemetry data to Fiware. The payload contains DeviceId, DeviceDateTime and Attribute values as follows:
{"humidity":50.5,"device_id":"WS-100","devicetime":"2020-06-08T17:38:35.629+5:30"}
But we have observed that millisecond level tracking is not available in MongoDB and also Fiware does not notify the Draco subscription when data received at millisecond level. It only sends one payload per second. This is our Draco subscription:
curl -iX POST \
'http://52.172.34.29:1026/v2/subscriptions?options=skipInitialNotification' \
-H 'Content-Type: application/json' \
-H 'fiware-service: openiot' \
-H 'fiware-servicepath: /' \
-d '{
"description": "Subscription",
"subject": {
"entities": [
{
"idPattern": ".*"
}
],
"condition": {
"attrs": []
}
},
"notification": {
"http": {
"url": "http://52.172.34.29:3003/v2/notify"
},
"attrs": [],
"onlyChangedAttrs":true,
"throttling": 5
}
}'
Can you please let us know how to handle this millisecond changes in Orion subscription.
Thanks!

Answer 1

Milliseconds support is part of Orion backlog (see issues #3412, #2670 and #432) but it has not been implemented yet. I know there are people in the FIWARE community working on this feature, but I don't know when it will be available.
However, even if Orion doesn't support milliseconds natively, the application always has the option to manage it itself. For instance, using a devicetimeMs which value is an integer with time in milliseconds, included along with the other data when you send a telemetry measure. This is the typical workaround.
UPDATE: milliseconds support for DateTime attributes and metadata has been implemented. The feature will be avaiable in next Orion version (2.5.0) but it can be used right now if you get :latest container from dockerhub.