Dexcom on Android: AAPS uploader
Connect an already working AAPS uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Nightscout Pro help
Connect your data, then add the apps and displays that will follow it. Your guide puts the steps in order.
Already connected but something has stopped working? Start with troubleshooting.
Your combined setup guide
0 follower choices · 0 related tasks. Complete the connection and check fresh data before adding followers.
Trio has separate general-upload and Upload Glucose controls. Verify glucose, treatments and profile/status separately.
These steps connect an already-working app to Pro. They do not establish that every sensor or pump works directly with that app.
Open full article: Connect Trio to Nightscout Pro
Send data from your already configured Trio app on iPhone to your Nightscout Pro site, then view it in Nightscout or a follower app. Nightscout Pro hosts the site for you; you do not need to create a server or database.
These steps cover the Trio 1.0.x screens, checked against version 1.0.1. Older builds may group the connection and upload controls on one screen. This guide connects your data; it does not set up insulin delivery or change your therapy settings.
https://your-site.nightscoutpro.com; remove any path, ?token=... or other query text.Use your site's API Secret, not your Pro sign-in password or a follower's read-only token. Keep the address and secret in separate fields. Do not add /api/v1/, an @ secret prefix or a token to Trio's URL. See API Secret and access tokens if you need help finding it.
If your older build shows the URL and secret directly on the Nightscout screen, enter them there and use its connection check. A successful connection is the first check; confirm actual uploads in the next steps.
Open Nightscout → Upload in Trio:
If a deliberately retained uploader already supplies glucose, keep a single glucose path and verify it separately; Trio can still supply its other data. Do not add Pro Connect just to make Trio upload.
Fetch is the opposite direction: it brings selected Nightscout data into Trio. Backfill Glucose also reads from Nightscout into Trio. Neither is needed to send Trio's readings to your site. Leave fetching, remote control, CGM and therapy settings unchanged for this connection task.
In your Pro account, open this site's Site Settings. Trio uses Nightscout's openaps display plugin; the label does not need to say Trio.
| In Site Settings | What to select | Name used in self-hosted instructions |
|---|---|---|
| Plugins → ENABLED | Tick openaps | ENABLE |
| Plugins → SHOW_PLUGINS | Tick openaps | SHOW_PLUGINS |
| Forecast | Select openaps if you want the uploaded predictions displayed | SHOW_FORECAST |
Save using Update / restart Nightscout or Update Nightscout, then allow the site to restart and refresh it. Preserve your other required plugins. These controls affect the website's display; they do not configure Trio's dosing algorithm.
If you have moved from Loop to Trio, replace the loop selection with openaps in these three places. Once Trio is your intended uploader, remove the old site's Nightscout connection from the previous Loop app so it cannot keep overwriting Trio's profile/status. Follow the Trio migration guidance for the wider app migration.
The quickstart's Check my readings checks glucose only. Mark the full guide complete after verifying the other data you need. A site receiving treatments is still in use even when it receives no glucose; that is different from having a current glucose reading.
Use the Trio quickstart builder to add LoopFollow, a display or other follower steps to this guide. Give viewers the access described in their own guide; do not share the uploader's API Secret unnecessarily.
Remote commands are a separate setup. Follow Trio's remote-control documentation for your installed versions rather than applying Loop's remote-command instructions to Trio.
https://, the hostname and the absence of extra URL text. Keep the exact connection error.If these checks do not resolve it, contact support with your Trio and iOS versions, your source app/sensor, which data types arrive, the last successful time, the exact redacted error and the checks already completed. Never send your API Secret, tokens or an unredacted settings screenshot.
Nightscout is a supplementary viewing and sharing tool, not a medical device or a replacement for your primary glucose monitor, care plan or healthcare advice. Readings and alerts can be delayed or unavailable; see Nightscout's purpose and limitations.
Trio Nightscout documentation · Trio CGM requirements · Trio 1.0.1 connection screen · Trio 1.0.1 upload controls.
Instructions reviewed against those sources and the live Pro settings on 27 September 2026. Sensor compatibility remains specific to your installed Trio version and source; see Trio's CGM requirements before changing an existing setup.
Check the failing layer: current data in the source, then Nightscout, then the follower. Keep the exact error, app version and last successful reading time. Use the troubleshooting guide or contact support with this guide link and details already available. Do not send passwords, API Secrets, access tokens or authorization codes.
A follower display and its alerts can lag or stop. Check the source and your usual care plan before acting on an unexpected value.
Connect an already working AAPS uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Use Pro Connect with a working Dexcom Share account. Model and regional Share availability determine this route.
Modified Dexcom app setup is outside this guide’s support scope. Use the documented Dexcom Share route when it works, or an established xDrip+/AAPS upload path.
Alternative setup neededConnect an already working xDrip+ uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Connect an already working AAPS uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Connect an already working xDrip+ uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Import Libre 1 readings already present in a linked LibreLinkUp account. Scanning-based sources update after scans/uploads; this does not promise continuous automatic sensor collection.
Connect an already working AAPS uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Connect an already working xDrip+ uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Use a LibreLinkUp follower account that already displays this person’s readings; scanning and regional app capabilities determine which readings exist.
Use a LibreLinkUp follower account that already displays this person’s readings; scanning and regional app capabilities determine which readings exist.
Upload existing fresh xDrip+ readings only. For a new Medtronic connection, use native Pro Connect CareLink; this route does not establish legacy pump compatibility.
Connect an already working Loop uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Connect an already working iAPS uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Use Pro Connect with a working Dexcom Share account. Model and regional Share availability determine this route.
Connect an already working Loop uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Connect an already working iAPS uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Connect an already working xDrip4iOS uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Connect an already working Shuggah uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Import Libre 1 readings already present in a linked LibreLinkUp account. Scanning-based sources update after scans/uploads; this does not promise continuous automatic sensor collection.
Connect an already working Loop uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Connect an already working iAPS uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Connect an already working xDrip4iOS uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Connect an already working Shuggah uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.
Use a LibreLinkUp follower account that already displays this person’s readings; scanning and regional app capabilities determine which readings exist.
Use a LibreLinkUp follower account that already displays this person’s readings; scanning and regional app capabilities determine which readings exist.
No maintained Guardian Monitor setup is verified here. Use the current Pro Connect CareLink workflow for eligible accounts with fresh source data.
Alternative setup neededConnect an already working Trio app, enable glucose and other uploads, and display Trio data in Nightscout Pro.
Glucose through a working Dexcom Share account; model and region limits apply.
Glucose from a linked LibreLinkUp follower; no insulin, carbohydrate or profile import.
Connect a dedicated Care Partner account; fresh source data and exact device eligibility are required.
Tandem Source glucose and available pump data; treatment timing differs from glucose timing.
Available Glooko glucose and treatments; allow up to an hour and do not assume profile import.
Native Insiight follower connection with bounded data coverage; optional Tidepool enrichment.
Import data that is actually available in the selected Tidepool account.
Testing connection: verify actual glucose and treatment coverage before depending on it.
Testing — check limitationsImport glucose using a linked EasyFollow follower account, rather than your Medtrum patient login.
Distinguish the Android phone path from experimental adapters unavailable in the Pro Connect menu.
Testing — check limitationsCheck exact device, region, app and data type; use the Eversense NOW guide for its follower route, and check other unlisted sources with support.
Alternative setup neededSend readings already present in xDrip4iOS to Nightscout; sensor support remains app-specific.
Connect the Nightscout service in a working Shuggah installation; do not upload to a site followed by the same app.
Check whether your site has a current glucose reading, then confirm the rest of your guide separately.
Sign in to your Pro account to check your own site. This check does not change your connection.
Sign in to Nightscout Pro, then return here and check again.
We record the reading check and your confirmation separately. The report does not save glucose values, your site name or your account details.