nightscout-connect
v0.0.12
Published
Connect common cloud platforms to Nightscout.
Downloads
1,015
Readme
nightscout-connect
Nightscout's methods for synchronizing with common diabetes cloud providers. This module provides a single entry point to Nightscout for similar modules and allows managing http library and injecting dependencies from a single point.
Roadmap
- Nightscout
- [x] hello world
- [x] better gap finding
- [x] glucose
- [ ] treatments, profiles, devicestatus
- [x] Dexcom
- [x] Glooko
- [x] fetch data
- [x] translate data (likely needs work)
- [x] LibreLinkUp (needs testing)
- [x] ~~Medtronic~~
- [x] hello world
- [x] glucose, stub devicestatus
- [ ] treatments, profiles, devicestatus
- [ ] Tidepool
- [ ] Tandem
- [ ] ~~Diasend - obsolete~~
Lower priority
- Better UI integration, diagnostics, test connection, fix errors, manage plugin...
- Generate predictable pattern eg sine for test.
- run in capture mode to generate up to date test fixtures
- better sidecar support
- better cli support (pipe to/from anywhere:
* | nightscout-connect | *
, file, fixtures, csv, json, web services...
Help wanted
- more vendors
- better design suggestions
- testing
Brief Doc
ENABLE=connect
include the keywordconnect
in theENABLE
list.- Environment variable prefix
CONNECT_
:CONNECT_SOURCE
- The name for the source of one of the supported inputs. one ofnightscout
,dexcomshare
, etc...
How to use
For now there are two "output" devices available, internal Nightscout as a plugin, or external Nightscout as a sidecar from the commnandline. We will consider additional output targets.
From Nightscout
This is a Nightscout plugin. Enable the plugin by including the word connect
in the ENABLE
list. Select a data source by providing CONNECT_SOURCE
.
Make sure to provide the credentials needed by your data source. If they are
missing, the plugin will produce a helpful error through Nightscout indicating
which variables to set.
From command line
Running from the commandline for development purposes, as a sidecar, for
example, use npm install
and consider npm ln
to place the
nightscout-connect
shell script in your path. Once in your path, it will offer --help
for all subcommands.
$ nightscout-connect --help
nightscout-connect <cmd> [args]
Commands:
nightscout-connect capture <dir> [hint] Runs as a background server forever.
nightscout-connect forever [hint] Runs as a background server forever.
nightscout-connect demo a quick demo using timers instead of
I/O
nightscout-connect completion generate completion script
Options:
--version Show version number [boolean]
--help Show help [boolean]
nightscout-connect
will read the environment variables the same way as Nightscout
extended variables using the prefix CONNECT_
.
Development use typically consists of commands like this:
../cgm-remote-monitor/node_modules/.bin/env-cmd -f ../minimed-envs/subject.env nightscout-connect capture logs
Where subject.env
typically consists of something like this:
CONNECT_API_SECRET=626753d7f62f000078e8f6e2
CONNECT_NIGHTSCOUT_ENDPOINT=http://localhost:3030
CONNECT_SOURCE=minimedcarelink
CONNECT_CARELINK_USERNAME=your username
CONNECT_CARELINK_PASSWORD=your password
CONNECT_CARELINK_REGION=your region
CONNECT_COUNTRY_CODE=your country code
Input Data Sources
Nightscout
Work in progress
To sync from another Nightscout site, include CONNECT_SOURCE_ENDPOINT
and
CONNECT_SOURCE_API_SECRET
.
CONNECT_SOURCE=nightscout
CONNECT_SOURCE_ENDPOINT=<URL>
CONNECT_SOURCE_API_SECRET=<OPTIONAL_API_SECRET>
The CONNECT_SOURCE_ENDPOINT
must be a fully qualified URL and may contain a
?token=<subject>
query string to specify an accessToken.
The CONNECT_SOURCE_API_SECRET
, if provided, will be used to create a token
called nightscout-connect-reader
. This information or the token provided in
the query will be used to read information from Nightscout and is optional if
the site is readable by default.
Select this driver by setting CONNECT_SOURCE
equal to nightscout
.
Dexcom Share
To synchronize from Dexcom Share use the following variables.
CONNECT_SOURCE=dexcomshare
CONNECT_SHARE_ACCOUNT_NAME=
CONNECT_SHARE_PASSWORD=
Optional, CONNECT_SHARE_REGION
and CONNECT_SHARE_SERVER
do the same thing, only specify one.
CONNECT_SHARE_REGION=
ous
orus
.us
is the default if nothing is provided. Selectingus
setsCONNECT_SHARE_SERVER
toshare2.dexcom.com
. Selectingous
here setsCONNECT_SHARE_SERVER
toshareous1.dexcom.com
.CONNECT_SHARE_SERVER=
set the server domain to use.
Glooko
Note: Experimental.
To synchronize from Glooko use the following variables.
CONNECT_SOURCE=glooko
CONNECT_GLOOKO_EMAIL=
CONNECT_GLOOKO_PASSWORD=
CONNECT_GLOOKO_TIMEZONE_OFFSET=0
By default, CONNECT_GLOOKO_SERVER
is set to api.glooko.com
because the
default value for CONNECT_GLOOKO_ENV
is default
.
CONNECT_GLOOKO_ENV
is the worddefault
by defalt. Other values areeu
,development
,production
, forapi.glooko.work
, andexternalapi.glooko.com
, respectively.CONNECT_GLOOKO_SERVER
the hostname server to use -api.glooko.com
bydefault
, oreu.api.glooko.com
for EU users.CONNECT_GLOOKO_TIMEZONE_OFFSET
defines the time zone offset you are at from the UTC time zone, in hours
If both, CONNECT_GLOOKO_SERVER
and CONNECT_GLOOKO_ENV
are set, only
CONNECT_GLOOKO_SERVER
will be used.
Libre Link Up
To synchronize from Libre Link Up use the following variables.
CONNECT_SOURCE=linkup
CONNECT_LINK_UP_USERNAME=
CONNECT_LINK_UP_PASSWORD=
By default, CONNECT_LINK_UP_SERVER
is set to api-eu.libreview.io
because the
default value for CONNECT_LINK_UP_REGION
is EU
.
Other available values for CONNECT_LINK_UP_REGION
:
US
,EU
,DE
,FR
,JP
,AP
,AU
,AE
For folks connected to many patients, you can provide the patient ID by setting
the CONNECT_LINK_UP_PATIENT_ID
variable.
Minimed Carelink
To synchronize from Medtronic Minimed Carelink, set the following environment variables.
CONNECT_SOURCE=minimedcarelink
CONNECT_CARELINK_USERNAME
CONNECT_CARELINK_PASSWORD
CONNECT_CARELINK_REGION
Eithereu
to setCONNECT_CARELINK_SERVER
tocarelink.minimed.eu
orus
to usecarelink.minimed.com
.
For folks using the new Many to Many feature, please provide the username of the
patient to follow using CONNECT_CARELINK_PATIENT_USERNAME
variable.
Tidepool
- [ ] TODO
Tandem
- [ ] TODO
History
Initially there was share2nightscout-bridge
, then
minimed-connect-to-nightscout
.
The request
library was deprecated in February, 2020, and Nightscout needs to
adapt by using currently maintained and supported dependencies. The initial
goal is to help deprecate share2nightscout-bridge
and use currently supported
dependencies.
Now there are more:
- https://github.com/burnedikt/diasend-nightscout-bridge
- https://github.com/jpollock/glooko2nightscout-bridge
- https://github.com/timoschlueter/nightscout-librelink-up
- https://github.com/jwoglom/tconnectsync
- https://github.com/skalahonza/TidepoolToNightScoutSync
This module should be sufficient to replace share2nightscout-bridge
as an
initial minimum viable project. There are a few minor enhancements to help
encourage migration away from share2nightscout-bridge
:
- Less latency: new glucose fetches will be tightly aligned to the previous glucose reading. In most cases, new glucose readings will be produced within 30 seconds.
- Safe retries: There is an exponential backoff system to help prevent locking your account if the password changes. Each retry will take a much longer amount of time.
- Safe community: There are now randomization behaviors to prevent tragedy of the commons from occurring. These features help spread the load to avoid accidentally overwhelming vendor servers.