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

6th
May 2018
Andrew Kirkby
@kirkbysound
May 06 2018 00:45
@scottleibrand @danamlewis It only took 3 hours but here we are! That tallies up nicely with my report guesswork.
Screen Shot 2018-05-06 at 01.43.35.png
Thanks for both of your help, yet again.. If you're ever in Edinburgh, the juice boxes are on me :)
Scott Leibrand
@scottleibrand
May 06 2018 01:13
@mhaeberli post-dated carb corrections should help autotune and autosens, yes.
Dana Lewis
@danamlewis
May 06 2018 01:53
@kirkbysound we'll take your wifi password in lieu of juice boxes ;) don't need many of those anymore thankfully! Glad it's all sorted. Good job spotting the disparity!
Martin Haeberli
@mhaeberli
May 06 2018 04:28
@scottleibrand :+1: thx
LinnBee
@petrichordb
May 06 2018 09:37
Still struggling with future entries (Medtronic 522 and Medtronic enlites). Have done all usual troubleshooting multiple times as suggested in docs. I have now resorted to new mlab, new openAPS install, everything looks good but still getting futures, have only 1 NS profile. I spotted someone had resolved all MDT time problem by the script being changed to running some things is a different order (simpleton's explanation and it wasn't a future data issue). It appeared that the fact it could not set a time on a CGM was also in the mix. The underlying problem seems to be the data going up to the db. Suggestions welcomed.
LinnBee
@petrichordb
May 06 2018 12:28
I have weak internet at home. The android phone uses BT a lot. It is set to switch between WiFi and mobile. Overnight data flowed well. Once up and about and rig out of range, then in range, future entries appear again. There was no issue when stable and static overnight.
Martin Haeberli
@mhaeberli
May 06 2018 16:52
@scottleibrand - for the discussions yesterday about target_bg, keep in mind we are now running 0.6.0 - is there any substantial reason other than testing and feedback to cut over to dev or to the new release candidate? thx
Scott Leibrand
@scottleibrand
May 06 2018 17:12
I would read the release notes to see if you'd benefit from any of the improvements in 0.6.1-dev. If you want to test it while it's a release candidate, we could use the input. Otherwise, you can upgrade as soon as it's released.
rhysjones
@rhysjones
May 06 2018 18:53
Not sure if this is the right place. My NS sight seems to be running crazily slowly, and I'm also unable to run auto tune with attached error
any ideas?
Screen Shot 2018-05-06 at 19.53.34.png
I've checked it's not short on space (<250mb)
Martin Haeberli
@mhaeberli
May 06 2018 19:04
@scottleibrand :+1: thx
@rhysjones suggest you maybe ask in the openaps/autotune channel if you haven’t already. I’m not enough of a master in this aspect to offer more.
Martin Haeberli
@mhaeberli
May 06 2018 21:24
i’m having some issues where NightScout claims OpenAPS offline for 15-20 minutes, but papertrail logs show control is still happening. where/how best to ask? intend-to-bolus? oref0? cgm-remote-monitor? (I can send screenshots)
Jon Cluck
@cluckj
May 06 2018 21:36
@mhaeberli check the /var/log/openaps/ns-loop.log around the times that happens?
Martin Haeberli
@mhaeberli
May 06 2018 21:37
ok - back in a few - just started happening suddenly as far as I can tell in the last day or so. what’s really weird is that it sees the smbs and temp basals change, but forecasts are missing, and it claims openaps is offline in the NS pill...
Jon Cluck
@cluckj
May 06 2018 21:39
it could be something silly like the battery poll failing
LinnBee
@petrichordb
May 06 2018 22:21
Screen Shot 2018-05-06 at 23.18.44.png
Ref my messages above, I am still getting - Refreshed pumphistoryWarning: clock input Invalid Date is unzoned; please pass clock-zoned.json instead
Warning: clock input Invalid Date is unzoned; please pass clock-zoned.json instead. This is new lab and new install. I would appreciate any help with this.
Scott Leibrand
@scottleibrand
May 06 2018 22:48
@petrichordb that is a harmless warning afaik.
LinnBee
@petrichordb
May 06 2018 22:50
Ok, what about the future entries that are still appearing?
Scott Leibrand
@scottleibrand
May 06 2018 23:00
You’ll need to actually dive in and start debugging.
Figure out where they’re being reported as “future” and start debugging there to see what exactly it’s seeing, what code is declaring it “future” etc.
If you don’t yet know how to use the appropriate debugging tools, you’ll need to pair up with someone who does and give them access to look at your stuff in real time to debug it.
We’ve done all we can over Gitter I think.
LinnBee
@petrichordb
May 06 2018 23:08
Sorry, what do you mean where they are being reported as future?
Scott Leibrand
@scottleibrand
May 06 2018 23:08
First, let’s restate the problem in exact detail
What doesn’t work? What other symptoms occur when it doesn’t work?
I know you’ve shared all this before, but my memory is vague.
LinnBee
@petrichordb
May 06 2018 23:10
NS display is incomplete, for example.
Scott Leibrand
@scottleibrand
May 06 2018 23:10
Is this only a display problem? Or does it ever stop setting temps?
LinnBee
@petrichordb
May 06 2018 23:11
I am using BT a lot. WiFi connection is not often, if that matters. Not sure.
Temp targets ok.
Martin Haeberli
@mhaeberli
May 06 2018 23:12
On the one hand, I’m getting No recent valid BG found. Most recent:
on the other hand, I’m getting recent enact/smb-suggested.json: {"temp":"absolute","bg":104,"tick":-5,"eventualBG":209,"insulinReq":0,"reservoir":"192.775","deliverAt":"2018-05-06T23:08:39.000Z","sensitivityRatio":0.78,"predBGs":{"IOB":[104,99,95,90,86,82,78,74,70,66,62,58,55,51,47,43,40,39],"ZT":[104,101,98,95,92,89,87,84,81,78,76,73,70,68,66,64,62,60,59,58,57,56,56,57,57,58,59,60,62,64,66,68,70,74,79,83,88,92,97],"COB":[104,100,96,92,89,86,84,82,81,79,78,78,78,78,78,79,80,82,84,86,89,92,95,99,104,109,115,120,126,132,137,142,146,153,159,164,170,175,180,184,188,192,196,199,202,205,207,209],"UAM":[104,99,95,90,86,82,78,74,70,66,62,58,55,51,47,43,40,39]},"COB":28,"IOB":2.634,"reason":"COB: 28, Dev: 0, BGI: -3, ISF: 45, CR: 5.8, Target: 100, minPredBG 84, minGuardBG 68, IOBpredBG 39, COBpredBG 209, UAMpredBG 39; minGuardBG 68<70 56m left and 0 ~ req 0U/hr: no temp required”}
(the no recent valid BG are intermittent)
Scott Leibrand
@scottleibrand
May 06 2018 23:13
@petrichordb never mind temp targets or nightscout for the moment. The most important question is: is it ever failing to set temp basals (not looping) from the point of view of the pump?
Martin Haeberli
@mhaeberli
May 06 2018 23:13
somehow, though, that results in OpenAPS pill incorrectly saying ’32 m ago’ even though there have been abunch more recently accepted enacts ...
suggests to me two branches: a) when ‘no recent’ - what is the root cause; b) when quite recent enacts - why very stale ‘OpenAPS’ in NightScout. Probably neither are core intend-to-bolus issues
advice welcome
LinnBee
@petrichordb
May 06 2018 23:14
No
Martin Haeberli
@mhaeberli
May 06 2018 23:16
IMG_3548.PNG
the above is an example of a resulting display. Note the ‘old’ OpenAPS pill along with recent SMB postings ...
Scott Leibrand
@scottleibrand
May 06 2018 23:16
@petrichordb so it’s always looping, just not consistently telling Nightscout about it, correct?
@mhaeberli I’ve seen that as well. Not sure what is causing it, but it generally resolves itself in a couple minutes.
LinnBee
@petrichordb
May 06 2018 23:17
@Lee-S
Yes.
typo above. Amateur.
Scott Leibrand
@scottleibrand
May 06 2018 23:19
@mhaeberli We’ll probably need to catch it in the act and see what is in /api/v1/devicestatus.json at the time, vs. when it’s working.
LinnBee
@petrichordb
May 06 2018 23:20
@scottleibrand
Scott Leibrand
@scottleibrand
May 06 2018 23:20
@petrichordb ok, so we’ve confirmed it is “just” a display issue. Which specific thing is the most problematic there? The way @mhaeberli is reporting his issue is the kind of approach that works well for this kind of thing.
LinnBee
@petrichordb
May 06 2018 23:20
How do I find a de bugging buddy?
Scott Leibrand
@scottleibrand
May 06 2018 23:21
First step is what we’re doing now: clearly articulating the problem.
Then we’ll know where we need to debug.
Martin Haeberli
@mhaeberli
May 06 2018 23:21
@scottleibrand - thx - I’ll set up the curl commands to pull devicestatus.json s...
Scott Leibrand
@scottleibrand
May 06 2018 23:21
Most likely it will either be someone here or on FB Looped group.
@mhaeberli :+1: good idea
LinnBee
@petrichordb
May 06 2018 23:23
Ok. I’m afraid it’s very late here in U.K. and I will have to try this another time, unfortunately as need to call it a day.
Scott Leibrand
@scottleibrand
May 06 2018 23:23
K