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

19th
May 2018
Travis Cannell
@diabeticpilot
May 19 2018 03:31
I'm on the .7-dev branch and started getting pump update fails today after I added a Meter ID to the pump. I got BG sent to the pump from logger a few times, then it started throwing these errors and stopped looping. Any ideas on how to fix? I tried rebooting the rig and rebooting the pump with no luck.
May 18 20:23:29 bearpanks pump-loop.log: Pump history update failed. Last record 2018-05-18T18:49:31-07:00
May 18 20:23:32 bearpanks pump-loop.log: Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
May 18 20:23:32 bearpanks pump-loop.log: Continuing oref0-pump-loop at Fri May 18 20:23:32 PDT 2018
May 18 20:23:32 bearpanks pump-loop.log: Retry 2 of invoke_pumphistory_etc
May 18 20:23:40 bearpanks pump-loop.log: Pump history update failed. Last record 2018-05-18T18:49:31-07:00
May 18 20:23:46 bearpanks pump-loop.log: Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
May 18 20:23:46 bearpanks pump-loop.log: Continuing oref0-pump-loop at Fri May 18 20:23:47 PDT 2018
May 18 20:23:46 bearpanks pump-loop.log: Retry 3 of invoke_pumphistory_etc
May 18 20:23:51 bearpanks pump-loop.log: Pump history update failed. Last record 2018-05-18T18:49:31-07:00
May 18 20:23:51 bearpanks pump-loop.log: Couldn't invoke_pumphistory_etc - continuing
May 18 20:23:51 bearpanks pump-loop.log: Retry 1 of monitor_pump
May 18 20:23:58 bearpanks pump-loop.log: Pump history update failed. Last record 2018-05-18T18:49:31-07:00
May 18 20:23:58 bearpanks pump-loop.log: Retry 1 of invoke_pumphistory_etc
May 18 20:24:07 bearpanks pump-loop.log: Pump history update failed. Last record 2018-05-18T18:49:31-07:00
May 18 20:24:11 bearpanks pump-loop.log: Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
May 18 20:24:11 bearpanks pump-loop.log: Continuing oref0-pump-loop at Fri May 18 20:24:11 PDT 2018
May 18 20:24:11 bearpanks pump-loop.log: Retry 2 of invoke_pumphistory_etc
May 18 20:24:19 bearpanks pump-loop.log: Pump history update failed. Last record 2018-05-18T18:49:31-07:00
May 18 20:24:26 bearpanks pump-loop.log: Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
May 18 20:24:26 bearpanks pump-loop.log: Continuing oref0-pump-loop at Fri May 18 20:24:26 PDT 2018
May 18 20:24:26 bearpanks pump-loop.log: Retry 3 of invoke_pumphistory_etc
May 18 20:24:33 bearpanks pump-loop.log: Pump history update failed. Last record 2018-05-18T18:49:31-07:00
May 18 20:24:33 bearpanks pump-loop.log: Couldn't invoke_pumphistory_etc - continuing
May 18 20:24:36 bearpanks pump-loop.log: Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
May 18 20:24:36 bearpanks pump-loop.log: Continuing oref0-pump-loop at Fri May 18 20:24:36 PDT 2018
May 18 20:24:36 bearpanks pump-loop.log: Retry 2 of monitor_pump
May 18 20:24:44 bearpanks pump-loop.log: Pump history update failed. Last record 2018-05-18T18:49:31-07:00
May 18 20:24:44 bearpanks pump-loop.log: Retry 1 of invoke_pumphistory_etc
May 18 20:24:52 bearpanks pump-loop.log: Pump history update failed. Last record 2018-05-18T18:49:31-07:00
May 18 20:27:18 bearpanks pump-loop.log: Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
May 18 20:27:18 bearpanks pump-loop.log: Continuing oref0-pump-loop at Fri May 18 20:24:55 PDT 2018
May 18 20:27:18 bearpanks pump-loop.log: Retry 2 of invoke_pumphistory_etc
Jon Cluck
@cluckj
May 19 2018 03:41
can you paste stuff from pump-loop.log?
Travis Cannell
@diabeticpilot
May 19 2018 03:45
where is that log located?
Jon Cluck
@cluckj
May 19 2018 03:46
if you enter l into the command line, it'll bring it up for you
Travis Cannell
@diabeticpilot
May 19 2018 03:47
Pump history update failed. Last record 2018-05-18T18:49:31-07:00
Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Fri May 18 20:45:42 PDT 2018
Retry 3 of invoke_pumphistory_etc
Pump history update failed. Last record 2018-05-18T18:49:31-07:00
Couldn't invoke_pumphistory_etc - continuing
Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Fri May 18 20:45:49 PDT 2018
Retry 2 of monitor_pump
Pump history update failed. Last record 2018-05-18T18:49:31-07:00
Retry 1 of invoke_pumphistory_etc
Pump history update failed. Last record 2018-05-18T18:49:31-07:00
Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Fri May 18 20:46:10 PDT 2018
Retry 2 of invoke_pumphistory_etc
Pump history update failed. Last record 2018-05-18T18:49:31-07:00
Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Fri May 18 20:46:24 PDT 2018
Retry 3 of invoke_pumphistory_etc
Pump history update failed. Last record 2018-05-18T18:49:31-07:00
Couldn't invoke_pumphistory_etc - continuing
Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Fri May 18 20:46:38 PDT 2018
Retry 3 of monitor_pump
Pump history update failed. Last record 2018-05-18T18:49:31-07:00
Retry 1 of invoke_pumphistory_etc
Pump history update
Jon Cluck
@cluckj
May 19 2018 03:49
is it showing indications of being able to communicate with the pump, like preflight ok and stuff?
Travis Cannell
@diabeticpilot
May 19 2018 03:50
Looks like it is mmtuning.. Yeah you can see preflight ok
Pump history update failed. Last record 2018-05-18T18:49:31-07:00
Couldn't invoke_pumphistory_etc - continuing
Couldn't monitor_pump - continuing
Couldn't refresh_pumphistory_and_meal
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 29 s silence before mmtuning
Listening: ..No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Fri May 18 20:47:33 PDT 2018
Listening for 29 s silence before mmtuning: Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Fri May 18 20:48:04 PDT 2018
mmtune: "916.700", 3, -65 -- "916.750", 3, -65 waiting for 10 second silence before continuing
Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Fri May 18 20:48:37 PDT 2018
Preflight OK. Done waiting for rigs with better signal.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Fri May 18 20:48:39 PDT 2018
i'll try re-running setup
Jon Cluck
@cluckj
May 19 2018 03:55
yeah, it could be something weird in the pump history that it's having trouble parsing
I'm not sure I'm awake enough to help with that tonight, sorry :\
Travis Cannell
@diabeticpilot
May 19 2018 04:04
thanks anyway!
Dana Lewis
@danamlewis
May 19 2018 04:15
@diabeticpilot what type of rig?
Travis Cannell
@diabeticpilot
May 19 2018 04:15
edison
Dana Lewis
@danamlewis
May 19 2018 04:16
I'd switch to master or dev then if you want to get it up and running tonight
Travis Cannell
@diabeticpilot
May 19 2018 04:16
:+1:
I do like those new go libraries. So fast and good on the battery :)
Travis Cannell
@diabeticpilot
May 19 2018 05:23
Now it looks like the dev branch is having problems for me too with a comms exception
Radio check failed. mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?
Listening for 40s silence before mmtuning: ....................................................................................................................................................................................................
Tim Gunn
@Tornado-Tim
May 19 2018 05:35
How old is the batteries on your pump?
Travis Cannell
@diabeticpilot
May 19 2018 05:36
i added a new battery about an hour ago
Tim Gunn
@Tornado-Tim
May 19 2018 05:36
your on the edison correct?
Travis Cannell
@diabeticpilot
May 19 2018 05:36
yeah
Tim Gunn
@Tornado-Tim
May 19 2018 05:37
might be worthwhile checking the seating on the breakout board and make sure its flush.....
(ie: all the contact pins on the connector are flat)
naboull1
@naboull1
May 19 2018 05:38

:~ $ sudo npm run global-install
npm ERR! Error: ENOENT: no such file or directory, open '/home/pi/package.json'
npm ERR! at Error (native)
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/npm/npm/issues

npm ERR! System Linux 4.14.34+
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "run" "global-install"
npm ERR! cwd /home/pi
npm ERR! node -v v4.8.2
npm ERR! npm -v 1.4.21
npm ERR! path /home/pi/package.json
npm ERR! syscall open
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/pi/npm-debug.log
npm ERR! not ok code 0

@danamlewis . i tried installing your branch but not sure of the code to do it

hamishsprocket
@hamishsprocket
May 19 2018 09:22
I've just tried to update my rig to 0.6.1 I've followed the documentation as closely as I can, but haven't been able to establish a loop since running the script. The problem appears to be that bg data is too old. Xdrip is updating to Nightscout, but it looks like my rig is not getting data from nightscout. I've checked and it shouldn't be an Mlab issue. Any suggestions about what my next step should be? Thanks!
hamishsprocket
@hamishsprocket
May 19 2018 09:53
@hamishsprocket I reran the setup script and have it looping now.
Travis Cannell
@diabeticpilot
May 19 2018 14:23
I'm still having some radio errors. Anyone know how to reset the radio or otherwise fix it? There are some strange errors that the system is throwing
May 19 07:11:55 bearpanks pump-loop.log:  mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?
May 19 07:11:55 bearpanks pump-loop.log:  Radio check failed. mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?
May 19 07:14:32 localhost remote_syslog:  2018-05-19 14:14:31 INFO  remote_syslog.go:202 Forwarding file: /var/log/openaps/pump-loop.log
May 19 07:15:03 bearpanks pump-loop.log:  Starting oref0-pump-loop at Sat May 19 07:15:03 PDT 2018 with 2 second wait_for_silence:
May 19 07:15:04 bearpanks pump-loop.log:  Waiting up to 4 minutes for new BG: ls: cannot access /tmp/pump_loop_completed: No such file or directory
May 19 07:15:09 bearpanks pump-loop.log:  Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
May 19 07:15:42 bearpanks pump-loop.log:  Preflight OK. Old pumphistory-24h, waiting for 2 seconds of silence: Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
May 19 07:16:09 bearpanks pump-loop.log:  Old pumphistory-24h refreshed
May 19 07:16:37 bearpanks pump-loop.log:  Profile less than 60m old; Profile valid. Refgrep: monitor/status.json: No such file or directory
May 19 07:16:37 bearpanks pump-loop.log:  cat: monitor/status.json: No such file or directory
May 19 07:16:38 bearpanks pump-loop.log:  /usr/local/bin/oref0-pump-loop: line 491: test: ==: unary operator expected
May 19 07:16:38 bearpanks pump-loop.log:  cat: monitor/status.json: No such file or directory
May 19 07:16:40 bearpanks pump-loop.log:  /usr/local/bin/oref0-pump-loop: line 492: test: ==: unary operator expected
May 19 07:16:40 bearpanks pump-loop.log:  cat: monitor/status.json: No such file or directory
May 19 07:16:40 bearpanks pump-loop.log:  Couldn't refresh_pumphistory_and_meal
May 19 07:16:40 bearpanks pump-loop.log:  oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
May 19 07:17:22 bearpanks pump-loop.log:  Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Jon Cluck
@cluckj
May 19 2018 15:07
are you using an x12 pump?
the radio problem seems to be intermittent, could you have two instances of openaps running?
Travis Cannell
@diabeticpilot
May 19 2018 15:20
I have an x15 pump
how could I tell if I have 2 instances running?
I tried going back to the latest dev but that didn't help so I'm reinstalling the 0.7.0-dev branch
Travis Cannell
@diabeticpilot
May 19 2018 15:26
i'll reflash the radio next
Jon Cluck
@cluckj
May 19 2018 15:32
hmm, could oref0-pump-loop be crashing into fakemeter? @alimhassam @efidoman
Travis Cannell
@diabeticpilot
May 19 2018 15:34
it seemed that this all started when I added the meter ID and then I started getting BGs to the pump
Scott Leibrand
@scottleibrand
May 19 2018 15:35
@naboull1 you forgot to cd ~/src/oref0 first.
naboull1
@naboull1
May 19 2018 15:36
ill try that now thanks
Jon Cluck
@cluckj
May 19 2018 15:36
yeah....
@diabeticpilot rm /usr/local/bin/fakemeter?
Travis Cannell
@diabeticpilot
May 19 2018 15:38
I can try removing that... the 0.7.0-dev branch is throwing "full pump history refresh failed"
naboull1
@naboull1
May 19 2018 15:40

tried still nothing im stuck on this error

Radio check failed. ImportError: No module named spi_serial

Listening for 40s silence before mmtuning: ........

Travis Cannell
@diabeticpilot
May 19 2018 15:40
also if I try 'killall -g oref0-pump-loop; openaps mmtune' I get a "Not an openaps environment, run: openaps init"
Jon Cluck
@cluckj
May 19 2018 15:41
you need to be in ~/myopenaps/ for openaps commands to work, and there's a different (not yet documented) way of doing mmtune with 0.7.0-dev
Travis Cannell
@diabeticpilot
May 19 2018 15:43
would it be worth it to try that?
Jon Cluck
@cluckj
May 19 2018 15:43
nah, try removing fakemeter
naboull1
@naboull1
May 19 2018 15:43

i can see when i check the setup file in the bin folder the text contains the update that @danamlewis made adding the pump.ini to auto add the carelink usb is there

however im still stuck with the carelink not being detected
@scottleibrand

Jon Cluck
@cluckj
May 19 2018 15:43
do you still have xdrip-js running?
Travis Cannell
@diabeticpilot
May 19 2018 15:43
do I need to do anything other than the rm command you posted?
I ran that and I'll reboot
naboull1
@naboull1
May 19 2018 15:44
is there a command to check if its is being detected? @scottleibrand
Jon Cluck
@cluckj
May 19 2018 15:45
@diabeticpilot :thumbsup:
Travis Cannell
@diabeticpilot
May 19 2018 15:47
:worried:
May 19 08:46:31 bearpanks pump-loop.log: Preflight OK. Profile less than 60m old; Profile valid. Full history refresh failed. 
May 19 08:46:31 bearpanks pump-loop.log: Retry 1 of invoke_pumphistory_etc
May 19 08:46:43 bearpanks pump-loop.log: Full history refresh failed. 
May 19 08:46:43 bearpanks pump-loop.log: Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
May 19 08:46:43 bearpanks pump-loop.log: Continuing oref0-pump-loop at Sat May 19 08:46:39 PDT 2018
May 19 08:46:43 bearpanks pump-loop.log: Retry 2 of invoke_pumphistory_etc
Jon Cluck
@cluckj
May 19 2018 15:47
failures are going to happen sometimes, give it a bit :)
alimhassam
@alimhassam
May 19 2018 16:02
@diabeticpilot fakemeter works for me on 0.7.0 with logger.
You can try to tail the xdrip-js logs to see if it's working or causing issues
From your log it seems like pumphistory is not working but other pump communication works?
You can also try to run the pumphistory command manually (when the loop isn't using the radio) it might give a more descriptive error message
Dana Lewis
@danamlewis
May 19 2018 16:06
@naboull1 sorry, not sure what else to try. @MilosKozak got it to work after setting carelink=on in the file; you could try changing the text to that just to make sure it doesn't make a difference . And if not, he may be able to share if there was anything else he did to get it to work
alimhassam
@alimhassam
May 19 2018 16:06
(Sorry I'm on mobile otherwise I would Right the full command to try)
Ah @diabeticpilot just saw you have an x15 pump could that cause pumphistory parsing issues?
Jon Cluck
@cluckj
May 19 2018 16:14
have we tested 0.7.0-dev on an x15 before?
naboull1
@naboull1
May 19 2018 16:15
@danamlewis ill try starting from scratch fresh sd card format. if i install again from the documentation. would that include the updates you made or would i have to install the branch separately after?
Dana Lewis
@danamlewis
May 19 2018 16:18
Nah, the setup script installs master, so you'll want to switch to the fix-carelink branch after.
(Or just modify the text yourself in the file from master)
Probably faster 🙃
alimhassam
@alimhassam
May 19 2018 16:19
@cluckj seems like at least @diabeticpilot was successful on x15 until he started haven't meter BG records. Could that be the issue?
Eric
@ecc1
May 19 2018 16:20
@cluckj I don't think I ever tried x15. I have one in my test bin, so I'll fire it up and check that we can parse its history
Jon Cluck
@cluckj
May 19 2018 16:21
@alimhassam that's what I'm thinking? it may be storing BG records in pump history or something strange like that...
and pumphistory can't parse it
@ecc1 :thumbsup: thanks
kallnap
@kallnap
May 19 2018 16:26
I do not have my 715 anymore, so I can´t test but @AdrianLxM my be able to double check ;-)
Travis Cannell
@diabeticpilot
May 19 2018 16:27
@ecc1 @cluckj 0.7.0-dev was working for several days really well. Issue happened last night when I added in that meter ID
now it is mmtuning, etc but just failing to make any read or coms with the pump
Scott Leibrand
@scottleibrand
May 19 2018 16:28
Obvious question: did you try removing the meter ID?
Eric
@ecc1
May 19 2018 16:29
Bingo: after running fakemeter, I get an unknown record type in the 515's history. I'll fix it this afternoon, but I have a meeting to go to soon.
Travis Cannell
@diabeticpilot
May 19 2018 16:29
yes and turned off "meter options"
@cluckj also just saw your question: yes, logger is still working and posting BGs to NS
Jon Cluck
@cluckj
May 19 2018 16:31
haha nice :D
Eric
@ecc1
May 19 2018 16:31
Unfortunately it will keep failing until either the history is flushed out or I get you a fix :-(
Jon Cluck
@cluckj
May 19 2018 16:31
(nice that you found the problem)
Travis Cannell
@diabeticpilot
May 19 2018 16:33
yay! found the error. And shoot, no easy way to fix. No problem. Any simple way to flush the history?
Jon Cluck
@cluckj
May 19 2018 16:34
@diabeticpilot it looked like you got a pumphistory refresh on 0.6.1, so switch back to that until it can be patched?
Travis Cannell
@diabeticpilot
May 19 2018 16:35
.6.1 was still throwing errors and never looped
Eric
@ecc1
May 19 2018 16:36
Yeah, it looks like that history record (type 05) isn't handled yet by either decocare or @ps2's minimedkit (my usual cheat-sheets), so a little sleuthing will be in order
Jon Cluck
@cluckj
May 19 2018 16:37
oh no
@diabeticpilot do you have a backup pump?
this is a "not working today" not a "broken forever" problem, don't worry :)
Travis Cannell
@diabeticpilot
May 19 2018 16:38
no :worried: but at least logger is getting my BGs
yeah I can go back to doing things manually and remember what that was like :)
and we found a good bug on 0.7.0-dev that can break the x15 pumps too, so that's a win :)
Jon Cluck
@cluckj
May 19 2018 16:41
it's a pretty nice bug
it'll "fix itself" on your pump 27 hours from whenever logger stopped sending BGs to your pump too
Eric
@ecc1
May 19 2018 16:57
Hmm, might not be a new history record, but a different size for a known record on just that model of pump ... more later
Scott Leibrand
@scottleibrand
May 19 2018 17:38
You can flush the pump history if you set up a while loop to continuously cancel temp basals until it fills up all the history pages.
Jon Cluck
@cluckj
May 19 2018 17:39
obliterate-pump-history.sh
that's a lot of history pages
fidoman
@efidoman
May 19 2018 18:28
@cluckj - I haven't ever had a case where fakemeter caused a problem with oref0-pump-loop. Doesn't mean it can't happen. I suggest that @diabeticpilot try turning off the meter on his pump and see if the problem goes away. If so, that definitely points in that direction.
Jon Cluck
@cluckj
May 19 2018 18:28
I think we found it, it's an x15 + fakemeter issue :)
fidoman
@efidoman
May 19 2018 18:29
Ahh ... sneaky one
Travis Cannell
@diabeticpilot
May 19 2018 19:37
@efidoman yeah I did try that btw, the meter is set to off on my pump now
Eric
@ecc1
May 19 2018 20:57
@diabeticpilot I have a first cut at handling the x15 history more robustly; do you have some time to retrieve some pump history data for me?
live4sw
@live4sw
May 19 2018 23:09
Have been getting blank screen (sometimes allowing me to turn on backlight) and A17/A21 errors a couple times recently only a few days into a new battery on my 522. Figure it might be a bad set of lithium AAA's so I'm trying a new package, and might replace the battery cap as well (some very slight wear), but anything else people have noticed/tried?
Jon Cluck
@cluckj
May 19 2018 23:17
@rollerdecom still looping?