search

nightscout / cgm-remote-monitor

nightscout web monitor
GNU Affero General Public License v3.0
2.38k stars 71.59k forks source link

Extended Blus Functionality #8086

Open ChiSoxDev opened 1 year ago

ChiSoxDev commented 1 year ago

If you need support for Nightscout, PLEASE DO NOT FILE A TICKET HERE For support, please post a question to the "CGM in The Cloud" group in Facebook (https://www.facebook.com/groups/cgminthecloud) or visit the WeAreNotWaiting Discord at https://discord.gg/zg7CvCQ

Is your feature request related to a problem? Please describe. Extended boluses added by various pump manufacturers are not shown in Nightscout at all if you are not operating with a closed loop system such as Loop or OpenAPS.

Describe the solution you'd like Extended boluses are two part: First the initial amount. This can display like any other bolus. Second, a continual delivery of the remaining amount over the selected period of time. This would probably best be displayed as a different color, but additive to basils.

Describe alternatives you've considered Not everyone that can benefit from Nightscout can or would like to use a closed loop system. Unforutnately I don't see any alternatives besides being unable to see the information, or just not using extended.

Additional context When searching for this feature I saw a couple of closed feature requests that never got to resolution but without explanation. I am hopeful this can be investigated again. Thank you.

psonnera commented 1 year ago

Extended bolus should be logged like this https://nightscout.github.io/nightscout/discover/#combo-bolus As far as I can understand, the issue is not on Nightscout side (as this is a supported feature) but on the uploader side.

sulkaharo commented 1 year ago

Yup this sounds like an uploader feature, not anything related to Nightscout the cloud service. Which uploader are you using to send data to Nightscout?

ChiSoxDev commented 1 year ago

I didn't see this in the docs, thank you for linking. I'm using tconnectsync for a Tandem pump. I'll take a look at the API data received to see if the issue is the Tandem side, or the tconnectsync application. If you would like I can update this issue to be Tandem specific and then also update with my findings for future reference.

ChiSoxDev commented 1 year ago

@psonnera I tested this again and it appears Nightscout is getting the correct data from the uploader, but it is not displaying the added basal or taking that into IOB calculations.

Screenshot_20230906-111627.png

bewest commented 1 year ago

Are you able to find the record in your json documents at /api/v1/treatments.json? I can take a look at the tconnectsync code and double check with Medtronic stuff in nightscout-connect as well.