nightscout
Preselection of hypo TT in carb UI
Recently, I went on a day-long cycling tour and set a 70% profile with an activity TT for 10 hours. After two hours I got slightly low, so I ate some carbs, and entered them. Unfortunately, I didn't notice the preselected "start hypo TT". There was no problem for the next hour, but then the target was reset to the default (instead of activity TT). The loop gave me too much insulin, and I had a severe hypo.
Suggestion: Do not preselect "Start hypo TT" if the currently set TT is higher and longer than the hypo TT would be.
I recently encountered the same issue. In a caretaker configuration, a low profile combined with a high temporary target (TT) set 1.5 hours prior to exercise caused an interaction problem. The caretaker treated the low with carbohydrates, which effectively shortened the TT duration. When the TT expired, the system reverted to the default target, thereby blocking the expected automation from being triggered.
When low, I think Hypo TT should automatically be selected when entering carbs, unless: There is already a high TT > 100 mg/dl or 5,5 mmol/L with a duration longer than preset Hypo TT duration.
This will avoid Hypo TT cancelling out Activity TT or custom high TT with a longer duration than preset Hypo TT.
We experience this issue from time to time with Hypo TT cancelling out Activity TT when entering carbs when low. I think this proposal will fix issue as described in this ticket and other scenarios. It's recommended to not allow SMB when a high TT is set (above 100mg/dl)
@MilosKozak @widmann this issue can be closed due to merging of https://github.com/nightscout/AndroidAPS/pull/4339
Thank you for providing the patch! It is much appreciated.
You are welcome and thanks for reporting this issue. I also helped myself as we experience this from time to time.
Feel free to close the issue 😉