Repository navigation
Therapy settings | Basal rates and insulin sensitivity history #2234
Description
Hi dear developers,
Changing basal rates in the therapy settings is something I do once in a while. I usually look at my cgm data, i.e. 30 days overview, and bring up or bring down the basal rate for a time slot. I might also change the time slots themselves to better suit to the cgm data I inspect. The problem is, I don't remember what I changed last, and I don't know when I did it. Have I already changed the basal 7 days ago? Was the change I did last night after an annoying hypo (or hyper) a reckless and wrong change?
I would like to have a clear history of the basal rates that were last changed. It would look like a list of charts. The chart would look like the basal rates table itself - rows of timeslots and basal rate (u/hr), and the list would hold these tables with timestamps. This way I can look at the differences between different basal therapies I recently had.
An alternative I considered would be to take a screenshot every time I do any change to the basal rate treatment.
The history of the insulin sensitivity is also something that would help, in exactly the same way and reasoning.
Thanks a lot in advance
Nadav
Activity
marionbarker commentedon Oct 1, 2024
Great request. I'm not sure if anyone will work on this for Loop. (Takes someone with skill and time to prepare the code.)
But there are 2 ways to get the capability now.
Options 1 - Use released code
Option 2 - Use a Customization
Stampertina commentedon Oct 1, 2024
Those are great solutions- thanks, Marion. Thanks for explaining them.
Nadav, your idea for screenshots is a good one. I do that on my son's Loop phone for any settings changes and send it to my phone. It's easy to keep track of that way. I have also used a spreadsheet in the past for all of the settings, but did not keep up with that.
nadavv commentedon Oct 2, 2024
Thanks for your replies and ideas.
nadavv commentedon Feb 11, 2026
Hi Marion, I'd like to try building this myself on a side branch.
Is there somewhere a dev contributor faq or starters guide?
Thanks!
Edit: As I'm a windows user, I'm still on my way to find a way to develop on Mac.
marionbarker commentedon May 2, 2026
I recommend you read this document on contributing to Trio. Then apply the same principals to how you would contribute to Loop.
https://github.com/nightscout/Trio/blob/main/CONTRIBUTING.md
If you start with a feature coded by claude (or some other AI), you are responsible for understanding every requested change - whether is makes sense or is superfluous and what it actually does. And then testing the feature. A completely vibe-coded PR will not be considered for inclusion.
taylorpatterson-T1D commentedon May 2, 2026
@nadavv the capability you are seeking may be addressed by LoopInsights
#2405
As Marion mentions a completely vibe-coded PR will not be considered into the main branch which is why I am maintaining mine via separate installation script: LoopPowerPack/LoopWorkspace#2
nadavv commentedon May 6, 2026
Thanks for your responses. I'll update if and when this feature is polished enough for master.