Closed milleniumfalcon900 closed 8 months ago
I tested and confirmed future carbs do not show up. Thanks for the report.
I'm curious about how far in advance it would be reasonable for LoopFollow to check for future carbs. What do you think?
I know from the FB group that some people schedule their carbs well ahead of time. We don’t usually do more than 20 minutes. My view is that it’s a bit risky, you never know what might happen that might prevent someone from eating at a scheduled time, even if it’s a child at school.
I guess the counter argument is for people who schedule extra carbs to deal with really long acting meals they’ve already eaten maybe 4 hours out so earlier. I guess if you’re looking at that scenario then maybe 6 hours might be a sensible time limit.
Is there a consequence of loop follow looking really far ahead?
We can try 6 hours.
The filtering out future treatments was due to Loop dev added sensor starts in year 2159, messing things up.
The update to LoopFollow 2.0.0.1 seems to have prevented future carbs showing in LoopFollow. When my son boluses 15 minutes in advance the carbs don't show, although they are there in Nightscout. Has anyone else experienced this? LoopFollow built with Xcode and running on iOS 17.0.3
Thanks for your continued hard work.