In the portal I see message timestamps in millisecondes precision. The actual senml messages I receive are in seconds at best. Is there a possibility to get a milliseconds timestamp in the device-uplink-message? Preferrably timestamped by the gateway?
Beste antwoord door Rick S.Bekijk origineel
that is a pity, as the portal does report in milliseconds, but the message does not. Is there an API to the portal in order for me to merge the portal data with the message data? It’s very cumbersome but better than designing and implementing a date-time recovery protocol between device and server.
Happy New Year!
I discussed this again with my colleague. Again I get the feedback that we don't send millieseconds with SenML messages. I'm afraid this is the answer we have to deal with.
Thanks for replying. It is possible to send anything using senml, including timestamp in millieseconds, nano if you want. Just not with bt. My question is about some meta-value in the payload.
I also went through this question again with the specialists and the conclusion is that we cannot send the timestamp in milliseconds. This is because we use the SenML standard. In this default the time is in seconds (as stated on the page I sent earlier) and we cannot change that.
This is not a question about senml, but about the metadata I reveive along with the device payload. The timestamp is in seconds. Is it possible to get milliesecond accuracy? The portal has millisecond accuracy, so the information is available somwhere.
All information related to SenML can be found on the page Sensor Measurement Lists (SenML)