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

29th
Sep 2018
Scott Leibrand
@scottleibrand
Sep 29 2018 02:46
Andrew Kirby: do it the other way around: do a small easy bolus first, then enter the carbs with the bolus wizard as soon as it completes. The just-completed easy bolus will prevent SMB from issuing another one for 3 minutes.
Carl
@c-robertson
Sep 29 2018 14:09
Running a new PI HAT rig, consistent get 'pump history too old' errors, probably because I've only been using it sporadically as I get it built out with WIfi, prefs, BT tether, etc. How would I remove the old pump history to start fresh?
Error: pumphistory too old
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
Radio ok. Listening: ..........No interfering pump comms detected from other rigs (this is a good thing!)
Listening for 40s silence before mmtuning: ...................No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: "916.540", 5, -50 No wait required.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Sat 29 Sep 09:58:22 EDT 2018
Ebgineer
@Ebgineer
Sep 29 2018 14:11
@c-robertson That error will usually go away after a few cycles. The problem isn't the presence of data that is too old, it is the absence of data that is new enough.
Once the rig gets enough info from the pump it will start using it and the loop should succeed.
Carl
@c-robertson
Sep 29 2018 14:20
@Ebgineer I get that, but the last successful loop is really old, like > 7 days old. Is it trying to fill in from then to now? This has been going on for a few days, just haven't had time to troubleshoot until now...
Ebgineer
@Ebgineer
Sep 29 2018 14:21
It won't go back that far to fill data. If it hasn't succeeded for several days then there's something else wrong.
Can you post the log for a complete cycle, i.e. just after "Unsuccessful oref0-pump-loop" up through the next similar message.
Tore Bjørndalen
@BjoTore_twitter
Sep 29 2018 14:23
try to do something that updates history. A small bolus?
Carl
@c-robertson
Sep 29 2018 14:34
Starting oref0-pump-loop at Sat 29 Sep 10:24:30 EDT 2018 with 2 second wait_for_silence:
Retrying without waiting for new BG
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Old pumphistory-24h, waiting for 2 seconds of silence: Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Old pumphistory-24h refreshed
Profile less than 60m old; Profile valid. Refreshed pumphistorySkipping bolus wizard entry 5 in the pump history with 0 g carbs and no insulin.
This is caused by a BolusWizard without carbs. If you specified insulin, it will be noted as a seperate Bolus
Timestamp of bolus wizard: 2018-09-28T21:39:11-04:00
Skipping bolus wizard entry 9 in the pump history with 0 g carbs and no insulin.
This is caused by a BolusWizard without carbs. If you specified insulin, it will be noted as a seperate Bolus
Timestamp of bolus wizard: 2018-09-28T14:15:09-04:00
 and meal.json
Checking pump clock: "2018-09-29T10:29:16-04:00" is within 90s of current time: Sat 29 Sep 10:29:17 EDT 2018
Error: pumphistory too old
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: "916.492", 5, -32 No wait required.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Sat 29 Sep 10:32:13 EDT 2018
Tore Bjørndalen
@BjoTore_twitter
Sep 29 2018 14:40
try a simple bolus not using the wizard(left button)
PieterGit
@PieterGit
Sep 29 2018 14:48
if people want to join the discussion on the future 0.11 Nightscout release, please join the discussion at https://gitter.im/nightscout/public?at=5baf8f7b5af4853068365138
Carl
@c-robertson
Sep 29 2018 14:48
Well, I turned off my Edison rig which seems to have helped. Guess I would've expected something other than 'No interfering pump comms detected...' above. Of course, all it did was cancel the temp set by the Edison rig, still not successfully looping yet...
Starting oref0-pump-loop at Sat 29 Sep 10:33:04 EDT 2018 with 22 second wait_for_silence:
Retrying without waiting for new BG
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Profile less than 60m old; Profile valid. Refreshed pumphistory^[Skipping bolus wizard entry 5 in the pump history with 0 g carbs and no insulin.
This is caused by a BolusWizard without carbs. If you specified insulin, it will be noted as a seperate Bolus
Timestamp of bolus wizard: 2018-09-28T21:39:11-04:00
Skipping bolus wizard entry 9 in the pump history with 0 g carbs and no insulin.
This is caused by a BolusWizard without carbs. If you specified insulin, it will be noted as a seperate Bolus
Timestamp of bolus wizard: 2018-09-28T14:15:09-04:00
 and meal.json
Checking pump clock: "2018-09-29T10:36:15-04:00" is within 90s of current time: Sat 29 Sep 10:36:17 EDT 2018
Temp refreshed
Autotune exists! Hoorah! You can use microbolus-related features.
{"carbs":35,"nsCarbs":35,"bwCarbs":0,"journalCarbs":0,"mealCOB":23,"currentDeviation":4.3,"maxDeviation":3.17,"minDeviation":2.77,"slopeFromMaxDeviation":0,"slopeFromMinDeviation":0.344,"allDeviations":[4,3,3],"lastCarbTime":1538227653000,"bwFound":false}
{"iob":1.977,"activity":0.0171,"basaliob":-0.012,"bolusiob":1.99,"netbasalinsulin":0.35,"bolusinsulin":3.1,"time":"2018-09-29T14:36:29.000Z","iobWithZeroTemp":{"iob":1.977,"activity":0.0171,"basaliob":-0.012,"bolusiob":1.99,"netbasalinsulin":0.35,"bolusinsulin":3.1,"time":"2018-09-29T14:36:29.000Z"},"lastBolusTime":1538227653000,"lastTemp":{"rate":0.625,"timestamp":"2018-09-29T10:08:10-04:00","started_at":"2018-09-29T14:08:10.000Z","date":1538230090000,"duration":29.64}}
{"delta":2,"glucose":88,"noise":null,"short_avgdelta":0.67,"long_avgdelta":-0.45,"date":1538230320000}
2018-09-29T14:37:20.655Z
Checking deliverAt: 2018-09-29T14:37:20.655Z is within 1m of current time: Sat 29 Sep 10:37:21 EDT 2018
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"reason":"If current system time Sat Sep 29 2018 10:37:20 GMT-0400 (EDT) is correct, then BG data is too old. The last BG data was read 25.3m ago at Sat Sep 29 2018 10:12:00 GMT-0400 (EDT). Canceling high temp basal of 0.625","deliverAt":"2018-09-29T14:37:20.655Z","temp":"absolute","duration":0,"rate":0}
Temp refreshed: monitor/temp_basal.json: {"duration":2,"rate":0.625,"temp":"absolute"}
enact/smb-enacted.json: "Rate: 0 Duration: 0"
Temp refreshed: monitor/temp_basal.json: {"duration":0,"rate":0,"temp":"absolute"}
No bolus needed. Pump profile refreshed; Settings refreshed; Edison on battery: 94%. Pumphistory-24 < 30m old
Completed oref0-pump-loop at Sat 29 Sep 10:39:22 EDT 2018
Carl
@c-robertson
Sep 29 2018 14:55
Seems like it is not getting updated BGs...
Starting oref0-pump-loop at Sat 29 Sep 10:40:04 EDT 2018 with 14 second wait_for_silence:
Waiting up to 4 minutes for new BG: .............parse error: Unfinished string at EOF at line 8591, column 20
...........Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Profile less than 60m old; Profile valid. Refreshed pumphistorySkipping bolus wizard entry 5 in the pump history with 0 g carbs and no insulin.
This is caused by a BolusWizard without carbs. If you specified insulin, it will be noted as a seperate Bolus
Timestamp of bolus wizard: 2018-09-28T21:39:11-04:00
Skipping bolus wizard entry 9 in the pump history with 0 g carbs and no insulin.
This is caused by a BolusWizard without carbs. If you specified insulin, it will be noted as a seperate Bolus
Timestamp of bolus wizard: 2018-09-28T14:15:09-04:00

Warning: setting mealCOB to 0 because currentDeviation is null/undefined
 and meal.json
Checking pump clock: "2018-09-29T10:47:16-04:00" is within 90s of current time: Sat 29 Sep 10:47:18 EDT 2018
Temp refreshed
Autotune exists! Hoorah! You can use microbolus-related features.
{"carbs":35,"nsCarbs":35,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":null,"maxDeviation":0,"minDeviation":999,"slopeFromMaxDeviation":0,"slopeFromMinDeviation":999,"allDeviations":[],"lastCarbTime":1538227653000,"bwFound":false}
{"iob":1.789,"activity":0.0171,"basaliob":-0.01,"bolusiob":1.799,"netbasalinsulin":0.25,"bolusinsulin":3.1,"time":"2018-09-29T14:47:30.000Z","iobWithZeroTemp":{"iob":1.789,"activity":0.0171,"basaliob":-0.01,"bolusiob":1.799,"netbasalinsulin":0.25,"bolusinsulin":3.1,"time":"2018-09-29T14:47:30.000Z"},"lastBolusTime":1538227653000,"lastTemp":{"rate":0.625,"timestamp":"2018-09-29T10:08:10-04:00","started_at":"2018-09-29T14:08:10.000Z","date":1538230090000,"duration":29.57}}
{"delta":2,"glucose":88,"noise":null,"short_avgdelta":0.67,"long_avgdelta":-0.45,"date":1538230320000}
null
No deliverAt found.
{"reason":"If current system time Sat Sep 29 2018 10:48:09 GMT-0400 (EDT) is correct, then BG data is too old. The last BG data was read 36.2m ago at Sat Sep 29 2018 10:12:00 GMT-0400 (EDT). Temp 0 <= current basal 0.575U/hr; doing nothing. "}
Couldn't smb_verify_suggested
oref0-pump-loop failed. Waiting up to 4 minutes for new BG: ........................Unsuccessful oref0-pump-loop (BG too old) at Sat 29 Sep 10:52:32 EDT 2018
Wondering about the parse error:
Waiting up to 4 minutes for new BG: .............parse error: Unfinished string at EOF at line 8591, column 20
Ebgineer
@Ebgineer
Sep 29 2018 14:59
yeah its like the file containing the bg data doesn't have the right format. Could be that the rig was turned off while writing the file, or maybe there wasn't enough disk space to fit the whole set of data.
Carl
@c-robertson
Sep 29 2018 15:00
Any idea what the actual filename is and whether I can just delete it to start fresh?
Ebgineer
@Ebgineer
Sep 29 2018 15:00
I don't know without searching the code, maybe glucose.json - somebody else here will know offhand
Carl
@c-robertson
Sep 29 2018 15:01
With the PI rig, I was going to ask if the power switch does a clean shutdown. Judging by the way all the LEDs switch off, I am guessing not...
Just for completeness sake, here's the latest - back to the 'pump history too old' error...
Starting oref0-pump-loop at Sat 29 Sep 10:53:03 EDT 2018 with 9 second wait_for_silence:
Waiting up to 4 minutes for new BG: ........................Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Profile less than 60m old; Profile valid. Refreshed pumphistorySkipping bolus wizard entry 5 in the pump history with 0 g carbs and no insulin.
This is caused by a BolusWizard without carbs. If you specified insulin, it will be noted as a seperate Bolus
Timestamp of bolus wizard: 2018-09-28T21:39:11-04:00
Skipping bolus wizard entry 9 in the pump history with 0 g carbs and no insulin.
This is caused by a BolusWizard without carbs. If you specified insulin, it will be noted as a seperate Bolus
Timestamp of bolus wizard: 2018-09-28T14:15:09-04:00

Warning: setting mealCOB to 0 because currentDeviation is null/undefined
 and meal.json
Checking pump clock: "2018-09-29T11:00:20-04:00" is within 90s of current time: Sat 29 Sep 11:00:22 EDT 2018
Error: pumphistory too old
oref0-pump-loop failed. If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Sat 29 Sep 11:00:23 EDT 2018
Carl
@c-robertson
Sep 29 2018 15:16
There is a glucose.json in the myopenaps/cgm folder, looks like it is well formed with the latest entry at 10:12 as reflected in the log.
Ebgineer
@Ebgineer
Sep 29 2018 15:22
This is beyond my level of knowledge, but I see in the setglucosetimestamp function in oref0-pump-loop.sh that it is parsing (using jq) a file monitor/glucose.json
Tore Bjørndalen
@BjoTore_twitter
Sep 29 2018 15:25
@alimhassam or @ecc1 is this bolus wizard entry messing up the logic?
Carl
@c-robertson
Sep 29 2018 15:29
monitor/glucose.json also looks to be intact. Nothing weird about line 8591, column 20 (from the parse error text above)
Ebgineer
@Ebgineer
Sep 29 2018 15:38
Great :) I see the error also went away, so maybe there was a partial glucose.json file overwritten by a complete one on the next read.
Carl
@c-robertson
Sep 29 2018 15:42
@Ebgineer Unfortunately, the error persists:
Starting oref0-pump-loop at Sat 29 Sep 11:29:04 EDT 2018 with 7 second wait_for_silence:
Waiting up to 4 minutes for new BG: glucose.json newer than pump_loop_completed
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Profile less than 60m old; Profile valid. Refreshed pumphistorySkipping bolus wizard entry 5 in the pump history with 0 g carbs and no insulin.
This is caused by a BolusWizard without carbs. If you specified insulin, it will be noted as a seperate Bolus
Timestamp of bolus wizard: 2018-09-28T21:39:11-04:00
Skipping bolus wizard entry 9 in the pump history with 0 g carbs and no insulin.
This is caused by a BolusWizard without carbs. If you specified insulin, it will be noted as a seperate Bolus
Timestamp of bolus wizard: 2018-09-28T14:15:09-04:00

Warning: setting mealCOB to 0 because currentDeviation is null/undefined
 and meal.json
Checking pump clock: "2018-09-29T11:31:34-04:00" is within 90s of current time: Sat 29 Sep 11:31:35 EDT 2018
Temp refreshed
Autotune exists! Hoorah! You can use microbolus-related features.
{"carbs":35,"nsCarbs":35,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":null,"maxDeviation":0,"minDeviation":999,"slopeFromMaxDeviation":0,"slopeFromMinDeviation":999,"allDeviations":[],"lastCarbTime":1538227653000,"bwFound":false}
{"iob":1.09,"activity":0.0142,"basaliob":-0.002,"bolusiob":1.091,"netbasalinsulin":0.2,"bolusinsulin":2.8,"time":"2018-09-29T15:31:48.000Z","iobWithZeroTemp":{"iob":1.09,"activity":0.0142,"basaliob":-0.002,"bolusiob":1.091,"netbasalinsulin":0.2,"bolusinsulin":2.8,"time":"2018-09-29T15:31:48.000Z"},"lastBolusTime":1538227653000,"lastTemp":{"rate":0.625,"timestamp":"2018-09-29T10:08:10-04:00","started_at":"2018-09-29T14:08:10.000Z","date":1538230090000,"duration":29.57}}
{"delta":2,"glucose":88,"noise":null,"short_avgdelta":0.67,"long_avgdelta":-0.45,"date":1538230320000}
null
No deliverAt found.
{"reason":"If current system time Sat Sep 29 2018 11:32:16 GMT-0400 (EDT) is correct, then BG data is too old. The last BG data was read 80.3m ago at Sat Sep 29 2018 10:12:00 GMT-0400 (EDT). Temp 0 <= current basal 0.575U/hr; doing nothing. "}
Couldn't smb_verify_suggested
oref0-pump-loop failed. Waiting up to 4 minutes for new BG: ........................Unsuccessful oref0-pump-loop (BG too old) at Sat 29 Sep 11:36:37 EDT 2018
Only saw the parse error that one time, nevertheless the rig is not get updated BGs successfully....
Ebgineer
@Ebgineer
Sep 29 2018 15:51
With the pump communication seeming to be ok but times seeming to be too old, it makes me want to check the time zones on all the devices. I'd also want to ensure that the method you're using to get the bg data is flowing ok, e.g. if it is from nightscout check that it looks ok there. Or if it is from the cgm, make sure that connection is ok.
Somebody else will have to pick it up from here since I'm headed out for a while.
Carl
@c-robertson
Sep 29 2018 15:52
There is a file cgm/cgm-glucose.json where the most recent entry is really old "display_time": "2018-09-09T16:36:00",
@Ebgineer Thanks for the help.
FWIW, I have an Enlite sensor, the CGM data is updated consistently on the pump. Also, the PI rig is updating Nightscout fine, see the same 'BG data is too old...' error there.
Carl
@c-robertson
Sep 29 2018 17:52
Does the PI rig, running 0.7.0 dev, work with token access for Nightscout?
Eric
@ecc1
Sep 29 2018 17:59
not yet, there's a patch being tested: ecc1/nightscout#4
(anyone have updated status on whether it's ready?)
PieterGit
@PieterGit
Sep 29 2018 18:56
@ecc1 @c-robertson token based it's not completely ready for 0.7.x yet. I had some issues with it, but had problems compiling the go libs for x86
Carl
@c-robertson
Sep 29 2018 19:28
Thanks @ecc1 @PieterGit. I had it setup for token access. Just got latest and ran oref0 setup again with the API secret instead of the token. PI rig is back in business, looping successfully.
PieterGit
@PieterGit
Sep 29 2018 19:30
if you can help test/implement ecc1/nightscout#4 please do.
Carl
@c-robertson
Sep 29 2018 21:03
@PieterGit I would be happy to help test it, not sure where to start...
Xabeth
@Xabeth
Sep 29 2018 23:53
image.png
Working from sudo bash
curl -s https://raw.githubusercontent.com/openaps/oref0/dev/bin/openaps-install.sh > /tmp/openaps-install.sh && bash /tmp/openaps-install.sh
and have gotten this during the install. I searched github and didn't see anything about it
Is it ok to choose the first option?