Timestamp in asset/attributes endpoint

juanjimenez04 · September 18, 2024, 1:44am

Hello,
We have implemented OpenRemote to receive data from agricultural sensors, create dashboards and analyze them. The sensors transmit the data to a Gateway that adds a timestamp and stores it in a temporary database, every 15 minutes it reads the temporary database and sends it to OpenRemote through the /asset/attributes endpoint. Because the crops are located in areas with difficult communication, the Gateway normally cannot communicate 100% of the time and once it recovers communication it sends all the accumulated data.
Is there a way for the data to retain its original timestamp and not be plotted with the date and time it was received by OpenRemote?
We greatly appreciate your help.

Rich · October 22, 2024, 9:01am

Hi,

Indeed this seems like a shortfall in the attributes HTTP endpoint, I have created an issue to add this capability here:

github.com/openremote/openremote

Improve AssetResource writeAttributeValue/writeAttributeValues endpoints to allow timestamp to be supplied

opened 08:59AM - 22 Oct 24 UTC

richturner

The HTTP endpoints for writing attribute values don't currently allow a timestam…p to be supplied, make the following change(s): ``` @Path("{assetId}/attribute/{attributeName}/{param1 : (\\d+)?}") Response writeAttributeValue(@BeanParam RequestParams requestParams, @PathParam("assetId") String assetId, @PathParam("attributeName") String attributeName, Object value); ``` ``` AttributeWriteResult[] writeAttributeValues(@BeanParam RequestParams requestParams, AttributeStateWithTimestamp[] attributeStates); AttributeStateWithTimestamp extends AttributeState { protected Long timestamp; } ```