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

19th
Jan 2018
mkericson
@mkericson
Jan 19 2018 01:31
So I noticed my rig lost its loop while at work, reset a few times, still nothing. Seemed to be running hotter than normal. When I logged in tonight the view the status "l" it stops with an invalid date error. When I reboot is shows a few failures and lists this:
[ 17.333626] pca953x 1-0023: failed reading register
[ 18.096096] pmic_ccsm pmic_ccsm: Error reading battery profile from battid frmwrk
[ 18.109095] pmic_ccsm pmic_ccsm: Battery0 temperature outside boundary
any thoughts?
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
Martin Haeberli
@mhaeberli
Jan 19 2018 02:40
@scottleibrand are there recent published notes on Pi + Explorer HAT ? if so, where?
mkericson
@mkericson
Jan 19 2018 02:45
When I bash runagain I get this error: Continue? y/[N] y
Removing any existing git
Removed any existing git
Checking openaps 0.2.1 installation with --nogit support
openaps 0.2.1-dev
Checking /root/myopenaps: mkdir: cannot create directory ‘/root/myopenaps’: File exists
/root/myopenaps initialized
mv: error writing ‘./oref0-runagain.sh’: No space left on device
mv: failed to extend ‘./oref0-runagain.sh’: No space left on device
/root/src/decocare/ already exists; pulling latest 0.1.0-dev
fatal: unable to write new index file
Couldn't pull latest decocare 0.1.0-dev
Would you say my Edison the issue
Ebgineer
@Ebgineer
Jan 19 2018 03:06
@mkericson It looks like you are out of disk space
may want to see if there are any excess log files that can be deleted
mkericson
@mkericson
Jan 19 2018 03:09
@Ebgineer You mean disk space on the 'edison'? As I cleaned mLab a few weeks ago
mkericson
@mkericson
Jan 19 2018 03:18
Thanks. this is what I found:
118M ./root/src/decocare
229M ./root/src
245M ./root
781M ./var/log
181M ./var/cache/apt
185M ./var/cache
1.1G ./var
1.4G .
mkericson
@mkericson
Jan 19 2018 03:35
781M ./log
133M ./cache/apt/archives
181M ./cache/apt
185M ./cache
1.1G .
When I run this: logrotate -f /etc/logrotate.conf _ it gives me errors that the files already exist.
If delete some of these log files will get me back up. Any particular one I can purge without running into further issues?
mkericson
@mkericson
Jan 19 2018 04:45
OK purged some of the log files and got total disk size down to 784M. reran the setup script.
Now I'm getting these errors when booting: [ OK ] Started Initialize hardware monitoring sensors.
[FAILED] Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
See 'systemctl status dnsmasq.service' for details.
[DEPEND] Dependency failed for Host and Network Name Lookups.
Starting Load/Save RF Kill Switch Status of rfkill3...
[ OK ] Reached target Bluetooth.
Any Thoughts?
jzycom123
@jzycom123
Jan 19 2018 06:00
Has anyone used a pebble watch? Can you help me set?
help!
Dana Lewis
@danamlewis
Jan 19 2018 07:15
@jzycom123 unfortunately, Pancreabble is not a well documented option. Most people are relying on internet connectivity currently for watch display.
jzycom123
@jzycom123
Jan 19 2018 07:16
@danamlewis thank you!
Scott Leibrand
@scottleibrand
Jan 19 2018 07:17
@mkericson those warnings are normal I believe.
jzycom123
@jzycom123
Jan 19 2018 07:17
@scottleibrand @danamlewis I would like to have a plan without a cell phone, I think this watch can be achieved.
Scott Leibrand
@scottleibrand
Jan 19 2018 07:17
@hichameyessou it’s easiest to modify oref0-runagain and re-run it to modify your API_SECRET.
jzycom123
@jzycom123
Jan 19 2018 07:20
I have to connect the watch with EDISON, no matter how hard it is.
Scott Leibrand
@scottleibrand
Jan 19 2018 08:10
It can be done, but we personally do not use it, so won’t be much help beyond the limited documentation.
@mhaeberli check out the hardware-dev channel and mailing list to start.
jzycom123
@jzycom123
Jan 19 2018 08:14
@scottleibrand Oh, that is to say, this does not have any effect?
RamiLaakso
@RamiLaakso
Jan 19 2018 08:17
Running oref0 successfully about 5 months. It's been so carefree, that I have forgotten the early couple of weeks of troubleshooting.
I have checked the troubleshooting documentation, but did not find where to start with this one.
We have MDT pump. Since last night NS is showing the BG values fine, but rig is not sending any temp basal commands. And we ended up having a sweaty hypo at night. Of course, I noticed the rig issue only this morning, 10 minutes before the son left for school, so I could not investigate more, just rebooted the rig. That did not help. Can someone already give a hint on where to start in the evening, when I'm with the rig again? There are no future values or events in the DB.
Scott Leibrand
@scottleibrand
Jan 19 2018 08:43
@jzycom123 I don’t understand what you mean by “this”.
@RamiLaakso start by checking the rig logs.
jzycom123
@jzycom123
Jan 19 2018 08:45
@scottleibrand pebble and connect the edison has no effect?
Scott Leibrand
@scottleibrand
Jan 19 2018 08:46
You can certainly do that. I just can’t help you with it.
jzycom123
@jzycom123
Jan 19 2018 08:48
@scottleibrand Ok, thank you!
Martin Haeberli
@mhaeberli
Jan 19 2018 09:11
@scottleibrand thx!
jzycom123
@jzycom123
Jan 19 2018 09:50
@scottleibrand Add cron entry to start the microservice at startup,what should I do?
RamiLaakso
@RamiLaakso
Jan 19 2018 09:53
@scottleibrand Thanks, I would have. But finally, after the kid was in school for 4 hours, rig just finally did a temp basal. There would have been reason earlier already. I will browse the logs anyway in the evening, to learn if it happens again.
jzycom123
@jzycom123
Jan 19 2018 13:57

Pair
Start daemon: systemctl start bluetooth

Pair using bluetoothctl:

power on
agent on
scan on
... wait ...
scan off
pair <dev>
Create serial device: rfcomm bind 0 <dev>

What should I do at this step? Create serial device: rfcomm bind 0 <dev>?
Can anyone help me?
Peter Miller
@ochenmiller
Jan 19 2018 19:13
hi @jzycom123 , I have pebble/edison/pancreable working on a few rigs. It looks like you're most of the way there with pancreabble. The instructions at the bottom of the readme have most of the info. Once you've paired the device you need to sudo rfcomm bind hci0 <mac address>. This is all assuming you've installed and configured urchin on the pebble from an alternate source (phone). Once this is all set up, it's reliable and works really well.
live4sw
@live4sw
Jan 19 2018 21:38
I haven't inputted or consumed carbs in 4 hours, however, I just started getting SMBs, with a recent log entry of Jan 19 16:29:28 [rig name] pump-loop.log: enact/bolused.json: {"insulinReq":1.36,"status":"normal","_type":"BolusRequest","bg":144,"bolusing":true,"reservoir":"115.0","requested":{"units":0.4,"params":[4]},"timestamp":"2018-01-19T16:29:28.392733","raw":"00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000","rate":2.1,"COB":30,"eventualBG":241,"suspended":false,"duration":30,"tick":"+3","deliverAt":"2018-01-19T21:28:57.951Z","received":true,"temp":"absolute","predBGs":{"ZT":[144,143,142,141,141,140,140,140,140,140,140,140,141,141,142,143,144,144],"COB":[144,146,148,149,152,154,156,158,160,163,165,167,169,172,174,176,178,181,183,185,187,189,192,194,196,198,200,202,204,206,208,210,212,214,216,218,220,222,224,226,228,230,231,233,235,237,239,241],"UAM":[144,143,142,141,141,140,140,139,139,138,138,138,137,137,137,137,136,136,136,136,136,135,135,135,135,135,134,134,134,134,134,134,134,133,133,133,133,133,133,133,133,133,133,133,132],"IOB":[144,146,147,148,149,151,152,152,153,153,153,153,153,153,152,152,152,152,151,151,151,151,151,150,150,150,150,150,150,149,149,149,149,149,149,149,148]},"reason":"COB: 30, Dev: 17, BGI: -1, ISF: 50, CR: 9.15, Target: 115, minPredBG 183, minGuardBG 140, IOBpredBG 148, COBpredBG 241, UAMpredBG 132; insulinReq 1.36; maxBolus 0.4. Microbolusing 0.4U. adj. req. rate: 3.55 to maxSafeBasal: 2.1, temp 0.85<2.1U/hr. ","sensitivityRatio":1,"units":0.4,"IOB":0.295}
I'm sure there's a good explanation for this, just trying to understand what it is
I thought I just had enable SMB with COB, but I don't know where the COB: 30 comes from since I last inputted carbs 4 hours ago
(when I had 30g of carbs)
the carbs are now starting to decay on a normal rate and are now down to 27, but i'm still flummoxed as to where they originally came from
live4sw
@live4sw
Jan 19 2018 21:46
The 30g of carbs appeared to pop up on carbhistory a few minutes prior:
Jan 19 16:25:49 [rig name] ns-loop.log: Refreshed carbhistory; COB: 0
Jan 19 16:27:49 [rig name] ns-loop.log: Refreshed carbhistory; COB: 30
It's weird as well, since the COB pill on NS says that my last carbs were 4 hours ago when I last inputted in IFTTT
Scott Leibrand
@scottleibrand
Jan 19 2018 21:48
Check the files in the monitor/ directory
kenkotch
@kenkotch
Jan 19 2018 21:51
hey all, my nightscout site is not showing that it is connected to my pump, though my openaps is communicating w/ it. when i run openaps upload i get this: ~# openaps upload
Not an openaps environment, run: openaps init root@TheBrain:~# openaps init Traceback (most recent call last): File "/usr/local/bin/openaps", line 170, 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", line 155, in run builtins.dispatch(args, self) File "/usr/local/lib/python2.7/dist-packages/openaps/builtins.py", line 44, in dispatch command(args) File "/usr/local/lib/python2.7/dist-packages/openaps/init.py", line 6, in init if args.args[1] == '--nogit': IndexError: list index out of range
any ideas what i am doing wrong?
live4sw
@live4sw
Jan 19 2018 21:51
@scottleibrand I'm in the monitor directory, which file should I be looking at?
i cat'ed carbhistory.json, shows last IFTTT input of 30g of carbs at T17:38
I assume that's UTC, since I inputted 30g at 12:38 EST
The NS pill has me with 24g of carbs on board (the phantom 30g from 17 minutes ago, decayed), despite the mouseover saying last carbs at 12:38pm
Dana Lewis
@danamlewis
Jan 19 2018 22:12
@kenkotch cd myopenaps first
Scott Leibrand
@scottleibrand
Jan 19 2018 22:13
@live4sw any carbs in pumphistory?
live4sw
@live4sw
Jan 19 2018 22:16
Only entries in pumphistory.json are TempBasal, TempBasalDuration, and Bolus entries
Goes back about an hour
Scott Leibrand
@scottleibrand
Jan 19 2018 22:16
And -merged?
live4sw
@live4sw
Jan 19 2018 22:18
nope, just TempBasal, TempBasalDuration, and Bolus entries. that file goes back to yesterday
that should make sense i would think, since I never use bolus wizard on my pump to input carbs
i only use IFTTT
kenkotch
@kenkotch
Jan 19 2018 22:21
Screen Shot 2018-01-19 at 3.20.19 PM.png
@danamlewis duh. thanks. upload is successful but i still have this on nightscout:
live4sw
@live4sw
Jan 19 2018 22:22
is it possible this is UAM working? otherwise this is confusing/unexpected, to see something like this:
image.png
(the phantom 30g has decayed to 15g now)
Dana Lewis
@danamlewis
Jan 19 2018 22:24
@kenkotch read the NS troubleshooting docs for all the next steps (make sure you're on latest NS, check for future entries, and check mlab size and donate data before/if you need to delete anything)
Scott Leibrand
@scottleibrand
Jan 19 2018 22:24
You might want to manually run the commands that oref0-pump-loop is running to calculate the COB
and possibly add some debugging to the code to see what it’s doing and why.
Or run oref0-pump-loop with debugging turned on (see comments at the top)
kenkotch
@kenkotch
Jan 19 2018 22:26
thanks @danamlewis ill take a look
live4sw
@live4sw
Jan 19 2018 23:53
I'm going to try to do debugging tonight, but something seems like it could be an oref0 problem. I don't see how these two lines can be internally consistent, regardless of what the loop is doing:
Jan 19 17:42:38 [rig name] pump-loop.log:  Last carbs 302 minutes ago; remainingCATime: 10.6 hours; 82% carbs absorbed
Jan 19 17:44:27 [rig name] pump-loop.log: {"carbs":50,"nsCarbs":50,"bwCarbs":0,"mealCOB":8,"currentDeviation":-1.68,"maxDeviation":1.17,"minDeviation":-1.66,"slopeFromMaxDeviation":-0.321,"slopeFromMinDeviation":0,"allDeviations":[-2,-2,-1,1,1,-1,-1,-1,1],"lastCarbTime":1516383521040,"bwFound":false}
that there would be COB, but last carbs listed as 302 minutes ago (which is accurate, my last carbs at that point had been 5h2m ago)
unless this is how UAM works
a little nervewracking - this is my daytime rig, and so it was easy to have some rescue carbs, and I have my nighttime rig maxIOB set lower, but seeing COB pop up out of nowhere (and not be consistent with what the rig is reporting in the logs) is worrisome