-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Comments
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. |
Got another report of this today. (I'll add notes in a bit.) The proposed fix is in OmniXXX. |
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:
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: |
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
Phone
Loop Version
CGM
Pump
Omnipod Dash
The text was updated successfully, but these errors were encountered: