Juggluco

Juggluco Juggluco is an alternative Android app for reading glucose sensors (FreeStyle Libre 1/2/2+/3/3+, Dexcom G7/ONE+, Sibionics GS1/GS3, CareSens Air, Linx/Aidex-X, and others). It supports continuous glucose readings every minute via Bluetooth, NFC scanning, insulin/carbohydrate/activity logging, and Nightscout integration. Requirements - Android 5+ phone (Android 8+ is required for Libre 3 and US Libre 2) - Juggluco app (download from [ juggluco.nl]( https://www.juggluco.nl/Juggluco/download.html)) - A sensor supported by the app - Bluetooth enabled - For Libre 3: the Libreview account used to activate the sensor Basic sensor setup 1. Install and launch Juggluco. 2. Enable Use Bluetooth (left menu → Sensor ). 3. Scan the sensor via NFC (hold the phone close to the sensor). - Libre 2: scanning activates the Bluetooth connection. - Libre 3: first go to Settings → Data exchange → Libreview , enter your account details, press Get Libreview Account ID , wait for it to be retrieved, and then scan the sensor. - Dexcom G7/ONE+, Sibionics, and similar sensors: left menu → Photo → scan the QR/data matrix code. 4. Accept the Bluetooth pairing request (if it appears) - do it quickly before the screen turns off. 5. Check the connection in the left menu → Sensor . Current stream values should start appearing. Disable or force-close the official LibreLink / Libre 3 app (and FreeStyle readers) to avoid connection conflicts. Nightscout integration (Uploader) Juggluco can send glucose values (stream) directly to a Nightscout instance. 1. Left menu → Settings → Data exchange → Uploader . 2. In the URL field, enter the address of your instance, for example: https://test.diab.ninja 3. In the api_secretfield (or Access Token when using V3), enter the secret from your Nightscout configuration. 4. Select Active . 5. Optionally select Send values (for doses/insulin/carbohydrates) - define the label mapping first. 6. If needed, use Send now or Resend data . Stream values are sent immediately after they are received from the sensor. V3 option (api/v3) Select test V3 only if the Nightscout server is configured for V3. Instead of api_secret, enter an Access Token with permissions for entries and treatments (created in the Admin Tools panel in Nightscout). Do not mix V1 and V3 on the same server. Web server in Juggluco (local Nightscout) Juggluco includes a built-in web server compatible with some Nightscout and xDrip clients. 1. Left menu → Settings → Data exchange → Web server . 2. Set api_secret . 3. Select Active . 4. For local access, use: https://127.0.0.1:17580 5. Optionally deselect Local only if you want access from other devices on the local network. 6. Internet access requires port forwarding + an SSL certificate (private key + full chain). The server implements basic Nightscout endpoints (`/api/v1/entries`, `/sgv.json`, etc.). Checking that it works - The current glucose value should appear on the main Juggluco screen (the sensor ID color indicates how old the reading is). - In the left menu → Sensor , check the time of the latest stream reading. - New values should appear in Nightscout (or the client) about once per minute. - Android notifications and the status bar can display the current glucose value (this requires the appropriate system notification settings). Notes and limitations - European Libre 2 sensors usually allow several apps to be used on the same phone at the same time (although alarms may be less reliable). US/CA/AU Libre 2 sensors and all Libre 3 sensors do not. - Juggluco does not require an account or a permanent Internet connection for basic sensor operation. - Bluetooth and scanned values may differ slightly at the beginning of use - the difference usually decreases over time. - Disable battery optimization for Juggluco (left menu → **Sensor** → **Sleep mode**) to keep the Bluetooth connection stable. - If you have connection problems: turn Bluetooth off and on, restart the phone, scan the sensor again, or use **Forget** / **Disconnect** in the Sensor menu. Troubleshooting Problem Possible solution No glucose values Check that the official Abbott app is closed. Scan the sensor. Turn Bluetooth off and on Connection error status=133 This commonly occurs when the device cannot be detected - try again or restart Bluetooth Uploader: `upload failure:` (empty) Check the network connection and make sure the hostname is correct Uploader: `FileNotFoundException` Incorrect URL (missing port, unnecessary path) or invalid api_secret. AAPS does not retrieve treatments Force-close and restart AAPS. Use NSClientV3 with api_secret as the token More details: Juggluco documentation There is also a blog post about Juggluco: Juggluco - what is it and why are more and more people with diabetes using it?