[thecosas]

You may want to look into Loop [0] or Trio [1] if you don't want to wait for FDA approval on a closed loop system. They have pretty thorough guides, but I know it can be a lot to take on as the person who doesn't have Type 1 and some endocrinologists aren't supportive of the DIY options. That said, both have great communities who are very supportive and helpful, not just with the software. Best of luck to your partner!

[0] https://loopkit.github.io/loopdocs/

[1] https://docs.diy-trio.org/en/latest/

[titusjohnson]

Thank you for the recommendations! If I had the condition you can bet your ass I'd be building these, both look fantastic. I'm going to bookmark both so I can take the time to read their docs later -- Diabetes management from the POV of a developer is right up my alley and I see tons of interesting info in there already.

There is no way I'm bringing these up to her, though. For my own self-preservation. Over the last few months we've had a long-running argument about the operation of her Dexcom glucose monitor -- she's been convinced that it requires a continuous, active internet signal to function. Her proof was that every time she went into the basement at work, her Dexcom stopped reporting her glucose levels. When she comes upstairs, then she suddenly gets notified that she's been spiking or dipping for the last hour.

Everything under the sun, included the sun (remember that solar flare the other week? Yeah that was also pointed at as a problem) has been blamed for her Dexcom not informing her of dips and spikes. Yesterday evening her new Omnipod app told her to stop enabling Airplane Mode or BatterySaver, as these toggles interrupt bluetooth communications. She's been turning those on every time she goes into the basement at work to save battery.

It's just best if nothing I have touched or created is involved in any way.