Accurate insulin dose calculations are the backbone of effective diabetes management, especially for users of the Loop app. Loop is an open-source, do-it-yourself automated insulin delivery system that leverages an algorithm to recommend insulin doses based on continuous glucose monitor (CGM) data, carbohydrate intake, and user-configured settings. When these calculations go wrong, the consequences can range from frustrating hyperglycemia to dangerous hypoglycemia. This guide provides a systematic, in-depth approach to diagnosing and resolving insulin dose calculation problems in the Loop app, helping you regain confidence in your therapy and maintain tight control.

Common Causes of Calculation Errors

Understanding why a calculation error occurs is the first step toward a fix. Errors typically fall into one of four categories: data input mistakes, software issues, configuration problems, or connectivity failures. Below, each cause is examined in detail.

Incorrect Input Data

The most frequent source of dose miscalculation is inaccurate data entry. Loop relies on two primary inputs from the user: carbohydrate count and current blood glucose level. Even a small error in carb counting (e.g., estimating 30 grams instead of the true 45 grams) can lead to an incorrect bolus recommendation. Similarly, if you manually enter a fingerstick glucose value that differs from your CGM reading, the algorithm may base its recommendation on flawed data.

To minimize this risk, always weigh or measure carbohydrate sources when possible, use up-to-date nutrition labels, and verify that your blood glucose meter or CGM is calibrated correctly. Entering data in a hurry or while distracted is a common pitfall—take a moment to double-check every number before confirming.

Outdated App Version or Software Bugs

Loop is a rapidly evolving community-driven project. Older versions may contain bugs that affect dose calculations—for example, miscalculations in insulin on board (IOB) or incorrect treatment of temp basals. The LoopDocs site maintains a changelog and known issues list. If you are running a build that is several months old, chances are a fix has already been released for the problem you are encountering.

Additionally, the underlying iOS or watchOS operating system updates can occasionally break compatibility. Always ensure both your Loop app and your device’s operating system are up to date. Avoid using beta versions of iOS unless you are prepared to troubleshoot potential issues.

Misconfigured Settings

Loop’s algorithm is only as good as the settings you feed it. Key parameters include insulin sensitivity factor (ISF), carbohydrate ratio (CR), basal rates, and target blood glucose range. If any of these are off—even slightly—the recommended doses will be systematically incorrect. For instance, an ISF that is too aggressive (i.e., too many mg/dL per unit) can result in overdosing and hypoglycemia, while a too-conservative ISF leads to underdosing and persistent hyperglycemia.

It is critical to review and validate these settings periodically, especially after changes in weight, activity level, illness, or hormonal cycles. Many users find it helpful to run a “settings audit” using tools like the Tidepool platform to compare predicted glucose curves against actual CGM data.

Connectivity Issues Affecting Synchronization

Loop relies on Bluetooth communication between your iPhone, CGM receiver (or the Dexcom G6/G7 directly), and the insulin pump. Interference, distance, or low battery levels can cause intermittent drops in data. When the app loses the most recent CGM reading or pump status, it may fall back to stale data or stop delivering corrections altogether. The most visible symptom is a “No Data” warning or a dose recommendation that seems out of touch with your current glucose level.

Physical obstructions, such as carrying the phone in a different pocket or leaving it in another room, can also degrade the signal. Restarting the devices and ensuring they are within a few feet of one another usually resolves the issue.

Step-by-Step Troubleshooting Methodology

Follow these steps in order. Each builds upon the previous one, so skipping ahead may waste time chasing symptoms rather than root causes.

Step 1: Verify Input Data Thoroughly

Before touching any settings or restarting anything, examine the data you have entered. In the Loop app, navigate to the bolus screen and review the carb entry and glucose value. Questions to ask yourself:

  • Did I accidentally type 45 grams instead of 15?
  • Is my CGM value from 20 minutes ago still being used because I didn’t allow the app to update?
  • Did I enter a snack that I actually didn’t eat?

If you suspect an entry error, cancel the bolus, correct the data, and recalculate. For blood glucose readings, cross-check with a fingerstick meter to confirm accuracy. If your CGM reading is significantly different from a fingerstick (more than 20%), recalibrate the CGM per manufacturer instructions before proceeding.

Pro tip: Use the “Logbook” feature in Loop to review past calculation attempts. You may spot a pattern—for example, errors always occurring after high-fat meals (which delay carbohydrate absorption) or after exercise sessions.

Step 2: Update the App and Check for Known Issues

Open the Loop app’s “About” screen (found in settings) to see your build version. Compare it against the latest release listed on the Loop GitHub releases page. If you are more than one major release behind, updating is the most effective fix for calculation bugs.

Before updating, back up your settings and data—either via the app’s export function or by noting down critical numbers. Installation instructions vary depending on whether you build the app yourself (via Xcode) or use a third-party signing service. If you are not comfortable building the app, consider joining a community like the Looped Facebook group for step-by-step guides.

After updating, test the dose calculation by entering a test scenario (e.g., 30g carbs with a glucose of 120 mg/dL) and verify the recommended bolus matches what you would expect based on your ISF and CR. Discrepancies may indicate a configuration reset during the update.

Step 3: Review and Validate All Settings

Incorrect settings are the most common chronic cause of calculation errors. Access the settings menu (gear icon) and systematically review each parameter:

  • Insulin Sensitivity Factor (ISF): How many mg/dL does one unit of insulin lower your blood glucose? Use the “1500 rule” (for rapid-acting insulin) as a starting point, then refine based on actual glucose outcomes. If your doses consistently overshoot or undershoot, adjust by 10% and re-evaluate.
  • Carb Ratio (CR): Grams of carbohydrate covered by one unit. A ratio that is too low (e.g., 8:1 when you need 12:1) will cause overdosing at meals. Conversely, a too-high ratio leads to underdosing. Review post-meal glucose patterns over several days to spot trends.
  • Basal Rates: The foundation of any Loop setup. Run a 24-hour fasting test (no boluses) and compare actual glucose changes against expected flat line. Adjust each half-hour segment by 0.05–0.1 U/h as needed.
  • Target Blood Glucose Range: Typically 80–120 mg/dL for most users. If your target is too tight, you may experience frequent, aggressive corrections that lead to rebound hypoglycemia. Loosen the range by 10 mg/dL on each side and observe.

Record your settings before making any changes, and only adjust one parameter at a time. Wait at least three days before judging the impact, as insulin adjustments require time to stabilize.

Using the “Override” Feature for Troubleshooting

Loop allows temporary overrides to ISF, CR, and targets (e.g., for exercise or illness). If you have an active override, it will skew your recommended doses. Check the status at the top of the app screen—if an override is in effect, the dose calculation may appear incorrect. Disabling the override will return to your default settings.

Step 4: Test Connectivity Between Devices

Even if your settings and data are perfect, a weak Bluetooth connection can cause the app to use outdated information. Perform the following connectivity checks:

  1. Restart your iPhone: This clears temporary Bluetooth cache issues. Do the same for your pump (if possible) and your CGM transmitter.
  2. Check proximity: Keep your iPhone within 6 feet of the pump and CGM receiver during critical times (meals, corrections). Wall materials and metal furniture can attenuate the signal.
  3. Verify CGM readings: In the Loop app, the CGM graph should update at least every 5 minutes. If you see gaps longer than 10 minutes, the connection is likely weak. Move the phone closer and ensure the transmitter battery is not low.
  4. Re-pair devices: As a last resort, unpair the pump from the Loop app (Settings > Pump) and re-pair it fresh. This often resolves stubborn sync issues.

Note: If you use multiple iOS devices (e.g., an iPad as a secondary controller), ensure only one is actively communicating with the pump to prevent data conflicts.

Additional Tips for Long-Term Accuracy

Troubleshooting is not a one-time event—it is an ongoing practice. Incorporate these habits into your daily routine to minimise future calculation errors.

Consult Your Healthcare Provider

No algorithm replaces clinical judgment. Your endocrinologist or certified diabetes educator (CDE) can help you validate settings through periodic review of your CGM and pump downloads. Bring a report from Tidepool or other data aggregator to appointments. Many clinics now offer telemedicine specifically for closed-loop users, so ask if your provider has experience with Loop.

Engage with the User Community

The Loop community is one of the most active and generous in diabetes technology. The Looped Facebook group has thousands of members who share troubleshooting tips, customizations, and real-world experiences. Searching past posts or asking a question can save hours of trial and error. Additionally, the Diabetes Discord offers real-time chat channels for urgent issues.

Document Your Findings

Keep a simple log (paper or digital) of every calculation error: date, time, input values, recommended dose, and what you actually delivered along with the outcome. Over weeks, patterns become visible that would otherwise go unnoticed. For example, you may discover that errors consistently occur after 10 PM, pointing to a basal rate issue during the night.

Regularly Review Community Updates

Loop development is active, with new features and bug fixes released every few months. Subscribe to the LoopDocs newsletter or follow the GitHub repository to stay informed. Setting aside an hour each month to update the app and review your settings can prevent many issues before they start.

Conclusion

Insulin dose calculation errors in the Loop app are usually solvable through a methodical approach: verify your inputs, update the app, validate your settings, and ensure robust connectivity. By treating each problem as a learning opportunity and leveraging the resources of the Loop community and your healthcare team, you can achieve consistent, safe, and effective automated insulin delivery. Remember, the goal is not just to fix a single error but to build a system that you trust day after day. With the steps outlined in this guide, you are well-equipped to troubleshoot with confidence and return to what matters most—living well with diabetes.