Skip to content
Help
← Choose another setupOpen full help article

Your setup guide

Trio on iPhone: connect to Nightscout

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

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

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:

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

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.

Copy link to this guide

Still stuck? Contact support with this guide and the exact error. Keep passwords and tokens out of your message.

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.