Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attribute.setTimestamp() seems to not be working #13

Open
pankalog opened this issue Nov 12, 2023 · 1 comment
Open

Attribute.setTimestamp() seems to not be working #13

pankalog opened this issue Nov 12, 2023 · 1 comment

Comments

@pankalog
Copy link
Member

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.

@pankalog
Copy link
Member Author

I am going to store the payloads from the device to recreate the bug, @richturner do you have any idea why this would happen?

@pankalog pankalog self-assigned this Nov 12, 2023
@pankalog pankalog transferred this issue from openremote/openremote Dec 12, 2023
@pankalog pankalog removed their assignment Jul 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant