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

30th
Mar 2019
Martin Haeberli
@mhaeberli
Mar 30 00:40
@cluckj - any experience automatically bluetooth tethering with jubilinux stretch 0.3.0 ? I get some errors on bootup (i’ll try posting later) - I paired successfully, trusted successfully, but didn’t test the next stage yet. Trying it now while on the move it’s not working the way it used to on 0.2.0
Jon Cluck
@cluckj
Mar 30 01:01
yep, I got it paired/trusted/tethered testing it earlier this week, let me know what the errors are when you get a chance?
Martin Haeberli
@mhaeberli
Mar 30 01:05
Yes ok thx
Steve Bernacki
@sbernacki
Mar 30 01:44
Just built a fresh Edison on Jubi 0.2.0 a few days ago. Trying to install dev. I've updated my packages list to point to archive.debian.org, but getting this early on in the install: The following packages have unmet dependencies: jq : Depends: libjq1 (= 1.5+dfsg-1.3~bpo8+1) but it is not going to be installed Depends: libonig2 (>= 5.9.5) but it is not installable
So obviously jq 1.5 isn't installing and everything else blows up. Anyone know how I can manually install it? I spend most of my time in RPM land so deb/apt is a bit foreign to me
Jon Cluck
@cluckj
Mar 30 01:50
if you can find the .deb files for those packages, you can install them like an rpm with dpkg -i
Jon Cluck
@cluckj
Mar 30 01:56
http://archive.debian.org/debian/pool/main/libo/libonig/libonig2_5.9.5-3.2+deb8u1_i386.deb 

http://archive.debian.org/debian/pool/main/j/jq/libjq1_1.5+dfsg-1.3~bpo8+1_i386.deb 

http://archive.debian.org/debian/pool/main/j/jq/jq_1.5+dfsg-1.3~bpo8+1_i386.deb
Steve Bernacki
@sbernacki
Mar 30 02:06
Thanks @cluckj . Not sure why apt didn't pick those up after modifying the repo but I'll try that. May just pave and re-flash with 0.3.0 since that's looking a lot more promising, but I don't want to give up just yet...
Jon Cluck
@cluckj
Mar 30 02:09
I don't know either, I was banging my head against it earlier this week and found reflashing to be a lot faster and easier :)
Alan
@Alzibiff
Mar 30 14:53
Some assistance required to troubleshoot BT problems with my Edison/Explorer rig which has been tethered and working well with my XIAOMI phone for some time. This morning, it lost connection and despite several reboots, the phone fails to pair up with it again. The rig loops OK when on WiFi so I am wondering how to confirm that the BT circuits are still operational. (I normally do not have the rig on WiFi - keep it permanently tethered to my phone which provides all the internet connectivity required).
The phone's BT is OK as my G6 has continued to provide readings to XDRIP+ running on the phone
Alan
@Alzibiff
Mar 30 14:58
Scratch that .... I just rebooted my phone out of frustration and all seems to be back in order. Very odd but all fine and dandy again now :-)
samueldemers2
@samueldemers2
Mar 30 15:05
I think I might have some trouble. Is my display broken?
Seem I cannot upload a picture. I will find a way around
samueldemers2
@samueldemers2
Mar 30 15:17
But if I someone know something. The display on my pi0 show one pixel line on two (one light up, the next one dont and repeat)
samueldemers2
@samueldemers2
Mar 30 16:06
If it is broken, is it possible to disable it?
Jon Cluck
@cluckj
Mar 30 18:43
that does sound broken
samueldemers2
@samueldemers2
Mar 30 18:52
The lower right corner of the glass has cracked
I looked at the files on github to find if there is a way to simply power off the screen and just goes as i do with my edison but I didn't find anything Hat related
Jon Cluck
@cluckj
Mar 30 19:04
I think I put something in there to turn it off, let me check
either way, deleting ~/src/openaps-menu/lib/display/ssd1306.js should keep it from doing display stuff
nope, no easy preferences switch :)
samueldemers2
@samueldemers2
Mar 30 19:17
Good, ill give it à try then
Does rm ~/src/openaps-menu/lib/display/ssd1306.js should do the trick ?
Jon Cluck
@cluckj
Mar 30 19:22
yep
haven't tried it though :laughing: let me know how it works
samueldemers2
@samueldemers2
Mar 30 19:25
I reboot the rig and come back
Up until now, the screen doesn't wake up and the loop is running.
I'll come back in an hour and I'll comment back to confirm that everything is going as usual. Then I'll buy a HAT eventually.
Thanks a lot. Again !
Jon Cluck
@cluckj
Mar 30 19:32
yep, everything else (radio, battery charger/monitor) should keep working fine without a screen
samueldemers2
@samueldemers2
Mar 30 19:56
Everything is fine
Jon Cluck
@cluckj
Mar 30 20:09
great :D
Carl
@c-robertson
Mar 30 21:21
Starting on my G6 today (yay!), can someone confirm which is the appropriate CGM option in OpenAPS, 'g5' or 'xdrip'? Also, for Nightscout config vars, do I need a BRIDGE_SERVER or is it sufficient to just include 'bridge' in the ENABLE var?
pauljbenedict
@pauljbenedict
Mar 30 22:06
Hi - is this the right place to seek assistance with an OpenAPS Dev channel install?
Dana Lewis
@danamlewis
Mar 30 22:07
@ carl G5, yes
@pauljbenedict yes!
pauljbenedict
@pauljbenedict
Mar 30 22:09

If so, I'm on an Edison rig with a fresh Jubilinix 0.2.0 flash and everything goes well until I run the setup script and I get this:
code
Continue? y/[N] y
Removing any existing git in /root/myopenaps/.git
Removed any existing git
Checking openaps 0.2.2 installation with --nogit support
Installing latest openaps w/ nogit
Downloading/unpacking git+https://github.com/openaps/openaps.git@nogit
Cloning https://github.com/openaps/openaps.git (to nogit) to /tmp/pip-aiXjvs-build
Running setup.py (path:/tmp/pip-aiXjvs-build/setup.py) egg_info for package from git+https://github.com/openaps/openaps.git@nogit

Requirement already satisfied (use --upgrade to upgrade): openaps==0.2.1-dev from git+https://github.com/openaps/openaps.git@nogit in /home/.rootfs/usr/local/lib/python2.7/dist-packages
Requirement already satisfied (use --upgrade to upgrade): pyserial in /home/.rootfs/usr/local/lib/python2.7/dist-packages (from openaps==0.2.1-dev)
Requirement already satisfied (use --upgrade to upgrade): python-dateutil in /home/.rootfs/usr/local/lib/python2.7/dist-packages (from openaps==0.2.1-dev)
Requirement already satisfied (use --upgrade to upgrade): argcomplete in /home/.rootfs/usr/local/lib/python2.7/dist-packages (from openaps==0.2.1-dev)
Requirement already satisfied (use --upgrade to upgrade): gitpython in /home/.rootfs/usr/local/lib/python2.7/dist-packages (from openaps==0.2.1-dev)
Requirement already satisfied (use --upgrade to upgrade): mock in /home/.rootfs/usr/local/lib/python2.7/dist-packages (from openaps==0.2.1-dev)
Requirement already satisfied (use --upgrade to upgrade): nose in /home/.rootfs/usr/local/lib/python2.7/dist-packages (from openaps==0.2.1-dev)
Requirement already satisfied (use --upgrade to upgrade): decocare>0.0.26 in /home/.rootfs/usr/local/lib/python2.7/dist-packages (from openaps==0.2.1-dev)
Requirement already satisfied (use --upgrade to upgrade): dexcom-reader>=0.1.8 in /home/.rootfs/usr/local/lib/python2.7/dist-packages (from openaps==0.2.1-dev)
Cleaning up...
Checking /root/myopenaps: mkdir: cannot create directory ‘/root/myopenaps’: File exists
/root/myopenaps initialized
usage: openaps-alias show [-h] [--ini] [--json] [{}]
openaps-alias show: error: argument name: invalid choice: '*' (choose from )
/root/src/oref0/ already exists; pulling latest
Already up-to-date.
Upgrading to node 8

Installing the NodeSource Node.js 8.x LTS Carbon repo...

Populating apt-get cache...

`code`
`code` 

Get:12 http://http.debian.net jessie/non-free Translation-en [72.0 kB]
Err http://http.debian.net jessie-updates/main i386 Packages

Ign http://http.debian.net jessie-updates/contrib Translation-en_IE
Ign http://http.debian.net jessie-updates/contrib Translation-en
Ign http://http.debian.net jessie-updates/main Translation-en_IE
Ign http://http.debian.net jessie-updates/main Translation-en
Ign http://http.debian.net jessie-updates/non-free Translation-en_IE
Ign http://http.debian.net jessie-updates/non-free Translation-en
Ign http://http.debian.net jessie-backports/main Translation-en_IE
Ign http://http.debian.net jessie-backports/main Translation-en
Err http://http.debian.net jessie-updates/main i386 Packages
404 Not Found [IP: 151.101.184.204 80]
Err http://http.debian.net jessie-updates/contrib i386 Packages
404 Not Found [IP: 151.101.184.204 80]
Err http://http.debian.net jessie-updates/non-free i386 Packages
404 Not Found [IP: 151.101.184.204 80]
Err http://http.debian.net jessie-backports/main i386 Packages
404 Not Found [IP: 151.101.184.204 80]
W: Failed to fetch http://http.debian.net/debian/dists/jessie-updates/main/binary-i386/Packages 404 Not Found [IP: 151.101.184.204 80]

W: Failed to fetch http://http.debian.net/debian/dists/jessie-updates/contrib/binary-i386/Packages 404 Not Found [IP: 151.101.184.204 80]

W: Failed to fetch http://http.debian.net/debian/dists/jessie-updates/non-free/binary-i386/Packages 404 Not Found [IP: 151.101.184.204 80]

W: Failed to fetch http://http.debian.net/debian/dists/jessie-backports/main/binary-i386/Packages 404 Not Found [IP: 151.101.184.204 80]

E: Some index files failed to download. They have been ignored, or old ones used instead.
Error executing command, exiting
Couldn't setup node 8
root@jubilinux:~#

`code` 
Should i be flashing with Jubilinix 0.3.0 for the Dev channel, and if so, is the rest of the setup the same? Thanks!
@danamlewis Awesome! And thank you for this life changing system! I can't tell you how grateful I am! Full nights of sleep... awesome :)
Scott Leibrand
@scottleibrand
Mar 30 22:22
@pauljbenedict yes, you now need to use Debian stretch, from jubilinux 3.0, because Debian dropped support for jessie.
pauljbenedict
@pauljbenedict
Mar 30 22:25
@scottleibrand Ok cool - thanks! Do you know where I can download that image, and is the flash the same as the main channel setup? I've been looking for instructions for the Dev channel all day - do those exist as part of the OpenAPS docs? Thank you so much!
Jon Cluck
@cluckj
Mar 30 22:27
@pauljbenedict you can get the image from http://www.jubilinux.org/dist/
pauljbenedict
@pauljbenedict
Mar 30 22:27
@cluckj Sweet! It that the: jubilinux-v0.3.0.zip ? :)
Jon Cluck
@cluckj
Mar 30 22:28
the flashing instructions are the same as with jubilinux 0.2.0, and you'll want to use this bootstrap script (if you are okay with the dev branch): https://github.com/openaps/docs/blob/7128440b989e3602a3d64fe05831adc9c104d11a/docs/docs/Build%20Your%20Rig/edison-install.md
yes :D
pauljbenedict
@pauljbenedict
Mar 30 22:28
@cluckj And do I still add the: libusb-1.0.dll and dfu-util.exe files like before?
Jon Cluck
@cluckj
Mar 30 22:29
yes
pauljbenedict
@pauljbenedict
Mar 30 22:30
@cluckj You guys are the BEST! Thank you so much! I can't tell you how grateful I am!
Jon Cluck
@cluckj
Mar 30 22:32
:) you're welcome
if you encounter any other issues please let us know, the jubilinux stretch thing is still a teensy bit experimental on the edison
Dana Lewis
@danamlewis
Mar 30 22:34
@pauljbenedict :+1: :confetti_ball:
pauljbenedict
@pauljbenedict
Mar 30 22:34
Seriously - this is the best customer support ever :)
@cluckj Will do!
pauljbenedict
@pauljbenedict
Mar 30 23:26
@cluckj Clean flash to an Edison using jubilinux-v0.3.0.zip, the bootstrat script here: https://github.com/openaps/docs/blob/7128440b989e3602a3d64fe05831adc9c104d11a/docs/docs/Build%20Your%20Rig/edison-install.md and then the dev setup script (it auto-prompted to do so) and it looks like it worked - oref0@0.7.0-dev!
@cluckj The script asked to add openaps to the cron tab and I said yes, then it asked to remove the old cron tab and I said no. It also said "no crontab for root" in both cases.
Jon Cluck
@cluckj
Mar 30 23:30
yep that's the usual message from that :)
pauljbenedict
@pauljbenedict
Mar 30 23:32
hum. edit-wifi and edit-pref don't seem to be doing anything. Are those supposed to work in the dev channel?
Jon Cluck
@cluckj
Mar 30 23:35
yeah, you may need to do cd ~/src/oref0 && npm run global-install then re-run setup
pauljbenedict
@pauljbenedict
Mar 30 23:53
Hi - I did both of those and it seems to run fine, but the edit-pref isn't working. Could this be an Edison thing? Like the Dev channel works better with the Pi and Hat setup? Here is the entire output from the Edison setup script running again: https://docs.google.com/document/d/1wKExFnTz7ofamCJHEnKO6uSEJHwoYfKES4u5wcVb40o/edit?usp=sharing
Nevermind - a reboot did the trick :)
Jon Cluck
@cluckj
Mar 30 23:55
ah
needed a .bash_profile refresh (a reboot'd do that)
pauljbenedict
@pauljbenedict
Mar 30 23:56
Thank you so much for your help - I really appreciate it!
Jon Cluck
@cluckj
Mar 30 23:58
you're welcome! thanks for being a guinea pig :)