In looking at the API for creating a data stream, there is the "at" attribute, which is a timestamp of the value. https://www.carriots...agement#streams
1. Please update the documentation to describe what this timestamp is based from. Is it UNIX? What is the epoch? How does one calculate the timestamp?
2. Please consider the following in making this field very valuable and highly usable across all types of devices.
- Allow a value of "at" to be "now". Then the Carriots server will timestamp the value for when the value was received. Some devices have no timekeeping ability, and the application is not time sensitive, but still needs some approximate time of data.
- Create an API function that a device can call to get the current time. Sure, a device can implement a time server protocol, but that could be added trouble, especially in resource constrained equipment. It would be great if Carriots had a way for a device to query the time, and then also specify the format that it would like the data in. That way, the end device doesn't need to do conversion, it could apply the data directly. Maybe a way to use a rule.
- It would be nice if the "at" attribute also accepted time in the format as described at the bottom of Core Concepts. https://www.carriots...i/core_concepts