Add support for DanaKit and MedtrumKit to Loop

[marionbarker]

Purpose

Draft PR while we work through updates required before landing the support for DanaKit and MedtrumKit into LoopWorkspace dev branch.

The mixing of these two pump managers is for my convenience. Both are at about the same stage of development and are being developed by the same person, @bastiaanv.

Method

Testers will continue to build the feat/dev-dana-medtrum branch for testing. This branch can be updated as frequently as needed without a formal review process - although every update includes local testing prior to pushing the update to GitHub.

When a tester has an issue or concern, they should add a comment to this PR.

When we are ready to get formal approval for the merge, the target branch for this PR will be moved to a new branch, update_dev_to_M.m.x, with the appropriate version number.

Documentation

I will configure 2 comments, one for Dana and one for Medtrum, that can be edited as testing proceeds. These comments will summarize status and indicate must-have and nice-to-have features for the Pump Managers before landing this PR.

Testing

Testers should create a new comment each time they wish to document a bug or feature request for the pump.

For your comment - please Include:

• the LoopWorkspace SHA - this identifies the DanaKit and MedtrumKit version. (This information is in the LoopReport.)
• which pump is being tested
• whether this is a possible bug report or a desired feature
• If it is a possible bug report, then
  • add enough documentation including a timestamp so we can diagnose the issue
    • include screenshots
    • include the pump log files (scroll to the bottom of the pump manager screen in Loop and tap on Share Dana/Medtrum logs
    • include the LoopReport
    • include the Critical Event Log

[marionbarker]

Dana Status

Placeholder for summarizing Dana.

[marionbarker]

Medtrum Status

Placeholder for summarizing Medtrum.

[marionbarker]

Medtrum test

Feature requests

• Add the orange underline warning on the HUD when the patch is nearing the 3 day expiration, changing to red during the grace period
• Add an urgent warning to Loop when patch is out of insulin or not delivering insulin because of a patch failure
• When sharing pump logs, prepend the date to the name of the XX_log.txt and XX_log_prev.txt (for today and yesterday)
• Add some Medtrum log information to the LoopReport - particularly dosing information

Details

Description

I tested a Medtrum patch for myself. Everything was nominal. I did not notice much difference from when I use an Omnipod.

Note - I was running a sick override most of the time - I got some injections in my knees and was needing on the order of 20% more insulin than normal. It could have been the switch from Omnipod to Medtrum, but I suspect it was the injections. It was not cortisone but there was a fair amount of local swelling.

I let it go past the 3 day plus 8 hour mark so I could see what happened when the pump ran out of insulin.

I think the warning provided by Loop was inadequate. There should be a more urgent message that the pump is out of insulin.

The Medtrum does have an on-patch alert, but it is incredibly quiet and very high pitched.

SHA

The Medtrum SHA for the test where I ran the pump out of insulin was
0905638 fix: better rounding bolus Entries

Although this commit was available before the end of the patch, I did not build it to my phone (sorry):
1a3b75e fix: pump events after new patch activated fix: improved PumpHighlight during non-active state

I did update my build after applying the new patch. The Loop Report is from before the update.

Files

The LoopReport and daily Medtrum logs are provided.
I did not get the full log_prev on the first day, but got all subsequent days.
I included 2 log files on the last day - one before removing the patch and one after adding the new patch.

Medtrum_logs_Archive.zip

Loop Report 2026-01-17 09_18_21-08_00.md

[bastiaanv]

Thank you for testing @marionbarker !

Medtrum Feature request:

• This is fixed in today's version: c124c7e
• This was fixed in version: 1a3b75e
• I will add it to the TODO
• Same