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

4th
Apr 2019
Ralsty12
@Ralsty12
Apr 04 02:00
So I'm definitely in the dev branch yet still get the subg_rfspy error
Ralsty12
@Ralsty12
Apr 04 03:44
Would the rfm69 even need subg_rfspy?
vsherbeck
@vsherbeck
Apr 04 05:17
For some reason I thought the second time around an install would be much easier... it was but also not successful. Well this time I'm starting over for the zillionth time but damnit, I'm drinking. Maybe I'll be more successful tipsy :P...
vsherbeck
@vsherbeck
Apr 04 07:44

Starting oref0-pump-loop at Thu 4 Apr 00:42:27 PDT 2019 with 25 second wait_for_silence:
Waiting up to 4 minutes for new BG: jq: error: Could not open file monitor/glucose.json: No such file or directory
jq: error: Could not open file monitor/glucose.json: No such file or directory
date: invalid date ‘@’
ls: cannot access '/tmp/pump_loop_completed': No such file or directory
ImportError: No module named spi_serial

Radio check failed. ImportError: No module named spi_serial

Nope... same problem.
Ralsty12
@Ralsty12
Apr 04 08:22
I'm also now getting the Radio check Failed. ImportError: No module named spi_serial, now
no other errors tho
Ralsty12
@Ralsty12
Apr 04 10:27
is there a way to install the spi_serial module?
Bernhard Klein
@Volberger
Apr 04 17:05
@cluckj @scottleibrand
Abigail Cember
@acember
Apr 04 17:06
@vsherbeck I got a lot of "no glucose.json" errors when I thought Nightscout was properly set up, but it actually wasn't. Perhaps try to just plug in your receiver and see if at least that problem goes away?
Bernhard Klein
@Volberger
Apr 04 17:07

@cluckj @scottleibrand Thank you very much for your help!!! My rig: Paradigm 712, Pi0 + Explorer HAT

A few days ago I was able to start the loop. Yeah! Now I have new questions:
Since a short time it is no longer necessary to create three separate scripts when installing an x12 pump (settings.json / bg-targets-raw.json / basal-profile.json). Now it seems that everything is read from the pump. In the target-raw.json it was previously possible to set high-targets and low-targets and thus determine a bandwidth. In the Bolus Wizard of my 712 it is only possible to set a blood sugar target for a desired period of time (Example: 00:00 high 120 low 100 / 06:00 high 140 low 90 ....) but no range.
Do you / anyone know if and if so where to determine low and high targets instead? Grettings from Cologne, Europe

Dana Lewis
@danamlewis
Apr 04 17:13
OpenAPS only uses the single number at the bottom of the range - it doesn’t use a range
So it’s using the 100 and the 90 for your OpenAPS Target
Bernhard Klein
@Volberger
Apr 04 17:21
@danamlewis How does openaps know that insulin should be given when, for example, the blood glucose value has reached 250? I thought the low and the high value were to limit insulin (for example, when 90 is reached) and to give more insulin when 180, 220, 250 ... are exceeded.
Eric
@ecc1
Apr 04 17:44
@Ralsty12 your configuration is still incorrect if it's trying to use spi_serial etc. If you can't update it, it's probably easier to just reinstall and make sure you're using dev
Dana Lewis
@danamlewis
Apr 04 18:05
no, we just use the bottom number (90) as the target for all calculations and predictions (both high and low corrections) @Volberger. Originally (4 years ago) we did use a range and only correct when the prediction was out of range (e.g. 90-150, if that was your range), but most people wanted the system to do more, so OpenAPS now uses a single target (i.e. the 90) instead of range. You can still have a range in your pump, and use that higher number for any manual dosing you do; but OpenAPS only uses the lower number for it's target.
there are some examples with visuals here that may help for understanding how OpenAPS uses future predictions relative to target (and the safety threshold we calculate) to drive dosing decisions: https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html#openaps-algorithm-examples
so if you are just getting started and are more comfortable correcting to a higher number, you can start your target higher (e.g. 120 mg/dL), and once you get your settings nailed down, decided whether you want to change your target.
Alfredo kachy
@kachytronico
Apr 04 19:32
Please, help. Papertrail and jubilinux 0.3.0 with dev.
root@edison:~# cd remote_syslog root@edison:~/remote_syslog# root@edison:~/remote_syslog# sudo cp ./remote_syslog /usr/local/bin root@edison:~/remote_syslog# vi /etc/log_files.yml root@edison:~/remote_syslog# sudo remote_syslog 2019-04-04 19:29:05 CRITICAL remote_syslog.go:244 Failed to start server: No destination hostname specified
vsherbeck
@vsherbeck
Apr 04 19:38
I am using dev... also cluckj clone of oref0 for my radiofruit bonnet + pi setup. Unforuntately I don't have a receiver to plug into as I'm using an xdrip based set up with libre... idk... maybe I'll try to install everything over again.
My nightscout was crashing prior to this... which was caused by my rig.
but it isn't on the reinstall.
vsherbeck
@vsherbeck
Apr 04 22:08

Listening for 40s silence before mmtuning: ..........................
Starting oref0-pump-loop at Thu 4 Apr 15:04:13 PDT 2019 with 26 second wait_for_silence:
Waiting up to 4 minutes for new BG: ls: cannot access '/tmp/pump_loop_completed': No such file or directory
ImportError: No module named spi_serial

Radio check failed. ImportError: No module named spi_serial
Starting oref0-pump-loop at Thu 4 Apr 15:04:30 PDT 2019 with 11 second wait_for_silence:
Waiting up to 4 minutes for new BG: ls: cannot access '/tmp/pump_loop_completed': No such file or directory
ImportError: No module named spi_serial

now I'm only having spi_serial errors... getting closer I guess ?
I think I might have to wait for someone here to weigh in on the spi-serial bit bc I've tried installing in many different ways now and this is the closest I've got... and it appears I'm not the only one having issues so... there might be something all of us are missing