Skip to content

Transition from other closed-loop solutions

If you've been using other closed-loop solutions, it's essential to understand the differences between the one you're used to and Trio.

In this section of the documentation, we'll explain the differences from a user perspective.

Coming From AndroidAPS

AndroidAPS and Trio are based on the same algorithm (Oref) and base system (Artificial Pancreas System, APS). While there are several differences between AndroidAPS and Trio, the main algorithm is the same, meaning you can expect Trio to behave the same way AndroidAPS does generally.

Benefits of AndroidAPS
  • Custom automation
  • Detailed reporting
  • Working remote bolus (for caregivers, not working at the moment in Trio)
  • A built-in learning program
Benefits of Trio
  • Trio works on your iPhone and Apple Watch
  • Trio has dynamic CR support
Should I switch from AndroidAPS to Trio?
  • If you have been successful with AndroidAPS but prefer the Apple ecosystem, you can easily transition to Trio.
  • If you've struggled to get stable BG with AndroidAPS, you may have the same issues with Trio.

Take some time to read the docs and fine-tune your settings.
Once your settings are in order, consider switching to Trio.

Coming From iOS Loop

iOS Loop uses different algorithms, meaning it has a different approach than Trio. If you're coming from iOS Loop, you must change how you think. Please read that statement again three times, as it is crucial.

Benefits of Loop
  • A very clean, minimalistic user interface
  • A built-in onboarding guide
  • Simple settings
  • A dedicated Loop Follow app for caregivers
Benefits of Trio
  • Unannounced meals
  • Less user interaction/correction
  • Dynamic ISF and CR
  • Highly customizable temporary profiles
  • Adaptive algorithm
Should I switch from Loop to Trio?
  • If Loop works well for you, you should not switch to Trio.
  • Switching to Trio will not resolve Loop build issues. The build process is the same for both Loop and Trio.
  • If you find it difficult to understand how Loop works, Trio is even more complex.

You should consider switching to Trio if you've been using Loop for a while and have issues that Loop can't solve even after tweaking and re-tweaking your settings and profile.

Common Reasons Users Switch from Loop and How Trio Addresses Them

Incorrect or missing carb entries

Trio has a feature called Unannounced Meals (UAM). With this option enabled and properly configured, Trio will react to rising BG by giving insulin through a Super Micro Bolus (SMB) even if no carbohydrates are registered. UAM helps in two scenarios: forgetting to add carbohydrates for a meal and entering carbohydrates but not the correct amount.

Lots of manual corrections and "fake carbs

With UAM and SMB active and properly configured, Trio will make any necessary corrections. There is no need to add "fake carbs" to make Trio give insulin, as many Loop users are used to.

Persistent highs because of variations in Insulin Sensitivity Factor (ISF) and Insulin-to-Carbohydrate Ratio (CR)

Many people with diabetes need more insulin as their BG rises. Because Loop uses constant, pre-set ISF and CR values; it cannot address the unexpected change in sensitivity. With dynamic ISF and dynamic CR enabled and properly configured, Trio will give enough insulin to lower those highs without user interaction. More aggressive settings might lead to a low. With less aggressive settings, it will take Trio some time to get BG back in range. The key is to find the effective balance between conservative and aggressive to meet your needs.

Recurring/Rebound Lows

Properly configured, Trio will not give you insulin if you don't need it. A typical issue with Loop is that it stops delivering insulin when BG falls and then gives insulin from the "negative IOB" once BG starts rising again. For some users, this is too much insulin and leads to recurring lows. Properly configured, Trio will not overcompensate for the rapid BG rise after a low.

Difficulties dealing with exercise

Exercise is good for everyone, including people with diabetes. People with insulin-dependent diabetes often struggle with lows during exercise and highs afterward. Trio has a built-in exercise mode that will reduce basal and ISF whenever you set a higher temporary BG target. Trio also has Profile Presets that can help you get the right amount of insulin during exercise. Profiles can also adjust CR, unlike temporary targets.

Frequent, consistent variations in profile (Basal, ISF, CR)

Illness, menstrual cycle, inactive days, active days, home office days, stressful events... In these situations, the overall insulin need differs from your usual need. Like Loop's Overrides, Trio has Profiles that can change basal rate, ISF, CR, and target BG within a pre-set timeframe. What Trio Profiles do that Loop Overrides do not do is provide the option to temporarily disable SMBs and apply adjustments to only basal, basal, and ISF, basal and CR, or all three.

If any of those sound familiar, consider a switch to Trio

Important

You must read extensively and adapt to a new approach to diabetes management.

What's All That Talk About Changing the Way I Think?

Loop is carb-centric. Loop users have been instructed to enter carbs, including future carbs (fat, protein), to ensure Loop gives the right amount of insulin. Some users also enter "fake carbs" to force Loop to give more insulin.

The Trio algorithm does not consider future carbs. What does this mean? The algorithm considers many factors, adds guardrails, and then acts by setting a temporary basal, administering a bolus (SMB), or both. Future carbs are not considered. The algorithm does not care about any future carbohydrates you might have entered.

Wait, what!? You have to consider carbohydrates, right? Why else would I add them? Trio considers carbohydrates only once absorbed and part of Carbohydrates On Board (COB).

Mealtime Strategy

So what's the mealtime strategy then?
  1. Use the bolus calculator before you eat. Enter carbohydrates (and fat and protein if you want). Look at the recommended bolus and tap the info button if you disagree with it.
  2. Change the recommendation if you want to, and then bolus. If the recommendation is way off, you should check your settings. Remember that the recommendation is based on your settings, including the "Recommended bolus percentage" setting.
  3. Depending on your insulin type and sensitivity, you should consider doing this some minutes before eating. You do not need to adjust the carbohydrate timestamp to the actual time you plan to eat; you can keep it when you announce the meal and pre-bolus.
  4. Enjoy your meal. In most cases, Trio will set a temporary low/zero basal.
  5. If Trio detects BG is rising faster or more than expected, it will give more insulin (SMB) depending on the settings.
  6. If Trio detects BG falling, a low/zero temporary basal will continue.
  7. If you think Trio is not giving enough or too much insulin, you should look at your settings, including MAX IOB and all SMB-related settings.
Does everyone do it like that?

No

What are the alternatives?
  • Some Trio users don't bolus for meals. They wait for Trio to detect rising BG and let Trio handle it. This usually leads to a temporary high BG, but Trio will get you back to target with the correct settings. If you're OK with a temporary high, then go ahead and try to skip bolus. You can start with small meals and tune your settings. You will need aggressive settings to let Trio give enough insulin.
  • Some Trio users do a manual pre-bolus and skip entering carbs. Trio will predict a low BG until the meal kicks in and BG begins rising. If the pre-bolus is insufficient, Trio will give more insulin based on your settings. Yes, even without entering any carbohydrates. This approach will also result in a temporary high that is shorter than the completely unattended approach.
What do most people do?

Most Trio users take a bit of all these approaches. They have an apple without entering anything into the app. Then, they pre-bolus for lunch because it is high in carbohydrates. Then, they use the calculator for dinner. This is all OK, and it comes down to the variation you accept for your BG.

Coming From iAPS

iAPS Ver 2.3.3 or Earlier

Transitioning from iAPS 2.3.3 to Trio is currently straightforward. The screens and menus will be very familiar.

Settings

Your settings will need to be entered manually, but they can all be entered one-by-one from your iAPS settings without adjustment. If you have Nightscout, you can import your Pump Settings, Basal Profile, ISF, CR, Target Glucose, and previous CGM readings from the Nightscout Menu.

Import Settings With Nightscout

  1. Connect Nightscout to your Trio app (If you've already connected your Nightscout site, skip to step 2)
    • Open the Settings Menu ⚙️ in the Trio app
    • Tap Nightscout to open the Nightscout Menu
    • Tap Connect >
    • Enter your Nightscout URL and API Secret in the spaces provided
    • Press Connect to Nightscout
  2. Verify the Glucose Units in the Trio app match the units used in Nightscout (If they do not match, the import will fail)
    • Open the Settings Menu ⚙️ in the Trio app
    • Tap Preferences to open the Preferences Menu
    • Verify the Glucose Units are correct
  3. Import settings
    • Open the Settings Menu ⚙️ in the Trio app
    • Tap Nightscout to open the Nightscout Menu
    • Tap Import settings
  4. Backfill Glucose
    • In the same Nightscout Menu, you can also backfill missing glucose readings from Nightscout

Dynamic Settings

Because Trio is a separate app, your historical data from iAPS will not transfer. It is recommended that you wait 7 days before you enable dynamic settings. In the meantime, you may notice some adjustments made by autosens.

iAPS ver 3.0 or Later

Settings

As with iAPS ver 2.3.3, your settings must be entered manually and/or transferred from Nightscout. It is also recommended that you wait 7 days before enabling dynamic settings. In the meantime, you may notice some adjustments made by autosens.

Other Differences

Trio was forked from iAPS ver 2.3.3. If you used iAPS prior to February 2024, you may recognize the main screen. As the Trio app develops, the screen and menus will diverge substantially from iAPS 2.3.3 and 3.0+. For now, the focus has been on the code behind the scenes. For a comprehensive list of all changes and updates made to create Trio, please view the PR that merged all the foundational, developmental work into the main version used today.

Coming From Commercial Closed-Loop Systems

Are you using a commercial closed-loop system like Insulet's Omnipod 5, Tandem's Control IQ, Medtronic's 780G, etc.? If you're happy, please stay; if you're not getting the desired results, take the time to read through the Coming From iOS Loop chapter to see the main issues Trio solves.

I Want to Try Trio. How Do I Proceed?

  • Read the documentation.
  • Build the app.
  • Go through all the settings and tap the setting name to get an explanation of what each setting does.

If you have any questions, feel free to reach out on Discord or Facebook. But please read the docs first.

Watch the Loop and Learn Videos on Trio (Previously Referred to as "iAPS"):