Bolus Suggestion from Watch higher than on Loop Phone

[marionbarker]

Describe the bug Bolus Suggestion from Watch higher than on Loop Phone.

See this Facebook post for details - the post is one Looper parent reporting it happening to her son and a comment is from another Looper parent where it happened to her daughter.

I am gathering details from the second incident which was reported today. (The first incident is from March 10.)

I will come back and update this comment when I've had a change to look at the files emailed to me. If anyone else has seen this, please add a comment. Include your hardware and software configuration.

Attach an Issue Report Tap the Loop settings icon on the bottom of the screen, then tap Issue Report and attach it to this ticket. Extract today's zip from the Critical Event Log and include it as well.

Note - the unexpected bolus, entered from the watch recommendation, occurred at UTC timestamp:

• 2024-04-23 17:09:01
• No alerts were reported near that timestamp
• No unusual communications reported in the ## Device Communication Log near that timestamp

To Reproduce Steps to reproduce the behavior: Unknown

Expected behavior Watch should match Loop app for recommended bolus. The recommended bolus at 2024-04-23T17:08:48 is out of line with values before and after. This might be driven by when watch was opened to check for recommended dose (times for automated updates are at 17:07 and 17:12)

Screenshots If applicable, add screenshots to help explain your problem.

Copy configuration from Loop Report

• appNameAndVersion: Loop v3.2.3 (57)
• profileExpiration: 2025-03-10 19:53:53 +0000
• gitRevision: c6b058b
• gitBranch: N/A
• workspaceGitRevision: 81a3d9b
• workspaceGitBranch: main
• sourceRoot: /Users/sithlord/Downloads/BuildLoop/Loop-240310-1551/LoopWorkspace/Loop
• buildDateString: Sun Mar 10 18:07:50 EDT 2024
• xcodeVersion: 15E204a

Phone

• systemVersion: 17.4.1
• modelIdentifier: iPhone12,8
• batteryLevel: 0.35
• batteryState: unplugged

CGM

• Device: Dexcom G7
• Manager app: Dexcom

Pump

• Omnipod DASH

Additional context Add any other context about the problem here.

Examine Carbs.json and see that carbs were entered at:

16:10, 19 g, 1.5 hr (consume 15 min in future)
16:11, 64 g, 3 hr (consume 15 min in future)
and after the "event", extra carbs were consumed and reported:
17:18, 8 g, 1.5 hr

Note that maxBolus is 4.95 U for this individual.

Examine the DosingDecision.json before the watch recommendation was accepted:

2024-04-23T16:05, COB 1 g, Rec Dose 0.0, 
2024-04-23T16:10, carb entries processed, manualBolusRecommendation: 6.85, pod AB 1.4 U at 16:12
subsequent AB were quite reasonable: 1.35, 2.0, 1.6, 1.4, 0.75, 0.4
Temp basal set to 0 around 16:52

examine manualBolusRecommendation near time of event:

"manualBolusRecommendation":{"date":"2024-04-23T16:57:01.790Z","recommendation":{"amount":0.25,"notice":{"currentGlucoseBelowTarget"; glucose 100
"manualBolusRecommendation":{"date":"2024-04-23T17:02:04.502Z","recommendation":{"amount":0.15,"notice":{"currentGlucoseBelowTarget";  glucose 99
"manualBolusRecommendation":{"date":"2024-04-23T17:07:11.421Z","recommendation":{"amount":0.4,"pendingInsulin":0}}; glucose 124
"manualBolusRecommendation":{"date":"2024-04-23T17:08:48.822Z","recommendation":{"amount":5.15,"pendingInsulin":0}},"manualBolusRequested":4.95; glucose 124
"manualBolusRecommendation":{"date":"2024-04-23T17:12:03.380Z","recommendation":{"amount":0,"notice":{"glucoseBelowSuspendThreshold"; glucose 131

Today's zip with the json files I examined above.

20240423T211826Z.zip

Loop Report 2024-04-23 18_34_19-04_00.md