Dexcom G7, ONE+ and Stelo

Fundamental in advance

Noteworthy is the fact that the G7, ONE+ and Stelo systems, compared to the G6, do not smooth the values, neither in the app, nor in the reader. More details about this here.

Smoothing method

Read Smoothing method suggestions to use for Dexcom G7/ONE+/Stelo

1. xDrip (direct connection to G7, ONE+ or Stelo)

  • xDrip connects to the sensor itself: uninstall the Dexcom app, as only one app can connect to the sensor. To keep the Dexcom app, use xDrip Companion App instead.

  • Follow the instructions here: xDrip G7, ONE+ and Stelo. A recent xDrip release is required — see the linked page for the minimum version.

  • Select xDrip in Configuration → BG Source.

  • Adjust the xDrip settings according to the explanations on the xDrip settings page xDrip settings.

2. Build Your Own Dexcom App (G7 only)

Old app version

Dexcom BYODA is now a very old version of the app and cannot be updated. Not available for ONE+ or Stelo.

  • Build Your Own Dexcom App (BYODA) supports local broadcast to AAPS

  • This app lets you use your Dexcom G7 with any Android smartphone.

  • Uninstall the original Dexcom app

  • Install the downloaded apk

  • Enter sensor code in patched app

  • After a short time BYODA should pick up the sensor signal.

3. xDrip Companion App (G7, ONE+ and Stelo)

The official Dexcom app stays connected to the sensor. xDrip reads the glucose values from the notifications of the Dexcom app and sends them to AAPS.

Not a trusted data source

AAPS does not consider xDrip in Companion App mode a trusted BG data source: SMBs are not allowed all the time.

To read the Dexcom app notifications without xDrip, as a trusted data source, use the Notification Reader.

Read the Dexcom app notifications

  • Keep the Dexcom app installed and connected to the sensor. Its notifications must stay visible: do not silence or hide them.

  • Download and install xDrip. Use the same glucose units in xDrip as in the Dexcom app.

  • In xDrip, go to Settings > Hardware Data Source and select Companion App.

    xDrip Hardware Data Source: Companion App

  • xDrip asks for permission to read notifications. Tap OK, then select xDrip in the list and turn on Allow notification access.

    Notification access list

  • If Allow notification access is greyed out (Controlled by Restricted Setting), Android blocks it because xDrip was not installed from the Play Store:

    Notification access controlled by restricted setting

    Open the xDrip app info (long press the xDrip icon > App info), tap the three dots menu at the top right and select Allow restricted settings. Then go back to the notification access screen and allow it.

    App info: Allow restricted settings

    Notification access allowed for xDrip

  • Readings appear in xDrip when the Dexcom app shows a new value. If nothing appears, you may need to start a sensor in xDrip: this has no effect on the real sensor. Stelo gives a reading every 15 minutes in this mode.

Companion Bluetooth (G7)

When the Dexcom app is connected to a G7 sensor, xDrip can also listen to the readings the sensor sends to the Dexcom app over Bluetooth. xDrip does not pair with the sensor and you do not need to enter the sensor code: the Dexcom app stays in control.

With Companion Bluetooth, xDrip gets the exact time and trend of each reading from the sensor, instead of the time the notification appeared, and fills gaps when the phone was out of range (backfill).

  • In xDrip, go to Settings > Less common settings > Bluetooth Settings and enable Companion Bluetooth.

    xDrip Bluetooth Settings: Companion Bluetooth

  • This does not work on all phones and Android versions. Disable it if you see problems.

  • If an old Dexcom sensor is still in the phone’s Bluetooth list, xDrip might listen to the wrong one: in Android Settings > Connected devices, forget sensors you no longer use.

  • Companion Bluetooth is made for the G7. With ONE+ and Stelo, rely on notifications.

Configuration in AAPS

4. Juggluco (G7 and ONE+)

Version 9.0+ required

  • Disable the app previously connected to the sensor: Uninstall the app or use “Force Stop.” Disable “Nearby Devices” permission in app settings. Restrict the app’s battery usage.

  • Forget the sensor in Bluetooth settings: In Android settings, find the sensor in bonded devices and select “Forget.” Dexcom G7 sensor names start with DXCM.

  • Avoid interference from other sensors: Keep old Dexcom sensors out of Bluetooth range.

  • Connect the G7 sensor to Juggluco: Open Juggluco → Left menu → Photo. Scan the data matrix on the G7 sensor’s applicator. Wait up to 5 minutes for Juggluco to find the sensor.

  • Pairing requirements: Agree to pair the sensor with Juggluco. Ensure the screen isn’t locked during pairing. If pairing fails, wait 5 minutes before trying again.

  • Exception: Wear OS watches can bond without pressing an agree button.

5. Notification Reader (G7, ONE+ and Stelo)

The official Dexcom app stays connected to the sensor. AAPS reads the glucose value directly from the notification of the Dexcom app, without any other app in between.

Trusted data source

Readings from the Dexcom G7, ONE+ and Stelo apps are a trusted BG data source: SMBs can be allowed all the time.

Compared to the other methods on this page, the Notification Reader has limits:

  • No trend arrow and no backfill: readings missed while the phone was off or out of range are lost.

  • Each reading gets the time the notification appeared, not the exact time of the sensor reading.

  • Only values between 40 and 405 mg/dL (2.2 and 22.5 mmol/L) are read. “LOW” and “HIGH” are not read.

  • Stelo gives a reading every 15 minutes.

Set up the Dexcom app

  • Keep the Dexcom app installed and connected to the sensor.

  • Make sure the Dexcom app shows the current glucose value in its notification. Its notifications must stay visible: do not silence or hide them.

  • Use the same glucose units (mg/dL or mmol/L) in the Dexcom app as in AAPS. Otherwise AAPS cannot read the value.

Configuration in AAPS

  • Select Notification Reader in Configuration → BG Source and confirm the switch.

    BG Source: Notification Reader selected

  • Back on the main screen, AAPS shows Permissions Required. Next to Notification Access, tap Grant.

    Permissions Required: Notification Access

  • Android opens its notification access list (its name depends on your Android version, for example Notification read, reply & control). Select AAPS, turn on Allow notification access and confirm with Allow.

    Android asks to allow notification access for AAPS

    Android warns that AAPS could read all your notifications. AAPS only reads the notifications of supported CGM apps and ignores all others.

    Notification access allowed for AAPS

  • If Allow notification access is greyed out (Controlled by Restricted Setting), Android blocks it because AAPS was not installed from the Play Store. Open the AAPS app info (long press the AAPS icon > App info), tap the three dots menu at the top right and select Allow restricted settings. Then go back to the notification access screen and allow it.

  • Readings appear in AAPS when the Dexcom app shows a new value.

Warning

If the Dexcom app notification shows more than one glucose number, or none, AAPS skips that notification.