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

28th
May 2017
rsilvers129
@rsilvers129
May 28 2017 00:55 UTC
I have had the Tylenol thing happen to me. It is real, but only for Dexcom. Their G6 won’t be affected by it.
peterfulvi
@peterfulvi
May 28 2017 01:26 UTC

I just satrted my rig after 2-3 days of it not working this is what it is doing:

Listening: .Starting pump-loop at Sat May 27 21:18:31 EDT 2017:
Radio ok, Listening: .No pump comms detected from other rigs
MDT cgm data retrieved
MDT cgm data reformatted
Old pumphistory: Refreshed pumphistory
rm: cannot remove ‘enact/suggested.json’: No such file or directory
Could not parse input data:  [SyntaxError: /root/myopenaps/monitor/iob.json: Unxpected end of input]
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
cat: enact/enacted.json: No such file or directory
Old pumphistory-24h refreshError, retrying
Listening: .No pump comms detected from other rigs
mmtune: pump://JSON/mmtune/monitor/mmtune.json
reporting monitor/mmtune.json
"916.612", 5, -52 Starting pump-loop at Sat May 27 21:21:19 EDT 2017:
Radio ok, Listening: .No pump comms detected from other rigs
MDT cgm data retrieved
MDT cgm data reformatted
Old pumphistory-24h refreshError, retrying
Listening: .No pump comms detected from other rigs
mmtune: pump://JSON/mmtune/monitor/mmtune.json
reporting monitor/mmtune.json
"916.612", 5, -49 Starting pump-loop at Sat May 27 21:23:23 EDT 2017:
Radio ok, Listening: .No pump comms detected from other rigs
MDT cgm data retrieveError, retrying

It always errors after trting to gather readings from my transmitter. Could someone point me in the right direction

I reran setup a few times with no luck.
Dana Lewis
@danamlewis
May 28 2017 02:11 UTC
Do you have CGM data on the pump?
peterfulvi
@peterfulvi
May 28 2017 02:38 UTC
Yes that's the confusing part. I can't tell if it is hardware or something corrupt with the loop
rsilvers129
@rsilvers129
May 28 2017 03:12 UTC
I see papertrail is $5 to $7 a month for 1 GB. Logdna is $1.25 per GB per month. Loggly is free for 200 MB a day for 7 day retention. Anyone try the others?
rsilvers129
@rsilvers129
May 28 2017 03:52 UTC
Did another test today with Master and AMA. I had a cheeseburger and barely a blip. I went up to about 120 something. So then I went to Shake Shack and had a double-frozen custard and an order of Cheese Fries. That comes to 111 grams of carb. I was lowish and didn’t want to bolus the normal amount, so I did a 50% bolus but told it the correct number of carbs. 3-4 hours after eating, I did go up to 164, but it is chipping away at it and coming down. If I did this manually I could easily have reached 300.
Dana Lewis
@danamlewis
May 28 2017 03:55 UTC
:+1:
rsilvers129
@rsilvers129
May 28 2017 04:25 UTC
I have loggly working. It is monitoring the entire /var/log/openaps directory and is free up to 200 MB per day.
Martin Haeberli
@mhaeberli
May 28 2017 04:34 UTC
@rsilvers129 not able to justify a bake-off, but papertrail works pretty well. why / how is logly better?

May 27 21:29:54 etghopenaps0 pump-loop.log: reporting enact/suggested.json
May 27 21:29:54 etghopenaps0 pump-loop.log: {"temp":"absolute","bg":67,"tick":"+0","eventualBG":143,"snoozeBG":104,"insulinReq":0,"reservoir":null,"deliverAt":"2017-05-28T04:29:52.841Z","minPredBG":999,"predBGs":{"IOB":[67,66,66,66,66,68,69,70,71,72,72,72,72,72,73,74,75,77,78,79,81,82,83,83,84,85,85,85,86],"aCOB":[67,66,66,67,69,72,76,80,84,89,93,97,102,107,111,116,121,125,129,132,135,137,139,140,141,141,142,142,143],"COB":[67,66,67,68,71,74,78,82,86,91,95,100,104,109,113,118,123,127,130,134,136,138,139,140,141,141,142,142,142,143]},"COB":17,"IOB":0.777,"reason":"COB: 17, Dev: 63, BGI: -10.53, ISF: 35, Target: 110, minPredBG 104, IOBpredBG 86, COBpredBG 143; 143-104 in range: no temp required, temp 1.125 ~ req 1.15U/hr. "}
May 27 21:29:54 etghopenaps0 pump-loop.log: {"insulinReq":0,"bg":67,"reservoir":null,"temp":"absolute","snoozeBG":104,"rate":1.125,"predBGs":{"COB":[67,66,67,68,70,73,77,82,86,91,95,100,104,109,114,118,123,127,131,134,136,138,139,140,141,142,142,143,143,144],"aCOB":[67,65,64,65,66,68,72,76,80,84,88,93,97,102,107,112,117,122,126,130,133,136,139,140,142,142,143,143,144,144,144,145],"IOB":[67,66,65,65,66,67,68,69,70,71,71,71,70,70,71,72,73,75,76,78,79,80,81,82,83,84,84,85,85,85,86]},"minPredBG":999,"IOB":0.953,"reason":"COB: 18, Dev: 68, BGI: -11.43, ISF: 35, Target: 110, minPredBG 104, IOBpredBG 86, COBpredBG 144; 144-104 in range: no temp required; setting current basal of 1.15 as temp. . Setting neutral temp basal of 1.15U/hr","COB":18,"eventualBG":144,"recieved":true,"duration":30,"tick":"+0","timestamp":"2017-05-27T21:26:50.575833","deliverAt":"2017-05-28T04:26:46.041Z"}
rsilvers129
@rsilvers129
May 28 2017 04:34 UTC
papertrail is $80 a year. Loggly is free.
Martin Haeberli
@mhaeberli
May 28 2017 04:35 UTC
current: 67, forecasts end up at 80 (at the low end purple) and high end 150
why not continue zero-temp?
@rsilvers129 thx good reason - look forward to your write - up when you get a chance
it may be / must be COB
can I set an absolute low bg suspend threshhold below which it will want to keep on zero temping?
Scott Leibrand
@scottleibrand
May 28 2017 04:37 UTC
it says so explicitly:minPredBG 104, IOBpredBG 86, COBpredBG 144; 144-104 in range: no temp required
peterfulvi
@peterfulvi
May 28 2017 04:38 UTC

I just satrted my rig after 2-3 days of it not working this is what it is doing:

Listening: .Starting pump-loop at Sat May 27 21:18:31 EDT 2017:
Radio ok, Listening: .No pump comms detected from other rigs
MDT cgm data retrieved
MDT cgm data reformatted
Old pumphistory: Refreshed pumphistory
rm: cannot remove ‘enact/suggested.json’: No such file or directory
Could not parse input data:  [SyntaxError: /root/myopenaps/monitor/iob.json: Unxpected end of input]
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
cat: enact/enacted.json: No such file or directory
Old pumphistory-24h refreshError, retrying
Listening: .No pump comms detected from other rigs
mmtune: pump://JSON/mmtune/monitor/mmtune.json
reporting monitor/mmtune.json
"916.612", 5, -52 Starting pump-loop at Sat May 27 21:21:19 EDT 2017:
Radio ok, Listening: .No pump comms detected from other rigs
MDT cgm data retrieved
MDT cgm data reformatted
Old pumphistory-24h refreshError, retrying
Listening: .No pump comms detected from other rigs
mmtune: pump://JSON/mmtune/monitor/mmtune.json
reporting monitor/mmtune.json
"916.612", 5, -49 Starting pump-loop at Sat May 27 21:23:23 EDT 2017:
Radio ok, Listening: .No pump comms detected from other rigs
MDT cgm data retrieveError, retrying

It always errors after trting to gather readings from my transmitter. Could someone point me in the right direction

Scott Leibrand
@scottleibrand
May 28 2017 04:39 UTC
@mhaeberli there already is such a threshold.
Martin Haeberli
@mhaeberli
May 28 2017 04:39 UTC
k thx
Scott Leibrand
@scottleibrand
May 28 2017 04:39 UTC
although I guess it's not "absolute"
Martin Haeberli
@mhaeberli
May 28 2017 04:40 UTC
@scottleibrand so target is 110. minPredBG 104, IOBpredBG 86 are both below target. low end of cobpredbg overlaps target ...
what is it called (about to google rtd in parallel)
Scott Leibrand
@scottleibrand
May 28 2017 04:41 UTC
you might want to actually review the determine-basal code for that. there are also some updates to it in dev...
@mhaeberli as a general rule, if something "overlaps target" we'll run a neutral temp until we can tell whether you're going to end up above or below target
Martin Haeberli
@mhaeberli
May 28 2017 04:43 UTC
k got it
Scott Leibrand
@scottleibrand
May 28 2017 04:43 UTC
in this case, you had a huge amount of carb absorption going on, enough to offset 11 mg/dL/5m of BGI and give you a +0 delta. so there's a good chance you're going to rise pretty rapidly from that
Martin Haeberli
@mhaeberli
May 28 2017 04:43 UTC
(running dev)
k thx
Scott Leibrand
@scottleibrand
May 28 2017 04:44 UTC
@peterfulvi when you get persistent Error, retrying you need to pause the cron and run the commands manually to dig into what's really going on.
also keep in mind that zero temps take up to 2 hours to really kick in, so if there's reason to think your BG will rebound by then, it'll be looking at what you need 2-3 hours from now, not what you wish you could've done differently 2 hours ago.
Martin Haeberli
@mhaeberli
May 28 2017 04:47 UTC
thx right now just trying to avert immediately pre-bedtime low - our practice had been for comfort level to run a bit higher at night; we probably need to tell the pump new night time target ~125 not 110
peterfulvi
@peterfulvi
May 28 2017 04:48 UTC
Thanks. I'll look at the docs. Would that be in the openaps tool kit far as what reports to run individually? I'm going to pause cron tight now @scottleibrand
Scott Leibrand
@scottleibrand
May 28 2017 04:50 UTC
all the details on how to run reports manually is in the docs under troubleshooting oref0-setup
peterfulvi
@peterfulvi
May 28 2017 04:50 UTC
Thanks
Martin Haeberli
@mhaeberli
May 28 2017 04:51 UTC
@scottleibrand for clarity, if I set my own zero temp, I think openaps will supplant it at the next 5-6 minute update, is that correct?
Scott Leibrand
@scottleibrand
May 28 2017 04:52 UTC
yes, it will likely cancel it, unless it thinks you need it. you'll probably want to set a high temp target if you don't trust the predictions and want it to be more aggressive at getting BG up
Martin Haeberli
@mhaeberli
May 28 2017 04:53 UTC
ok - so high temp target set in pump as far as I know
?
Scott Leibrand
@scottleibrand
May 28 2017 04:54 UTC
huh? you don't use temp targets? you're missing out. you set them in Nightscout care portal (or with IFTTT or similar)
Martin Haeberli
@mhaeberli
May 28 2017 04:54 UTC
ok i’ll check it.
Scott Leibrand
@scottleibrand
May 28 2017 04:54 UTC
you might want to set aside some time this weekend to read through the rest of the docs and see what else you missed
Martin Haeberli
@mhaeberli
May 28 2017 04:54 UTC
started on the plane yesterday; i agree
ok, set in careportal … d’oh but waiting for Edison to check in again ...
thx 4 all the help
peterfulvi
@peterfulvi
May 28 2017 05:01 UTC

Ok ran openaps refresh-old-pumphistory did not do anything
ranopenaps alias show refresh-old-pumphistory this was the output

refresh-old-pumphistory ! bash -c "find monitor/ -mmin -15 -size +100c | grep -q pumphistory-zoned || ( echo -n \"Old pumphistory: \" && openaps gather && openaps enact ) "

Ran openaps gather nothing happened either

Scott Leibrand
@scottleibrand
May 28 2017 05:01 UTC
"nothing happened"?
peterfulvi
@peterfulvi
May 28 2017 05:03 UTC
No i just echoed it and returned with a zero
im going back and echoing those commands
Scott Leibrand
@scottleibrand
May 28 2017 05:04 UTC
so you'll need to openaps alias show gather and then run the appropriate subset of that
peterfulvi
@peterfulvi
May 28 2017 05:09 UTC
root@petersrig2:~/myopenaps# openaps alias show gather
gather ! bash -c "openaps report invoke monitor/status.json 2>/dev/null >/dev/null && echo -n Ref && test $(cat monitor/status.json | json bolusing) == false && echo -n resh && ( openaps monitor-pump || openaps monitor-pump ) 2>/dev/null >/dev/null && echo ed pumphistory || (echo; exit 1) 2>/dev/null"
Whats the subset?
I echoed refresh-old-pump-history. It came up 0
root@petersrig2:~/myopenaps# echo $? openaps refresh-old-pumphistory
0 openaps refresh-old-pumphistory
Scott Leibrand
@scottleibrand
May 28 2017 05:09 UTC
look at the output of openaps alias show gatherthere and compare it to your pump-loop.log output from before
you should see which command was being run when it gave you the Error
peterfulvi
@peterfulvi
May 28 2017 05:12 UTC
it was Old pumphistory-24h refreshError, retrying
Scott Leibrand
@scottleibrand
May 28 2017 05:13 UTC
yeah, so look through the gather alias to see where it prints out refresh and then see what's immediately after that
peterfulvi
@peterfulvi
May 28 2017 05:18 UTC
@scottleibrand I ran openaps alias show gather than ran the inivdual report `monitor-pum and got this output
root@petersrig2:~/myopenaps# openaps monitor-pump
pump://JSON/read_clock/monitor/clock.json
reporting monitor/clock.json
pump://JSON/read_temp_basal/monitor/temp_basal.json
reporting monitor/temp_basal.json
pump://JSON/iter_pump_hours/monitor/pumphistory.json
reporting monitor/pumphistory.json
tz://JSON/rezone/monitor/pumphistory-zoned.json
reporting monitor/pumphistory-zoned.json
tz://JSON/clock/monitor/clock-zoned.json
reporting monitor/clock-zoned.json
iob://text/shell/monitor/iob.json

module.js:485
    throw err;
          ^
SyntaxError: /root/myopenaps/settings/profile.json: Unexpected end of input
    at Object.parse (native)
    at Object.Module._extensions..json (module.js:482:27)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/root/src/oref0/bin/oref0-calculate-iob.js:43:22)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
reporting monitor/iob.json
meal://text/shell/monitor/meal.json
Could not parse input data:  [SyntaxError: Unexpected end of input]
reporting monitor/meal.json
pump://JSON/reservoir/monitor/reservoir.json
reporting monitor/reservoir.json
pump://JSON/read_battery_status/monitor/battery.json
reporting monitor/battery.json
pump://JSON/status/monitor/status.json
Scott Leibrand
@scottleibrand
May 28 2017 05:19 UTC
what do your profile.json and iob.json look like?
peterfulvi
@peterfulvi
May 28 2017 05:22 UTC
Do i invoke a report on it ?
```
its a pretty long output
they look the same
root@petersrig2:~/myopenaps# openaps report invoke iob.json
usage: openaps-report invoke [-h]
                             {cgm/cgm-glucose.json,cgm/ns-glucose.json,enact/enacted.json,enact/suggested.json,monitor/battery.json,monitor/cgm-glucose.json,monitor/cgm-mm-glucosedirty.json,monitor/cgm-mm-glucosetrend.json,monitor/clock-zoned.json,monitor/clock.json,monitor/glucose.json,monitor/iob.json,monitor/meal.json,monitor/mmtune.json,monitor/pumphistory-zoned.json,monitor/pumphistory.json,monitor/reservoir.json,monitor/status.json,monitor/temp_basal.json,nightscout/glucose.json,nightscout/recent-missing-entries.json,nightscout/uploaded-entries.json,raw-cgm/raw-entries.json,settings/autosens.json,settings/basal_profile.json,settings/bg_targets.json,settings/bg_targets_raw.json,settings/carb_ratios.json,settings/insulin_sensitivities.json,settings/insulin_sensitivities_raw.json,settings/model.json,settings/profile.json,settings/pumphistory-24h-zoned.json,settings/pumphistory-24h.json,settings/pumpprofile.json,settings/settings.json,upload/pebble.json,xdrip/glucose.json}
                             [{cgm/cgm-glucose.json,cgm/ns-glucose.json,enact/enacted.json,enact/suggested.json,monitor/battery.json,monitor/cgm-glucose.json,monitor/cgm-mm-glucosedirty.json,monitor/cgm-mm-glucosetrend.json,monitor/clock-zoned.json,monitor/clock.json,monitor/glucose.json,monitor/iob.json,monitor/meal.json,monitor/mmtune.json,monitor/pumphistory-zoned.json,monitor/pumphistory.json,monitor/reservoir.json,monitor/status.json,monitor/temp_basal.json,nightscout/glucose.json,nightscout/recent-missing-entries.json,nightscout/uploaded-entries.json,raw-cgm/raw-entries.json,settings/autosens.json,settings/basal_profile.json,settings/bg_targets.json,settings/bg_targets_raw.json,settings/carb_ratios.json,settings/insulin_sensitivities.json,settings/insulin_sensitivities_raw.json,settings/model.json,settings/profile.json,settings/pumphistory-24h-zoned.json,settings/pumphistory-24h.json,settings/pumpprofile.json,settings/settings.json,upload/pebble.json,xdrip/glucose.json} ...]
openaps-report invoke: error: argument report: invalid choice: 'iob.json' (choose from u'cgm/cgm-glucose.json', u'cgm/ns-glucose.json', u'enact/enacted.json', u'enact/suggested.json', u'monitor/battery.json', u'monitor/cgm-glucose.json', u'monitor/cgm-mm-glucosedirty.json', u'monitor/cgm-mm-glucosetrend.json', u'monitor/clock-zoned.json', u'monitor/clock.json', u'monitor/glucose.json', u'monitor/iob.json', u'monitor/meal.json', u'monitor/mmtune.json', u'monitor/pumphistory-zoned.json', u'monitor/pumphistory.json', u'monitor/reservoir.json', u'monitor/status.json', u'monitor/temp_basal.json', u'nightscout/glucose.json', u'nightscout/recent-missing-entries.json', u'nightscout/uploaded-entries.json', u'raw-cgm/raw-entries.json', u'settings/autosens.json', u'settings/basal_profile.json', u'settings/bg_targets.json', u'settings/bg_targets_raw.json', u'settings/carb_ratios.json', u'settings/insulin_sensitivities.json', u'settings/insulin_sensitivities_raw.json', u'settings/model.json', u'settings/profile.json', u'settings/pumphistory-24h-zoned.json', u'settings/pumphistory-24h.json', u'settings/pumpprofile.json', u'settings/settings.json', u'upload/pebble.json', u'xdrip/glucose.json')
Scott Leibrand
@scottleibrand
May 28 2017 05:32 UTC
you have to specify the relative path
so openaps report invoke monitor/iob.json for example
peterfulvi
@peterfulvi
May 28 2017 05:35 UTC
ok thats what im doing. Here is the output for iob.json
root@petersrig2:~/myopenaps# openaps report invoke monitor/iob.json
iob://text/shell/monitor/iob.json

module.js:485
    throw err;
          ^
SyntaxError: /root/myopenaps/settings/profile.json: Unexpected end of input
    at Object.parse (native)
    at Object.Module._extensions..json (module.js:482:27)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/root/src/oref0/bin/oref0-calculate-iob.js:43:22)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
reporting monitor/iob.json
now its rebooting to fix radio errors!
peterfulvi
@peterfulvi
May 28 2017 05:43 UTC
this is the output for monitor.json
root@petersrig2:~/myopenaps# openaps report invoke  monitor/status.json
pump://JSON/status/monitor/status.json
monitor/status.json  raised  /dev/spidev5.1 already in use
Traceback (most recent call last):
  File "/usr/local/bin/openaps-report", line 82, in <module>
    app( )
  File "/usr/local/lib/python2.7/dist-packages/openaps/cli/__init__.py", line 51, in __call__
    self.run(self.args)
  File "/usr/local/bin/openaps-report", line 75, in run
    output = app(args, self)
  File "/usr/local/lib/python2.7/dist-packages/openaps/cli/subcommand.py", line 52, in __call__
    return self.method.main(args, app)
  File "/usr/local/lib/python2.7/dist-packages/openaps/reports/invoke.py", line 40, in main
    output = task.method(args, app)
  File "/usr/local/lib/python2.7/dist-packages/openaps/uses/use.py", line 44, in __call__
    self.before_main(args, app)
  File "/usr/local/lib/python2.7/dist-packages/openaps/vendors/medtronic.py", line 62, in before_main
    self.setup_medtronic( )
  File "/usr/local/lib/python2.7/dist-packages/mmeowlink/vendors/mmeowlink.py", line 115, in setup_medtronic
    setup_func(self)
  File "/usr/local/lib/python2.7/dist-packages/mmeowlink/vendors/mmeowlink.py", line 75, in setup_medtronic_link
    link = builder.build(radio_type, port)
  File "/usr/local/lib/python2.7/dist-packages/mmeowlink/link_builder.py", line 16, in build
    return SubgRfspyLink(port)
  File "/usr/local/lib/python2.7/dist-packages/mmeowlink/vendors/subg_rfspy_link.py", line 55, in __init__
    self.open()
  File "/usr/local/lib/python2.7/dist-packages/mmeowlink/vendors/serial_interface.py", line 23, in open
    raise AlreadyInUseException("%s already in use" % self.device)
mmeowlink.vendors.serial_interface.AlreadyInUseException: /dev/spidev5.1 already in use
Scott Leibrand
@scottleibrand
May 28 2017 05:50 UTC
I was actually asking you to just cat those files and see if they look correct
specifically, settings/profile.json looks like it's truncated, based on the way the iob.json report is complaining
Matthias
@ceben80
May 28 2017 05:59 UTC
@peterfulvi during troubleshooting did you disable your cron job?
peterfulvi
@peterfulvi
May 28 2017 06:06 UTC
@ceben80 i ran killall -g
Matthias
@ceben80
May 28 2017 06:11 UTC
If your troubleshooting actions are taking more time for investigations I'd recommend disable the cron when performing manual openaps cmds
peterfulvi
@peterfulvi
May 28 2017 06:11 UTC
@ceben80 i just did that thanks
image.png
nothing for the profile
I ran cat for all three in that directory and got nothing
Weird
Iain
@iainct
May 28 2017 06:52 UTC
I am having trouble using the gitter search (it used to be heaps better!)... I maybe missing the obvious but I am wanting to setup oref1 (SMB) on one of my rigs, but the how to do that is not jumping out at me... where should i look? thanks
Iain
@iainct
May 28 2017 07:00 UTC
@danamlewis thank you
peterfulvi
@peterfulvi
May 28 2017 07:47 UTC
@scottleibrand im running another rig and its has the same error Old pumphistory-24h refreshError, retrying
in the same place. This is why im thinking its hardware
im waiting to get new sensors. Im also wondering if its the pump itself
This is from my other rig @scottleibrand
Starting pump-loop at Sun May 28 03:40:07 EDT 2017:
Radio ok, Listening: .No pump comms detected from other rigs
MDT cgm data retrieved
MDT cgm data reformatted
Old pumphistory: Refreshed pumphistory
{"carbs":0,"boluses":0,"mealCOB":0}
{"ratio":1.05}
{"iob":0,"activity":0,"bolussnooze":0,"basaliob":0,"netbasalinsulin":0,"hightempinsulin":0,"time":"2017-05-28T07:41:39.000Z"}
{"delta":-4,"glucose":108,"short_avgdelta":-2.44,"long_avgdelta":-0.4}
{"duration":0,"rate":1.25,"temp":"absolute"}
Adjusting basal from 1.22 to 1.3
Adjusting target_bg from 100 to 98
Adjusting sens from 35.19 to 33.5
Carb Impact: -4 mg/dL per 5m; CI Duration: 0 hours
Accel. Carb Impact: 10 mg/dL per 5m; ACI Duration: 0 hours
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
{"temp":"absolute","bg":108,"tick":-4,"eventualBG":93,"snoozeBG":93,"predBGs":{"IOB":[108,104,101,98,95,93,91,89,88,87,86,86,86]},"COB":0,"IOB":0,"reason":"COB: 0, Dev: -15, BGI: 0, ISF: 34, Target: 98; Eventual BG 93 > 89 but Min. Delta -4.00 < Exp. Delta 0.2; setting current basal of 1.3 as temp","duration":30,"rate":1.3}
pump://JSON/set_temp_basal/enact/enacted.json
reporting enact/enacted.json
{"bg":108,"temp":"absolute","snoozeBG":93,"recieved":true,"predBGs":{"IOB":[108,104,101,98,95,93,91,89,88,87,86,86,86]},"rate":1.3,"reason":"COB: 0, Dev: -15, BGI: 0, ISF: 34, Target: 98; Eventual BG 93 > 89 but Min. Delta -4.00 < Exp. Delta 0.2; setting current basal of 1.3 as temp","COB":0,"eventualBG":93,"timestamp":"2017-05-28T03:41:28.677369","duration":30,"tick":-4,"IOB":0}
Old pumphistory-24h refreshError, retrying
Listening: .No pump comms detected from other rigs
mmtune: pump://JSON/mmtune/monitor/mmtune.json
reporting monitor/mmtune.json
"916.588", 5, -57 Starting pump-loop at Sun May 28 03:42:43 EDT 2017:
Radio ok, Listening: .No pump comms detected from other rigs
MDT cgm data retrieved
MDT cgm data reformatted
Old pumphistory-24h refreshError, retrying
Listening: .No pump comms detected from other rigs
mmtune: pump://JSON/mmtune/monitor/mmtune.json
reporting monitor/mmtune.json
"916.588", 5, -67 Starting pump-loop at Sun May 28 03:44:45 EDT 2017:
Radio ok, Listening: .No pump comms detected from other rigs
MDT cgm data retrieved
MDT cgm data reformatted
Old pumphistory-24h refreshError, retrying
francesc0-cgm
@francesc0-cgm
May 28 2017 07:50 UTC
Thinking about bolussnooze...if my son starts to run or hard play after a meal i observed how loop starts zero temping immediately when it observes a drop while openaps does it later. If i set bolus snooze to zero will openaps works better with these sudden drops after meal too.
skubesch
@skubesch
May 28 2017 07:54 UTC
@scottleibrand Thanks, I have placed an order for the explorer board (backordered) and the Edison rig has unfortunately been out of stock since I've been trying to order. Is flashing really that miserable of an experience? I've only been looping one day and the wifi on my RPi has already crashed and I'd like to move forward with another setup sooner than later.
Dana Lewis
@danamlewis
May 28 2017 07:57 UTC
@francesc0-cgm I would set temp targets in the case of increased activity
@skubesch if you've been toughing it out with the Pi and the outdated docs for that, you can probably handle flashing the Edison. It's a pain in some cases, but conquerable.
Iain
@iainct
May 28 2017 08:04 UTC
@danamlewis regarding To test SMB, you'll need to run oref0-setup with a "microbolus" enable flag I am on the oref0 dev branch and have tried manually entering microbolus as an enable flag as there was no option prompted from the setup script. However I do have all the relevant options in my preference.json file. What have I missed to enable microbolus? thanks
Diadon81
@Diadon81
May 28 2017 08:05 UTC
Dears, could you explain me differences in behavior for the following settings "enableSMB_with_bolus": true,
"enableSMB_with_COB": false,
"enableSMB_with_temptarget": false
Dana Lewis
@danamlewis
May 28 2017 08:24 UTC
@iainct if you see the options, you enabled it
rsilvers129
@rsilvers129
May 28 2017 11:39 UTC
This morning I woke up to “OpenAps last looped six hours ago.” I looked at my rig, and the charging cable had pulled out and it was dead. The good news is last night I had looked at the auto-time logs and programmed my pump with the recommended basals. I woke up at 103. That is awesome. I do have a question though. NS is missing my glucose from about 3am onward. Dexcom had the data. Why is that missing from NS?
IMG_6299.PNG
FullSizeRender.jpg
rsilvers129
@rsilvers129
May 28 2017 11:52 UTC
@skubesch Flashing is one of the easiest steps in the OpenAPS process, at least on a Mac. It is 15 minutes of work. You just plug it in and copy and paste a few command lines. Just remember to be patient as it looks like it is stuck in a loop and it repeats a reboot 3-4 times, but that is a normal part of the process. The docs even say you will think it is stuck in a loop but it is not.
cameronrenwick
@cameronrenwick
May 28 2017 11:54 UTC
flashish?
aah..gotcha!
PieterGit
@PieterGit
May 28 2017 12:11 UTC
@rsilvers129 the rig only uploads a bit of cgm data each time, so if the upload fails for a while you'll miss some data. I'm planning on writing a buffered-curl that will upload when the rig is online again
rsilvers129
@rsilvers129
May 28 2017 12:13 UTC
@PieterGit I thought NightScout pulled the data from DexCom’s site using Heroku? I am using G5 Share.
rsilvers129
@rsilvers129
May 28 2017 12:32 UTC
I don’t see how the rig can effect it at all.
rsilvers129
@rsilvers129
May 28 2017 12:38 UTC
I got a no loop alert. I looked at the log and had a -99 signal. Pump was 2-3 feet from Explorer. I moved the pump to a few inches away, and the loop started working again. I just want to confirm that this is not unusual and that the RF distance is sometimes less than two feet.
rsilvers129
@rsilvers129
May 28 2017 12:47 UTC
@PieterGit This is my startup oref0-setup --dir=/root/myopenaps —serial=123456 --cgm=G5 --ns-host=https://rsilvers.herokuapp.com --api-secret=not_this
--tty=/dev/spidev5.1 --enable=' autosens autotune meal ' --radio_locale='US' --btmac='20:AB:37:1D:FA:BA'
Tim Street
@tim2000s
May 28 2017 12:48 UTC
@rsilvers129 that is a bit unusual at that distance.
Matthias
@ceben80
May 28 2017 12:49 UTC
@rsilvers129 don't post your pump serial in a public room :wink:
rsilvers129
@rsilvers129
May 28 2017 12:50 UTC
Thanks.
Martin Haeberli
@mhaeberli
May 28 2017 13:12 UTC
I haven’t looked - has anyone done an FCC-style radio antenna lobe pattern diagram for the Explorer? Bonus points for typical battery and battery location?
double-bonus points for doing it with the tuned antenna
@rsilvers129 btw what are you using for no loop alert?
rsilvers129
@rsilvers129
May 28 2017 13:28 UTC
@mhaeberli I have set up Pushover to send alerts.
Iain
@iainct
May 28 2017 13:28 UTC
@mhaeberli if you find some results on that I would be super keen to see them, my long range rig uses the Ti stick as I just cant get the range with my edison even with making the cut to tune it to 915....
Martin Haeberli
@mhaeberli
May 28 2017 14:01 UTC
@iainct naively, it would seem to me that the Edison cases I have seen the LithiumIon battery right next to the explorer. So some loose exploration with the battery as far away as possible from the Edison/Explorer MIGHT show larger range...
rsilvers129
@rsilvers129
May 28 2017 14:27 UTC
@mhaeberli Maybe the rig was horizontal and the pump was vertical polarization.
Martin Haeberli
@mhaeberli
May 28 2017 15:33 UTC
:+1:
sdneufer
@sdneufer
May 28 2017 15:47 UTC
@rsilvers129 interested in what you find out however my experience is that the edison plugged in downstairs in the kitchen (which is under our master bedroom) was looping when the pi with carelink (extended cable was next to me and right net to my pump). At first I moved the edison down to the basement, then I gave up and plugged it in (to charge the battery overnight) and it is 2 to 3 feet away from the bed. Perhaps it is dependent on which pump you are using also? I am using a 554 (Canadian).
live4sw
@live4sw
May 28 2017 15:59 UTC
Quick question - with Adafruit and Amazon both sold out on the 2000mAH lipos for a little while, what have people been using instead?
Matthias
@ceben80
May 28 2017 16:04 UTC
@live4sw did you see my link above? LiPo from AliExpress, I ordered there, only need to solder a new connector....
live4sw
@live4sw
May 28 2017 16:14 UTC
Oh hmm, I'd rather buy from Amazon or Adafruit, I have less trust in a marketplace like Aliexpress (though it's reasonable to believe they all get their inventory from the same place.
I suppose I could just use a 2500mAH from Adafruit instead
Lynne Butts
@flutelynne_twitter
May 28 2017 16:33 UTC
I believe that the 2000 lipos will be in stock again May 31st. Explorer boards mid June. Not sure about the intel with jubilinx.
PopcornPam
@PopcornPam_twitter
May 28 2017 17:50 UTC
Hi, trying to run autotune with (oref0-autotune --dir=~/myopenaps --ns-host=https://pippidog.herokuapp.com--start-date=2017-05-26)
and getting back Couldn't download ns-treatments.json
Any ideas of what might be off?
PopcornPam
@PopcornPam_twitter
May 28 2017 17:59 UTC
oh, nevermind.. there was an extra space
peterfulvi
@peterfulvi
May 28 2017 18:01 UTC
Yay! I got my loop running after 3 days of troubleshooting. I did a reset on the pump itself. Now this is my output now. Any thoughts.
{"carbs":0,"reason":"not enough glucose data to calculate carb absorption"}
PopcornPam
@PopcornPam_twitter
May 28 2017 18:02 UTC
OK, i think i have a big problem. I have autotune turned on, and my rig was running while I was on beta bionics (more for curiosity than anything...) and now autotune says my isf is 85 (i thought it was set at 60) and CSF n/a, and carbs at 16. This probably explains the higher bgs since returning to openaps
I am not sure how to fix this, since the settings in nightscout and my pump are correct. I don't undertand where in edison it is setting these new basals, and how to fix it
Dana Lewis
@danamlewis
May 28 2017 18:03 UTC
@PopcornPam_twitter to start - if you want to, turn autotune off. other options include going in and editing the autotune file back (or deleting the files from when you were off OpenAPS) to something closer to your original ISF and letting it start tuning back from scratch
PopcornPam
@PopcornPam_twitter
May 28 2017 18:04 UTC
would that be nano.autotune ?
Helene Brashear
@sillystring13
May 28 2017 18:05 UTC
@danamlewis hopefully i've done this right - I've opened an issue #851 to discuss best practices for NS data back fill and then I sent a first draft as pull request
Dana Lewis
@danamlewis
May 28 2017 18:06 UTC
@sillystring13 :+1: thanks for opening!
Helene Brashear
@sillystring13
May 28 2017 18:06 UTC
@danamlewis of course! it took me a while to figure it out - our use case is that he drops connectivity during recess and lunch, so we want to aggressively backfill data to keep things moving
i'm curious about crafting a best practices (vs. our very specific use case)
PopcornPam
@PopcornPam_twitter
May 28 2017 18:08 UTC
and if I disable autotune (I assume by running runagain?) will it default back to what the pump has on it?
Dana Lewis
@danamlewis
May 28 2017 18:09 UTC
yes. that’s the short term solution. but I would also consider deleting the data from the days you weren’t actually using OpenAPS, or putting in a revised file from yesterday for it to use that’s closer/is what’s in your pump
PopcornPam
@PopcornPam_twitter
May 28 2017 18:10 UTC
I can't figure out how to access that file
nano autotune doesn't seem to be the right command
I assume it is in this directory? root@myopenaps2:~/myopenaps/autotune#
Dana Lewis
@danamlewis
May 28 2017 18:11 UTC
It’s good that you’re trying to nano into things; but there are some other basics you should remember for learning your way around the rig and figuring out exactly what files are named and how things are structured. A re-read of this page might help: http://openaps.readthedocs.io/en/latest/docs/introduction/understand-this-guide.html
PopcornPam
@PopcornPam_twitter
May 28 2017 18:15 UTC
OK, that was super helpful, but anytime I am using nano and the file name, I get blank files... this is confusing
Dana Lewis
@danamlewis
May 28 2017 18:17 UTC
That means you are not in the right directory or there is not a file named the way you think it is named
Use ls to list the files and check what they are named
You can try cat instead do nano to check contents first, if it's easier to see what's in them
peterfulvi
@peterfulvi
May 28 2017 18:28 UTC
How do i get everything to synchronize.??
Starting pump-loop at Sun May 28 14:25:10 EDT 2017:
Radio ok, Listening: .No pump comms detected from other rigs
MDT cgm data retrieved
MDT cgm data reformatted
Profile less than 60m old
glucose.json newer than temp_basal.json
Temp refreshed
{"carbs":0,"reason":"not enough glucose data to calculate carb absorption"}
BG data is too old (it's probably this), or clock set incorrectly.  The last BG data was read at Sun May 28 2017 02:23:00 GMT-0400 (EDT) but your system time currently is Sun May 28 2017 14:26:26 GMT-0400 (EDT)
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
{"reason":"BG data is too old (it's probably this), or clock set incorrectly.  The last BG data was read at Sun May 28 2017 02:23:00 GMT-0400 (EDT) but your system time currently is Sun May 28 2017 14:26:26 GMT-0400 (EDT)"}
{"reason":"BG data is too old (it's probably this), or clock set incorrectly.  The last BG data was read at Sun May 28 2017 02:23:00 GMT-0400 (EDT) but your system time currently is Sun May 28 2017 14:26:26 GMT-0400 (EDT)"}
Waiting for ntpd to synchronize... No!
ntpd did not synchronize.
Restarting ntp (via systemctl): ntp.service.
Waiting for ntpd to synchronize... No!
ntpd did not synchronize.
Setting system time to later of Sun May 28 14:26:39 EDT 2017 or "2017-05-28T02:25:37-04:00":
(date +%s; date -d 2017-05-28T02:25:37-04:00 +%s) | sort -g | tail -1 | while read line; do sudo date -s @$line; done;
Sun May 28 14:26:39 EDT 2017
cat: enact/enacted.json: No such file or directory
glucose.json newer than pumphistory: Refreshed pumphistory
{"carbs":0,"reason":"not enough glucose data to calculate carb absorption"}
BG data is too old (it's probably this), or clock set incorrectly.  The last BG data was read at Sun May 28 2017 02:23:00 GMT-0400 (EDT) but your system time currently is Sun May 28 2017 14:27:21 GMT-0400 (EDT)
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
cameronrenwick
@cameronrenwick
May 28 2017 19:16 UTC
@peterfulvi there is something not correct with your times. How do you get BGs to NS? have you checked your phone, pump, and NS? Your BG time and system time are several hours off.
peterfulvi
@peterfulvi
May 28 2017 19:26 UTC
image.png
I have the URL correct i cannot get it to temp basal.Like i said i was getting an error code evert yime it would refresh old pum history, so i reloaded my pump settings on my actual pump. That seemed to get thiungs moving, now my loo[p is having a hard time getting in sync. NS is reading the loop but not any BG'S
Thanks . @cameronrenwick I was reading the wrong time
peterfulvi
@peterfulvi
May 28 2017 19:31 UTC
DUH!
PieterGit
@PieterGit
May 28 2017 20:14 UTC
can anybody explain the difference between the UAM, COB, aCOB, IOB prediction lines/array's of BG in determine-basal. Is the UAM one the only prediction that tries to take into account for unabsorbed carbs. If I would want a good prediction to see "hypo expected in X minutes" should I use the UAM one?
PieterGit
@PieterGit
May 28 2017 20:23 UTC
found: some link (removed) @danamlewis @scottleibrand : Is aCOB or COB the one that assumes 10 mg/dL/5m)? Is UAM BG forecast always available and the one that is the best of those 4 prediction lines/ forecasts?
Dana Lewis
@danamlewis
May 28 2017 20:24 UTC
Acob. UAM not always available.
Can you delete that link? That's a very WIP doc version that's not ready for eyes
Same info on AMA and the lines is in the regular docs
Thanks!
garykidd
@garykidd
May 28 2017 20:27 UTC
@scottleibrand yeah---just happening on one rig---good idea to try swapping edison module or explorer board (same difference I suppose) to other rig... ALso wondering if just re-running script at this point would have any effect on issues...seems to happen when coming/going from BT hotspot to/from home wifi...
PieterGit
@PieterGit
May 28 2017 20:29 UTC
the pushover notification do some of the carbsreq notification, but i noticed it doesnot warn in all cases.
so i think i'll parse the UAM array (if available) and warn for "hypo of X expected in Y minutes". If there is no UAM, I'll use the COB Bg array. Is that the best way to guestimate future BG values?
Dana Lewis
@danamlewis
May 28 2017 20:31 UTC
That's more complicated than needs to be, I think. Check for some of the TODO's in the code for some places where we've flagged needing to add carbsreq but haven't gotten to it yet - that may get closer to what you're wanting it to do
PieterGit
@PieterGit
May 28 2017 20:32 UTC
I'll have a look at the code. btw I already have direct pebble notification working, but it's integrated in oref0-pushoverso not ready to merge
Dana Lewis
@danamlewis
May 28 2017 20:32 UTC
:+1:
garykidd
@garykidd
May 28 2017 20:36 UTC
Is there supposed to be another directory with your openaps instance's name... i.e. openaps_name and openaps_name\ ?
PieterGit
@PieterGit
May 28 2017 20:40 UTC
@garykidd i only know of myopenaps and myopenaps-cgm-loop (for CGM=G4-upload)
cameronrenwick
@cameronrenwick
May 28 2017 20:54 UTC
me too..
PieterGit
@PieterGit
May 28 2017 21:17 UTC
@danamlewis : created openaps/oref0#483 for discussion. don't think i understand the code that's needed. Helps wanted, because this case quite often occurs for us.
Kendra H.S.
@Kendra_HS_twitter
May 28 2017 22:23 UTC
Hi folks. Any suggestion for this...
it.exc.GitCommandError: Cmd('git') failed due to: exit code(128)
May 28 18:21:58 eviesaps pump-loop.log: cmdline: git add monitor/mmtune.json
May 28 18:21:58 eviesaps pump-loop.log: stderr: 'fatal: Unable to create '/root/Eviesaps/.git/index.lock': File exists.
May 28 18:21:58 eviesaps pump-loop.log: If no other git process is currently running, this probably means a
May 28 18:21:58 eviesaps pump-loop.log: git process crashed in this repository earlier. Make sure no other git
May 28 18:21:58 eviesaps pump-loop.log: process is running and remove the file manually to continue.'
I've rebooted...
PieterGit
@PieterGit
May 28 2017 22:28 UTC
@Kendra_HS_twitter : if you're sure none other git processes are running ps -ef | grep git you can rm -rf /root/Eviesaps/.git/index.lock. If that doesn't work save the git for future reference and create a new one mv .git ../git-corrupted ; git init
Kendra H.S.
@Kendra_HS_twitter
May 28 2017 22:32 UTC

@PieterGit thanks for the response. I haven't dealt with this before, so I'm not totally understanding what you are saying, sorry! I had this before, but just deleted and re-installed everything! Can you help me understand?

SO I ran the first command, and got this response... what does that mean? root 7736 2700 0 18:30 pts/0 00:00:00 grep git

What is "the git", when you say save for future...
PieterGit
@PieterGit
May 28 2017 22:32 UTC
that means no other git process is running. so you can safely delete the git lock with rm -rf /root/Eviesaps/.git/index.lock (as the error suggests)
if that doesn't work, move the old .git away and recreate a new one with git init
Kendra H.S.
@Kendra_HS_twitter
May 28 2017 22:33 UTC
Okay! Thanks... Will try!
PieterGit
@PieterGit
May 28 2017 22:34 UTC
ps -ef | grep git shows all the processes that have git in their names. the only one running is the command trying to find the git processes, so it's safe to remove the lock
if a git process is running, removing the lock is not a good idea
i'll stop for toningt, but if you need more help i'm sure somebody else would be willing to help. good luck getting your rig back online. reinstalling a rig because of a broken git repo is a bit too much (and that's an understatement :smile: )
Kendra H.S.
@Kendra_HS_twitter
May 28 2017 22:36 UTC
Thats awesome. I'll try these thanks so much!
PieterGit
@PieterGit
May 28 2017 22:38 UTC
git stores it's repository information (all the inforamtion about files that are changed) in a directory /root/Eviesaps/.git. That directory / repo can get corrupt (or a git processes did not return the lock when it was ready; e.g. because you ran out of battery or the rig was out of power for some reason)