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

25th
Nov 2018
Jon Cluck
@cluckj
Nov 25 2018 00:30
@tzachi-dar put the SD card in a computer and turn the hdmi port back on in /boot/config.txt
Brian Rabinovitz
@bdr1177
Nov 25 2018 00:57
@danamlewis I manually ran autotune, but it still used the old autotune numbers as the basis for the new autotune calculations. The new pump settings show up for comparison, but they were not used by autotune. Is there a way to force autotune to use the numbers programmed into the pump? Do I just delete the whole autotune directory before running it manually?
tzachi-dar
@tzachi-dar
Nov 25 2018 01:09
@cluckj I have tried puting hdmi on safe mode, but it did not help. I see it when the boot starts but not later.
Here is my file:

For more options and information see

http://rpf.io/configtxt

Some settings may impact device functionality. See link above for details

uncomment if you get no picture on HDMI for a default "safe" mode

hdmi_safe=1

uncomment this if your display has a black border of unused pixels visible

and your display can output without overscan

disable_overscan=1

uncomment the following to adjust overscan. Use positive numbers if console

goes off screen, and negative if there is too much border

overscan_left=16

overscan_right=16

overscan_top=16

overscan_bottom=16

uncomment to force a console size. By default it will be display's size minus

overscan.

framebuffer_width=1280

framebuffer_height=720

uncomment if hdmi display is not detected and composite is being output

hdmi_force_hotplug=1

uncomment to force a specific HDMI mode (this will force VGA)

hdmi_group=2
hdmi_mode=18

uncomment to force a HDMI mode rather than DVI. This can make audio work in

DMT (computer monitor) modes

hdmi_drive=2

uncomment to increase signal to HDMI, if you have interference, blanking, or

no display

config_hdmi_boost=4

uncomment for composite PAL

sdtv_mode=2

uncomment to overclock the arm. 700 MHz is the default.

arm_freq=800

Uncomment some or all of these to enable the optional hardware interfaces

dtparam=i2c_arm=on

dtparam=i2s=on

dtparam=spi=on

Uncomment this to enable the lirc-rpi module

dtoverlay=lirc-rpi

Additional overlays and parameters are documented /boot/overlays/README

Enable audio (loads snd_bcm2835)

dtparam=audio=on
dtparam=i2c1=on,i2c1_baudrate=400000

Brian Rabinovitz
@bdr1177
Nov 25 2018 01:10
Deleting the autotune directory didn't work either. Do I maybe need to delete myopenaps/settings/autotune.json to force autotune to use the pump basals?
tzachi-dar
@tzachi-dar
Nov 25 2018 01:10
anything else that I should try and change.
Jon Cluck
@cluckj
Nov 25 2018 01:11
hmm
can you plug it into ethernet?
if you remember the wpa_supplicant.conf trick, that might work too to get it connected to whatever network you're around
tzachi-dar
@tzachi-dar
Nov 25 2018 01:28
@cluckj tried both of them did not work :-(
What do I need to copy after a clean install?
Only config files?
glenrob1940
@glenrob1940
Nov 25 2018 01:44
Problems with Nightscout and with openAPS. I've got to be doing something (several things??) wrong. I haven't been able to get Nightscout to update - several attempts with both dev and master pulls. I have loop successfully running and updating in nightscout, but glucose is not being updated in my herokuapp site, and the heroku logs show now delta data. Loop runs fine; both open and closed loops. To aid in troubleshooting, decided to bring up one of my openAPS rigs. Did a new update from master following steps in the docs. It all seemed to go okay, and I tweaked preferences.jsson to my normal settings, and added an rsync line to crontab. All looked okay, however, ... log shows a successful mmtune every x times through the loop (approximately 10 minutes), but the loop always fails with 'jq: monitor/glucose.json no such file or directory'. When I look in ~/myopenaps/ I find just 3 json files, none of which are glucose.json. In my old (~/Old-myopenaps) directory there are lots of files, most of which are json's. I tried running oref0-runagain.sh to see if that would clear any problems, but I still have the same behavior.. Ideas? My guess is that both problems (nightscout glucose, and no json file are related to a problem with nightscout access, but have no idea where to go next.
Dana Lewis
@danamlewis
Nov 25 2018 01:46
@glenrob1940 what CGM type and how do you get that data to NS?
glenrob1940
@glenrob1940
Nov 25 2018 01:52
G5, I just followed the directions in the openaps read the docs nightscout setup section. Deployed to Heroku, built the app and then went to view it from heroku, or just from any browser. I used to have token based, but in trying to get this running, I got rid of my other apps in heroku and the current iteration is gtrobfcn if you want to take a look at it. Once I get things working again, I will shut down that app and put up a token based one.
glenrob1940
@glenrob1940
Nov 25 2018 02:02
For what it's worth, my dexcom app and dexcom's clarity work just fine and are being updated and I think loop works because it goes to dexcom's servers for glucose.
Dana Lewis
@danamlewis
Nov 25 2018 02:08
So your issue then is between dexcom and NS. You may want to quadruple check that it is share-ing; kill and reopen the app, etc to see if that will kickstart it
Having the follow app on your phone is helpful to see if data is flowing from your local app up to the server
glenrob1940
@glenrob1940
Nov 25 2018 02:19
That may be the problem. I have been just using the mobile app, and haven't been carrying the Dexcom receiver. I'll get it and see if that fixes things.
Dana Lewis
@danamlewis
Nov 25 2018 02:59
If you are G5 and getting data to the phone, but not to NS, the receiver is not the issue
Troubleshoot share to NS
Martin Haeberli
@mhaeberli
Nov 25 2018 03:39
so - I was having trouble with bluetooth on Edison - somehow, bluetoothd wasn’t being started on boot. I THOUGHT I had solved this issue by erasing the Edisons and doing a fresh install of dev, but that now seems no longer to be working.
Martin Haeberli
@mhaeberli
Nov 25 2018 05:05
ok - somehow - service cron stop; killall -g oref0-pump-loop; cd ~/src/oref0 ; npm run global-install (and oref0-setup or oref0-runagain, not sure which was more reliable) fixed it. Symptom is - i try to run bluetoothctl and it hangs trying to connect to daemon. When all is good, I get a happy result from bluetoothctl .
glenrob1940
@glenrob1940
Nov 25 2018 05:19
Removed and then reinstalled dexcom mobile and restored my previous share, and it is now working. I don't really understand what was wrong previously, the triangle shaped icon was colored before. It was gray after reinstall, and then went colored again when I re-entered my previous share. Things are working now. Thanks.
wilson99
@wilson99
Nov 25 2018 09:38
Is there any version or branch of OpenAPS that would allow me to bolus from my smartphone using NSClient, IFTTT or even via command on the SSH app?
ArvoNiilo
@ArvoNiilo
Nov 25 2018 10:00
I had my sensor off for about one hour . During this period the pump gave me four SMBs making together 0.9 units. On what basis does OpenAps decide on the delivery of SMBs when the sensor is off-line? I have a European Veo and Enlite sensors.
Dana Lewis
@danamlewis
Nov 25 2018 13:33
@ArvoNiilo it should not when data is missing. Can you pull your logs from that time frame?
Dana Lewis
@danamlewis
Nov 25 2018 13:44
@wilson99 there is not
Ebgineer
@Ebgineer
Nov 25 2018 14:56
Coincidentally my G4 sensor just went bad (shows ???? on the receiver). This was read by the rig as BG=181, 89 mg/dl higher than the previous cycle. It might be looking at raw BG. It correctly detected high deviation, >20% of current BG. But then it issued two different temp basal rates during the same loop cycle, 0 for 116 min and then 1.85 for 30 min.
Scott Leibrand
@scottleibrand
Nov 25 2018 15:44
@wilson99 we don’t recommend manually remote-bolusing. But as a safer alternative, you can just enter carbs and let SMB do the bolusing for you.
@ArvoNiilo I believe that the “BG too old” time-out is 10 minutes, so it should’ve stopped SMBing after that time.
tzachi-dar
@tzachi-dar
Nov 25 2018 16:21
@scottleibrand Are there instructions of what files I should copy when moving from one raspberry pi to the other?
Scott Leibrand
@scottleibrand
Nov 25 2018 16:51
not really. probably just your oref0-runagain, preferences.json, and autotune directory
Martin Haeberli
@mhaeberli
Nov 25 2018 17:37
@tzachi-dar @scottleibrand concur assuming a fresh install of oref0 on the second Pi beforehand.
Cas Eliëns
@cascer1
Nov 25 2018 17:47
I just ran an install based on the dev branch, but my crontab looks like a much older version
oref0 version returns 0.7.0-dev
Cas Eliëns
@cascer1
Nov 25 2018 18:08
oh apparently the setup script straight up skips the npm run global-install step
Cas Eliëns
@cascer1
Nov 25 2018 18:25
even after that, oref0-setup still dies very much
npm WARN deprecated crypto@0.0.3: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.                                                          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 link 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.79+                                                                                                                                                                                                               npm ERR! command "/usr/bin/node" "/usr/bin/npm" "run" "global-install"                                                                                                                                                                       npm ERR! cwd /root/src/oref0
Cas Eliëns
@cascer1
Nov 25 2018 18:40
oh my bad this was already reported in openaps/oref0#1145
I'll check openaps/oref0#1150 to see if it works
jgslade
@jgslade
Nov 25 2018 19:38

my rig has stopped connecting to my phone via bluetooth. When I try to reconnect it I get this error:

[bluetooth]# connect 20:39:56:DD:B7:97
Attempting to connect to 20:39:56:DD:B7:97
Failed to connect: org.bluez.Error.Failed
[CHG] Device 20:39:56:DD:B7:97 Connected: yes
[CHG] Device 20:39:56:DD:B7:97 Connected: no

Looking online for this error I found this thread:
https://raspberrypi.stackexchange.com/questions/67617/bluetoothctl-fails-to-connect-to-any-device-failed-to-connect-org-bluez-erro
But the recommended fix gives a command not found error so over the last year and a half something has changed in raspbian causing the fix to not work.
I have rebooted the rig and my phone and they won't connect anymore. Any suggestions on how to get them to talk again?
Thank you.

Martin Haeberli
@mhaeberli
Nov 25 2018 20:44
@jsalmon1966 maybe try re-setting up the pairing of the device per instructions? (you can do a remove 20:39:56:DD:B7:97 first within bluetoothctl, and do a ‘forget’ from your phone.
jgslade
@jgslade
Nov 25 2018 21:23

still a no-go, looked promising for a moment there but...

[CHG] Device 20:39:56:DD:B7:97 Modalias: bluetooth:v000Fp1200d1436
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001103-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001106-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001112-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001115-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001116-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 0000112d-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device 20:39:56:DD:B7:97 UUIDs: fafbdd20-83f0-4389-addf-917ac9dae5b2
[CHG] Device 20:39:56:DD:B7:97 ServicesResolved: yes
[CHG] Device 20:39:56:DD:B7:97 Paired: yes
[CHG] Device 20:39:56:DD:B7:97 ServicesResolved: no
[CHG] Device 20:39:56:DD:B7:97 Connected: no
[CHG] Device 20:39:56:DD:B7:97 Connected: yes
[CHG] Device 20:39:56:DD:B7:97 Connected: no

still disconnects just after connecting

tzachi-dar
@tzachi-dar
Nov 25 2018 21:58
while installing the pi from scratch, I get the following error:
npm install && sudo npm install -g && sudo npm link && sudo npm link oref0

(node:1833) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
npm WARN package.json crypto@0.0.3 crypto is also the name of a node core module.
npm WARN package.json crypto@0.0.3 No license field.
npm WARN package.json json@9.0.6 No license field.
npm WARN package.json share2nightscout-bridge@0.1.6 license should be a valid SPDX license expression
npm ERR! Error: Method Not Allowed
npm ERR! at errorResponse (/usr/share/npm/lib/cache/add-named.js:260:10)
npm ERR! at /usr/share/npm/lib/cache/add-named.js:203:12
npm ERR! at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:167:7)
npm ERR! at FSReqWrap.oncomplete (fs.js:135:15)
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/npm/npm/issues

npm ERR! System Linux 4.14.79-v7+
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! cwd /root/src/oref0
npm ERR! node -v v8.11.1
npm ERR! npm -v 1.4.21
npm ERR! code E405
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

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 link 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.79-v7+
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

anyone knows how to continue?
Martin Haeberli
@mhaeberli
Nov 25 2018 21:59
funny - same just happened to me on an Edison at the npm run global-install step running dev
Martin Haeberli
@mhaeberli
Nov 25 2018 22:12
how do I revert dev to an earlier commit - the 11/18 update seemed to be ok, maybe. I guess I can just checkout that branch. How do I prevent it from trying to go forward from there?
ok, trying git checkout a156832 and seeing what happens
tzachi-dar
@tzachi-dar
Nov 25 2018 22:16
"git checkout a156832" solved the problem @mhaeberli at my case.
Martin Haeberli
@mhaeberli
Nov 25 2018 22:18
also in mine
@scottleibrand @tzachi-dar - I have not tried to diagnose why the recent checkin broke the npm install
looks like it broke both Edison and RPi installs
tzachi-dar
@tzachi-dar
Nov 25 2018 22:29
When entering max iob - Does this include the basal or only boluses?
Dana Lewis
@danamlewis
Nov 25 2018 22:36
Both
tzachi-dar
@tzachi-dar
Nov 25 2018 22:40
Thanks
tzachi-dar
@tzachi-dar
Nov 25 2018 23:06
I'm getting an error: "Could not parse profile.json: SyntaxError: Unexpected end of JSON input"
The file ./myopenaps/settings/profile.json is empty.
How should it be created?
Martin Haeberli
@mhaeberli
Nov 25 2018 23:43
@tzachi-dar did you use oref0-runagain or oref0-setup ? if the former, advise doing the latter, interactive setup, paste in the right parameters
tzachi-dar
@tzachi-dar
Nov 25 2018 23:52
@mhaeberli I have run oref0-setup and running it again.
I must say that I did move to master at some point, should I return back to a156832 ?
Martin Haeberli
@mhaeberli
Nov 25 2018 23:53
on an RPi / Explorer HAT the recommendation as I understand it is dev, NOT master
so I would recommend a156832
BUT it was reported to me (but I did not test and reproduce) that mixed installations, going backwards and forward to master and then to dev and back is at best unreliable and at worst ill-advised/known to break
so advice often is - fresh install, direct to dev, or fresh install, install master, run, upgrade to dev
tzachi-dar
@tzachi-dar
Nov 25 2018 23:57
Well, I was doing dev, and then had to move to a156832.