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

Auto bolus is giving a different amount than it shows in the UI #2196

Open
DavidRYL opened this issue Jul 21, 2024 · 4 comments
Open

Auto bolus is giving a different amount than it shows in the UI #2196

DavidRYL opened this issue Jul 21, 2024 · 4 comments

Comments

@DavidRYL
Copy link

Describe the bug
In the UI it shows one amount but the auto bolus keep going

Attach an Issue Report
See reports attached.

To Reproduce
Steps to reproduce the behavior:

Unknown how to reproduce
Expected behavior
Give only the amount the UI shows it will give

Screenshots
See attached.
Loop Report 2024-07-21 000507-0400.md
Export-20240721T040614Z.zip

IMG_2935

Phone

  • Ihpone 14 pro
  • OS Version: 17.4.1

Loop Version

  • Loop 3.4
  • Repo: github.com/DavidRYL/LoopFollow
    CGM
  • Device: Dexcom G7
  • Manager app: Dexcom App

Pump
Omnipod Dash

@itsmojo
Copy link
Contributor

itsmojo commented Jul 22, 2024

See latest comments on LoopKit 2195. OmniBLE PR #125 and OmniKit PR #36 might eliminate the possibility of this happening any more. But if this is not sufficient, Loop should also check bolusState to not start a bolus when one is currently in progress.

@marionbarker
Copy link
Contributor

Got another report of this today. (I'll add notes in a bit.)

The proposed fix is in OmniXXX.
@ps2: Can we get a patch added to Loop 3.4.1 to include the updated OmniXXX code?

@marionbarker
Copy link
Contributor

I got a Loop report from Facebook user Stefano Anghera who experienced this display bug.

The csv file from that report is attached.

The user reported:

"this morning the event timestamp is about at 09:24 after the manual bolus of 6 units at 09:17, it starts an automatic bolus but i stopped it after 0,75 units (the automatic bolus showed was about over 5 units)."

This is an excerpt from my email to him.

It is a display problem only. The amount indicated for the total bolus on the HUD is left over from the previous manual bolus. 

The logs are in UTC, so 9:24 your time (local) is 7:24 in the logs.

I see:

  • 2024-08-12 07:17:13: Manual Bolus of 6 U
    • subsequent messages (means pod got the request and is reporting on status): 
    • PodSent:SchBasal running; Bolus accepted, 6.00 u not yet delivered
    • PodSent:SchBasal running; Bolus accepted, 2.70 u not yet delivered
  • 2024-08-12 07:23:42 (means manual bolus completed):
    • PodSent:SchBasal running
  • 2024-08-12 07:24:45: an automatic bolus of 0.75 U was sent: 
    • See graphic of the commands from Loop phone and responses from pod.

automatic-bolus-user-cancel

I understand why you canceled the automatic bolus - I would have done the same. But the pod delivery would have stopped on its own.

csv file of pod messages from the Loop Report:

podState_Stefano_Anghera_20240812_1214_1.csv

@DavidRYL
Copy link
Author

IMG_3234

I got this again last week! I didn't catch the logs in time. I had a 200% override turned on and basal lock turned on at 200. I stopped it here as I had no idea when it would stop. From what I checked afterward, it intended to bolus me a total of 1.8.

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

3 participants