Press enter or click to view image in full size
tl;dr
I got myself a Roche Accu-Chek SmartGuide continuous glucose monitor because of the fuss about blood sugar variations being the culprit behind several common conditions. The first one stopped working before it could warm up. The replacement was dead in two days. I got a refund, but I was disappointed that a $100 device could fail so often and without any kind of diagnostics about its own health. Being a software engineer and data scientist and knowing a thing or two about embedded devices, I turned to Codex and OpenAI Astra to look for clues.
Some Soul Searching, Some Dumpster Diving
After I wrote to Roche for a refund, I had binned the sensor. A day later, the software engineer-turned data scientist beckoned: “We should not just bury a problem like that. We have never done that!” I had known that the sensor still had 2 weeks of lifetime left. So I dove back into the bins to find the sensor and its applicator bearing the Bluetooth PIN.
Salvaging Some Bits
I hadn’t hoped to root into a proprietary sensor and read raw data, but I hoped to salvage some diagnostics, which, I thought, might not have been shown in their app. Since Astra has been in the news for being able to cobble up some software on-the-fly, I asked it this:
I have a bricked continuous glucose monitor made by Roche. It’s lying near this laptop. It identifies itself as AC-1R00075XXXX. Can you establish a Bluetooth connection and retrieve whatever data it is sending?
Within a few minutes, Codex strung together some Python code to scan Bluetooth devices. The code paired with the sensor and dumped the data still sitting on the sensor. It pulled a day’s worth of glucose readings, information about the mode the sensor was operating in, and a status bit indicating abnormal operation.
Press enter or click to view image in full size
Discovering Scraps
As it turned out, there was no diagnostics information in the dump. It wasn’t unexpected since the Bluetooth connection relays information to users and doesn’t provide debugging information. Or does it? I don’t know yet, but given these devices are used in therapeutic settings as well, and conform to strict regulations, I didn’t expect retrieving diagnostics to be a cakewalk.
All I can is that if I built such a system, I’d include some telemetry. Had the sensing element failed? Was there a calibration problem? Had the software decided that the measurements were no longer trustworthy?
If you have read so far, and you are also someone who does not go to sleep without finding the root cause, read on and hit me up if you would like to team up.
The Tidbits
We used Python and Bleak, a library for communicating with Bluetooth Low Energy devices. On my Mac, it used Apple’s CoreBluetooth interface.
The sensor appeared in the scan and accepted a connection. It exposed three services:
- Device Information
- Continuous Glucose Monitoring
- Reconnection Configuration.
The device information returned Roche Diabetes Care GmbH, model `303`, and firmware `FW_V7.5.1–9205bbad`. The radio and enough of the firmware to answer these requests were clearly still functioning.
The sensor implements the standard Bluetooth Continuous Glucose Monitoring service. Among its characteristics is a Record Access Control Point, which lets a client request stored measurements.
We issued two requests: count all records, then report all records. The sensor reported 96, delivered 96, and returned a successful completion response. The Bluetooth CGM service specification describes this retrieval procedure.
The records contain:
- 34 numeric glucose values
- 29 `NaN` values, indicating that no numeric measurement was available.
- 33 `−Infinity` values, accompanied by a warning that the result was below the range the device could process.
All 96 record checksums passed. That gives us confidence in the integrity of the retrieved packets; it does not validate the underlying glucose measurements.
Reading the Fault Flags
The sensor advertized a particular service characteristic that corresponds to CGM Status. We read it, and it was only three bytes:
09 00 00
In its first byte, `0x09` has bits 0 and 3 set: session stopped and sensor malfunction. That is a useful confirmation, but it is still a broad diagnosis. There is no accompanying explanation such as a broken filament or a particular failed internal check.
We also decoded the other flags. None of the retained records or the fresh status read reported low battery, excessive temperature, insufficient temperature, or a general device fault. The sensor’s feature information says it supports detecting those conditions. The field definitions are in the Bluetooth GATT Specification Supplement.
The Calibration Issue
All 96 records were tagged “calibration required”. In 63, “calibration not allowed” is also set.
Roche documents the calibration-required flag as indicating Trend Mode, which was expected since these sensors require calibration against a prick-based monitor and I had not done any calibration. In Trend Mode, the reported readings could deviate from true readings by up to 10%.
What Might Have Happened?
The strongest conclusion from the capture is that the sensor repeatedly failed to produce a usable measurement, often while reporting a result below its processable range.
Several physical or software explanations could fit parts of that pattern. Pressure on a worn sensor can produce falsely depressed CGM readings, as observed in a study of sleep position and sensor performance. However, that study involved other sensors and does not demonstrate what happened to this Roche unit.
Sensor displacement, damage to the sensing element, or a problem in measurement processing are also possibilities. We have no raw electrode signal or independent glucose reference in this capture with which to distinguish them.
The discovered Bluetooth services exposed no detailed fault log, raw electrode-current stream, battery-voltage history, or crash dump. A manufacturer-specific diagnostic procedure may exist, but we did not discover one. We also did not try undocumented commands, reset the sensor, change its calibration, or restart the session.
An Invitation to Investigate
I now have the raw Bluetooth captures, decoded records, a plot, and the Python scripts used to retrieve and inspect them. The next useful step is to have more informed eyes on the evidence.
I’d particularly like to hear from people who can help with:
- Roche CGM behavior: What conditions produce the combination of malfunction, below-range results, and calibration-not-allowed flags? Is there a documented distinction between a transient measurement fault and a stopped session?
- Sensor engineering: What additional observation would help distinguish pressure or displacement from a defective sensing element
- Bluetooth and firmware: Is there a documented diagnostic interface we missed? Are there details in the standard fields that deserve a different interpretation?
- Comparable cases: Has anyone captured the same model and firmware while it was working normally, or around a similar failure?
- Hardware Debug Interface: If all else fails, prying open the sensor and trying to find any debugging pads on the circuit board or the chips can be a final resort. The small size of the package would make it a challenge still to solder on any debugging leads.
If you have relevant experience, or work on similar devices, please leave a comment. I’d like to compare the captures and turn the hypotheses into questions we can actually test.