Collect
The collector retrieves authorized follower telemetry on a controlled schedule and keeps authentication state in memory.
GlucoseReporter™ is a lightweight, self-hosted bridge that reads authorized Twiist follower data, stores it locally, and makes it available to compatible displays such as SugarPixel. It was built especially with Android families in mind, where official Twiist caregiver access is currently limited to Apple's ecosystem.
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 displays that already understand Nightscout-style glucose data.
The collector retrieves authorized follower telemetry on a controlled schedule and keeps authentication state in memory.
Glucose samples are normalized, deduplicated, and stored locally in SQLite so the display path is independent of each upstream request.
A tiny read-only adapter exposes compatible glucose entries while Cloudflare Tunnel provides stable HTTPS access without exposing the Raspberry Pi directly.
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.
The bridge runs on a Raspberry Pi, not on the caregiver's phone, so compatible displays and future clients are not tied to iOS.
GlucoseReporter uses legitimate follower authentication and reads telemetry already made available to an authorized caregiver account.
It does not control the Twiist pump, deliver insulin, change settings, or replace the official Twiist treatment interface.
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.
GlucoseReporter is intentionally separated from treatment control. Its job is to report data, not make therapy decisions or send commands.
The first production milestone was declared after a real reboot test: the collector, display adapter, and Cloudflare tunnel all returned automatically without manual intervention.
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.
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.
Version 1.0 • Self-hosted • Read-only