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

1st
Sep 2018
Dromore1911
@Dromore1911
Sep 01 2018 05:30

Okay so i reflashed the edison, installed the master branch and installed Logger through master. I'm getting BG's to nightscout again, but i am getting a loop error.

profile less than 60m old; Profile valid. Refreshedjq: monitor/pumphistory-zoned.json: No such file or directory
jq: settings/pumphistory-24h-zoned.json: No such file or directory
jq: error: Cannot iterate over null
jq: error: null and array cannot be sorted, as they are not both arrays
module.js:674
throw err;
^

SyntaxError: /root/myopenaps/monitor/pumphistory-merged.json: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Object.Module._extensions..json (module.js:671:27)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/home/.rootfs/usr/local/lib/node_modules/oref0/bin/oref0-calculate-iob.js:43:18)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
pumphistoryCould not parse input data: SyntaxError: Unexpected end of JSON input
at JSON.parse (<anonymous>)
at Object.<anonymous> (/home/.rootfs/usr/local/lib/node_modules/oref0/bin/oref0-meal.js:47:37)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
and meal.json
Checking pump clock: "2018-08-31T22:25:06-07:00" is within 90s of current time: Fri Aug 31 22:25:40 PDT 2018
Error: pumphistory too old
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning

I do not understand what this error means.

Jeremy Cunningham
@jpcunningh
Sep 01 2018 05:33
@Dromore1911 , what were the results of the mmtune that should have printed out to the log file shortly after your capture? It looks like the rig is not talking to the pump very well.
Dromore1911
@Dromore1911
Sep 01 2018 05:35
mmtune: "916.588", 5, -77 waiting for 34 second silence before continuing
Radio ok. Listening: .No interfering pump comms detected from other rigs (this i s a good thing!)
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 Aug 31 22:33:00 PDT 2018
this is from the loo
loop*
Could it be that my pump itself is failing?
I get this error on both my edison and my pi0 rig
mmtune: /usr/bin/env: node: No such file or directory
mmtune: /usr/bin/env: node: No such file or directory
mmtune: /usr/bin/env: node: No such file or directory
mmtune: /usr/bin/env: node: No such file or directory
mmtune: /usr/bin/env: node: No such file or directory
mmtune: /usr/bin/env: node: No such file or directory
mmtune: /usr/bin/env: node: No such file or directory
mmtune: /usr/bin/env: node: No such file or directory
mmtune: /usr/bin/env: node: No such file or directory
mmtune: "916.612", 5, -78 waiting for 36 second silence before continuing
mmtune: "916.588", 5, -76 waiting for 32 second silence before continuing
mmtune: "916.612", 5, -78 waiting for 36 second silence before continuing
mmtune: "916.612", 5, -73 waiting for 26 second silence before continuing
mmtune: "916.588", 5, -77 waiting for 34 second silence before continuing
mmtune: "916.612", 5, -65 waiting for 10 second silence before continuing
mmtune: "916.612", 5, -77 waiting for 34 second silence before continuing
mmtune: "916.588", 5, -72 waiting for 24 second silence before continuing
mmtune: "916.588", 5, -75 waiting for 30 second silence before continuing
mmtune: "916.588", 5, -85 waiting for 50 second silence before continuing
mmtune: "916.636", 5, -90 waiting for 60 second silence before continuing
mmtune: "916.636", 5, -84 waiting for 48 second silence before continuing
mmtune: "916.612", 5, -81 waiting for 42 second silence before continuing
mmtune: "916.636", 5, -81 waiting for 42 second silence before continuing
mmtune: "916.588", 5, -79 waiting for 38 second silence before continuing
mmtune: "916.588", 5, -88 waiting for 56 second silence before continuing
mmtune: "916.588", 5, -77 waiting for 34 second silence before continuing
mmtune: "916.612", 5, -86 waiting for 52 second silence before continuing
root@NS1911:~#
there is the mmtune results
Jeremy Cunningham
@jpcunningh
Sep 01 2018 05:38
The /usr/bin/env: node: No such file or directory messages are odd.
Dromore1911
@Dromore1911
Sep 01 2018 05:39
It could have been when i was installing Logger onto the rig when it requires you to remove and reinstall node
Jeremy Cunningham
@jpcunningh
Sep 01 2018 05:40
what is the output if you do env node -v?
Dromore1911
@Dromore1911
Sep 01 2018 05:40
v8.11.4
Which I assume is the latest version
Jeremy Cunningham
@jpcunningh
Sep 01 2018 05:42
Make sure to scrub the API_SECRET, NIGHTSCOUT_HOST, and Dexcom transmitter ID... what is the output of crontab -l
That's the version I'm running.
Dromore1911
@Dromore1911
Sep 01 2018 05:44
root@NS1911:~/myopenaps# crontab -l
NIGHTSCOUT_HOST=XXXXXXXXXXXXXXXXXXXXXX
API_SECRET=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
          • ps aux | grep -v grep | grep -q "oref0-online " || cd /root/myopenaps && oref0-online 2>&1 >> /var/log/openaps/network.log
            0,20,40 touch /tmp/disable_hotspot
            1,21,41 rm /tmp/disable_hotspot
          • sudo wpa_cli scan
          • ( killall -g --older-than 30m openaps; killall -g --older-than 30m oref0-pump-loop; killall -g --older-than 30m openaps-report )
          • find /var/log/openaps/pump-loop.log -mmin +5 | grep pump && ( killall -g --older-than 5m openaps; killall -g --older-than 5m oref0-pump-loop; killall -g --older-than 5m openaps-report )
          • cd /root/myopenaps && ps aux | grep -v grep | grep -q 'monitor-xdrip' || monitor-xdrip | tee -a /var/log/openaps/xdrip-loop.log
            @reboot python /root/.xDripAPS/xDripAPS.py
          • cd /root/myopenaps && ps aux | grep -v grep | grep -q 'openaps ns-loop' || openaps ns-loop | tee -a /var/log/openaps/ns-loop.log
          • cd /root/myopenaps && ps aux | grep -v grep | grep -q 'oref0-autosens-loop' || oref0-autosens-loop 2>&1 | tee -a /var/log/openaps/autosens-loop.log
            5 4 * ( oref0-autotune -d=/root/myopenaps -n=https://ns1911b.herokuapp.com && cat /root/myopenaps/autotune/profile.json | jq . | grep -q start && cp /root/myopenaps/autotune/profile.json /root/myopenaps/settings/autotune.json) 2>&1 | tee -a /var/log/openaps/autotune.log
            @reboot reset_spi_serial.py
          • oref0-radio-reboot
          • cd /root/myopenaps && ( ps aux | grep -v grep | grep bash | grep -q 'bin/oref0-pump-loop' || oref0-pump-loop ) 2>&1 | tee -a /var/log/openaps/pump-loop.log
            /15 cd /root/myopenaps && sudo ~/src/EdisonVoltage/voltage json batteryVoltage battery | jq .batteryVoltage | awk '{if ($1<=3050)system("sudo shutdown -h now")}'
            @reboot cd /root/myopenaps && oref0-delete-future-entries
            0
            * cd /root/myopenaps && oref0-version --check-for-updates > /tmp/oref0-updates.txt
            @reboot cd ~/src/oref0/www && export FLASK_APP=app.py && flask run -p 80 --host=0.0.0.0
          • cd /root/src/Logger && ps aux | grep -v grep | grep -q 'XXXXXX' || /usr/local/bin/Logger XXXXXX >> /var/log/openaps/logger-loop.log 2>&1
Jeremy Cunningham
@jpcunningh
Sep 01 2018 05:47
I don't see anything jumping out at me
Dromore1911
@Dromore1911
Sep 01 2018 05:48
Ill fire up the pi0 rig tomorrow and see what happens. But i'm thinking my pump from 2004 is finally crapping out.
Jeremy Cunningham
@jpcunningh
Sep 01 2018 05:50
you may try running the pump-loop with debug turned on. that should reveal why the files aren't getting created.
Dromore1911
@Dromore1911
Sep 01 2018 05:50
What is the command for that? Sorry im not very software savvy
Jeremy Cunningham
@jpcunningh
Sep 01 2018 05:56
The easiest way may be to add OREF0_DEBUG=1 to the top of your crontab. After you add it, the next time cron starts the loop, debug will be enabled.
Don't forget to remove it, though. It can fill up the flash drive storage quickly.
Dromore1911
@Dromore1911
Sep 01 2018 05:57
I will do it tomorrow then, i have it saved. just shut down the rig for the night. thank you @jpcunningh for your help
Nalla306
@Nalla306
Sep 01 2018 10:23
Wondering if anyone can help, lost my original rig yesterday and have setup my backup. All was fine until i enabled bluetooth tethering. Now it will only connect via bluetooth to my phone and not to my home or car wifi. Logs show the error "dhclient: send_packet : Network is down"
Nalla306
@Nalla306
Sep 01 2018 14:00
completely reflashed jubilinux and reinstalled openaps, wifi all fine until i enable bluetooth tethering. As soon as thats done it will no longer connect to any of my wifi networks.
Error is now "wifi_get_mac_addr_intel: unable to open /config/wifi/mac.txt"
Dana Lewis
@danamlewis
Sep 01 2018 15:05
If anyone gets weird npm issues during install today or tomorrow, might be related to https://status.npmjs.org
Dana Lewis
@danamlewis
Sep 01 2018 15:12
(Potential workaround: try dev install from source and npm global install)
PCTamer
@PCTamer
Sep 01 2018 20:13
? originally i setup and used ns/heroku/minimed connect with my medtronic pump. as the connect was no longer supported i've tried to and have setup edision with open aps for hopefully read only looping. Are there any changes that need to be made to my ns scout(hosted on heroku) in order for it to receive data from edison?
GlossySwan
@GlossySwan
Sep 01 2018 20:14
Looping
Thanks to all of you for all the work and effort that has gone into this and for all your help in getting to this landmark
Dana Lewis
@danamlewis
Sep 01 2018 23:20
@pctamer check the NS page in the OpenAPS docs to see how to enable the OpenAPS pill etc
@GlossySwan πŸŽ‰πŸŽŠπŸ™ŒπŸΌπŸ’œ