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

10th
Nov 2018
Tim Howard
@tghoward
Nov 10 2018 00:32
@cluckj thanks for checking. I failed last night, but I'm trying again now. Am hopeful.
Interesting, this happens a few times (with four different packages, I think).
  Running setup.py install for decocare

    warning: no files found matching 'CHANGES.*'
Tim Howard
@tghoward
Nov 10 2018 00:38
More tidbits. Default npm version from apt-get is still very old: v 1.4.21
Tim Howard
@tghoward
Nov 10 2018 00:52

drat. This is what happened last night, too.

/home/.rootfs/usr/local/lib/node_modules/npm/bin/npm-cli.js:85
      let notifier = require('update-notifier')({pkg})
          ^^^^^^^^
SyntaxError: Unexpected identifier
    at Module._compile (module.js:439:25)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:906:3

This time during second run of openaps-install.sh after updating npm using npm i -g npm

And then npm won't even show the version
~# npm -v

/home/.rootfs/usr/local/lib/node_modules/npm/bin/npm-cli.js:85
      let notifier = require('update-notifier')({pkg})
          ^^^^^^^^
SyntaxError: Unexpected identifier
    at Module._compile (module.js:439:25)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:906:3
Jon Cluck
@cluckj
Nov 10 2018 02:11
:/
Is this on an Edison?
Tim Howard
@tghoward
Nov 10 2018 02:15
yes. I'm deciding there's a disconnect between npm version and nodejs and nodejs-legacy. So I've uninstalled those per the first block of instructions here: https://github.com/xdrip-js/Logger and it looks like I may be getting a full install ... still working. (Funny, I said no to BT Tethering but it's in the middle of installing Bluez right now)
x3nr1qu3x
@x3nr1qu3x
Nov 10 2018 02:20
Hi, I'm installing openAPS on a Raspberry Pi Zero, but I have some problems in instalation. When I run command "npm run global-install" I have this issue
Sin título.png
and when I run it a second time, it seems to install correctly...
Tim Howard
@tghoward
Nov 10 2018 02:25
@x3nr1qu3x you aren't running the standard setup script? cd && ~/src/oref0/bin/oref0-setup.sh
x3nr1qu3x
@x3nr1qu3x
Nov 10 2018 02:25
yes
and then restart the rig
and when i run that command "npm run global-install" i get those errors
but i ran the same command again and it seems to install correctly...
Tim Howard
@tghoward
Nov 10 2018 02:29
then continue on if it seemed ok the second time. I'm confused, though, because you normally wouldn't need to run that command (as far as I know).
x3nr1qu3x
@x3nr1qu3x
Nov 10 2018 02:30
no? why? Im following the tutorial
x3nr1qu3x
@x3nr1qu3x
Nov 10 2018 02:32
yes
x3nr1qu3x
@x3nr1qu3x
Nov 10 2018 02:33
Sin título2.png
Tim Howard
@tghoward
Nov 10 2018 02:34
Aha! yep, my bad, Sorry. Continue on!
x3nr1qu3x
@x3nr1qu3x
Nov 10 2018 02:34
Ok thanks
on raspberry it should install oref0 0.7.0-dev ??
Jon Cluck
@cluckj
Nov 10 2018 02:40
yes, dev will work a lot better
Tim Howard
@tghoward
Nov 10 2018 03:40
For my issues ... it looks like installing oref0 master finally got the radio working. And Logger too. Although they might be stepping on each other
Jon Cluck
@cluckj
Nov 10 2018 03:46
they're probably not going to coexist nicely for long
Tim Howard
@tghoward
Nov 10 2018 03:50
ok, thanks. good to know
Eden Grown-Haeberli
@edengh
Nov 10 2018 03:56
I’m setting up the bluetooth on a 3rd openaps and struggling to finish the connection. I keep getting this message as a response to every : [bluetooth]# power on
No default controller available
Sorry, to every command I enter into bluetoothctl. For context - the bluetooth on my other two devices broke after trying to update them last night. Anyone have any ideas?
Martin Haeberli
@mhaeberli
Nov 10 2018 04:27
on a related note to @edengh issue - running dev from last weekend, and at least in some cases, somehow, bluetoothd is not being started at boot. makes it kind of hard to automatically tether. even though it was configured with oref0-setup and oref0-runagain
another angle - which logs should I look in to figure out why bluetoothd isn’t started ...
x3nr1qu3x
@x3nr1qu3x
Nov 10 2018 14:55
someone know if i can turn off the display in rapsberry pi hat for save battery?
Martin Haeberli
@mhaeberli
Nov 10 2018 15:21
I believe it is possible to turn off display. But I don’t know how.
Scott Leibrand
@scottleibrand
Nov 10 2018 18:04
There’s no concept of completely turning it off. You just black out all the pixels if you want to. Even fully lit up it uses less battery than the LED though.
If you want to manage power usage you should look at underclocking instead.
Martin Haeberli
@mhaeberli
Nov 10 2018 18:07
:+1:
Jon Cluck
@cluckj
Nov 10 2018 18:16
Yeah, the power draw is less than the green activity LED on the pi
Martin, is bluetoothd crashing or just not starting?
I was having trouble with it on the Edison too
journalctl -u bluetooth should show you the logs
Or systemctl status bluetooth
x3nr1qu3x
@x3nr1qu3x
Nov 10 2018 18:21
Thank you
Martin Haeberli
@mhaeberli
Nov 10 2018 18:47
@cluckj - don’t know if it’s crashing or just not starting. thx for suggestion re journalctl .
(where) is it started or supposed to be started?
what I find is on those devices that are being ‘silly’, invocation of bluetoothctl just hangs. or, as @edengh described above, if it doesn’t, one gets ‘No default controller available’ in response to ‘power on'
it appears maybe like it crashes after a while, but rebooting doesn’t reliably fix it. (all this applies to Edisons running most recent dev, although the ‘cleanliness’ of the install does need to be reviewed.
Martin Haeberli
@mhaeberli
Nov 10 2018 19:04
@scottleibrand (or others) I have my Edisons/Pi s setting up a tunnel to a common static public ip address (running linux) so I can reverse tunnel in from that common point. The tunnels are established by cron jobs. but they often get ‘stuck’; sometimes reboots fix, but sometimes not. sometimes by non-relevant magic (remote access to the rig’s wifi network) I’m able to reach in and kill the tunnel process, and then cron comes around and fixes it. But I’m still looking for best practice for this stuff - any suggestions?
Martin Haeberli
@mhaeberli
Nov 10 2018 20:16
@ecc1 - i get:
systemctl status bluetooth
● bluetooth.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

and

journalctl -u bluetooth
-- Logs begin at Fri 1999-12-31 16:00:21 PST, end at Fri 1999-12-31 16:03:29 PST
lines 1-1/1 (END)

(because it can’t NTP it’s back in time)

tried this:
sudo bt-pan client C8:D0:83:89:07:A1
Traceback (most recent call last):
  File "/usr/local/bin/bt-pan", line 228, in <module>
    if __name__ == '__main__': sys.exit(main())
  File "/usr/local/bin/bt-pan", line 196, in main
    try: iface = net.Connect(opts.uuid)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.Failed: Input/output error
Raymond Richmond
@PedanticAvenger
Nov 10 2018 20:29
System behavior question. From my last night graph (which is pretty typical of open aps behavior at night for me) I feel like it could be less oscillating and suspect a general parameter being out of line. Thoughts?
Argh, darn mobile app, can't post the pic.
Just a sec
Raymond Richmond
@PedanticAvenger
Nov 10 2018 20:37
Dana Lewis
@danamlewis
Nov 10 2018 21:59
@PedanticAvenger check and see what Autotune says about your ISF
Martin Haeberli
@mhaeberli
Nov 10 2018 22:06
weirder and weirder - I swapped explorer boards on the same Edison that was happily tethering earlier, and its bluetooth daemon is not even started this time (after a reboot) - hard to understand how this tracks to the Explorer boards and not the edison rigs
where and how is the bluetooth daemon supposed to get started?
so the status shows ‘inactive (dead)'
Eric
@ecc1
Nov 10 2018 22:39
@mhaeberli Bluetooth is started by systemd. if you run "systemctl status" it will show you all the services currently running. You can try "systemctl restart bluetooth" and check the logs if it doesn't stay up. Perhaps you have a mix of locally-compiled and system versions of bluetoothd?
Martin Haeberli
@mhaeberli
Nov 10 2018 22:40
thx 4 suggestion
updatedb ; locate bluetoothd | grep ‘\/bluetoothd$’ results in
/home/.rootfs/usr/lib/bluetooth/bluetoothd
/home/.rootfs/usr/local/bin/bluetoothd
/home/.rootfs/usr/local/libexec/bluetooth/bluetoothd
/home/.rootfs/usr/sbin/bluetoothd
/root/src/bluez-5.48/src/bluetoothd
which bluetoothd
/usr/local/bin/bluetoothd
Eric
@ecc1
Nov 10 2018 22:48
what does "apt-cache policy bluez" say?
(checking if system bluetooth is recent enough for you to do without those local versions)
Martin Haeberli
@mhaeberli
Nov 10 2018 23:13
I’ll ask in a minute (if reverse tunnel is still up)
timberFrame
@timberFrame
Nov 10 2018 23:18
do the share endpoints work the same way for G6 as they do for G5?