LoopKit
Extreme negative glucose prediction
Describe the bug Loop is predicting an extremely negative blood glucose (-141 mmol/L). Two recent carb entries are showing an absorption value that is greater than the original carb amount. 172g absorbed of 76g entered. 16g absorbed of 9g entered.
Attach an Issue Report Attached
To Reproduce This has happened now for the first time, there have been no recent changes to the system or to treatment settings. This seems to be a spontaneous error.
- Enter carbs as usual via watch app
- Allow bolus of suggested insulin as usual via watch
- Wait for half of meal absorption time
- Highly negative glucose predicted
Expected behavior A clear and concise description of what you expected to happen.
Screenshots Screenshot added.
Phone
- Hardware: iPhone 12 mini, Apple Watch 2
- OS Version: 18.6.2, WatchOS 8.8.1
Loop Version
- Version Number: 3.6.4 (57)
- Repo: [default released Master from automatic build script]
CGM
- Device: Dexcom G6
- Manager app: Dexcom G6 App
Pump
- Manufacturer: Omnipod
- Model: Dash
Additional context This is a surprising event with no history of similar problems.
Loop Report 2025-09-13 20:51:32+01:00.md Export-20250913T200236Z.zip
Additional screenshots. I suspected that the low glucose prediction was due to negative remaining carbs, but it appears to be a result of insulin effect.
Ich habe das gleiche Problem seit 2 Tagen, auch der Bolus Vorschlag passt nicht zum Kh Menge. Gibt es eine Lösung des Problems?
Typically this is a signature of an extreme override being set when either carbs or insulin is entered. Please read this section of LoopDocs
- https://loopkit.github.io/loopdocs/operation/features/overrides/#avoid-extreme-insulin-needs-setting
