These are chat archives for nightscout/intend-to-bolus

4th
Jan 2019
Katja Jacob
@straykatz
Jan 04 2019 00:00 UTC
Well, alright... I just read that bolus snooze has been eliminated in 0.6.0 release notes. How should I deal when I want to partially manually bolus for a portion of a meal?
Scott Leibrand
@scottleibrand
Jan 04 2019 01:24 UTC
Are you entering the carbs as well? Is SMB enabled?
Katja Jacob
@straykatz
Jan 04 2019 01:27 UTC
@scottleibrand Yes to both. I entered the carbs separately in NS (without insulin, to avoid double-counting as the bolus is uploaded.) SMB is enabled.
also, using Easy-bolus on 522.
Scott Leibrand
@scottleibrand
Jan 04 2019 01:55 UTC
Did you see it start to issue SMBs after you entered the carbs? If not, what did the OpenAPS pill or pump-loop.log say why?
For Scott :smile:
Katja Jacob
@straykatz
Jan 04 2019 03:18 UTC
It did only one SMB, went to zero temp and only came out at 12:43 when the BG curve crossed the upper target line. https://share.icloud.com/photos/0b04I8VrnKnPaR2tkOyV8mqkw
Katja Jacob
@straykatz
Jan 04 2019 03:30 UTC
Hmm, the log says it did lots of SMBs. But NS is not showing them, and the BGs did not behave like they arrived/
@straykatz check on your pump, under Bolus > Bolus History
Katja Jacob
@straykatz
Jan 04 2019 03:36 UTC
History does not go that far back ..
Good idea though
the pump stores much more history though, so if you want you can retrieve it via the pumphistory command
Katja Jacob
@straykatz
Jan 04 2019 03:47 UTC
ah, cool. how?
root?
no need for root, just run it from the command line in a terminal session on your rig
do pumphistory -help to see the options
you'll need to have the MEDTRONIC_PUMP_ID env variable set in that shell
Katja Jacob
@straykatz
Jan 04 2019 03:55 UTC
hmm. I know so little about command line. ... and I am so literal:) ... root@DiaBolus:~/myopenaps# pumphistory -help
-bash: pumphistory: command not found
what version of openaps are you running?
Katja Jacob
@straykatz
Jan 04 2019 03:56 UTC
Jan 03 13:59:58 DiaBolus pump-loop.log: Your instance of oref0 [0.6.2, master] is up-to-date.
ah, OK, you don't have that command. you can run the Python equivalent ("openaps something-or-other ...") but I don't remember what that is, off hand. Sorry, maybe someone else can help
Katja Jacob
@straykatz
Jan 04 2019 03:58 UTC
:)
thank you for trying to help.
Scott Leibrand
@scottleibrand
Jan 04 2019 04:41 UTC
The pump-loop.log should show whether or not the bolus was successful.
Katja Jacob
@straykatz
Jan 04 2019 05:06 UTC
It looks like many were successful, some failed. Any idea why they are not showing in NS?
(the successful ones)
Scott Leibrand
@scottleibrand
Jan 04 2019 07:23 UTC
Does the IOB go up by the amount of the bolus on the next pump-loop run after each successful one?
thanksegon
@thanksegon
Jan 04 2019 13:42 UTC
HI, folks. Updated from 0.6.0 to dev. Now the rig won't connect to pump. Log shows a recurring message:pump-loop.log: serial.serialutil.SerialException: Attempting to use a port that is not open.
@thanksegon that message means the 0.6 Python code is still running. How did you update to dev?
thanksegon
@thanksegon
Jan 04 2019 17:32 UTC
@ecc1 I changed to the Dev branch (cd ~/src/oref0 && git checkout dev && git pull) and then ran setup again.
Scott Leibrand
@scottleibrand
Jan 04 2019 18:00 UTC
Did you ever do npm run global-install?
thanksegon
@thanksegon
Jan 04 2019 18:02 UTC
Yes, sorry. I forgot to say that I did that also. Switched to Dev, checkout and pull, npm global-install and then setup.
Scott Leibrand
@scottleibrand
Jan 04 2019 18:02 UTC
One of those might have failed: might want to try them again and watch for errors.
Katja Jacob
@straykatz
Jan 04 2019 19:28 UTC
@scottleibrand Yes, IOB changed accordingly. Eventually, the missing SMBs showed up in Nightscout. That coincided with me starting a new rig with 0.7.0 loaded. All good now. Thank you.
Scott Leibrand
@scottleibrand
Jan 04 2019 20:12 UTC
ok, glad to hear it's fixed.