Collect
The collector retrieves authorized follower telemetry on a controlled schedule and keeps authentication state in memory.
Actively Maintained
Your glucose data.
Where you need it.
GlucoseReporter™ is a lightweight, self-hosted bridge that reads authorized Twiist follower data and makes it available through a dedicated Android app and compatible displays such as SugarPixel. Each household gets its own isolated, secure connection — built especially with Android families in mind, where official Twiist caregiver access is currently limited to Apple's ecosystem.
SOURCE
Twiist follower data
Authorized read-only access
BRIDGE
GlucoseReporter™
Normalize • store • serve
DISPLAY
SugarPixel
Nightscout-compatible output
Read-onlyNo pump control
Self-hostedRuns on a Raspberry Pi, tenant-isolated
RecoverableAuto-starts after reboot
Private by designNo public dashboard required
HOW IT WORKS
A small bridge with a very specific job.
GlucoseReporter keeps the moving parts narrow. It authenticates as a legitimate follower, retrieves telemetry, stores normalized readings locally, and serves a small compatibility layer for the GlucoseReporter Android app and displays that already understand Nightscout-style glucose data.
Normalize
Glucose samples are normalized, deduplicated, and stored locally in SQLite so the display path is independent of each upstream request.
Serve
A tiny read-only adapter exposes compatible glucose entries while Cloudflare Tunnel provides stable HTTPS access without exposing the Raspberry Pi directly.
BUILT FOR THE ANDROID GAP
Caregiver glucose data should not depend on owning an iPhone.
Twiist provides its caregiver experience through the twiist insiight app, while its current phone ecosystem remains centered on compatible iPhones and Android compatibility is still described by Twiist as future work. GlucoseReporter™ grew out of a practical need to make authorized follower glucose data useful for families and caregivers who live on Android.
A real Android app
GlucoseReporter now ships a dedicated Android app with secure, self-serve enrollment — no manual key entry, no waiting on Twiist's iOS-first roadmap.
Authorized data only
GlucoseReporter uses legitimate follower authentication and reads telemetry already made available to an authorized caregiver account.
Not a replacement controller
It does not control the Twiist pump, deliver insulin, change settings, or replace the official Twiist treatment interface.
Important distinction
GlucoseReporter™ is not an Android version of twiist insiight. It is an independent, read-only interoperability bridge designed to make authorized follower glucose data available beyond an iPhone-only workflow.
SEE IT IN ACTION
The GlucoseReporter Android app.
A live glucose reading with trend and history, full therapy detail beyond just the number, and configurable low/high alarms that sound until acknowledged — all from data already available to an authorized follower.
SAFETY BOUNDARY
Read-only means read-only.
GlucoseReporter is intentionally separated from treatment control. Its job is to report data, not make therapy decisions or send commands.
✓
Reads authorized follower telemetryGlucose and related display data only
✓
Stores data locallySmall, purpose-built SQLite storage
×
No bolus or basal commandsNo insulin delivery control
×
No pump setting changesNo treatment-state writes or acknowledgements
CURRENT RELEASE
The latest release is live.
This release adds secure multi-household support: each family gets its own isolated, tenant-specific connection, provisioned through self-serve enrollment and the new GlucoseReporter Android app.
Releasev2.5
PlatformRaspberry Pi
Display outputAndroid app + SugarPixel
AccessMulti-household, isolated
WHY GLUCOSEREPORTER
Built to make useful data easier to reach.
GlucoseReporter™ started as a practical interoperability project born from a real gap: an Android-using caregiver needed dependable access to follower glucose data without depending on an iPhone-only workflow. The goal became simple: take glucose data already available to an authorized follower and make it useful on the displays and platforms a family already relies on. As more households asked for the same thing, GlucoseReporter grew to serve more than one family at a time — each one fully isolated from the others.
The project favors small components, local storage, clear operational logs, and a strict read-only boundary. The result is intentionally boring infrastructure, which is exactly what always-on infrastructure should be.
Simple bridge. Stable endpoint. No treatment control.
Actively Maintained • Self-hosted • Read-only