Skip to content
Help

Nightscout Pro help

Build your setup guide

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.

1 Your data source

Choose the phone that collects the data. Follower phones can be different. This checks our documented upload routes; your sensor, pump and app must already work together.

2 Choose the connection that sends data

Using Trio on iPhone? Open the Trio connection guide, or select Trio below to add follower apps to your guide.

Use one primary upload path to this Nightscout site. If Loop, Trio or AAPS already receives your glucose, choose that app. Its CGM source is a prerequisite; you do not need to turn on a second Nightscout uploader.

Connect an already working Trio app, enable glucose and other uploads, and display Trio data in Nightscout Pro.

Check device, app and data coverage

3 Add follower apps or displays (optional)

These read your Nightscout site. Set them up on the intended follower devices; changing a collecting app to follower mode can stop its direct sensor collection. Viewing access does not enable insulin commands.

4 Add related tasks (optional)

Already using Loop? Its remote-command prerequisites are separate from viewing and reporting.

Start again

You can share this guide without sharing your site address, credentials or health data. Do not put any of those into a guide link.

Your combined setup guide

Trio on iPhone: connect to Nightscout

0 follower choices · 0 related tasks. Complete the connection and check fresh data before adding followers.

Copy link to this complete guideEdit choices

Before you start

  1. Have an active Nightscout Pro site. If you still need to create one, follow the account and site setup guide.
  2. Confirm your source app or cloud account already has current readings. Check its supported sensor, app version, region and data types in the connection guide below.
  3. Open your Pro account and copy the complete HTTPS site address from Site Settings. Keep upload credentials private. Follower apps should receive only the separate viewing access they need.
  4. Keep one primary upload path to this site. Use your usual diabetes care process while testing; a missing or delayed website reading is not a treatment instruction.

Connect your data

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.

Connect Trio to Nightscout Pro

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.

Before you start

  • Trio should already show current glucose from its supported CGM source. Keep that working source in place.
  • Your Nightscout Pro site must be running and accessible. Open it from My account first.
  • Choose which app sends glucose to this site. For this guide, Trio is that uploader. If another uploader already sends glucose, decide which one to retain before enabling a second path.
  • For Trio 0.5.x and later, the upstream display guidance requires Nightscout 15.0.2 or newer. Find your site's version in its menu under About; contact support if it is older.

1. Get your site address and API Secret

  1. Sign in to Nightscout Pro and open the correct site. Copy its full HTTPS address, including its regional hostname if present. Keep only the origin, such as https://your-site.nightscoutpro.com; remove any path, ?token=... or other query text.
  2. Return to your account and open Site Settings for that same site.
  3. Find API Secret (Min. 12 Characters) and copy the existing value privately.

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.

2. Connect Trio

  1. On the Trio iPhone, open Settings → Services → Nightscout → Connect.
  2. Enter your site's HTTPS address in URL and its secret in API secret.
  3. Tap Connect to Nightscout and check for Connected!.
  4. Return to the Nightscout screen in Trio.

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.

3. Enable the data you want to upload

Open Nightscout → Upload in Trio:

  • Turn on Allow Uploading to Nightscout for Trio's data uploads.
  • Turn on Upload Glucose if Trio is the chosen glucose uploader for this site. This is a separate switch: check it even when treatments are already arriving.

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.

4. Display Trio data in Nightscout Pro

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 SettingsWhat to selectName used in self-hosted instructions
Plugins → ENABLEDTick openapsENABLE
Plugins → SHOW_PLUGINSTick openapsSHOW_PLUGINS
ForecastSelect openaps if you want the uploaded predictions displayedSHOW_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.

5. Check glucose, treatments and status separately

  1. Compare the latest glucose value, units and reading time in Trio with your Nightscout site. Wait for the next normal reading and confirm that the Nightscout time advances.
  2. Check a recent treatment already recorded during normal use, such as a carb entry, against Nightscout. Do not create a bolus, carb entry or temporary target just to test the connection.
  3. Check that Trio's uploaded status/profile information is present and current. An advancing glucose graph alone does not confirm this.

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.

6. Add a follower when uploads work

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.

If something is missing

  • Invalid URL or cannot connect: open the same site in the iPhone browser, check that it is running, and verify https://, the hostname and the absence of extra URL text. Keep the exact connection error.
  • Unauthorized / 401 / 403: recheck the API Secret for this specific site and remove accidental spaces. A working browser session does not prove Trio has the right credential. Do not repeatedly reset passwords or turn off site privacy.
  • Treatments arrive but glucose does not: check current glucose in Trio, then the separate Upload Glucose switch and your chosen glucose upload path.
  • Glucose arrives but Trio status or treatments are missing: check Allow Uploading to Nightscout, compare an existing record's time, and review the openaps display selections. Check for another app still writing its profile/status to the site.
  • Trio's profile is missing after moving from Loop: after stopping the old uploader, toggle Allow Uploading to Nightscout off and on once to request a fresh profile upload. Recheck the profile; repeated toggling is not a substitute for diagnosing an error.
  • Nightscout is current but a follower is stale: use that follower's connection and access guide. Changing Trio's sensor setup will not fix follower credentials.

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.

References and version scope

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.

Verify the data before following it

  1. Compare the newest glucose value, its timestamp and units with the source. Wait for the next normal source update and confirm that Nightscout advances.
  2. If you need treatments or profiles, inspect those records separately. A working glucose graph does not prove those data types are available.
  3. If data is missing here, use the failure checks in the connection guide. Adding a follower or enabling another uploader will not fix missing source data.

If something fails

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.

Browse all 41 individual connection guides

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.

Dexcom on Android: BYODA and Nightscout

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 needed

Libre 1 on Android: LibreLinkUp

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.

Libre 2 on Android: LibreLinkUp

Use a LibreLinkUp follower account that already displays this person’s readings; scanning and regional app capabilities determine which readings exist.

Libre 3 on Android: LibreLinkUp

Use a LibreLinkUp follower account that already displays this person’s readings; scanning and regional app capabilities determine which readings exist.

Medtronic on Android: xDrip+ uploader

Upload existing fresh xDrip+ readings only. For a new Medtronic connection, use native Pro Connect CareLink; this route does not establish legacy pump compatibility.

Dexcom on iPhone: Loop uploader

Connect an already working Loop uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.

Dexcom on iPhone: iAPS uploader

Connect an already working iAPS uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.

Libre 1 on iPhone: Loop uploader

Connect an already working Loop uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.

Libre 1 on iPhone: iAPS uploader

Connect an already working iAPS uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.

Libre 1 on iPhone: LibreLinkUp

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.

Libre 2 on iPhone: Loop uploader

Connect an already working Loop uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.

Libre 2 on iPhone: iAPS uploader

Connect an already working iAPS uploader to your Nightscout Pro site. Sensor model and region must also be supported by the app.

Libre 2 on iPhone: LibreLinkUp

Use a LibreLinkUp follower account that already displays this person’s readings; scanning and regional app capabilities determine which readings exist.

Libre 3 on iPhone: LibreLinkUp

Use a LibreLinkUp follower account that already displays this person’s readings; scanning and regional app capabilities determine which readings exist.

Twiist with Pro Connect

Native Insiight follower connection with bounded data coverage; optional Tidepool enrichment.

MyLife / CamAPS cloud testing

Testing connection: verify actual glucose and treatment coverage before depending on it.

Testing — check limitations

CamAPS companion routes

Distinguish the Android phone path from experimental adapters unavailable in the Pro Connect menu.

Testing — check limitations

Other devices and unlisted sources

Check 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 needed

xDrip4iOS upload

Send readings already present in xDrip4iOS to Nightscout; sensor support remains app-specific.

Shuggah upload

Connect the Nightscout service in a working Shuggah installation; do not upload to a site followed by the same app.

Check your setup

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.

We record the reading check and your confirmation separately. The report does not save glucose values, your site name or your account details.