update Nightscout 2022-01 #8
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
The /api-docs/ endpoint will now send the correct api-secret header when API_SECRET is used for authentication.
Forcing a newer version of share2nightscout-bridge in order to keep up with Dexcom changes.
Include enhancements on the minimed-connect-to-nightscout plugin to include fetching data from a Careportal account.
Using a ratio of 18 mg/ml to 1 mmol/l causes NightScout to report different values compared Dexcom app/receivers. A more accurate value is based on 0.0555 mmol/l to 1 mg/dl. The inverse is 18.018018018 mg/dl to 1 mmol/l This puts the value closer to the Dexcom app/receiver. Affected values: |mg/dl| 18|18.018018018| |----:|---:|-----------:| | 109| 6.1| 6.0| | 118| 6.6| 6.5| | 127| 7.1| 7.0| | 136| 7.6| 7.5| | 145| 8.1| 8.0| | 154| 8.6| 8.5| | 163| 9.1| 9.0| | 172| 9.6| 9.5| | 181|10.1| 10.0| | 190|10.6| 10.5| | 199|11.1| 11.0| | 208|11.6| 11.5| | 217|12.1| 12.0| | 226|12.6| 12.5| | 235|13.1| 13.0| | 244|13.6| 13.5| | 253|14.1| 14.0| | 262|14.6| 14.5| | 271|15.1| 15.0| | 280|15.6| 15.5| | 289|16.1| 16.0| | 298|16.6| 16.5| | 307|17.1| 17.0| | 309|17.2| 17.1| | 316|17.6| 17.5| | 318|17.7| 17.6| | 325|18.1| 18.0| | 327|18.2| 18.1| | 334|18.6| 18.5| | 336|18.7| 18.6| | 343|19.1| 19.0| | 345|19.2| 19.1| | 352|19.6| 19.5| | 354|19.7| 19.6| | 361|20.1| 20.0| | 363|20.2| 20.1| | 370|20.6| 20.5| | 372|20.7| 20.6| | 379|21.1| 21.0| | 381|21.2| 21.1| | 388|21.6| 21.5| | 390|21.7| 21.6| | 397|22.1| 22.0| | 399|22.2| 22.1|
Using share2nightscout-bridge, the device property is defined as 'share2' displayBg should honour the Dexcom HIGH and LOW values when the device is share2 This ensures that NightScout returns "LOW" for 39mg/dl and "HIGH" for 401mg/dl as is reported in the Dexcom app/receiver.
This reverts commit 513d155.
This patches uses a newer versin of minimed-connect-to-nightscout that is designed to work under the same version of node as Nightscout. It should result in Nightscout gaining a capability to use Medtronic Careportal accounts for cloud to cloud synchronization.
…pitchford/cgm-remote-monitor into dev
The `npm audit fix` in the `Dockerfile` is currently deleting vulnerable packages. Although we do want to have package security, this should be done in a development process, not as part of the Docker build. This commit also reduces the Docker image size and improves security.
…an/cgm-remote-monitor into dev
This should force the coverage job to return with a success error code. Codacy changed support for legacy projects. This change should not cause builds to fail and should not influence ability to merge pull requests. Until further work with coverage with codacy, this change emits a warning of "NO COVERAGE" while allowing the build to pass, rather than failing the build.
When collecting date from Dexcom via share2bridge-dexcom before we would poll at regular intervals. Dexcom transmitters / apps refresh every 5 minutes give/take the inaccuracy in the transmitters clock. If we poll every 5 minutes, we will randomly introduce up to 5 minutes of lag before we refresh. For example, if we poll 4:59s after dexcom refreshed we will face a 4:59s lag seeing the latest data arrive This patch introduces a refresh adjustment. We look at the timestamp of the most recent data item and aim to refresh 5 minutes plus a buffer after that timestamp. for example, 5:20s after the most recent data time. the additional buffer gives dexcom a chance to push the data through their application/infrastructure (after the app sends the data, it appears in testing to be around 20s before it is available in the API) This reduces the lag time to a reliable 20 seconds regardless of when nightscout was started and keeps it in track as it drifts forwards and back.
The default interval is increasd from 2.5 minutes to 2.6 minutes This change incorporates the lag between the app uploading and the data being available in share2nightscout-bridge This change also accomodates the optimisation of the refresh interval based on the last collected data timestamp
…excom_fetch_times Optimize time between polling share2nightscout-bridge to reduce ingest lag
systemcure
pushed a commit
that referenced
this pull request
Oct 25, 2022
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.
No description provided.