- Display latest CGM reading from either:
- Nightscout
- Tomato
- xDrip+ (android only)
- Clock colour changes with reading
- In range -> green
- High values -> orange/red
- Low values -> light/dark blue
- Minimal configuration
- Units + alarm thresholds are read from source
- Second time zone
- Toggle on/off and set the offset in the settings
- Install the app from the Fitbit Gallery
- Select your data source from the app Settings inside the Fitbit app
- If using Nightscout, enter your URL in the settings. Don't include
/api/v1
- If using Nightscout, enter your URL in the settings. Don't include
- That's it! You should see readings appear in the corner of your watch. If not, see troubleshooting
- High/low thresholds: Due to the different levels of detail available in each API, each source has slightly different behavior for thresholds. Nightscout provides 4 levels (urgent low/low/high/urgent high) based on the user's settings. xDrip+ provides just 2 (low/high), and so only 3 different colours will be used in the watch. Tomato provides no alarm information, so 4 hardcoded default thresholds are used.
- Offline mode: Only xDrip+ supports offline mode, meaning that results will still be updated on the watch when the phone has no internet connection. A bluetooth connection between the phone and the watch is always needed.
🚧 coming soon 🚧
In the meantime, you can contact me via the app page in the Fitbit gallery.
- run npm install
- make sure watch is connected to the Developer Bridge
- start fitbit console with npx fitbit
- build: fitbit$ build (see below about building for production)
- install: fitbit$ install
When creating a build for release, all tests need to run and pass. Therefore, this build should only be done using the build script:
npm run build
which runs the tests before building the app. The resulting build is placed in the build/
directory.