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

19th
Aug 2018
N3FM
@N3FM
Aug 19 2018 00:33
@coolestkidsever , try this: cd myopenaps then openaps first-upload .
Xabeth
@Xabeth
Aug 19 2018 00:45
@danamlewis If you use IFTTT for carb entry, how does your system know how much insulin you've given, like it would if you use the NS portal?
Dana Lewis
@danamlewis
Aug 19 2018 00:52
It reads any boluses from the pump
That's true regardless of how you choose to enter carbs
(The only record of insulin comes from the pump. Any insulin notes in NS will be ignored by OpenAPS for dosing decisions)
@xabeth ^
Xabeth
@Xabeth
Aug 19 2018 01:57
@danamlewis Thank you so much! I read the e
I r
*I read the doc, but I didn't understand why you would enter the tiny bolus in offline mode. This makes more sense now.
Dana Lewis
@danamlewis
Aug 19 2018 02:45
:+1:
Sacha M
@coolestkidsever
Aug 19 2018 04:28

Hi, i have a question on the datesrting I'm seeing, even though I selected the correct tz at start up, for some reason the screen on my Pi just decided to start showing something from this morn, so I wondered if it might be this.. anyway..

Aug 19 16:24:45 Pi4e ns-loop.log: {"glucose":182,"dateString":"2018-08-19T16:09:00+12:00"}
Aug 19 16:24:47 Pi4e ns-loop.log: {"sgv":182,"dateString":"2018-08-19T16:09:00+12:00"}

Is what I'm seeing, which is correct - 1600 hours, but not with the +12.. is it adding 12 hours to this time?

Sacha M
@coolestkidsever
Aug 19 2018 04:39
or.. what could be the reason that rig isn't picking up a BG value from pump.. It looks like auto-sensloop.log runs without errors, but ns-loop.log isn't ever getting BG values.. so rig not receiving any - .. expect that graph showed up this afternoon with this mornings info..
Paper
@PaperT1D
Aug 19 2018 04:41
the +12:00 is the time zone
Sacha M
@coolestkidsever
Aug 19 2018 04:41
ah ok, so that's c orrect..
trying to find the thing that's not correct :-)
Sacha M
@coolestkidsever
Aug 19 2018 04:57

@Ebgineer - oh I've rechecked the mmtune - and its actually at -128 not -99 (so it's worse!)
@N3FM - I tried that also, - this returned


[Errno 2] No such file or directory
openaps: 'first-upload' is not an openaps command. See 'openaps --help'.

which suggest I guess that something went wrong in the install of openaps..maybe? but I've installed 4 times ...

Paper
@PaperT1D
Aug 19 2018 08:53
@coolestkidsever if you do cd ~/myopenaps/monitor && cat mmtune.json is the frequency it is set to (setFreq) 0, -128 also?
Arnoud82
@Arnoud82
Aug 19 2018 08:54
@cluckj @scottleibrand can one of you please help me with my problem? Im on dev 0.7.0 and openaps is looping great but i do not get my bg in Nightscout. And yesterday i lost the connection between my pump and my rig because to far apart. Now i do not
Get any pump info in Ns
lotte
@loettz_twitter
Aug 19 2018 15:38
Hi everyone, I succesfully installed openaps for the second time now (my other pump died -> 522 NA) Now I have a 522 WW Pump, a Raspberry Pi Zero W and the Ti Stick with the subg_rfspy hex for WW pumps. I tried to install the latest Release (6.2.0). On my other rig I had an older Release (6.0.1 or 6.0.0 not sure) with the same rig but a NA pump and everything worked fine. Now Openaps wont start Looping. My logs look fine , Pump is Communicating with the rig and pumphistory gets uploaded to NS. My mmtune results look fine too. It seems like I only have these self resolving errors that are normal at the beginning but even after hours it won't start looping (I only have one or two succesful loops in one hour). Is my rig not compatible with the latest release? Is there anything else I could try. Have been Troubleshooting for a week now and couldnt find an answer why it wont work all the time when the logs say everything is fine

Starting oref0-pump-loop at Sat 18 Aug 12:05:04 CEST 2018 with 23 second wait_for_silence:
Waiting up to 4 minutes for new BG: ls: cannot access '/tmp/pump_loop_completed': No such file or directory
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Profile less than 60m old; Profile valid. Refreshed pumphistory and meal.json
Checking pump clock: "2018-08-18T12:08:55+02:00" is within 90s of current time: Sat 18 Aug 12:08:59 CEST 2018
Error: pumphistory too old
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
Radio ok. Listening: .
Starting oref0-pump-loop at Sun 19 Aug 17:29:08 CEST 2018 with 24 second wait_for_silence:
Waiting up to 4 minutes for new BG: ls: cannot access '/tmp/pump_loop_completed': No such file or directory
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Old pumphistory-24h, waiting for 24 seconds of silence: Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Old pumphistory-24h refreshed
Profile less than 60m old; Profile valid. Refreshed pumphistory and meal.json
Checking pump clock: "2018-08-19T17:36:33+02:00" is within 90s of current time: Sun 19 Aug 17:36:38 CEST 2018
Error: pumphistory too old
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)

The CC111x is located at /dev/ttyACM0
RileyLink OK
Version: subg_rfspy 0.8
OK

The CC111x is located at /dev/ttyACM0
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
RileyLink OK
Version: subg_rfspy 0.8
SUCCESS
Listening for 40s silence before mmtuning: .

Version: subg_rfspy 0.8
SUCCESS
Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: "868.342", 5, -49 No wait required.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Sun 19 Aug 17:39:59 CEST 2018
Scott Leibrand
@scottleibrand
Aug 19 2018 15:40
I would check the code to see what gives Error: pumphistory too old and try that manually.
lotte
@loettz_twitter
Aug 19 2018 15:41
Thank you! I'm gonna try that out
lotte
@loettz_twitter
Aug 19 2018 16:16
I tried to run "grep -q pumphistory" manually and it says "130" after I echoed. Wiki says if its returning non zero, the command fails. How can I find out more about the error codes to find out the reason for failing this command?
NSewar
@nsewar01
Aug 19 2018 16:41
After clocking PiHat0 from 700 to 500, 2000mAh battery life has doubled. Will the speed reduction have any effect on the time it takes to loop?
Scott Leibrand
@scottleibrand
Aug 19 2018 17:58
@loettz_twitter not following. Paste the command and output?
@nsewar01 yes, but it should still finish each loop in a bit less than 5m on average.
lotte
@loettz_twitter
Aug 19 2018 18:18

grep -q pumphistory
echo $?

130

there was only one code occurence where I could find the "pumphistory too old" message. So I tried grep -q pumphistory. I manually ran all aliases from "openaps alias show pump-loop" and everything was fine. I have no idea what the problem could be.

lotte
@loettz_twitter
Aug 19 2018 19:00

root@loettz:~/myopenaps# npm list -g oref0
(node:14497) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.

-bash: syntax error near unexpected token `('/usr/local/lib
└── oref0@0.6.2

NSewar
@nsewar01
Aug 19 2018 19:07
Is it possible to dim the screen or turn it off to extend battery life further?
Sacha M
@coolestkidsever
Aug 19 2018 20:22
@PaperT1D When I run the above command, I get no such file or dir..
Sacha M
@coolestkidsever
Aug 19 2018 21:11
oh but for some reason when i checked in the dir.. mmtune.json was there, so I cat that, and this is the result

    [
      "916.800",
      0,
      -128
    ],
    [
      "916.850",
      0,
      -128
    ],
    [
      "916.900",
      0,
      -128
    ]
  ],
  "setFreq": 916.6,
  "usedDefault": true
}