When the Teltonika device connects to OpenRemote and there are a lot of payloads to be delivered (that were not able to be delivered while the device cannot get a solid connection to OpenRemote), it seems that the set timestamps for the attributes are not being stored. We can see this by the fact that any attribute of the payload in question does not have the correct timestamp, but the attribute "lastContact", that stores that timestamp, has a completely different value compared to the attributes. The attributes have the timestamp of the current time.
Using a debugger, I can see that the timestamps are being stored properly until and when the attributes are passed to AssetProcessingService.
When the Teltonika device connects to OpenRemote and there are a lot of payloads to be delivered (that were not able to be delivered while the device cannot get a solid connection to OpenRemote), it seems that the set timestamps for the attributes are not being stored. We can see this by the fact that any attribute of the payload in question does not have the correct timestamp, but the attribute "lastContact", that stores that timestamp, has a completely different value compared to the attributes. The attributes have the timestamp of the current time.
Using a debugger, I can see that the timestamps are being stored properly until and when the attributes are passed to AssetProcessingService.