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
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.
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.
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.
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.
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.
Ben WestandGitHub
Chris Pitchford
Sulka Haro
Lennart Goedhart
Matthew Dawson