Improve decoding fractional epoch timestamps #79
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add `test_timestamp_seconds_float`: Publish single reading in JSON format to MQTT broker, using a timestamp as Unix Epoch in seconds, as float number. Proof that the timestamp is processed and stored correctly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi.
this aims to resolve #68, by verifying that Kotori already accepts fractional epoch timestamps. On top, the patch improves the situation by actually carrying over the corresponding precision to the database.
A test has been added to publish a single reading in JSON format to the MQTT broker, using a timestamp as Unix Epoch in seconds, as a floating point number. It proofs that the timestamp is processed and stored correctly.
With kind regards,
Andreas.