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

13th
Mar 2019
samueldemers2
@samueldemers2
Mar 13 00:13
@cluckj I just ran the lines of code you proposed me, then I ran the setup script again, but the log still show the same problem (preflight fail).
I must have run all the scripts about 12 times since sunday morning, but the loop log show the same problem everytime.
samueldemers2
@samueldemers2
Mar 13 00:18
@cluckj As i suspect a mmtune problem i tried to manually preform an mmtune (as shown in the troubleshoot) and here what I got
root@sadem1:~# cd ~/myopenaps && sudo service cron stop && killall -g openaps ; killall -g oref0-pump-loop; oref0-mmtune && sudo service cron start
openaps: no process found
oref0-pump-loop: no process found
mmtune: 2019/03/12 20:16:10 cannot connect to CC111x radio on /dev/spidev0.0
2019/03/12 20:16:10 /dev/spidev0.0: device is in use
monitor/mmtune.json is empty or does not exist
vsherbeck
@vsherbeck
Mar 13 01:30
Having some issues still
fatal: unable to access 'https://github.com/cluckj/oref0/': gnutls_handshake() failed: Error in the push function.
Couldn't pull latest oref0
this was during an attempt to do the startup script. I did the git pull and performed global install again without problems, though.
vsherbeck
@vsherbeck
Mar 13 01:42
guess I'll try global install and all again
CuriousFirefly
@CuriousFirefly
Mar 13 02:04

Hello All! I am trying to setup my Pi0 rig with Explorer Hat. Working from a Windows computer, in NA.

I keep getting stuck on global-install. I get several ‘deprecated warnings’, then a string of ‘npm ERR!’ that starts like this:

root@fireflypi:~/src/oref0# npm run global-install
(node:1462) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.

oref0@0.7.0-dev global-install /root/src/oref0
npm install && sudo npm link && sudo npm link oref0 && sudo npm install -g

(node:1477) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
npm WARN deprecated istanbul@0.4.5: This module is no longer maintained, try this instead:
npm WARN deprecated npm i nyc
npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.
npm ERR! cb() never called!
npm ERR! not ok code 0

… see file.

I tried the suggestion for troubleshooting global-install (link below), but when I get to oref0-setup.sh, it comes back as:

-bash: /root/src/oref0-setup.sh: No such file or directory

Any help/direction on how to proceed would be immensely appreciated.

My prior coding skills top out at learning html in high school, so I have mostly been following documentation verbatim. However, I’m excited for this project and eager to learn!

vsherbeck
@vsherbeck
Mar 13 02:13
so I just tried an install with build from source but still failed to reach the cron questions in my setup

npm ERR! cb() never called!
npm ERR! not ok code 0

npm ERR! oref0@0.7.0-dev global-install: npm install && sudo npm link && sudo npm link oref0 && sudo npm install -g
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the oref0@0.7.0-dev global-install script.
npm ERR! This is most likely a problem with the oref0 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! npm install && sudo npm link && sudo npm link oref0 && sudo npm install -g
npm ERR! You can get their info via:
npm ERR! npm owner ls oref0
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 4.14.98+
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "run" "global-install"
npm ERR! cwd /root/src/oref0
npm ERR! node -v v8.11.1
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /root/src/oref0/npm-debug.log
npm ERR! not ok code 0
/root/src/oref0/bin/oref0-setup.sh: line 759: oref0-get-profile: command not found

samueldemers2
@samueldemers2
Mar 13 02:15
@vsherbeck i guess you are runing npm run global-install
vsherbeck
@vsherbeck
Mar 13 02:15
that was reported during the interactive setup actually... but yeah, I did that just prior ?
samueldemers2
@samueldemers2
Mar 13 02:16
So you didn't got the same problem as i did.
mkericson
@mkericson
Mar 13 02:16
I was able to find and Edison EDI2.SPOF.AL.MP but does not have the ceramic antenna. Is that something I can add / solder on?
CuriousFirefly
@CuriousFirefly
Mar 13 02:19
@vsherbeck your output just posted is identical to what I get when I run global install. I am wondering what we are both doing wrong...
vsherbeck
@vsherbeck
Mar 13 02:20
Yeah, we did have a couple lines in common at least. Mine mentions telling the author so maybe I should tag @cluckj :p
are you on the dev branch @CuriousFirefly
CuriousFirefly
@CuriousFirefly
Mar 13 02:26
@vsherbeck I think so (is there a way to double-check from the output?)
so that "git checkout dev" command ?
CuriousFirefly
@CuriousFirefly
Mar 13 02:31
Yes for me then. (I legitimately couldn't remember if global install was before or after the dev branch.)
vsherbeck
@vsherbeck
Mar 13 02:32
fair enough XD I'm barely know 'up' from 'down'... maybe I don't even know that
CuriousFirefly
@CuriousFirefly
Mar 13 02:33

@vsherbeck I'm definitely not sure I do!

Question for the room at large, if someone knows: why do those of us on a pi HAT or RFM69HCW need to switch to the 'dev' branch? What does it do differently?

Dana Lewis
@danamlewis
Mar 13 02:39
@CuriousFirefly new radio stuff is in dev, and all the Pi compatibility was built on top of it
Haven’t fixed all the bugs yet, but once we do, then it’ll get released to master
CuriousFirefly
@CuriousFirefly
Mar 13 02:43
@danamlewis Thanks for the background!
Dana Lewis
@danamlewis
Mar 13 02:44
:+1: if you want to dig in to all the changes between master and dev, there’s an open PR where you can see all the commits and some summary (slightly out of date) of the biggest changes between the branches
samueldemers2
@samueldemers2
Mar 13 02:44
Yay ! I just started to loop on an edison rig.
Dana Lewis
@danamlewis
Mar 13 02:45
:clap: :sparkles: :confetti_ball:
samueldemers2
@samueldemers2
Mar 13 02:45
I've been looking at the log for a while, nut now I'm wondering how do i stop looking at it so i could add another wifi
Dana Lewis
@danamlewis
Mar 13 02:46
Control-C to cancel
samueldemers2
@samueldemers2
Mar 13 02:46
So simple and obvious that i missed it ... Thanks a lot! For all !
Dana Lewis
@danamlewis
Mar 13 02:46
:+1:
vsherbeck
@vsherbeck
Mar 13 06:16
what does
mmtune: "916.800", 3 , -99 -- "916.750", 3, -103
mean... is that the rig tuning the radio ?
I need to fashion some sort of other antenna but it's the first time I saw that in my log...
my garbage antenna actually broke off at the solder ! but ironically... this is the fartherst I've ever made it... it actually detected the pump and set the time on it
vsherbeck
@vsherbeck
Mar 13 06:27
I think at this point it's finally hardware not software problem though hahah... I can work on that...
Scott Leibrand
@scottleibrand
Mar 13 06:28
That’s the worst signal I’ve ever seen, but it is barely communicating. :smile:
vsherbeck
@vsherbeck
Mar 13 06:28
lol... thank XD
zasteph
@zasteph
Mar 13 06:28
@vsherbeck I just got at probably the same point as you..."mmtune: "916.636", 5, -61 waiting for 2 second silence before continuing".... But I have some errors...
Error: Cannot find module '/root/myopenaps/settings/bg_targets.json'
module.js:485
throw err;
^
SyntaxError: /root/myopenaps/settings/profile.json: Unexpected end of input
Could not parse input data: [SyntaxError: /root/myopenaps/monitor/iob.json: Unexpected end of input]
Is there something I should have configured?
In which step?...
vsherbeck
@vsherbeck
Mar 13 06:41
I'm not great at this obviously lol... but I think if it can't find some needed modules you may have to rerun the set up again ?
and is your pump set up to receive loop input ?
emmasusanna
@emmasusanna
Mar 13 09:38

Hey everyone, yesterday received a minilink transmitter, which had trouble updating to nightscout and an error with the clock-zone. I read through some posts and saw that a couple of people had luck updating to the dev branch. I think that I've followed all of the setup instructions, but my loop log is continuously displaying the following information:

Starting oref0-pump-loop at Wed Mar 13 09:38:03 CET 2019 with 7 second wait_for_silence:
Waiting up to 4 minutes for new BG: First loop: not waiting

Listening for 7s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Wed Mar 13 09:38:03 CET 2019
Preflight fail. Retry 1 of preflight
Preflight fail. Listening for 3s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Wed Mar 13 09:38:03 CET 2019
Retry 2 of preflight
Preflight fail. Listening for 7s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Wed Mar 13 09:38:03 CET 2019
Retry 3 of preflight
Preflight fail. Couldn't preflight
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 3 s silence before mmtuning
Listening for 3s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Wed Mar 13 09:38:03 CET 2019
Listening for 3 s silence before mmtuning: Listening for 3s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Wed Mar 13 09:38:03 CET 2019
Failed to get string preference .pump_serial
cat: monitor/medtronic_frequency.ini: No such file or directory
mmtune: /usr/local/bin/oref0-mmtune: line 34: Go-mmtune: command not found
monitor/mmtune.json is empty or does not exist
cat: monitor/medtronic_frequency.ini: No such file or directory
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
No wait required.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Wed Mar 13 09:38:04 CET 2019

I guess there's something vital that I'm missing. Would appreciate any advice, thank you !

It also comes up with this every time I try to run the setup script: SyntaxError: /root/myopenaps/updated_prefs.json: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Object.Module._extensions..json (module.js:672:27)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/home/.rootfs/usr/local/lib/node_modules/oref0/bin/oref0-get-profile.js:87:23)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
Could not run oref0-get-profile
zasteph
@zasteph
Mar 13 14:18
What these numbers mean, please, and where should they be?
mmtune: "916.636", 5, -61
Jon Cluck
@cluckj
Mar 13 14:20
that's the signal you're getting between your rig and the pump, and it's pretty good
are you still getting that bg_targets.json error?
zasteph
@zasteph
Mar 13 14:22
@cluckj Thank you, Jon. Yes, I am, but I shut it down now, went to work. The CGM was not working because it was in the warm-up period, could that be the issue? I'll resume the testing tonight. What should I look for?
Jon Cluck
@cluckj
Mar 13 14:23
the issue could be the pump isn't set up with a target
zasteph
@zasteph
Mar 13 14:23
target for...? You mean the remote id -> add id thing?
Jon Cluck
@cluckj
Mar 13 14:24
no, it's in the bolus wizard setup
zasteph
@zasteph
Mar 13 14:24
I'll check that. Thank you!
Jon Cluck
@cluckj
Mar 13 15:15
@emmasusanna it looks like you might have an incomplete install?
emmasusanna
@emmasusanna
Mar 13 15:39
@cluckj yeah, it seems that the

@cluckj yeah its seems that I'm missing a few files. Does anyone know how to replace them? (If that is the problem..) When ever I run the setup script, this is what appears:

SyntaxError: /root/myopenaps/updated_prefs.json: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Object.Module._extensions..json (module.js:672:27)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/home/.rootfs/usr/local/lib/node_modules/oref0/bin/oref0-get-profile.js:87:23)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
Could not run oref0-get-profile

Jon Cluck
@cluckj
Mar 13 15:47
can you tell me a little bit more about your current hardware setup, and what's changed? (I saw a bit of it on facebook)
Dana Lewis
@danamlewis
Mar 13 16:35
Also, can you double check your pump Sn and how you entered it in to the setup script? Saw an error that might be related to that, too
USUAGGIE
@usuaggie
Mar 13 17:29
I recently purchased a few Explorer Boards from the last offering they were available, however I am not able to get through an installation of the OpenAPS software without the rig rebooting during the process. I was wondering if anyone else was seeing the same issue?
emmasusanna
@emmasusanna
Mar 13 18:05
At the moment I'm using a 722 pump with Intel Edison, and Enlite sensors with a Minilink transmitter. Previously I was using the set up with my 640g, an OTG cable and xdrip, which got quite cumbersome so I found myself a Minilink. Set that up yesterday, which was having trouble with a clock zone error, and was quite slow at sending BGs to Nightscout, so I tired to switch to dev branch, and when installing the errors occurred. I've checked the sn in my set up settings, but will check again when I get home!
Dana Lewis
@danamlewis
Mar 13 18:05
@usuaggie have you already tested reseating the Edison in the board?
@emmasusanna Ah. Did you switch from xdrip to mdt as the cgm type as well?
emmasusanna
@emmasusanna
Mar 13 18:07
@danamlewis yes, I did! The rig was recieving the BGs, and looping perfectly, just not sending them to Nightscout as frequently as before. Is this perhaps what should be expected with this set up?
Dana Lewis
@danamlewis
Mar 13 18:12
@emmasusanna not sure we’ve had many testers with dev branch’s new stuff with mdt cgm yet - but that’s not ideal behavior overall. When you say infrequent, can you describe the timeline of uploads more specifically (eg 15 minutes or ?) also, can you glance at your ns loop logs to see if there are any errors there?