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

27th
Nov 2018
Dana Lewis
@danamlewis
Nov 27 2018 00:25
@scottleibrand seeing a couple of people with not-complete installs lately on dev. wonder if we need to error out better..or if there's something else going on
Scott Leibrand
@scottleibrand
Nov 27 2018 00:25
If anyone with an incomplete install could capture the output from the end of the install, that would help figure out what's going on
Deweyoxberg
@Deweyoxberg
Nov 27 2018 00:31

Question please: Ever since the fall time change, with a rig in JST (which does not change forward/back), errors similar to the following keep popping up and messing with reliable looping:
pump-loop.log: enact/smb-suggested.json: {"temp":"absolute","deliverAt":"2018-11-24T21:30:18.181Z","reason":"Warning: currenttemp rate 0.4 != lastTemp rate 0 from pumphistory; canceling temp","duration":0,"rate":0}

Is this fixable? If so, how?

Dana Lewis
@danamlewis
Nov 27 2018 00:31
@Deweyoxberg are you running multiple rigs, or a single rig?
Deweyoxberg
@Deweyoxberg
Nov 27 2018 00:32
Single
Dana Lewis
@danamlewis
Nov 27 2018 00:32
and are you setting any manual temps?
Deweyoxberg
@Deweyoxberg
Nov 27 2018 00:32
None that I'm aware of at the
Ack. At thw moment
Dana Lewis
@danamlewis
Nov 27 2018 00:33
k that's a bug then. what version are you running?
Deweyoxberg
@Deweyoxberg
Nov 27 2018 00:33
And asked the person with the edison and confirmed nope
Version ... Eh, can i check via paper trail? I believe we're on master and haven't gone into dev branches.
Dana Lewis
@danamlewis
Nov 27 2018 00:34
k. likely that you're on 0.6.2-ish?
Deweyoxberg
@Deweyoxberg
Nov 27 2018 00:34
Yep. Familiar version number. :)
Dana Lewis
@danamlewis
Nov 27 2018 00:35
k. are you on SMB? is it otehrwise (other times) SMB'ing correctly?
Deweyoxberg
@Deweyoxberg
Nov 27 2018 00:35
Supermicro? Yep and yep.
Just dawned on me. Rig is on jst which doesn't change time for daylight savings, but nightscout's server time would slide yes?
Dana Lewis
@danamlewis
Nov 27 2018 00:39
yes - that's probably it. try changing rig TZ and see if that fixes?
Deweyoxberg
@Deweyoxberg
Nov 27 2018 00:40
Ehhh, was hoping not having to do that because then I'd have to do it every time. Also doesn't that break stuff? Was reading about the command for that last night. Have to reread it
Or would a time change for the Nightscout profile do the trick too?
Ie: if its 1200 entered now, back it up an hour to 1100
Or... Forward i mean. Long day.
Almost home. Will tackle now that i know where to look. Thank you. And yes will report back :)
Deweyoxberg
@Deweyoxberg
Nov 27 2018 00:58
Ah, nightscout already has a timezone in the profile editor. Okay, timezone change on the rig then. Checking docs.
Scott Leibrand
@scottleibrand
Nov 27 2018 01:15
you should be able to set the rig to a TZ that doesn't change
the error you pasted doesn't look to me like a TZ thing: you might try manually setting a new temp basal and see if it clears up on the next pumphistory read
Deweyoxberg
@Deweyoxberg
Nov 27 2018 01:27
Will do, and thank you :)
#DiabeticinJapan
@LuminaryXion_twitter
Nov 27 2018 01:47
Hi! I'm the T1D that Dewey is helping
I wanted to give some potentially additional context. This happens after the rig sets a temporary basal. It sets the basal like this;
Nov 27 09:43:03 DiabeticinJapan pump-loop.log: enact/smb-suggested.json: {"temp":"absolute","bg":134,"tick":"+0","eventualBG":116,"insulinReq":0.49,"reservoir":"112.2","deliverAt":"2018-11-27T00:43:03.370Z","sensitivityRatio":1,"predBGs":{"IOB":[134,134,134,133,133,132,132,131,130,129,129,128,126,125,125,124,123,122,121,121,120,120,119,119,118,118,118,117,117,117,116,116,116,116,116,115,115,115,115,115,115,115,115,115,115,115,115,114],"ZT":[134,132,130,129,127,125,124,123,121,120,119,119,118,117,117,117,116,116,116,117,117,117,118,118,119,119],"UAM":[134,133,133,131,129,128,126,125,123,122,121,120,119,118,117,116,115,114,113,113,112,112,111,111,110,110,110,109,109,109,108,108,108,108,108,107]},"COB":0,"IOB":0.418,"reason":"COB: 0, Dev: 11, BGI: -2, ISF: 70, CR: 9, Target: 80, minPredBG 114, minGuardBG 107, IOBpredBG 114, UAMpredBG 107; Eventual BG 116 >= 80, no temp, setting 1.3U/hr. ","duration":30,"rate":1.3}
Nov 27 09:43:07 DiabeticinJapan pump-loop.log: Temp refreshed: monitor/temp_basal.json: {"duration":0,"rate":0,"temp":"absolute"}
Nov 27 09:43:10 DiabeticinJapan pump-loop.log: enact/smb-enacted.json: "Rate: 1.3 Duration: 30"
Nov 27 09:43:13 DiabeticinJapan pump-loop.log: Temp refreshed: monitor/temp_basal.json: {"duration":30,"rate":1.3,"temp":"absolute"}
then, a few minutes later:
Nov 27 09:46:31 DiabeticinJapan pump-loop.log: enact/smb-suggested.json: {"temp":"absolute","deliverAt":"2018-11-27T00:46:30.993Z","reason":"Warning: currenttemp rate 1.3 != lastTemp rate 0.7 from pumphistory; canceling temp","duration":0,"rate":0}
#DiabeticinJapan
@LuminaryXion_twitter
Nov 27 2018 01:53
possibly of relevant notice is the line above this which says:
Nov 27 09:46:31 DiabeticinJapan pump-loop.log: currenttemp: { duration: 28, rate: 1.3, temp: 'absolute' } lastTempAge: 59 m tempModulus: 27 m
I can confirm that it is correctly setting the temp basal, so it's just not seeing the setting in the pump history when it goes to check.
#DiabeticinJapan
@LuminaryXion_twitter
Nov 27 2018 02:15
here, it just happened now:
Nov 27 11:12:00 DiabeticinJapan pump-loop.log: enact/bolused.json: {"insulinReq":0.56,"status":"normal","_type":"BolusRequest","bg":136,"bolusing":true,"reservoir":"102.0","requested":{"units":0.1,"params":[1]},"timestamp":"2018-11-27T11:12:00.350076","raw":"00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000","rate":1.4,"COB":0,"eventualBG":128,"suspended":false,"duration":30,"tick":"+3","deliverAt":"2018-11-27T02:11:25.382Z","received":true,"temp":"absolute","predBGs":{"ZT":[136,134,133,131,130,128,127,125,124,123,122,121,120,119,119,118,117,117,117,117,117,117,117,117,117,118,118,119,119],"UAM":[136,138,140,141,141,141,140,138,137,135,134,133,131,130,129,128,127,126,125,124,123,122,121,120,120,119,118,118,117,117,116,116,115,115,115,114,114,114,114,113],"IOB":[136,139,141,143,144,146,146,147,147,147,146,145,144,143,141,140,139,138,137,136,135,134,134,133,132,131,131,130,130,129,129,128,128,127,127,127,126,126,126,126,126,125]},"reason":"COB: 0, Dev: 28, BGI: -2, ISF: 70, CR: 9, Target: 80, minPredBG 119, minGuardBG 112, IOBpredBG 125, UAMpredBG 113; Eventual BG 128 >= 80, insulinReq 0.56; maxBolus 0.1. Microbolusing 0.1U. temp 0.8<1.4U/hr. ","sensitivityRatio":1,"units":0.1,"IOB":0.521}
Nov 27 11:12:01 DiabeticinJapan pump-loop.log: Settings less than 15 minutes old. Edison battery at 64% is charged (>= 98%) or likely charging (60-70%). Pumphistory-24 < 15m old
Nov 27 11:12:38 DiabeticinJapan pump-loop.log: Pump profile refreshed; Settings refreshed; Refreshed pumphistory and meal.json
Nov 27 11:12:45 DiabeticinJapan pump-loop.log: IOB: null
Nov 27 11:12:45 DiabeticinJapan pump-loop.log: Your instance of oref0 [0.6.2, master] is out-of-date by 10 commits: you may want to consider updating.
Nov 27 11:12:45 DiabeticinJapan pump-loop.log: Please make sure to read any new documentation and release notes that accompany the update.
Nov 27 11:12:45 DiabeticinJapan pump-loop.log: Completed oref0-pump-loop at Tue Nov 27 11:12:45 JST 2018
Nov 27 11:13:02 DiabeticinJapan pump-loop.log: Starting oref0-pump-loop at Tue Nov 27 11:13:02 JST 2018 with 8 second wait_for_silence:
Nov 27 11:13:02 DiabeticinJapan pump-loop.log: Retrying without waiting for new BG
Nov 27 11:13:14 DiabeticinJapan pump-loop.log: Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Nov 27 11:13:50 DiabeticinJapan pump-loop.log: Preflight OK. Profile less than 60m old; Profile valid. Refreshed pumphistory and meal.json
Nov 27 11:13:53 DiabeticinJapan pump-loop.log: Checking pump clock: "2018-11-27T11:13:51+09:00" is within 90s of current time: Tue Nov 27 11:13:53 JST 2018
Nov 27 11:14:00 DiabeticinJapan pump-loop.log: Temp refreshed
Nov 27 11:14:04 DiabeticinJapan pump-loop.log: Autotune exists! Hoorah! You can use microbolus-related features.
Nov 27 11:14:04 DiabeticinJapan pump-loop.log: {"carbs":0,"nsCarbs":0,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":7.68,"maxDeviation":7.68,"minDeviation":-0.92,"slopeFromMaxDeviation":0,"slopeFromMinDeviation":2.466,"allDeviations":[8,8,4,-1,-1,5],"lastCarbTime":0,"bwFound":false}
Nov 27 11:14:04 DiabeticinJapan pump-loop.log: {"iob":0.558,"activity":0.0048,"basaliob":0.558,"bolusiob":0,"netbasalinsulin":1.8,"bolusinsulin":0,"time":"2018-11-27T02:13:54.000Z","iobWithZeroTemp":{"iob":0.558,"activity":0.0048,"basaliob":0.558,"bolusiob":0,"netbasalinsulin":1.8,"bolusinsulin":0,"time":"2018-11-27T02:13:54.000Z"},"lastBolusTime":1543253158000,"lastTemp":{"rate":0.8,"timestamp":"2018-11-27T10:56:21+09:00","started_at":"2018-11-27T01:56:21.000Z","date":1543283781000,"duration":18.61}}
Nov 27 11:14:04 DiabeticinJapan pump-loop.log: {"delta":3,"glucose":136,"noise":1,"short_avgdelta":5,"long_avgdelta":3.22,"date":1543284530757}
Nov 27 11:14:04 DiabeticinJapan pump-loop.log: Autosens ratio: 1; Basal unchanged: 0.3; ISF unchanged: 70; CR: 9
Nov 27 11:14:04 DiabeticinJapan pump-loop.log: currenttemp: { duration: 29, rate: 1.4, temp: 'absolute' } lastTempAge: 18 m tempMo
Nov 27 11:14:04 DiabeticinJapan pump-loop.log: Autosens ratio: 1; Basal unchanged: 0.3; ISF unchanged: 70; CR: 9
Nov 27 11:14:04 DiabeticinJapan pump-loop.log: currenttemp: { duration: 29, rate: 1.4, temp: 'absolute' } lastTempAge: 18 m tempModulus: 17 m
Nov 27 11:14:04 DiabeticinJapan pump-loop.log: 2018-11-27T02:14:04.020Z
Nov 27 11:14:04 DiabeticinJapan pump-loop.log: Checking deliverAt: 2018-11-27T02:14:04.020Z is within 1m of current time: Tue Nov 27 11:14:04 JST 2018
Nov 27 11:14:04 DiabeticinJapan pump-loop.log: and that smb-suggested.json is less than 1m old
Nov 27 11:14:04 DiabeticinJapan pump-loop.log: enact/smb-suggested.json: {"temp":"absolute","deliverAt":"2018-11-27T02:14:04.020Z","reason":"Warning: currenttemp rate 1.4 != lastTemp rate 0.8 from pumphistory; canceling temp","duration":0,"rate":0}
Scott Leibrand
@scottleibrand
Nov 27 2018 02:18
You might have better luck with 0.7.0 dev. It has completely new pump comms code.
#DiabeticinJapan
@LuminaryXion_twitter
Nov 27 2018 02:30
ok, thanks. :)
Monali Patel
@mhp118
Nov 27 2018 03:53
@scottleibrand and @danamlewis tried updating Dev and got the following error:
root@OpenAPS:~/src/oref0# cd ~/src/oref0 && git checkout dev && git pull
Already on 'dev'
error: object file .git/objects/93/3ab236887c55cb3419d960dfdf665dc9df7811 is empty
fatal: loose object 933ab236887c55cb3419d960dfdf665dc9df7811 (stored in .git/objects/93/3ab236887c55cb3419d960dfdf665dc9df7811) is corrupt
root@OpenAPS:~/src/oref0#
Scott Leibrand
@scottleibrand
Nov 27 2018 04:13
easiest fix for that is to remove the ~/src/oref0 directory and re-clone it
Cas Eliëns
@cascer1
Nov 27 2018 09:04
@scottleibrand here's the result of openaps-install I had a few days ago
Cas Eliëns
@cascer1
Nov 27 2018 09:29
RE: failing installs on dev
Scott Leibrand
@scottleibrand
Nov 27 2018 13:17
What did you end up doing to resolve that one?
Cas Eliëns
@cascer1
Nov 27 2018 15:23
nothing
I restored a backup and called it a night
Didn't have time to mess with it more I'm afraid
I think it might be an issue with some outdated npm installation
I don't see npm in openaps-packages so I guess we're depending on the default one in raspbian?
Cas Eliëns
@cascer1
Nov 27 2018 15:30
I also tried changing the order of the npm commands as suggested in openaps/oref0#1150 but that didn't work
all on the 2018-11-13 release of raspbian
fidoman
@efidoman
Nov 27 2018 17:01
@scottleibrand - Now I'm missing the basal profile updates to NS. ns-loop.log shows the following. Could this be another thing that my install missed?
Starting oref0-ns-loop at Tue Nov 27 12:00:02 EST 2018:
Glucose file is fresh
{"glucose":254,"dateString":"2018-11-27T11:55:35.206000-05:00"}
Latest NS temptargets: {"target":80,"duration":30,"start":"2018-11-27T11:57:52.786Z"}
Merging local temptargets: Temptargets merged: {"target":80,"duration":30,"start":"2018-11-27T11:57:52.786Z"}
Refreshed carbhistory; COB: 0
{"batteryVoltage":3886,"battery":71}
{"BG":254,"IOB":5.333,"rate":null,"duration":null,"units":null}
No new treatments to upload
Completed oref0-ns-loop at Tue Nov 27 12:00:17 EST 2018
Scott Leibrand
@scottleibrand
Nov 27 2018 18:07
I don't think automatic basal profile uploads to NS are supported yet in dev. I think there is a PR open for that, though, if you'd like to test it so we can merge it.
fidoman
@efidoman
Nov 27 2018 18:40
Sure - I will test. What's the PR#?
Dana Lewis
@danamlewis
Nov 27 2018 19:24
I'm thinking it's openaps/oref0#1098
fidoman
@efidoman
Nov 27 2018 20:42
My issue is the openaps set basal rate/duration and units is being picked up as null. NS isn't showing the icicle basal rates established by openaps. Is this related to autotune?
Dana Lewis
@danamlewis
Nov 27 2018 20:44
what does your profile look like in your NS?
dmdfreak
@dmdfreak
Nov 27 2018 23:24
I've installed to a newly built pi zero rig. Seems to be working over wifi, but I'm having issues setting it up for bluetooth. I'm getting
root@piztim:~# sudo: /usr/local/bin/bluetoothd: command not found
sudo /usr/local/bin/bluetoothd --experimental
sudo: /usr/local/bin/bluetoothd: command not found
[4]   Exit 1                  sudo /usr/local/bin/bluetoothd --experimental
root@piztim:~# sudo hciconfig hci0 name $HOSTNAME
Can't change local name on hci0: Network is down (100)
root@piztim:~# bluetoothctl
Waiting to connect to bluetoothd...
djnoor
@djnoor
Nov 27 2018 23:36
Is the Medtronic Guardian Connect CGM compatible with OpenAPS?
Dave Acklam
@dcacklam
Nov 27 2018 23:40
@djnoor
Guardian, as in the 670G's CGM?
Isn't that heavily integrated with the 670G pump?

@cascer1

You will need the nodesource repo to get nodejs working... The default versions in the various Raspbian iterations are very old

I ran into this same issue the last time I did a git pull - had to move to a more recent verison of node.js than the one I had been using, or install would fail.
Jon Cluck
@cluckj
Nov 27 2018 23:48
They've finally updated nodejs to 8 in the latest raspbian
dmdfreak
@dmdfreak
Nov 27 2018 23:56
Is the pi zero able to tether through Bluetooth?