4 ms·

Closed loop. Seriously, my t1d-related mental exhaustion is 90% reduced now that I'm using a closed loop. 95% if you don't count the "why did androidaps disco

Closed loop. Seriously, my t1d-related mental exhaustion is 90% reduced now that I'm using a closed loop. 95% if you don't count the "why did androidaps disconnect from my pump and which bit do I need to restart to get it working again" headaches. In a way it's eliminating too much mental effort; while it's useful as a backup, the fact I sometimes completely forget to take insulin with meals is not ideal, even if the closed loop notices and takes care of it for me (since there's inherently more lag when relying on the loop than if I dialed in the insulin at meal time).

Trasmatta 2y ago
Do you still enter carbs, or do you just announce meals? I know some people with closed loops just do the latter. If you don't mind sharing, what's your time in range? I have the Omnipod 5 which is decent, but it's "closed loop" abilities are extremely conservative and a bit disappointing. I've considered going the full way with androidaps, but haven't taken the leap yet.
- cperciva 2y ago
  Androidaps says I'm 85% within 3.9-10.0 (70-180) in the past week. I enter carbs but only to a resolution of 10g; and as I mentioned earlier I sometimes forget to enter them entirely. Are you using a Dexcom with your omnipod? My impression is that the quality of sensor is the most important factor; with a flaky sensor looping algorithms will be more conservative since they (reasonably) prioritize avoiding lows.
  - Trasmatta 2y ago
    > Androidaps says I'm 85% within 3.9-10.0 (70-180) in the past week Nice! > I enter carbs but only to a resolution of 10g; and as I mentioned earlier I sometimes forget to enter them entirely. I'm pretty bad at accurately entering carbs. I eat out enough that I've just gotten to the point where I just come up with a rough estimate (which is often wrong). Which means I have to adjust later pretty frequently with snacks or correction doses. Not ideal, but I got so much "carb counting fatigue" over the years. > Are you using a Dexcom with your omnipod? My impression is that the quality of sensor is the most important factor; with a flaky sensor looping algorithms will be more conservative since they (reasonably) prioritize avoiding lows. Yeah, I'm on the G6 still. I think the quality of my readings is pretty good, but the Omnipod 5 algorithm is pretty conservative anyway: rather than naturally bringing you down from a high, you usually have to explicitly give yourself a correction dose. Which I suppose makes sense, but I have read that some people have had a lot more success with looping in Androidaps vs the Omnipod 5's algo. I also wish you could set the "target" a bit lower in the 5. You can't tell it to target below 120: I feel like 100 or 110 would be more reasonable, but again, it makes sense that they prefer being conservative.
    - cperciva 2y ago
      Ah yes, I have my target set to 100. IIRC the first off the shelf closed loops were hardwired to 120 but newer ones are configurable.

Trasmatta 2y ago

Do you still enter carbs, or do you just announce meals? I know some people with closed loops just do the latter. If you don't mind sharing, what's your time in range? I have the Omnipod 5 which is decent, but it's "closed loop" abilities are extremely conservative and a bit disappointing. I've considered going the full way with androidaps, but haven't taken the leap yet.

cperciva 2y ago
Androidaps says I'm 85% within 3.9-10.0 (70-180) in the past week. I enter carbs but only to a resolution of 10g; and as I mentioned earlier I sometimes forget to enter them entirely. Are you using a Dexcom with your omnipod? My impression is that the quality of sensor is the most important factor; with a flaky sensor looping algorithms will be more conservative since they (reasonably) prioritize avoiding lows.
- Trasmatta 2y ago
  > Androidaps says I'm 85% within 3.9-10.0 (70-180) in the past week Nice! > I enter carbs but only to a resolution of 10g; and as I mentioned earlier I sometimes forget to enter them entirely. I'm pretty bad at accurately entering carbs. I eat out enough that I've just gotten to the point where I just come up with a rough estimate (which is often wrong). Which means I have to adjust later pretty frequently with snacks or correction doses. Not ideal, but I got so much "carb counting fatigue" over the years. > Are you using a Dexcom with your omnipod? My impression is that the quality of sensor is the most important factor; with a flaky sensor looping algorithms will be more conservative since they (reasonably) prioritize avoiding lows. Yeah, I'm on the G6 still. I think the quality of my readings is pretty good, but the Omnipod 5 algorithm is pretty conservative anyway: rather than naturally bringing you down from a high, you usually have to explicitly give yourself a correction dose. Which I suppose makes sense, but I have read that some people have had a lot more success with looping in Androidaps vs the Omnipod 5's algo. I also wish you could set the "target" a bit lower in the 5. You can't tell it to target below 120: I feel like 100 or 110 would be more reasonable, but again, it makes sense that they prefer being conservative.
  - cperciva 2y ago
    Ah yes, I have my target set to 100. IIRC the first off the shelf closed loops were hardwired to 120 but newer ones are configurable.