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

influxdb in node time precision has no effect #124

Open
Broadsens opened this issue Jul 3, 2022 · 2 comments
Open

influxdb in node time precision has no effect #124

Broadsens opened this issue Jul 3, 2022 · 2 comments

Comments

@Broadsens
Copy link

Version [V1.x]. At "influxdb in" node, the default time precision is "ms".
In the advanced query option of the "influxdb in" node, changed the time precision to "Microsecond (u)", but the query result is still showing "Millisecond (ms)" resolution in the debug window of node-RED. Also when using function node to handle the output from the node, the precision is also "ms".

What could be the cause?

@Broadsens
Copy link
Author

When using the "raw output" option, then the node-RED debug window shows the precision of "Microsecond (u)" no matter what time precision is set at the advanced query option of the "influxdb in" node.

@Broadsens Broadsens changed the title influxdb in node precision has no effect influxdb in node time precision has no effect Jul 3, 2022
@Broadsens
Copy link
Author

Solved the problem with the following approach:
Read out the first data in millisecond resolution, then calculating the time passed for the remaining samples using microseconds based on the sampling rate. Use this new time stamps with microseconds resolution.

BTW, the "influxdb in" node time stamp read out is a string. We saved the time stamp with microseconds resolution to Influxdb. Checking timestamp at command line shows correct values.

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