Fix linkup reporting delay #36
Open
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
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.
Fix the ~20min delay when importing glucose measurements from LinkUp
It appears Libre intentionally cuts the last 20 minutes, but does provide the latest value. This fix simple injects the latest value into the graph data stream and removes the filtering. The filter removal is required to allow the recovery of any missing 20 minute period missing at a restart - using the latest timestamp prevents bringing in data from any missing period prior to any imported value. Upon testing, I can confirm that NS does not maintain duplicates, the mongodb data only shows one value of each, so the filtering seems to be unnecessary either way and can only create issues.