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

5th
Dec 2017
Scott Leibrand
@scottleibrand
Dec 05 2017 00:34
If you’re having enough problems with decocare mis-parsing records to want to work on improving it, the proper fix would be to look at the raw pump history records and figure out what is causing the decoding error.
Unfortunately since Ben moved on we have had no one willing to do that. So the workaround of pushing the unparseable record off the last page ends up being our best solution for now.
cduarte
@cduarte
Dec 05 2017 01:02
2017-12-04_2301.png
why smb when have prediction line show down
and in the pill show is waiting 2.1m to more microbolus
alimhassam
@alimhassam
Dec 05 2017 01:15
@cduarte i guess it's because of the COB 31, was there cob at that time?
cduarte
@cduarte
Dec 05 2017 01:30
ooaa.png
yes, I aet last time at 21:29
alimhassam
@alimhassam
Dec 05 2017 01:38
so it's bolusing for that carb
cduarte
@cduarte
Dec 05 2017 02:24
I found it strange a forecast line showing very low
i understand now
alimhassam
@alimhassam
Dec 05 2017 02:35
:+1:
tepidjuice
@tepidjuice
Dec 05 2017 02:53
I have a nightscout question. I'm trying to update to 0.10.x but the node.js build keeps failing when I deploy in azure. Anyone able to help?
Ebgineer
@Ebgineer
Dec 05 2017 04:12
@endafarrell congrats! some folks are using soft cases with good success. if you'd like a hard case I can print one for you.
Tim Street
@tim2000s
Dec 05 2017 06:22
@tepidjuice I believe that’s a known problem that’s being worked on.
tepidjuice
@tepidjuice
Dec 05 2017 06:47
@tim2000s So how would I downgrade?
Tim Street
@tim2000s
Dec 05 2017 07:09
I’m not sure. Best ask in the CGM-remote-monitor channel?
Scott Leibrand
@scottleibrand
Dec 05 2017 08:22
@cduarte the prediction lines are scenarios. One such scenario is IOB-only, which shows what happens if your COB is way overestimated. But if both the COB and UAM lines show that is unlikely, it won’t use the IOB-only scenario for dosing.
tepidjuice
@tepidjuice
Dec 05 2017 08:25
@tim2000s This was the issue I had. nightscout/cgm-remote-monitor#3107 solved by repeatedly re-syncing until it deploys.
thanks
Lorenzo Sandini
@lsandini
Dec 05 2017 08:49
@tepidjuice I had trouble too upgrading, but now Sulka fixed that pesky node version compatibility problem, and deploying in azure works. Be sure you upgrade your repo to the latest version (if you want to be certain delete it and re-fork), and then redeploy. Check that your applications settings have the "WEBSITE_NODE_DEFAULT_VERSION" set to 8.9.0 before deploying. Worked for me, but took 5-6 min to deploy. Deploying to Heroku was a breeze, and I suggest you create a new NS site on Heroku instead.
Oceantragic / KevW
@OceanTragic_twitter
Dec 05 2017 08:58
BT tethering is working perfectly but the logs show 'my Bluetooth is connected to XT1068' when XT1068 is an old phone and P9000 is my new phone, so where does the XT1068 reference come from? In short I first tried Bt tethering against P9000, then tried XT1068, then went back to P9000.
Enda Farrell
@endafarrell
Dec 05 2017 09:48
@Ebgineer - re: a case - why thank you very much. Do you have a shapeways site or something similar?
Enda Farrell
@endafarrell
Dec 05 2017 09:54
@vebaba - re: SW3 - it can work, but it takes a large amount of time and effort. Perhaps it's a learning phase I have yet to go through, but I seem to need to reboot the watch after each (daily) recharge (and that's with a battery I believe to be good), then reboot the (old) android phone in order to get reliable readings. Keeping it in place is a chore too - I have a strap from https://www.freestylesticker.de/en/product/freestyle-libre-cgm-sony-smartwatch-adapter-2/ but if too loose it falls off, too tight and it itches and later hurts - I can't seem to find my Goldilocks zone ;-) At this point I can't "recommend" this as a loop cgm - but I am not waiting.
Enda Farrell
@endafarrell
Dec 05 2017 10:28
@all - odd question - but is there a setting where I can get OpenAPS's "open loop" recommendations without the rig being in communication with the pump? I've found https://openaps.readthedocs.io/en/stable/docs/walkthrough/phase-2/ but I don't think that those docs are current, and they don't address this proximity question.
Dana Lewis
@danamlewis
Dec 05 2017 10:44
You can set a % basal type to block temps being set on the pump
Probably easiest way to force an open loop
Enda Farrell
@endafarrell
Dec 05 2017 10:46
... and then carry the rig with me to work ... ta @danamlewis
Scott Leibrand
@scottleibrand
Dec 05 2017 12:37
@oceantragic the old phone name is because you haven’t removed it in bluetoothctl, so it still shows under paired-devices there.
tepidjuice
@tepidjuice
Dec 05 2017 12:51
@lsandini I have a test NS on heroku, for checking out new features, already. Updating that was very easy. I really should just forget about azure and set up a second heroku.
peterfulvi
@peterfulvi
Dec 05 2017 13:03
Can you run xdrip on an Android watch and use it with an openaps system. I'm been trying to decrease the size of everything including carrying a phone. A watch running xdrip uploading readings to my rig would be awesome. It would have to be able to be a though. Any advice?
Ebgineer
@Ebgineer
Dec 05 2017 13:03
@endafarrell The size of the case depends on what you built into your rig. This one has an edison, battery charger board, explorer board and 2000mah battery. If yours doesn't include all these components it would be shorter. https://imgur.com/a/ECcFj
Oceantragic / KevW
@OceanTragic_twitter
Dec 05 2017 13:05
I think my issue is just the message putting out the list of both phones it's ever had BT tethering set up for, as the line after it shows P9000 > @OceanTragic_twitter BT tethering is working perfectly but the logs show 'my Bluetooth is connected to XT1068' when XT1068 is an old phone and P9000 is my new phone, so where does the XT1068 reference come from? In short I first tried Bt tethering against P9000, then tried XT1068, then went back to P9000.
Oceantragic / KevW
@OceanTragic_twitter
Dec 05 2017 13:18
@scottleibrand thanks @scottleibrand , didn't see your reply, I'll take a look at bluetoothctl now
peterlynton
@peterlynton
Dec 05 2017 13:38
@peterfulvi have a look at xdrip-js. No need for a watch. It's early days but it's been running flawlessly for me.
Andrew Baugh
@baughaw
Dec 05 2017 14:02

Trying to figure out why I no longer get SMBs and I see this in the log. "SMB disabled (no enableSMB preferences active)"

I believe I have everything enabled.
"enableSMB_with_bolus": true,
"enableSMB_with_COB": true,
"enableSMB_with_temptarget": true,
"enableUAM": true

Any ideas?

Also have the hoorah msg, "Autotune exists! Hoorah! You can use microbolus-related features."
Scott Leibrand
@scottleibrand
Dec 05 2017 14:07
Do you have a temp target or COB?
The bolus one is deprecated and no longer does anything.
Andrew Baugh
@baughaw
Dec 05 2017 14:08
yep. Here is my log.
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 and meal.json
Checking pump clock: "2017-12-05T08:48:42-05:00" is within 1m of current time: Tue Dec  5 08:48:48 EST 2017
Temp refreshed
Autotune exists! Hoorah! You can use microbolus-related features.
{"carbs":17,"nsCarbs":17,"bwCarbs":0,"mealCOB":14,"currentDeviation":7.99,"maxDeviation":6.66,"minDeviation":-2.11,"slopeFromMaxDeviation":0,"slopeFromMinDeviation":1.509,"allDeviations":[8,7,3,0,-1,-2,-2,-2,-2],"lastCarbTime":1512480725000,"bwFound":false}
{"iob":0.077,"activity":-0.0005,"basaliob":-0.118,"bolusiob":0.195,"netbasalinsulin":-0.05,"bolusinsulin":0.2,"time":"2017-12-05T13:48:47.000Z","iobWithZeroTemp":{"iob":0.077,"activity":-0.0005,"basaliob":-0.118,"bolusiob":0.195,"netbasalinsulin":-0.05,"bolusinsulin":0.2,"time":"2017-12-05T13:48:47.000Z"},"lastBolusTime":1512480725000,"lastTemp":{"rate":2.125,"timestamp":"2017-12-05T08:38:28-05:00","started_at":"2017-12-05T13:38:28.000Z","date":1512481108000,"duration":11.44}}
{"delta":8,"glucose":161,"short_avgdelta":8.44,"long_avgdelta":4.85,"date":1512481492000}
Autosens ratio: 1.01; Adjusting basal from 1.05 to 1.1; ISF from 74.7 to 73.9; CR: 25
currenttemp: { duration: 21, rate: 2.125, temp: 'absolute' } lastTempAge: 10 m tempModulus: 1 m
SMB disabled (no enableSMB preferences active)
Limiting carb impact from 7.8 to 7.4 mg/dL/5m ( 30 g/h )
Last carbs 17 minutes ago; remainingCATime: 3.4 hours; 18% carbs absorbed
Carb Impact: 7.4 mg/dL per 5m; CI Duration: 0.9 hours; remaining CI (~2h peak): 0 mg/dL per 5m
predCIs (mg/dL/5m): 7 6 5 5 4 3 3 2 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
remainingCIs:       0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
UAM Impact: 7.8 mg/dL per 5m; UAM Duration: 1.3 hours
minPredBG: 196 minIOBPredBG: 198 minZTGuardBG: 161 minCOBPredBG: 195 avgPredBG: 196 COB: 14 / 17
BG projected to remain above 150 for 240 minutes
naive_eventualBG: 155 bgUndershoot: -60 zeroTempDuration: 240 zeroTempEffect: 315 carbsReq: -137
Checking deliverAt: 2017-12-05T13:48:57.779Z is within 1m of current time: Tue Dec  5 08:48:57 EST 2017
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"temp":"absolute","bg":161,"tick":"+8","eventualBG":202,"insulinReq":0.62,"reservoir":"45.35","deliverAt":"2017-12-05T13:48:57.779Z","sensitivityRatio":1.01,"predBGs":{"IOB":[161,168,174,180,185,189,193,196,199,200,202,202,202,202,202,202,202,202,202,202,202,202,202,202,202,201,201,201,201,200,200,199,199,198],"ZT":[161,161,161,162,162,162,163,163,164,164],"COB":[161,168,174,180,185,189,192,195,197,198,199,199,199,199,199,199,199,199,199,199,199,199,199,199,199,198,198,198,198,197,197,197,196,196,195]},"COB":14,"IOB":0.077,"reason":"COB: 14, Dev: 47, BGI: 0, ISF: 74, CR: 25, Target: 150, minPredBG 196, minGuardBG 168, IOBpredBG 198, COBpredBG 195; temp 2.125<2.35U/hr.  21m left and 2.125 ~ req 2.35U/hr: no temp required"}
No smb_enact needed. Temp refreshed: monitor/temp_basal.json: {"duration":21,"rate":2.125,"temp":"absolute"}
No bolus needed (yet). Settings less than 15 minutes old. Edison on battery: 84%. Pumphistory-24 < 30m old
Completed oref0-pump-loop at Tue Dec 5 08:49:06 EST 2017
ok, I will kill the bolus one from my preferences file.
Enda Farrell
@endafarrell
Dec 05 2017 14:22
@Ebgineer ta for the image :-) My rig seems smaller - an Edison plus a Rev 1.3 Explorer Board (which also serves as the battery charger) and a battery. Can't remember if it's the 2000 or 2500 mAh. Given my work, I'd need one that fits either into a jeans pocket or could be hung on a belt - couldn't tell from the image whether the green example would?
peterfulvi
@peterfulvi
Dec 05 2017 14:37
@peterlynton Wow. I'm not very code save but it looks like I would install and run the script on my rig and pai
pair
My transmitter to it. Correct?
Ebgineer
@Ebgineer
Dec 05 2017 14:54
It's 65x45x35 mm. Not outfitted with a belt clip but would fit in a pocket easily. You'd probably save 10mm thickness without the separate battery charger board so 65x45x25 mm. Also consider a soft case from www.tallygear.com or elsewhere http://openaps.readthedocs.io/en/master/docs/Gear%20Up/edison.html?highlight=case
Velibor Maric
@vebaba
Dec 05 2017 15:23
@endafarrell I use Blukon and I find it OK for intended use...
Enda Farrell
@endafarrell
Dec 05 2017 15:38
@Ebgineer ta - very much obliged. i'll give them a good look later.
@vebaba been thinking about it too - good to hear that someone is actually looping with it without too many headaches :-)
Enda Farrell
@endafarrell
Dec 05 2017 15:45
@vebaba 2 qq: "Trans AM" or "Nightrider"? And, is "Blukon" the same as nightscout/android-uploader or is it a hardware source within xDrip/xDrip+?
peterlynton
@peterlynton
Dec 05 2017 16:28
@peterfulvi Yes that's correct. We're running a parallel conversation in xdrip-js so lets move it over there :)
Martin Haeberli
@mhaeberli
Dec 05 2017 19:34
pseudo - random question - has anyone had luck using IFTTT and/or pushover and Alexa / Echo to make an audible alert on Alexa when, for example, a low is predicted?
rdobb
@rdobb
Dec 05 2017 19:45
Hi - New here but been watching Omnipod on Slack... Endo wants us to switch from Omnipod to Tslim... Any Open APS news on Tslim x2?
PopcornPam
@PopcornPam_twitter
Dec 05 2017 22:00
Hi all, I have been having a connection issue lately when tethering. I am running the latest master, and tethering to iphone 8. This all started a few weeks ago when I updated to a new dev branch (since switched to master). When I leave wifi my phone shows it is connected to the rig, but openaps does not run.
Papertrail stops running as soon as I leave wifi
Dec 05 15:49:43 myopenaps2 ns-loop.log: {"BG":162,"IOB":0.903,"rate":null,"duration":null,"units":null}
Dec 05 16:05:22 myopenaps2 pushover.log: No additional carbs or bolus required.
Thoughts?
Mike
@libxmike
Dec 05 2017 22:01
@rdobb why he wants you to switch? dont you have the freedom of what you want to use?
bjarecki
@bjarecki
Dec 05 2017 22:13
Anyone have any more detail about why a minimum DIA of 3 was added? The change is here openaps/oref0@e2ee0a6 I trying to understand how a value of 2 would interfere with bolus snooze. I had a rig die and 2 weeks ago and went ahead and upgraded and found the DIA of 2 I have used for years was not valid. I have tried 3 for the last 2 weeks and my sugars have not been this high since I started looping. Just looking to understand why this was implemented before I remove it my local.
philipgo
@philipgo
Dec 05 2017 22:19
@bjarecki Actually, any DIA under 5h will be changed to 5h. This has to do with the new exponential insulin activity curves: openaps/oref0#568
PieterGit
@PieterGit
Dec 05 2017 22:29
@drnoname82 @bjarecki : i wonder if the medtronic boluswizard algorithm also uses the DIA setting and if so, how. Does anybody know that? We also had/have issues with to high sugars. Part of it was explainable because we used multiple CR and ISF profiles, which are not supported by oref0/autotune yet. But I now wonder if it would not be better to have a clear distinquish between a DIA setting for the pump (and the pump BolusWizard) and a DIA setting for oref0/openaps. Thoughts?
bjarecki
@bjarecki
Dec 05 2017 22:34
@drnoname82 Okay well I guess I will revert back to my old build. Thanks.
@PieterGit Medtronics Bolus wizard has had a DIA setting as far back as I can recall, every docc and Medtronic rep who has looked at my settings always questioned my 2 hour setting
@PieterGit but it has been what worked for me for years
PieterGit
@PieterGit
Dec 05 2017 22:42
@bjarecki : we used DIA=3 on the pump previously, but I wonder if now oref0 uses DIA=5 by minimum, it would be benefical for me to use DIA=3 in the pump (for BolusWizard) and let oref0 use DIA=5 (the minimum) for oref0/openaps algorithms. The android nsclient app warns for small DIA's < 5 now , see https://github.com/MilosKozak/AndroidAPS/blob/2a62b47be751653749c1d61c7b7960d617884d33/app/src/main/java/info/nightscout/androidaps/plugins/Insulin/InsulinOrefBasePlugin.java#L54-L59
@bjarecki : do you use multiple CR's or ISF and have run autotune to make sure your CR's and ISF (and basals) are correct?
looking through the source, shouldn't https://github.com/openaps/oref0/blob/174ef43c7f5dfb7a9c3f578bf38a939d4bccb034/lib/iob/total.js#L22-L26 use a DIA minimum of 5 instead of 3?
philipgo
@philipgo
Dec 05 2017 22:47

@PieterGit @bjarecki Medtronic Bolus Wizard uses DIA to calculate IOB. However, it does this in a relatively primitive way using a linear insulin activity curve.

The exponential insulin curves are a huge step forward but of course since we all have always had to make things work with a much simpler model, changing to a model that much better resembles what actually happens will require some changes to carb ratios, basals etc. If you look at the exponential curves you will see that the insulin tail is long but very thin, so the difference between 3 and 5 hours is not as big as it seems. Since the the "new" insulin curves are much closer to physiology and the "old" curves will be deprecated, I think it is worth tuning your settings for the new ones.

PieterGit
@PieterGit
Dec 05 2017 22:47
bjarecki
@bjarecki
Dec 05 2017 22:54
@PieterGit I use a single ISF and multiple CR. @drnoname82 I hear you and that is why I gave it 2 weeks to autotune, but at this point I am just not happy with the result. You can call it a big step forward but the old build worked better and the simple fact is that I have years of experience as taking novolog and know after 2 hours it has negligible effect in my body
PieterGit
@PieterGit
Dec 05 2017 22:55
@drnoname82 : i'm still in the process of tuning them, but purely using the autotune profiles leads to either too high or too low results, i now solved it by using limiting autosens_min to 0.99, to make sure autotune does not change the ISF too far down.
rdobb
@rdobb
Dec 05 2017 22:57
@libxmike Sorry bad terminology - 1st its for my son, second that's the recommendation... Not forcing us to do anything. We have omnipod now but he is having terrible skin reactions so the thought was to move to a tubed unit. But I wanted to really use something that we could use Open APS on... so wanted to know if there was any headway on Tslim...
PieterGit
@PieterGit
Dec 05 2017 23:00
@bjarecki @drnoname82 do you also use Medtronic Bolus wizard?
@bjarecki setting insulinPeakTime and useCustomPeakTime work in your case? (did not try it myself)
I'm off to bed. I will be happy to have more discussion about correct DIA-usage later on.
philipgo
@philipgo
Dec 05 2017 23:31
@PieterGit We did use it, but since we never entered BG, DIA had no influence on bolus suggestions. Now we use Fiasp+eSMB+ultra-rapid curve and only bolus a tiny fraction of the required insulin up front and let OpenAPS handle the rest. Pump DIA thus has no influence anymore unless we set it to more than 5h (which we did, it is set to 6h since we had problems with lows in the middle of the night that could only explained by remaining meal time insulin activity)
fidoman
@efidoman
Dec 05 2017 23:40
@scottleibrand - I did a PR / branch proposing an enhancement to oref0-pushover that will optionally leverage the pushover glances api for smartwatch complications. Let me know if I did the PR wrong. I'm still new to git. openaps/oref0#856
Dave Acklam
@dcacklam
Dec 05 2017 23:52
Question in-re the various radio devices:
1) Does anyone know when the pi-hat explorer device will be out?
2) Do any of the alternatives to the explorer hardware and/or the carelink work without being JTAGEd
3) If No to (2), is there a cheaper option than the GoodFET for flashing it?
@scottleibrand
In-re yesterday's conversation, I was unable to make the 'new' 0.61-dev oref0-pump-loop work with my 712. I went back to the 'old' loop logic that was working, from when I pushed up those commits a few months back.