> ## Documentation Index
> Fetch the complete documentation index at: https://docs.customtypeone.com/llms.txt
> Use this file to discover all available pages before exploring further.
# CGM Connection
SugarPixel connects to supported CGMs to download glucose data and display alerts.
Choose your preferred glucose units (**mg/dL** or **mmol/L**) before continuing.
* Follow the setup steps **only for the CGM you use** below.
* SugarPixel can follow **one or two CGM users**.
* If using two users, complete the CGM setup steps **separately for each user** using their own login details.
* If using only one CGM user, leave **User 2** set to **Disabled**.
After completing your CGM setup, SugarPixel will briefly display **“DOWNLOAD”** and then begin showing glucose readings.
If you see a login error or **“No Data”**, review the troubleshooting steps for your CGM and use **Clear CGM** before re-entering detail
**Japan and Singapore users:** Follow the **Gluroo setup** instructions to link SugarPixel to your Dexcom account.
### 1. Select Correct Dexcom Server
* If your Dexcom account was **created in the USA**, leave **USA Server** enabled.
* If your account was **created outside the USA**, **turn off** the USA Server toggle.
### **2. Confirm your Dexcom Username**
SugarPixel must use the **exact username** your CGM is linked to.
In the Dexcom app:
* **G6:** Settings → Account
* **G7:** Profile → Account
Use the username shown under **LOGIN**.
**Dependent accounts:**
* If the account type shows **Dependent**, you must use the *dependent username*, not the caregiver login.
* If SugarPixel is synced to the caregiver account when the Dexcom app is logged in to the dependent account, it will show **No Data**.
**Phone number usernames:**
* Enter the username exactly as shown
* Include the country code (for example: +12345678901)
* Do not include spaces, dashes, or parentheses
### **3. Verify your Login**
SugarPixel can only login if you are able to login to the Dexcom website. Before continuing, confirm your password is correct and that your login works on Dexcom’s website.
* **USA:** [https://uam1.dexcom.com](https://uam1.dexcom.com)
* **Outside the USA:** [https://uam2.dexcom.eu](https://uam2.dexcom.eu)
If you cannot log in here, SugarPixel will not be able to connect and will show "CGM Login Error". You must be able to login to the Dexcom website before continuing.
**Password resets (if needed):**
* Reset passwords directly on Dexcom’s site
* For dependent accounts, enter the **dependent username** when resetting
* Reset emails are sent to the caregiver’s email address
* Some dependent accounts may need to reset via:
* **USA:** [https://clarity.dexcom.com](https://clarity.dexcom.com)
* **Outside the USA:** [https://clarity.dexcom.eu](https://clarity.dexcom.eu)
### **4. Confirm Sharing is Enabled**
Dexcom only uploads real-time data when **Sharing** is enabled and at least **one follower** exists.
* Add a follower in the Dexcom app before continuing
* If you don’t want others to follow you, you can invite **yourself** and install the Follow app with alerts disabled
### **5. Enter Login in SugarPixel**
After entering your Dexcom details and tapping the Sync CGM button, SugarPixel will display **“DOWNLOAD”** and then begin showing glucose readings.
**If you see "CGM Login Error"**
This means your Dexcom login details are incorrect.
Causes:
1. **Wrong username** — typically entering an invalid phone number format. You must enter is exactly as shown in the Dexcom app (example: +13334445555).
2. **Wrong password** — especially using a caregiver/parent password with a **Dependent** username. The dependent account has its own password that you created when setting it up.
Re-do the Dexcom steps above carefully and only proceed when you successfully login to the Dexcom website.
**If you see "No Data" or the Hourglass Icon**
This usually means SugarPixel is reaching Dexcom successfully, but **no readings are available to download**. In almost all cases, this happens when one of the setup steps was missed.
Most common causes:
1. **Wrong username** — especially using a caregiver/parent login instead of the **Dependent** username shown in Dexcom.
2. **Sharing not active** — you must have **Sharing enabled** and at least **one follower**.
Re-do the Dexcom steps above carefully, then try again.
SugarPixel supports **Libre sensors that provide automatic, real-time glucose readings** through LibreLinkUp.
* Sensors that require **manual scans** have limited functionality and are listed at the bottom of this section.
* Sensors that are connected to a pump and unable to use the Linkup app are not supported.
### **1. Select CGM for the Libre option**
* If your Libre app shows realtime readings, select CGM.
* If you use a Libre sensor requires manual scanning, select FGM and go to the expandable instructions for Libre FGM (Flash Glucose Monitor) below before proceeding.
### **2. Set Up LibreLinkUp**
SugarPixel connects using a **LibreLinkUp follower account**, not your main Libre account.
1. In the Libre app, open **Connected Apps → LibreLinkUp**
2. Create at least **one follower** if you do not have one
* If you don’t want others following you, invite **yourself using a different email.**
3. Install the **LibreLinkUp** app and confirm you have glucose readings
Use the **LibreLinkUp login** (email + password) when configuring SugarPixel.
**Important notes**
* If your Libre and LinkUp accounts use the same email, you must create a **separate LinkUp account** with a different email
* Avoid special characters in the LinkUp password (+ , ' ")
* SugarPixel only supports Linkup accounts that follow a single person
### **3. Accept LibreLinkUp License Terms**
LibreLinkUp often requires accepting updated license terms.
Before continuing:
* Log out of the LibreLinkUp app
* Log back in
* Accept any license or terms prompt that appears
### **4. Enter Login in SugarPixel**
After entering your Linkup details and tapping the Sync CGM button, SugarPixel will display **“DOWNLOAD”** and then begin showing glucose readings.
**If you see "No Data" or the Hourglass Icon**
* Confirm SugarPixel is running the **latest software**
* Verify you entered a **LibreLinkUp login**, not your main Libre login
* Confirm LibreLinkUp shows glucose readings
* Temporarily disable other apps or services connected to LibreLinkUp
* Some third-party apps can cause account lockouts
* Creating a dedicated LinkUp account just for SugarPixel can help
Gluroo provides a **free, Nightscout-compatible URL** that SugarPixel can use to download real-time glucose data. The Gluroo app is available on **iOS and Android**.
### **1. Confirm Glucose Data Is in Gluroo**
Open the Gluroo app and confirm that glucose readings are visible.
* If readings are already displayed, you’re ready to continue.
* If not, open the **Devices** tab in Gluroo and add your CGM as a data source.
* If you upload readings manually or use another source (such as **xDrip+**), you may skip CGM setup and continue below.
### **2. Copy Gluroo Global Connect Details**
SugarPixel connects using Gluroo’s **Global Connect** information.
In the Gluroo app:
1. Open the menu and go to **Devices**
2. Select the **Other** tab
3. Tap **Copy** under **Gluroo Global Connect**
You will receive:
* A **Nightscout-compatible URL**
* An **API Secret Token**
Paste both values into the **URL** and **Token** fields in the SugarPixel app.
### **3. When Setup Is Complete**
After entering the URL and token, SugarPixel will begin downloading glucose readings automatically.
If readings do not appear:
* Confirm Gluroo is actively receiving glucose data
* Double-check that the URL and token were pasted correctly
SugarPixel can connect directly to a **Nightscout site** to download glucose data.
### **1. Confirm Your Nightscout Site Is Working**
Open your Nightscout site in a web browser and confirm that glucose readings are visible.
* Copy your **Nightscout URL** and paste it into the SugarPixel URL field
### **2. Check Whether Your Site Requires a Token**
Many Nightscout sites restrict access by default. SugarPixel can connect either:
* **Without a token** (if your site is readable by default), or
* **With a read-only access token**
**How to check:**
* Open your Nightscout site in a private/incognito browser
* If you’re prompted for an API Secret, your site is restricted
* Or check the AUTH\_DEFAULT\_ROLES config variable
* If it is not set to readable, your site is restricted
### **3. Create a Read-Only Token (If Required)**
If your site is restricted, create a token for SugarPixel:
1. Open your Nightscout site and go to **Admin Tools**
2. Confirm a role named readable exists with permission: *:*:read
1. Create it if it does not exist
3. Add a new **Subject**:
* **Name:** SugarPixel
* **Roles:** readable
4. Copy the generated **access token**
5. Paste the token into the **Token** field in the SugarPixel app
### **4. When Setup Is Complete**
After entering your Nightscout URL (and token, if required), SugarPixel will begin downloading glucose readings.
If readings do not appear:
* Confirm your site is reachable
* Double-check token permissions
* Verify Nightscout is actively receiving data
**Unofficial CGM Connections**
Libre **FGM** sensors require manually scanning the sensor with your phone. Because readings are not automatic, SugarPixel has **limited functionality** when used with FGM sensors.
After reviewing the limitations below, follow the **main Libre setup steps** above and make sure **FGM** is selected in the app.
### **Display Behavior**
* When no scanned reading is available, SugarPixel shows the **current time** with a **minute ticker** indicating it is running normally
* SugarPixel checks for new data approximately every **60–70 seconds**
* After a manual scan, SugarPixel displays the **blood glucose value and time**
* Standard SugarPixel color coding is used
* The value turns blue after your configured *No Data* time
* The display returns to **clock-only mode after 30 minutes**
* Some display options are unavailable when using FGM
### **Alerts**
SugarPixel can alert from two sources:
* A **manually scanned** glucose value that crosses your low or high thresholds
* **LibreLinkUp alerts**, even when no scanned value is available
Important notes:
* Libre app alerts must be enabled for LinkUp-based alerts to work
* Alert thresholds are set **only in the Libre app**
* SugarPixel mirrors those thresholds and allows enabling/disabling alerts and snooze timing
* **No Data alerts are not available** with Libre FGM
### **Single User Mode Only**
Libre FGM can only be used in **single-user mode** on SugarPixel.
### **Before Continuing**
* Make sure your SugarPixel firmware is **version 1.72 or newer**
* Follow the **main Libre setup instructions** and select **FGM** when prompted
For full SugarPixel functionality, a **Libre CGM with real-time readings** is recommended.
SugarPixel does **not officially support Dexcom Stelo**. However, some users have successfully used the workaround below.
Important
* These steps should be tested **before ordering SugarPixel**
* Setup relies on third-party and DIY apps
* We may not be able to provide full support for issues related to this configuration
SugarPixel cannot connect to Stelo directly because Stelo has no realtime sharing capability. You must use an app that can **read Stelo and upload data** to one of the following:
* **Nightscout**
* **Gluroo**
* **Dexcom Share** (in limited cases)
### **1. Read Stelo Using a Compatible App**
### **iPhone**
You must use **Stelo + a third-party reader app**.
**Required Apps:**
* Stelo (App Store)
* **Zukka** (App Store) *or* **xDrip4iOS** (DIY)
**Basic flow:**
1. Start the sensor in the **Stelo app**
2. Open **Zukka / xDrip4iOS**
3. Go to **Bluetooth** → select **CGM** → choose **Stelo**
4. Scan for the sensor and pair
5. Readings should appear **15–20 minutes after warmup**
6. Both apps must continue running in the background
### **Android**
You must use **xDrip+** (DIY). The Stelo app alone is not supported.
**Basic flow:**
1. Install **xDrip+** from:
[https://jamorham.github.io/#xdrip-plus](https://jamorham.github.io/#xdrip-plus)
2. Allow all permissions and unrestricted battery usage
3. Use **Auto Configure** to scan the QR code from:
[https://navid200.github.io/xDrip/docs/Dexcom/G7.html](https://navid200.github.io/xDrip/docs/Dexcom/G7.html)
4. Insert the Stelo sensor
5. Select **Dexcom G6/G7/1/1+** hardware option
6. Enter the **4-digit transmitter ID**
7. Open **System Status** and wait for pairing and warmup
### **2. Upload Data for SugarPixel**
Once readings appear in your app, you must upload them so SugarPixel can download the data.
**Nightscout or Gluroo**
* If you already use **Nightscout**, upload directly and select **Nightscout** in SugarPixel
* If not, install **Gluroo** (free) and use **Gluroo Global Connect** as a Nightscout-compatible endpoint
**xDrip+ / xDrip4iOS / Zukka:**
* Configure Nightscout upload using: [https://YourToken@YourUrl/api/v1](https://YourToken@YourUrl/api/v1)
* Enter the same URL and token in SugarPixel
SugarPixel does **not officially support CamAPS**. However, some users have successfully connected SugarPixel by using **xDrip+** to read CGM values and upload them for SugarPixel to download.
**Important**
* These steps are **Android only**
* This is a **community-provided workaround**
* Setup should be tested **before ordering SugarPixel**
* We may not be able to provide full support for issues related to this configuration
These steps are commonly used with **Dexcom**, and users have reported that they also work with **Libre sensors** when paired with CamAPS.
### **Overview of How This Works**
1. CamAPS manages the CGM sensor
2. **xDrip+** runs on the same phone and reads CGM data
3. xDrip+ uploads glucose values to:
* **Nightscout or Gluroo** (recommended), or
* **Dexcom Share** (Dexcom sensors only)
4. SugarPixel downloads data from that upload source
### **1. Install and Configure xDrip+**
Install **xDrip+** on the same Android phone running CamAPS.
* xDrip+ is an open-source app and is not available in the Play Store
* Installation requires allowing apps from unknown sources
* Follow the community instructions for using **CamAPS with xDrip+**
Once configured, confirm that **xDrip+ is displaying glucose readings** before continuing.
### **2. Configure your Upload Method**
Once xDrip+ is receiving readings, configure it to upload data so SugarPixel can download it.
### **Nightscout or Gluroo**
This method works with **Dexcom and Libre sensors**.
* If you already have a **Nightscout** site, configure xDrip+ to upload directly to it.
In xDrip+, enter the Nightscout upload address in the **Cloud Upload → Nightscout Sync → Base URL** field using this format:
[**https://YourToken@YourUrl/api/v1**](https://YourToken@YourUrl/api/v1)
* If you do not already have a Nightscout site, install the **Gluroo** app (free).
During Gluroo setup, skip CGM sync. Then:
* Open **Devices**
* Go to the **Other** tab
* Copy the **Gluroo Global Connect** URL and API Secret
* Enter the upload address into xDrip+ using the same format:
[**https://YourToken@YourUrl/api/v1**](https://YourToken@YourUrl/api/v1)
After configuring the upload in xDrip+, enter the corresponding **URL and API Secret / Token** into the SugarPixel configuration fields.
SugarPixel does **not officially support Medtronic CGMs**. However, users have successfully connected SugarPixel by syncing Medtronic data through **CareLink** and uploading it to **Nightscout or Gluroo**.
This approach has been reported to work with:
* **Guardian sensors**
* **Simplera sensors**
* **Instinct sensors**
…as long as data is available through **Medtronic CareLink**.
**Important**
* This is a **community-provided workaround**
* Setup should be tested **before ordering SugarPixel**
* We may not be able to provide full support for issues related to this configuration
### \\
**Recommended Tutorial (Start Here)**
Justin from **Diabetech** created a step-by-step video showing how to sync Medtronic CGM data to **Nightscout or Gluroo**, which SugarPixel can then use. [Subscribe to his channel](https://www.youtube.com/@diabe_tech) for more diabetes tips and tricks.
After completing his tutorial, you can skip directly to **Step 3** below.
### **1. Install an App to Read CGM Data**
### **Android (xDrip+)**
* Install **xDrip+** from: [https://jamorham.github.io/#xdrip-plus](https://jamorham.github.io/#xdrip-plus)
* xDrip+ is not in the Play Store and requires allowing apps from unknown sources
* Install xDrip+ on the **same phone** as the Medtronic app
* Configure xDrip+ using **Companion Mode** following the xDrip documentation
### **iPhone (Guardian Monitor)**
* Install **Guardian Monitor** from the App Store
* Follow the app’s setup instructions
* A subscription is required to upload glucose data
* Guardian Monitor can upload readings to **Nightscout**
### **2. Set Up Nightscout or Gluroo**
SugarPixel cannot connect directly to Medtronic or CareLink. Data must be uploaded first.
* If you already use **Nightscout**, configure xDrip+ or Guardian Monitor to upload to your Nightscout site
* If you do not have Nightscout, install the **Gluroo** app (free)
* During Gluroo setup, skip CGM sync
* Open **Devices**
* Go to the **Other** tab
* Use **Gluroo Global Connect** details for uploads from xDrip+ or Guardian Monitor
### **3. Configure SugarPixel**
* In SugarPixel’s CGM setup, select **Nightscout** or **Gluroo**
* Enter the **same URL and API Secret / Token** used for uploads
* Only complete this step **after** you confirm real-time readings are visible in:
* Your Nightscout site, or
* The Gluroo app
Once connected, SugarPixel should begin downloading glucose readings.
SugarPixel does **not officially support Eversense sensors**. However, some users have successfully connected SugarPixel by uploading Eversense data to **Nightscout or Gluroo**.
**Important**
* These steps are **Android only**
* This is a **community-provided workaround**
* Setup should be tested **before ordering SugarPixel**
* We may not be able to provide full support for issues related to this configuration
SugarPixel cannot connect directly to Eversense. Data must be uploaded first.
### **1. Install an Eversense Uploader App**
You must install an app that can read Eversense data and upload it to Nightscout.
Nightscout maintains a list of supported Eversense uploader apps. Follow their documentation to install and configure the appropriate app for your setup:
**Supported Uploaders — Nightscout Documentation**
[https://nightscout.github.io/uploader/uploaders/#eversense](https://nightscout.github.io/uploader/uploaders/#eversense)
Before continuing, confirm that the uploader app is actively **receiving glucose readings**.
### **2. Set Up Nightscout or Gluroo**
Once your uploader app is receiving data, configure it to upload glucose readings so SugarPixel can download them.
### **Option A: Nightscout**
If you already have a Nightscout site:
* Configure the uploader app to upload to your Nightscout site
* Use the Nightscout upload address in this format:
[**https://YourToken@YourUrl/api/v1**](https://YourToken@YourUrl/api/v1)
* Later, select **Nightscout** in the SugarPixel CGM setup and enter the same URL and API Secret / Token
### **Option B: Gluroo (Free)**
If you do not already have a Nightscout site:
1. Install the **Gluroo** app
2. During setup, skip syncing Gluroo directly to a CGM
3. Open **Devices**
4. Go to the **Other** tab
5. Copy the **Gluroo Global Connect** URL and API Secret
Use the Gluroo Global Connect details:
* As the upload destination in your Eversense uploader app, using the same Nightscout-style format
[**https://YourToken@YourUrl/api/v1**](https://YourToken@YourUrl/api/v1)
* And enter the **URL and API Secret / Token** into the SugarPixel CGM configuration
### **4. Configure SugarPixel**
* In SugarPixel’s CGM setup, select **Nightscout** or **Gluroo**
* Enter the **same URL and API Secret / Token** used for uploads
* Only complete this step after you confirm **real-time glucose readings** are visible in Nightscout or the Gluroo app
Once configured, SugarPixel should begin downloading glucose readings.
### **4. Enter Login in SugarPixel**
After entering your Linkup details and tapping the Sync CGM button, SugarPixel will display **“DOWNLOAD”** and then begin showing glucose readings.