These are chat archives for nightscout/intend-to-bolus
01 04 00 05 10 03 03but on the Edison it's
01 04 00 01 10 00 01. Difference being MITM bit is set on the Mac and the Mac is offering to distribute more keys (bytes 6 and 7).
"enteredBy": "openaps://medtronic/523", "insulin": null
sudo bt-pan client AA:BB:CC:DD:EE:FF 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
@PieterGit @thebookins It's not hard to build just an Edison kernel (not a full flashable image) to drop into an Edison's /boot directory, and then boot it by hand in u-boot. I've done that to try patches on both 3.10 and 4.x kernels, and can help you through it.
My problem with Andy's 4.11 kernel has been that it boots OK when the Edison is on an Intel mini-breakout, but not when it's on a Sparkfun base board, for some reason that is beyond me. No idea whether it will boot on an Explorer board, but that would be an interesting data point.
openaps bg-fresh-check openaps get-ns-bg
openaps use pump model) , but there are GPIO stuff things that give quite a lot of errors in the logs and probably need to be rewritten for use with a 4.x kernel. It's on my wishlist, but not very high, because I first want token based authentication with Nightscout fixed.
hey all- I'm finally getting somewhere (I think) in troubleshooting. In ns-loop i keep getting:
May 17 12:55:03 pinky ns-loop.log: Starting ns-loop at Wed May 17 12:55:03 MDT 2017:
May 17 12:55:19 pinky ns-loop.log: ns://JSON/shell/cgm/ns-glucose.json
May 17 12:55:19 pinky ns-loop.log: No JSON object could be decoded
ns-glucose.json has no content. glucose.json is mostly up to date. Right now it is 17min behind. Not sure where to look next. Any ideas?
Background: on my NS site I do not see the temp basals displayed, just the normal and the pump pill is all red letters and missing how long ago it communicated, but accurately shows insulin left
oref0—set-device-clocksto reset my OpenAPS rig, will that mess up my connection with my Loop app and pump? I was hoping that by resetting the clock through Loop, that would be an easy fix, but I am not sure if that is a hindrance instead. Also, it is weird to see a 15 min or more gap in the NS pill while the pump is zero temping. It does pick up again, but is that a normal occurence?
@tim2000s so I see the line
* * * * * ps aux | grep -v grep | grep -q "oref0-online AA:BB:CC:DD:EE:FF" || oref0-online AA:BB:CC:DD:EE:FF >> /var/log/openaps/network.log
but not clear on how changing this line will do the trick ...