Manually stopping insulin shows as regular basal rate in nightscout

[vonstein2002]

Highlighted area on tconnect shows 0u/hr. in Nightscout it shows regular basal rate. tconnectsync version 0.4.1

[JMPZ11]

Does it show correctly in t:connect?

If you power off the pump, t:connect does something similar, assuming it delivered insulin at the basal rate till you power it back on...

[vonstein2002]

Yes, tconnect shows it correctly. There are no treatments entered in to nightscout for the manual stop or the manual restart but all treatments either side of the stop show up in nightscout.

[JMPZ11]

Oh, whoops! Helps to look at the attached images LOL

…

On Wed, Oct 27, 2021 at 5:37 PM vonstein2002 ***@***.***> wrote: Yes, tconnect shows it correctly. There is no treatments entered in to nightscout for the manual stop or the manual restart but all treatments either side of the stop show up in nightscout. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#17 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHDGDXMO3H757ZEMWMY45GDUJBWJVANCNFSM5G3DGHPA> .

[jwoglom]

Thanks for noticing and reporting this -- this is a perfect example of the sort of edge case that's easy to miss without either a lot of real-world use or very good test cases.

I've been looking into the data that tconnect returns from its API to pinpoint exactly how to detect when this situation occurs. Given the following data:

I was able to validate that the "0 u/hr Basal" basal events are properly being processed, as they show up in api.controliq.therapy_timeline with a 0.0 basal. There is also an associated suspensionDeliveryEvent with the same timestamp:

{
  'basal': {
    'algorithmDeliveryEvents': [
      ...
      {'y': 0.0, 'duration': 897, 'x': 1635195156}, # 1:52 PM
      ...
    ]
  },
  'suspensionDeliveryEvents': [
    ...
    {'continuation': None, 'suspendReason': 'control-iq', 'x': 1635195156}, # 1:52 PM
    ...
  ]
}

But, like you mentioned, "Manual/Alarm" basal events are not currently working.
I discovered this is because a suspensionDeliveryEvent exists for it, but there is no associated delivery happening at that time:

{
  'suspensionDeliveryEvents': [
    {'continuation': None, 'suspendReason': 'manual', 'x': 1635188855} # 12:07 PM
  ]
}

I've added some code to catch this case and add a manual basal event for 0u/hr at the time of the manual suspension, with a duration lasting until the next basal event detected by the pump.
The event should appear in the nightscout API (at /api/v1/treatments) with reason "manual suspension".

[vonstein2002]

Thanks for your work on this project! Allows me to use openaps autotune again :)