Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed remote carb/bolus #2171

Open
isumavut opened this issue Jun 3, 2024 · 3 comments
Open

Failed remote carb/bolus #2171

isumavut opened this issue Jun 3, 2024 · 3 comments

Comments

@isumavut
Copy link

isumavut commented Jun 3, 2024

When entering remote carb and bolus entries via loop caregiver the entries did not show up in NS, loop follow or loop caregiver. They did show up as remote carb/bolus entries on loop phone as notifications only. No entries in loop for carb or bolus insulin. Did not see the usual failed OTP message on the loop phone.

Loop Report 2024-06-03 14_54_29-07_00.md

Screenshot 2024-06-03 at 1 43 21 AM
Screenshot 2024-06-03 at 1 43 52 AM

Phone

  • Hardware: LCG iphone 14, Loop iphone 11
  • iOS Version: LCG 17.5.1 Loop 17.4.1

Loop Version

  • Version Number: 3.2.3

CGM

  • Device: Dexcom G6
  • Manager app: Dexcom

Pump

  • Manufacturer: Omnipod
  • Model: DASH

Updated the parent phone to the latest iOS 17.5.1 the day before.

@isumavut
Copy link
Author

isumavut commented Jun 4, 2024

@marionbarker
Copy link
Contributor

Summary:

The remote commands did not go through - that happens sometimes.

Instead of repeating remote commands quickly:

  • If the first one does not show up on Nightscout, wait at least 5 minutes before trying again
  • Always send Bolus first.
    • Follow up with Carb entry later to prevent the app staying at 0 U/hr. (One cycle won't make much difference.)

Analysis:

Time zone is -7 hours wrt UTC.
So an event at 1:40 am (1:43 on phone at 3 minutes ago) yesterday is 08:40 UTC June 3, 2024.
Before that, I see a number of entries in the notification about remote entries:

List in chronological order (apprx UTC, time ago, what) from phone time of 1:43 pm):

  • 2024-06-03T08:33, 10 m ago, Remote Carb Entry: 10 g x 6 hours
  • 2024-06-03T08:35, 8 m ago, Remote Bolus: 0.3 U
  • 2024-06-03T08:36, 7 m ago, Remote Carb Entry: 15 g x 6 hours
  • 2024-06-03T08:37, 6 m ago, Remote Bolus: 0.4 U
  • 2024-06-03T08:40, 3 m ago, Remote Bolus: 0.3 U (Mom)
  • 2024-06-03T08:40, 3 m ago, bolus in progress

Before I go any farther - please always send the remote bolus FIRST and then follow up with the remote carbs to go with it.

All I can tell you is that none of these were enacted. (Which you already knew).

I examined the critical logs:

  • (from carbs.json): None of those remote carbs were accepted by Loop.
  • (from doses.json): The only dosing entries during this time were automatic and they match the amounts reported in the event history for bolus (the temp basal entries at top level show the rates, not the delivered dose, which for these cases as 0 U.)

@isumavut
Copy link
Author

isumavut commented Jun 9, 2024

Thank you, appreciate your time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants