-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial bolus suggestion too low #1181
Comments
Maybe I have been compensating with the old algorithm and I need to set my food as a faster digestion , although I thought I would need to adjust the other direction from the docs. I understand it’s flying a bit close to the bottom and may be trying to avoid an early low but it literally suggests 7u more a few mins after initial 10u bolus starts. At this point if I just pretend that I am eating now and let it bolus and just wait to eat it will kinda do the right thing but don’t think I used to have to. I can work around this but wanted to report in case something is wrong or it causes others issues when this becomes general release |
It’s pretty likely I can reproduce if needed , similar happened yesterday but thought it was a one off |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
sorry if I miss some detail but I can't find the guide that tells me everything I should include for some reason and it's not showing the skeleton outline on here
pump: Omnipod eros
iOS : 13.2.2
loop branch - dev
version : listed as 1.10.1 - but that doesn't get bumped , I built it from the source approx 24 hours ago
steps to reproduce :
Put in various carbs , adding up to 160g + of carbs . Took screenshots and will attach
Initially bolus suggestion is about right .
I am going to pre bolus so turn off loop auto mode (if it kicks in with really high temp a load will added after bolus which pushes me low, this is to make up the temp it missed ) , I have with previous Omnipod / dev had times when it sets a high basal at 10u/hr when loop runs between input carbs and bolus. My bolus is so long the catch up after is 3u or so extra from where it should have done 10/u/ hr , but is not needed as the bolus covers. Got in habit of suspending loop till bolus is in progress to avoid this
4 . Move carbs 10 mins into future , suggestion drops from about 18 to 10 , much too low
Allow it to start doing 10 , click bolus button , it suggests you need another 7 already .
Wait till complete bolus , click bolus button, it’s suggesting 7 or more extra , if I don’t give this I will end up high as it will take about 40 mins with may temp set to 10u/hr
Re enable loop after bolus given
If I hadn’t manually given bolus I would be high
Logs and screenshots to follow
The text was updated successfully, but these errors were encountered: