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

4th
Jan 2019
straykatz
@straykatz
Jan 04 00:00
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 01:24
Are you entering the carbs as well? Is SMB enabled?
straykatz
@straykatz
Jan 04 01:27
@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 01:55
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:
straykatz
@straykatz
Jan 04 03:18
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
straykatz
@straykatz
Jan 04 03:30
Hmm, the log says it did lots of SMBs. But NS is not showing them, and the BGs did not behave like they arrived/
Eric
@ecc1
Jan 04 03:35
@straykatz check on your pump, under Bolus > Bolus History
straykatz
@straykatz
Jan 04 03:36
History does not go that far back ..
Good idea though
Eric
@ecc1
Jan 04 03:46
the pump stores much more history though, so if you want you can retrieve it via the pumphistory command
straykatz
@straykatz
Jan 04 03:47
ah, cool. how?
root?
Eric
@ecc1
Jan 04 03:51
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
straykatz
@straykatz
Jan 04 03:55
hmm. I know so little about command line. ... and I am so literal:) ... root@DiaBolus:~/myopenaps# pumphistory -help
-bash: pumphistory: command not found
Eric
@ecc1
Jan 04 03:55
what version of openaps are you running?
straykatz
@straykatz
Jan 04 03:56
Jan 03 13:59:58 DiaBolus pump-loop.log: Your instance of oref0 [0.6.2, master] is up-to-date.
Eric
@ecc1
Jan 04 03:58
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
straykatz
@straykatz
Jan 04 03:58
:)
thank you for trying to help.
Scott Leibrand
@scottleibrand
Jan 04 04:41
The pump-loop.log should show whether or not the bolus was successful.
straykatz
@straykatz
Jan 04 05:06
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 07:23
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 13:42
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.
Eric
@ecc1
Jan 04 16:28
@thanksegon that message means the 0.6 Python code is still running. How did you update to dev?
thanksegon
@thanksegon
Jan 04 17:32
@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 18:00
Did you ever do npm run global-install?
thanksegon
@thanksegon
Jan 04 18:02
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 18:02
One of those might have failed: might want to try them again and watch for errors.
straykatz
@straykatz
Jan 04 19:28
@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 20:12
ok, glad to hear it's fixed.