Medtronic State incorrect after Bolus is Cancelled

[marionbarker]

Describe the bug With a Medtronic Pump, issue a bolus and cancel it after it starts.

• The pump is suspended
• (I originally thought the pump was not suspended, but in fact it is - I'm confused obviously)
• No further closed loop action happens until manual action is taken:
  • (I thought I saw this but having trouble reproducing it) a new bolus restores the state
  • a tap on the unsuspend row restores the state

Attach an Issue Report I have the Xcode debug log for a test where this happened.

• Medtronic-suspend-when-cancel-2024-07-16 162304_Xcode_debug_log.txt

Phone

• Hardware: iPhone 7
• OS Version: iOS 15.8.2

Loop Version

• Version Number: 3.4.0, commit e70136b
• Repo: LoopKit/LoopWorkspace

CGM

• Nightscout as CGM

Pump

• Medtronic 515

Additional context I have seen a few Facebook questions about this - didn't really pay attention until I tested today.

Repeated testing:

• 0.5 U, cancel and see Suspend on Pump and Suspended on HUD
• Resume on phone
• 1.0 U, cancel and see Suspend on Pump and Suspended on HUD
• Both pump and Loop say suspended, but bolusing works, 6.5 U and then cancel
• 1.0 U and it boluses even though pump and Loop say suspended.

[elnjensen]

I believe that cancelling a bolus on a Medtronic pump (at least the ones we use for Loop) always leaves the pump in a suspended state. You've noted this in your edits.

I think it has been the case for a long time that issuing a manual bolus from the pump has unsuspended it. I've always taken that as intentional, a design feature reflecting a presumed user desire to bolus.

I'm not sure at this point whether you still think there is an issue here? Or just that the behavior could be better documented?

[elnjensen]

The one way I have found to put the pump and Loop into an inconsistent state is as follows:

• Press the left arrow on the pump to bring up the information screen. Leave that screen displayed.
• Issue a suspend command from Loop.
• The pump does not suspend, but apparently doesn't throw an error either, so Loop thinks it is suspended.

I believe that Loop will eventually notice and restore its state correctly, the same way it detects a manual resume from the pump interface, so the impact is small.

This deserves its own issue, but I haven't gotten around to writing it up. If someone can confirm, feel free to open a new issue and copy over any of this that's useful. The fix would be for Loop to check with the pump after an attempted suspend to verify that the suspend command had succeeded, even if there is no error.

[marionbarker]

Thanks Eric. I clearly was confused. I was testing pods and then switched to MDT.

I’m not sure what the design is regarding manual bolus when MDT pump is suspended.

I plan to do more testing later when I get time.