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

28th
Nov 2018
djnoor
@djnoor
Nov 28 2018 00:00
@dcacklam Yes as in the 670G's CGM
Dave Acklam
@dcacklam
Nov 28 2018 00:11
@dmdfreak
It is but it's bluetooth drivers/hardware sucks.
You are best off getting a USB bluetooth dongle & an OTG cable
jgslade
@jgslade
Nov 28 2018 00:13
@dmdfreak, yes it is. I had mine wiring for a day before it stopped staying connected to anything via Bluetooth.
Dave Acklam
@dcacklam
Nov 28 2018 00:13

@dmdfreak
I was running a pi zero (with 'Slice of Radio' RF hat) rig for most of this spring/fall (until I fixed my Edison by reflashing it).

I used always-on BT tethering (some hacking of the connect/networking scripts was done) and a 3rd-party dongle, and it worked fine...

Made a 3d printed case for the pi, the hat, OTG cable and dongle, 'lipo board' and a 6000mah (3x18650) battery pack... It was bulky, but it could go a very long time without a recharge...

The hat condenses all my clunky add-on boards into one, and would likely make a much thinner rig if I was going that way today...

(However, the edison is still going strong, so...)
Dana Lewis
@danamlewis
Nov 28 2018 00:49
@djnoor no, it's not compatible with any of the looping pumps. There's a few people with 640 that wear that to receive CGM, upload to NS, and then send commands to OpenAPS rig commanding a loopable model pump - but that's a lot of gear. Most people instead switch to another c
*cgm
djnoor
@djnoor
Nov 28 2018 00:53
@danamlewis Thanks
fidoman
@efidoman
Nov 28 2018 01:20
@danamlewis - NS profile is below:
11-27-2018 7-49-18 PM.png
Eric
@ecc1
Nov 28 2018 01:21
@dmdfreak My Pi Zero W rig tethers very reliably with my Android phone over Bluetooth. I use network-manager to handle switching automatically between wifi and BT, no custom scripts or cron jobs needed. It works great for me, although it often keeps a BT connection to the phone even when it's using WiFi, which I've been told would be a problem for iPhones.
Dana Lewis
@danamlewis
Nov 28 2018 01:32
@efidoman so that confirms your NS profile has not been updated with Autotune from the rig. If you do a manual upload; you will see the oodles of Autotune basals. If you check out the Pr I linked earlier though; you can confirm if it updates automatically tonight (and if so, then we can merge to dev). That would also be helpful for seeing if that version resolves your issues of not uploading treatments to NS
Martin Haeberli
@mhaeberli
Nov 28 2018 05:55
-is there a way to set a watchdog timer on the Edison so that IF it hangs it will automatically reboot?
dmdfreak
@dmdfreak
Nov 28 2018 07:06
Thanks everyone. Maybe it's a software glitch for me then. My Edison gives me no problems getting the connection with the same phone. I'll redo the Pi software again and see if that does it. @ecc1 @dcacklam @jgslade
tzachi-dar
@tzachi-dar
Nov 28 2018 07:51
Is Multiple ISF schedule supported? I have seen on openaps/oref0#567 that it was not supported. Has that changed?
fidoman
@efidoman
Nov 28 2018 11:24
@danamlewis - I will test this PR this morning manually and tonight as well. However, I noticed that even though I asked for my crontab to be written (replaced) as part of the freshly flashed edison install, apparently it must not have done it? I can't find oref0-cron-nightly.sh anywhere in my crontab. Is it supposed to be called from cron?
I think my install is not right ... I get the following when running it manually just now:
root@eddie1:~/myopenaps# oref0-cron-nightly
Failed to get string preference .enable
Failed to get string preference .nightscout_host
root@eddie1:~/myopenaps#
fidoman
@efidoman
Nov 28 2018 12:46
BTW - I didn't notice any errors when doing the global install of oref0 or running setup from scratch. Is the debug output from these installs logged to a file somewhere?
jgslade
@jgslade
Nov 28 2018 17:25
my pi stopped connecting to the network, how do I turn the hdmi port back on so I can fix it?
Eric
@ecc1
Nov 28 2018 17:41
Is the Pi set up with serial login on the USB port (ttyGS0)? If so, it's easiest to use minicom or screen over a USB cable. If not, you have to make it not run the "tvservice -o" command that it's probably running to save some power. Easiest way is to mount your SD card on a Linux machine and edit the relevant file. (I can help anyone who wants to add the necessary couple of commands to the install to make sure serial login is set up by default.)
jgslade
@jgslade
Nov 28 2018 17:50
I am unsure if the serial login is enabled
Is there a way using tvservice to turn in back on on the command line? The keyboard works, I just don't have a display
Jon Cluck
@cluckj
Nov 28 2018 17:51
tvservice -p, I think?
jgslade
@jgslade
Nov 28 2018 17:58
That didn't seem to work, which file is running the tvservice -o command on boot?
Eric
@ecc1
Nov 28 2018 18:16
might have to try it with/without the HDMI monitor attached
(tvservice -p, that is) then connect the monitor
This is all voodoo, controlled by a binary-only Broadcom blob
jgslade
@jgslade
Nov 28 2018 18:47
Still didn't light up the screen

if I plug it into my desktop with a usb cable this is what I get from dmesg

[1087957.674247] usb 3-4.4: SerialNumber: 20071114173400000
[1087968.122186] usb 3-4.4: USB disconnect, device number 9
[1087968.847012] usb 3-4.4: new high-speed USB device number 10 using xhci_hcd
[1087968.972822] usb 3-4.4: New USB device found, idVendor=0bda, idProduct=0159, bcdDevice=58.88
[1087968.972826] usb 3-4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1087968.972829] usb 3-4.4: Product: USB2.0-CRW
[1087968.972831] usb 3-4.4: Manufacturer: Generic
[1087968.972833] usb 3-4.4: SerialNumber: 20071114173400000
[1092676.867765] audit: type=1130 audit(1543429579.381:404): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[1092687.303446] audit: type=1131 audit(1543429589.815:405): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Not sure if that means a can acess it or not, I've not tried doing a serial connection before.

Eric
@ecc1
Nov 28 2018 19:15
Probably not, there would be a message about a ttyACM0 device being created (although you can try "sudo modprobe cdc-acm" and see if that causes it to appear)
jgslade
@jgslade
Nov 28 2018 19:27
I found where tvservice -o was being called and commented the section out. So I got my screen to light up, as I was going through trying to fix my network I got a massive kernel panic, at least the error messages scrolled for quite a while. So it may be time to start over, what files should I backup for saving my looping stuff?
MarvelousMarvin
@MarvelousMarvin
Nov 28 2018 21:18

are there any update problems known for dev on the pihat? I am getting the following msg on a update:
npm ERR! cb() never called!
npm ERR! not ok code 0

npm ERR! oref0@0.7.0-dev global-install: npm install && sudo npm install -g && sudo npm link && sudo npm link oref0
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 install -g && sudo npm link && sudo npm lin k oref0
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.52+
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

PieterGit
@PieterGit
Nov 28 2018 23:07
crossposting from https://gitter.im/nightscout/public?at=5bff1f5de25cc274055bd90d . To anyone who has installed the dev branch of Nightscout on october 22 or later: please update your Nightscout dev site. Current Nightscout 0.10.3.1 release (master) is not affected. There was a vulnerability in event-stream package that could steal bitcoin's (see https://snyk.io/blog/malicious-code-found-in-npm-package-event-stream for details) . This has been resolved in the latest dev. Current dev has extra https headers (HSTS) enabled by default. If you experience problems with these new headers, please report at nightscout/cgm-remote-monitor#4091 . Thanks @viq to alert us.
MarvelousMarvin
@MarvelousMarvin
Nov 28 2018 23:32
Anyone can tell me how to get the rig working again? I just tried the complete new install. Just cant get it to work again after the update dev.
tepidjuice
@tepidjuice
Nov 28 2018 23:44
Can anyone recommend a case for the rasp pi 0W and this https://core-electronics.com.au/polymer-lithium-ion-battery-2000mah-38459.html battery?
Dromore1911
@Dromore1911
Nov 28 2018 23:45

Okay, so I had my edison looping last night, 0.6.2 i think was the version, but i had to use my phone with Xdrip to get my BG's. So I decided to go ahead and pull dev so i could just use xdrip-js and logger. The logger side of things is working excellently. But now it seems that the rig and pump don't want to communicate. My loop log is this

Starting oref0-pump-loop at Wed Nov 28 15:37:03 PST 2018 with 1 second waitfor silence:
Waiting up to 4 minutes for new BG: First loop: not waiting

Listening for 1s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Wed Nov 28 15:37:05 PST 2018
Preflight fail. Retry 1 of preflight
Preflight fail. Listening for 9s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Wed Nov 28 15:38:26 PST 2018
Retry 2 of preflight
Preflight fail. Listening for 1s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Wed Nov 28 15:39:04 PST 2018
Retry 3 of preflight
Preflight Unsuccessful oref0-pump-loop at Wed Nov 28 15:36:12 PST 2018
grep: monitor/temp_basal.json: No such file or directory
fail. Couldn't preflight
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 9 s silence before mmtuning
Listening for 9s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Wed Nov 28 15:39:49 PST 2018
Listening for 9 s silence before mmtuning: Listening for 9s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Wed Nov 28 15:40:00 PST 2018
mmtune:
waiting for 90 second silence before continuing
Listening for 90s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Wed Nov 28 15:42:10 PST 2018
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 Wed Nov 28 15:42:10 PST 2018
grep: monitor/temp_basal.json: No such file or directory

Could anyone explain where i need to go and what i need to do to get this running fully offline again, and why its not communicating with the pump now. The pump is a 715 with 2.3a
Thank you

This is in my mmtune file

root@NS1911:~/myopenaps# grep mmtune /var/log/openaps/pump-loop.log
mmtune:
mmtune:
mmtune:
mmtune:
mmtune:
mmtune:
mmtune: 2018/11/28 15:09:07 cannot connect to CC111x radio on /dev/spidev5.1
mmtune:
mmtune:
mmtune:
mmtune: 2018/11/28 15:29:07 cannot connect to CC111x radio on /dev/spidev5.1
mmtune:
mmtune:

Eric
@ecc1
Nov 28 2018 23:52
@Dromore1911 are you using an Explorer board as your radio?
MarvelousMarvin
@MarvelousMarvin
Nov 28 2018 23:59
Is it possible to go back to an older branch?