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

21st
Jan 2019
Scott Leibrand
@scottleibrand
Jan 21 01:05
just rm /root/dead.letter to remove it, or use less or similar if you want to view it first
if it's a directory, that will fail, and you'll need to see what's inside it before deciding whether to rm -rf it
Martin Haeberli
@mhaeberli
Jan 21 01:07
after 'service cron stop; killall -g oref0-pump-loop’, tried mmtune - with this result. advice sought.
OREF0_DEBUG=1 oref0-mmtune
mmtune: 2019/01/20 17:05:36 cannot connect to CC111x radio on /dev/spidev5.1
2019/01/20 17:05:36 /dev/spidev5.1: device is in use
2019/01/20 17:05:36 cannot connect to CC111x radio on /dev/spidev5.1
2019/01/20 17:05:36 /dev/spidev5.1: device is in use
Eric
@ecc1
Jan 21 01:22
some other process is using the radio
Martin Haeberli
@mhaeberli
Jan 21 01:23
@ecc1 - ok, thx, but which one; trying to run mmtune; on other edison / explorer rigs I own, this sequence works
how to find and kill such a process?
Eric
@ecc1
Jan 21 01:31
ps awx
Martin Haeberli
@mhaeberli
Jan 21 01:32
ok and then?
Eric
@ecc1
Jan 21 01:32
kill the one using the radio
sudo fuser /dev/spidev0.0 might find it
Eric
@ecc1
Jan 21 01:38
sorry use /dev/spidev5.1 for edison
Martin Haeberli
@mhaeberli
Jan 21 01:42
no joy
again:
mmtune: 2019/01/20 17:43:21 cannot connect to CC111x radio on /dev/spidev5.1
2019/01/20 17:43:21 cc111x: no response
2019/01/20 17:43:22 cannot connect to CC111x radio on /dev/spidev5.1
2019/01/20 17:43:22 cc111x: no response
Martin Haeberli
@mhaeberli
Jan 21 02:30
I run fuser /dev/spidev5.1 and find a process ; but I kill that process and another one shows up
renegadeandy
@renegadeandy
Jan 21 02:35
For those interested, I have just submitted my first pull request to xDripAPS: colinlennon/xDripAPS#6
Martin Haeberli
@mhaeberli
Jan 21 02:35
:+1:
what is the -recommended- clean way to do a manual mmtune by way of testing on dev?
renegadeandy
@renegadeandy
Jan 21 02:37
I assume mmtune is part of the radio stuff? But what is it? What you trying to do @mhaeberli
Martin Haeberli
@mhaeberli
Jan 21 02:37
trying to figure out if my Explorer radio is able to reach my pump, and if not, why not
mmtune is the process that adjusts the Explorer radio frequency to talk to the identified pump
Eric
@ecc1
Jan 21 02:44
@mhaeberli just run mmtune from the command line
Martin Haeberli
@mhaeberli
Jan 21 02:46
right, which is when i get the no response / busy responses
i have a stable of Edisons and Explorer boards here, each with unique symptoms, and I’m trying to isolate working combinations.
renegadeandy
@renegadeandy
Jan 21 02:49
@ecc1 how do you run it from the command line?
Martin Haeberli
@mhaeberli
Jan 21 02:50
i had understood - ‘cd myopenaps; OREF0_DEBUG=1 oref0-mmtune'
renegadeandy
@renegadeandy
Jan 21 02:53
hmm...
i dont have a oref0-mmtune
Martin Haeberli
@mhaeberli
Jan 21 03:07
or ‘oref0 mmtune’ ; i’m running the dev branch
but the docs say one has to ‘service cron stop; killall -g oref0-pump-loop’ first
Dana Lewis
@danamlewis
Jan 21 04:55
Docs are not up to date w 0.7.0-dev
Martin Haeberli
@mhaeberli
Jan 21 04:59
ok thx; but where to find at least hints for 0.7.0-dev, at least for mmtune?
Jeremy Cunningham
@jpcunningh
Jan 21 05:33
I put this function in my .bash_profile:
mmtune() {
  cd ~/myopenaps
  sudo service cron stop
  killall -g openaps

  for x in $(ps x -o "%p %a" | grep oref0-pump-loop | grep -v grep | awk '{ print $1 }'); do
    echo PS ID: $x
    y=$(ps x -o "%p %r" | grep $x | awk '{ print $2 }')
    if [ "$y" != "" ]; then
echo PGID: $y
pkill -g $y
    fi
done

  oref0-mmtune

sudo service cron start

}
It finds the pump loop processes and kills the corresponding process group before running mmtune
killall doesn’t find the shell scripts unfortunately, so the function above goes the long way around.
Garrett Webb
@garetis
Jan 21 06:16
@jgslade Oh yeah, I remember I installed a couple different things to try out -- the ability to send emails as one of them. I think I tried to cd into it, but just deleted it and now root is down to 71%. But I think when I went through and deleted some of the logs I broke something, so just going to run an update and hope that fixes it
jgslade
@jgslade
Jan 21 06:24
@garetis Okay, that would make sense off why you had it. Good luck with the logs.
Dave Gourley
@RadEnder
Jan 21 08:50
I’ve updated to iOS 12 and Workflow is no longer available on the App Store. Apparently Apple acquired Workflow and has replaced it with an app called “Shortcuts”. It works Much the same but didn’t currently allow IFTTT workflows. Some people have figured out how to manually connect them but I haven’t been able to successfully setup new “Shortcuts” workflows to work with my IFTTT workflows on my iPhone and Apple Watch. Has anybody else been able to make this work using “Shortcuts”? If so, we should probably amend the IFTTT tutorial to include the steps necessary to work with the new app. I’ll ckntkntie to
Continue to get mine working and if I’m successful will share the steps I’ve needed to take.
tuzoenduro
@tuzoenduro
Jan 21 10:49
Hi, I'm trying to figure out why my setup does not connect and realized that I had not forked the dev branch of CGM remote monitor from Nightscout. However, when I corrected this NS does not load up, it asks for my API secret and will not accept it when I type it in.
Does anyone know why this is happening? I have run the setup script about 20 times and once the rig is done installing and I open the logs it never completes a single closed loop, and on the explorer HAT there are no BGs indicated (and in NS the openAPS pill is empty).
I do see this appear during the install script : npm ERR! invalid: oref0@0.7.0-dev /usr/local/lib/node_modules/oref0
npm ERR! not ok code 0 I don't know if it is normal
thank you for your help
tuzoenduro
@tuzoenduro
Jan 21 10:55
that and a lot of warnings that crypto and other scripts are deprecated, but I don't know if that is normal or not
Garrett Webb
@garetis
Jan 21 10:57
I can't help with NS but when I load my system I get some deprecated notices, my understanding after looking into it is that it's nothing to worry about
tuzoenduro
@tuzoenduro
Jan 21 11:00
cool, with NS do you have it on dev? or on Master? I had tried with my NS on master and the rig never looped.. I can see it reads the pump as when it's logging I see new events if I bolus for example, but nothing goes to NS...
tuzoenduro
@tuzoenduro
Jan 21 12:56
Ok, I'm somewhat at my wits end... I do not understand any of this... I went to the troubleshooting in the openaps docs page and tried the killall command and got this :
root@panfila:~/myopenaps# killall -g oref0-pump-loop
oref0-pump-loop: no process found
root@panfila:~/myopenaps# openaps alias show pump-loop
usage: openaps-alias show [-h] [--ini] [--json] [{git,invoke,}]
openaps-alias show: error: argument name: invalid choice: 'pump-loop' (choose from 'git', 'invoke', '
')
root@panfila:~/myopenaps# openaps pump-loop
[Errno 2] No such file or directory
openaps: 'pump-loop' is not an openaps command. See 'openaps --help'.
can anyone try and help telling me what could have gone wrong with my install ??
viq
@viq
Jan 21 12:58
how about openaps show alias pump-loop? I don't know it, just guessing
tuzoenduro
@tuzoenduro
Jan 21 12:58
did that as well... it's the second line
it told me usage: openaps-alias show [-h] [--ini] [--json] [{git,invoke,}]
openaps-alias show: error: argument name: invalid choice: 'pump-loop' (choose from 'git', 'invoke', '')
viq
@viq
Jan 21 13:18
No, you did openaps alias show, if I got such an error I'd try whether openaps show alias works
$ oref0-autosens-history.js
oref0-autosens-history.js <glucose.json> <pumphistory.json> <profile.json>
Can I get those somehow from nightscout? I'd like to run autosens "on the side" to see what it would be showing
tuzoenduro
@tuzoenduro
Jan 21 13:39
openaps show alias pump-loop throws this back at me :
Not an openaps environment, run: openaps init
@viq I had not seen you switched alias and show.... but yeah, both throw me errors
viq
@viq
Jan 21 13:52
OK, I don't know the system well, it was worth a shot ;)
ArvoNiilo
@ArvoNiilo
Jan 21 14:01
Is it possible to send a TEST pushover notification from the rig?
tuzoenduro
@tuzoenduro
Jan 21 14:05
thing is I get the idea that openaps is not running and it does not find either that or pump-loop... so everytime I try something it just shuts down..
If anyone could help tell me what to look for to get it talking I would appreciate, I just do not understand coding and need as much help as possible..
viq
@viq
Jan 21 14:05
@ArvoNiilo I'd have to spend more time looking how exactly it works, but there's oref0-pushover
@ArvoNiilo https://github.com/openaps/oref0/blob/master/bin/oref0-pushover.sh looks like if you managed to prepare what's usually in enact/suggested.json in a different file to make it look like something is required, you would be able to call this script and point it at that file instead to make it send a notification
Martin Haeberli
@mhaeberli
Jan 21 14:33
Pump pill is showing error in NightScout after reservoir change 90 minutes ago. How to resolve. I’m not with T1; she’s asleep at the moment
Martin Haeberli
@mhaeberli
Jan 21 14:58
Answer: rewind, reservoir change, but she forgot to prime. So pump status was ‘suspended’ for 30 minutes, then ‘error’. And set was not reconnected. Account to to set change while sleeping. Initial error that woke her was ‘motor error’. . (Reservoir was anyway quite low)
renegadeandy
@renegadeandy
Jan 21 15:05

This morning I am consistenly getting :

mmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?

Any tips on debugging

battery still has 1/3rd left...
Jon Cluck
@cluckj
Jan 21 15:26
most pumps will turn off wireless comms at about 1.2V
what's the last voltage your rig read, in ~/myopenaps/monitor/battery.json?
renegadeandy
@renegadeandy
Jan 21 16:10
{"batteryVoltage":3968, "battery":79}
{
"status": "normal",
"voltage": 1.18
}
im confused as to how the output of "edison-battery" correlates to battery.json
the output of edison-battery is 3968?
Jon Cluck
@cluckj
Jan 21 16:25
edison-battery.json is your rig's battery, battery.json is your pump's battery
and you should change your pump's battery :)
renegadeandy
@renegadeandy
Jan 21 16:27
ahhhh!
Woops of coufrse
so is it documented that the RF is turned off?
I can't believe the pump doens't tell you
Dave Cole
@Dave9111
Jan 21 16:37
@renegadeandy Turn off the RF.. it is mentioned someplace in the OpenAPS docs. I can't tell you where.. I read it a while ago.
If you aren't using Lithium batteries, consider it. Amazon has some - 20 for $24 the last time I looked. Just be warned that once they get down to about 1.25 volts, they only have minutes of life left.
So carry a spare battery.
renegadeandy
@renegadeandy
Jan 21 16:39
Just changed my battery, will see if that tidies up the issues
renegadeandy
@renegadeandy
Jan 21 16:45
Still getting : mmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?
{
"status": "normal",
"voltage": 1.46
}
Dave Cole
@Dave9111
Jan 21 17:10
I'm not familiar with mmeowlink, but my daughters Medtronic pump runs fine until not far below 1.3 volts... so your voltage looks fine. Have you tried restarting the rig?
renegadeandy
@renegadeandy
Jan 21 17:11
not yet... I am getting a lot of these issues now:
enact/smb-suggested.json: {"temp":"absolute","deliverAt":"2019-01-21T17:02:19.674Z","reason":"Warning: currenttemp rate 4 != lastTemp rate 3.5 from pumphistory; canceling temp","duration":0,"rate":0}
Why should I need to restart....?
Dave Cole
@Dave9111
Jan 21 17:13
If you things are stuck on a comm error... but that looks like it is running ok.
Its cancelling temp entirely... hmmm
What other messages are you getting...
... It says its enacting a SMB... so that may be why its cancelling the temp basal. I'm really not familiar with that message. Ive seen it set a zero temp when doing SMBs
renegadeandy
@renegadeandy
Jan 21 17:17
its cancelling temp because apparantly
Warning: currenttemp rate 4 != lastTemp rate 3.5 from pumphistory
why its doing that, i don't know
Dave Cole
@Dave9111
Jan 21 17:20
What does nightscout look like? Did it issue a SMB and cancel your temp basal. That would indicate that you are rapidly rising.. The individual messages can be very confusing. I think that looking at nightscout can tell a lot more. I look at nightscout, find odd things, and then go back and look at logs or the MongoDB to figure out why things happen.
If its not looping it will cancel all temp basals...
Jon Cluck
@cluckj
Jan 21 17:22
is it giving that same error in more than one loop?
renegadeandy
@renegadeandy
Jan 21 17:24
Ok ill paste same complete loops
at this point i have changed the battery
and rebooted
Dave Cole
@Dave9111
Jan 21 17:24
FWIW, with an Edison rig, Medtronic pump, OpenAPS on master, she has had to restart the rig to get out of a pump comm error and it had to do with a low battery...
renegadeandy
@renegadeandy
Jan 21 17:25

Loop 1

Starting oref0-pump-loop at Mon Jan 21 11:10:02 CST 2019 with 4 second wait_for_silence:
Retrying without waiting for new BG
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Old pumphistory-24h, waiting for 4 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 pumphistoryError: bad basalprofile_data:
 and meal.json
Checking pump clock: "2019-01-21T11:11:09-06:00" is within 90s of current time: Mon Jan 21 11:11:13 CST 2019
Temp refreshed
Autotune exists! Hoorah! You can use microbolus-related features.
Optional feature Meal Assist enabled, but could not read required meal data.
{"iob":0.399,"activity":0.009,"basaliob":0.155,"bolusiob":0.244,"netbasalinsulin":1.2,"bolusinsulin":2.7,"time":"2019-01-21T17:11:12.000Z","iobWithZeroTemp":{"iob":0.399,"activity":0.009,"basaliob":0.155,"bolusiob":0.244,"netbasalinsulin":1.2,"bolusinsulin":2.7,"time":"2019-01-21T17:11:12.000Z"},"lastBolusTime":1548078317000,"lastTemp":{"rate":3.5,"timestamp":"2019-01-21T07:50:41-06:00","started_at":"2019-01-21T13:50:41.000Z","date":1548078641000,"duration":30}}
{"delta":2,"glucose":167,"noise":1,"short_avgdelta":1.22,"long_avgdelta":0.58,"date":1548090500043}
Autosens ratio: 1.16; Adjusting basal from 1.45 to 1.65; ISF from 46.3 to 39.9; CR: 8.964
currenttemp: { duration: 28, rate: 4, temp: 'absolute' } lastTempAge: 201 m tempModulus: 19 m
2019-01-21T17:11:23.267Z
Checking deliverAt: 2019-01-21T17:11:23.267Z is within 1m of current time: Mon Jan 21 11:11:23 CST 2019
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"temp":"absolute","deliverAt":"2019-01-21T17:11:23.267Z","reason":"Warning: currenttemp rate 4 != lastTemp rate 3.5 from pumphistory; canceling temp","duration":0,"rate":0}
Temp refreshed: monitor/temp_basal.json: {"duration":28,"rate":4,"temp":"absolute"}
enact/smb-enacted.json: "Rate: 0 Duration: 0"
Temp refreshed: monitor/temp_basal.json: {"duration":0,"rate":0,"temp":"absolute"}
No bolus needed. Settings less than 15 minutes old. Edison on battery: 75%. pumphistory-24h refreshed
Your instance of oref0 [0.6.2, master] is up-to-date.
Completed oref0-pump-loop at Mon Jan 21 11:11:44 CST 2019

Loop 2

Starting oref0-pump-loop at Mon Jan 21 11:13:02 CST 2019 with 3 second wait_for_silence:
Retrying without waiting for new BG
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Old pumphistory-24h, waiting for 3 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 pumphistoryError: bad basalprofile_data:
 and meal.json
Checking pump clock: "2019-01-21T11:11:12-06:00" is within 90s of current time: Mon Jan 21 11:16:06 CST 2019
Pump clock is more than 55s off: attempting to reset it
Waiting for ntpd to synchronize... No!
ntpd did not synchronize.
Restarting ntp (via systemctl): ntp.service.
Waiting for ntpd to synchronize... No!
ntpd did not synchronize.
Error: pump clock refresh error / mismatch
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/spidev5.1
RileyLink OK
Version: subg_rfspy 0.8
OK

The CC111x is located at /dev/spidev5.1
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: .No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: "868.510", 2, -91 waiting for 62 second silence before continuing
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Done waiting for rigs with better signal.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Mon Jan 21 11:20:02 CST 2019
Loop 3:
Starting oref0-pump-loop at Mon Jan 21 11:21:02 CST 2019 with 13 second wait_for_silence:
Retrying without waiting for new BG
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Old pumphistory-24h, waiting for 13 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 pumphistoryError: bad basalprofile_data:
 and meal.json
Checking pump clock: "2019-01-21T11:11:12-06:00" is within 90s of current time: Mon Jan 21 11:22:51 CST 2019
Pump clock is more than 55s off: attempting to reset it
Waiting for ntpd to synchronize... OK!
Setting pump time to Mon Jan 21 11:22:51 CST 2019
mmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?
Error: pump clock refresh error / mismatch
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/spidev5.1
RileyLink OK
Version: subg_rfspy 0.8
OK

The CC111x is located at /dev/spidev5.1
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: .No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: 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 Mon Jan 21 11:25:27 CST 2019
Dave Cole
@Dave9111
Jan 21 17:26
The rig is not talking to the pump.
renegadeandy
@renegadeandy
Jan 21 17:27
Yes....I know!
the question is why!
The pump is in trouser's pocket. The rig is in my shirt pocket
Dave Cole
@Dave9111
Jan 21 17:28
Did you restart the rig - power off and on?
renegadeandy
@renegadeandy
Jan 21 17:29
i just issued 'reboot'
so not power on and off
Jon Cluck
@cluckj
Jan 21 17:30
the -91 RSSI value for that distance is not a good sign
renegadeandy
@renegadeandy
Jan 21 17:30

Loop 4

Starting oref0-pump-loop at Mon Jan 21 11:26:02 CST 2019 with 5 second wait_for_silence:
Retrying without waiting for new BG
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Old pumphistory-24h, waiting for 5 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 pumphistoryError: bad basalprofile_data:
 and meal.json
Checking pump clock: "2019-01-21T11:27:10-06:00" is within 90s of current time: Mon Jan 21 11:27:14 CST 2019
Temp refreshed
Autotune exists! Hoorah! You can use microbolus-related features.
Optional feature Meal Assist enabled, but could not read required meal data.
{"iob":0.27,"activity":0.0071,"basaliob":0.11,"bolusiob":0.159,"netbasalinsulin":1.05,"bolusinsulin":2.7,"time":"2019-01-21T17:27:13.000Z","iobWithZeroTemp":{"iob":0.27,"activity":0.0071,"basaliob":0.11,"bolusiob":0.159,"netbasalinsulin":1.05,"bolusinsulin":2.7,"time":"2019-01-21T17:27:13.000Z"},"lastBolusTime":1548078317000,"lastTemp":{"rate":3.5,"timestamp":"2019-01-21T07:50:41-06:00","started_at":"2019-01-21T13:50:41.000Z","date":1548078641000,"duration":30}}
{"delta":2,"glucose":171,"noise":1,"short_avgdelta":1.61,"long_avgdelta":1.06,"date":1548091399751}
Autosens ratio: 1.16; Adjusting basal from 1.45 to 1.65; ISF from 46.3 to 39.9; CR: 8.964
currenttemp: { duration: 0, rate: 0, temp: 'absolute' } lastTempAge: 217 m tempModulus: 7 m
SMB disabled (no enableSMB preferences active)
Carb Impact: 3 mg/dL per 5m; CI Duration: NaN hours; remaining CI (~2h peak): NaN mg/dL per 5m
UAM Impact: 3 mg/dL per 5m; UAM Duration: 0 hours
minPredBG: 176 minIOBPredBG: 176 minZTGuardBG: 164 avgPredBG: 176 COB: undefined / undefined
BG projected to remain above 4.8 for 240 minutes
naive_eventualBG: 160 bgUndershoot: -97 zeroTempDuration: 240 zeroTempEffect: 228 carbsReq: NaN
undefined 27
2019-01-21T17:27:24.544Z
Checking deliverAt: 2019-01-21T17:27:24.544Z is within 1m of current time: Mon Jan 21 11:27:24 CST 2019
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"temp":"absolute","bg":171,"tick":"+2","eventualBG":178,"insulinReq":1.73,"reservoir":"63.6","deliverAt":"2019-01-21T17:27:24.544Z","sensitivityRatio":1.16,"predBGs":{"IOB":[171,172,174,175,175,176,177,177,178,178,178,177,177,177,176],"ZT":[171,170,168,167,166,165,165,164,164,164,164,164],"UAM":[171,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null]},"IOB":0.27,"reason":"COB: undefined, Dev: 1.0, BGI: -0.1, ISF: 2.2, CR: 8.96, Target: 4.8, minPredBG 9.8, minGuardBG 55.5, IOBpredBG 9.8; Eventual BG 9.9 >= 4.8, max_iob 2, adj. req. rate: 5.1 to maxSafeBasal: 4, no temp, setting 4U/hr. ","duration":30,"rate":4}
Temp refreshed: monitor/temp_basal.json: {"duration":0,"rate":0,"temp":"absolute"}
enact/smb-enacted.json: "Rate: 4 Duration: 30"
Temp refresh




ed: monitor/temp_basal.json: cat: monitor/temp_basal.json: No such file or directory
Checking pump status (suspended/bolusing): {"status":"normal","bolusing":false,"suspended":false}
Temp refreshed: monitor/temp_basal.json: {"duration":30,"rate":4,"temp":"absolute"}
No bolus needed. Pump profile refreshed; Settings refreshed; Edison on battery: 72%. pumphistory-24h refreshed
Settings less than 3 minutes old. Refreshed pumphistory and meal.json
IOB: null
Completed oref0-pump-loop at Mon Jan 21 11:28:42 CST 2019

So this now sets a temp basal - which works, but i bet the next loop will get a temp basal cancel

Jon Cluck
@cluckj
Jan 21 17:31
Error: bad basalprofile_data: and meal.jsonand the clock mismatch :\
Dave Cole
@Dave9111
Jan 21 17:31
Before you get into this too deep, just turn the rig off and back on.... reboot is not the same.
renegadeandy
@renegadeandy
Jan 21 17:32
well @Dave9111 that's not really good enough imo, we need to fix the problem, a power of and on, is not the answer
Dave Cole
@Dave9111
Jan 21 17:32
I've seen similar in the last two weeks and a power off and on fixed it. Don't know why.
renegadeandy
@renegadeandy
Jan 21 17:32
it may well be a temp fix
but I want to fix the source of the problem
Kevin Marshall
@ruess
Jan 21 17:33
Hi all, just wondering if anyone knows . . . i have no logs in /var/log/openaps/ directory
Dave Cole
@Dave9111
Jan 21 17:34
Not allowing the battery to go dead seems to solve most of the problems. My daughter likes to run the batteries into the ground. When things are running at marginal voltages bad things happen.
Kevin Marshall
@ruess
Jan 21 17:34
just wondering if that means that my installation and setup of the rig has likely failed?
Jon Cluck
@cluckj
Jan 21 17:35
@ruess did you just install it?
Kevin Marshall
@ruess
Jan 21 17:35
yes reinstalled it
Jon Cluck
@cluckj
Jan 21 17:35
it may not have generated any logs yet
Kevin Marshall
@ruess
Jan 21 17:35
gotcha - ok hopefully that's the case :)
I did a reinstall yesterday and ran into the same issue, even after an hour of waiting for something to happen, but maybe it just needs more time
Crossing my fingers :)
thanks
Jon Cluck
@cluckj
Jan 21 17:37
did you reboot after finishing the setup?
@renegadeandy it sometimes takes a while for a rig to successfully start looping again after it's stopped; did the next loop have that same temp basal mismatch error?
Kevin Marshall
@ruess
Jan 21 17:39
i did @cluckj - i'm going to give it an hour or so and see what happens
renegadeandy
@renegadeandy
Jan 21 17:39

@cluckj yes it did:

Loop 5

Starting oref0-pump-loop at Mon Jan 21 11:29:03 CST 2019 with 12 second wait_for_silence:
Retrying without waiting for new BG
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Old pumphistory-24h, waiting for 12 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: "2019-01-21T11:30:11-06:00" is within 90s of current time: Mon Jan 21 11:30:15 CST 2019
Temp refreshed
Autotune exists! Hoorah! You can use microbolus-related features.
{"carbs":25,"nsCarbs":25,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":1.74,"maxDeviation":3.88,"minDeviation":2.5,"slopeFromMaxDeviation":-2.752,"slopeFromMinDeviation":0,"allDeviations":[4,3,3,3,3],"lastCarbTime":1548078317000,"bwFound":false}
{"iob":0.249,"activity":0.0068,"basaliob":0.103,"bolusiob":0.146,"netbasalinsulin":1,"bolusinsulin":2.7,"time":"2019-01-21T17:30:14.000Z","iobWithZeroTemp":{"iob":0.249,"activity":0.0068,"basaliob":0.103,"bolusiob":0.146,"netbasalinsulin":1,"bolusinsulin":2.7,"time":"2019-01-21T17:30:14.000Z"},"lastBolusTime":1548078317000,"lastTemp":{"rate":3.5,"timestamp":"2019-01-21T07:50:41-06:00","started_at":"2019-01-21T13:50:41.000Z","date":1548078641000,"duration":30}}
{"delta":-3,"glucose":168,"noise":1,"short_avgdelta":-1.17,"long_avgdelta":0.43,"date":1548091699654}
Autosens ratio: 1.16; Adjusting basal from 1.45 to 1.65; ISF from 46.3 to 39.9; CR: 9
currenttemp: { duration: 28, rate: 4, temp: 'absolute' } lastTempAge: 220 m tempModulus: 8 m
2019-01-21T17:30:25.331Z
Checking deliverAt: 2019-01-21T17:30:25.331Z is within 1m of current time: Mon Jan 21 11:30:25 CST 2019
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"temp":"absolute","deliverAt":"2019-01-21T17:30:25.331Z","reason":"Warning: currenttemp rate 4 != lastTemp rate 3.5 from pumphistory; canceling temp","duration":0,"rate":0}
Temp refreshed: monitor/temp_basal.json: {"duration":28,"rate":4,"temp":"absolute"}
enact/smb-enacted.json: "Rate: 0 Duration: 0"
Temp refreshed: monitor/temp_basal.json: {"duration":0,"rate":0,"temp":"absolute"}
No bolus needed. Settings less than 15 minutes old. Edison on battery: 71%. pumphistory-24h refreshed
Completed oref0-pump-loop at Mon Jan 21 11:30:45 CST 2019
then the one after that sets a temp basal of 4 per hour
then the next cancels it again
in an infinite loop
Jon Cluck
@cluckj
Jan 21 17:41
@ruess is cron running?
@renegadeandy looks like the clock has synced up, and you're not getting that strange basalprofile error anymore...give it another couple loops
Dave Cole
@Dave9111
Jan 21 17:43
@cluckj Good point... near the end of the install it asks if you want to setup the cron table - that schedules OpenAPS to run. If you don't do that I think that not much will happen
Jon Cluck
@cluckj
Jan 21 17:44
systemctl status cron will show you what's going on with it
renegadeandy
@renegadeandy
Jan 21 17:52

3 more loops:

Starting oref0-pump-loop at Mon Jan 21 11:45:02 CST 2019 with 11 second wait_for_silence:
Retrying without waiting for new BG
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Old pumphistory-24h, waiting for 11 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: "2019-01-21T11:46:22-06:00" is within 90s of current time: Mon Jan 21 11:46:26 CST 2019
Temp refreshed
Autotune exists! Hoorah! You can use microbolus-related features.
{"carbs":25,"nsCarbs":25,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":1.65,"maxDeviation":3.37,"minDeviation":0.13,"slopeFromMaxDeviation":-0.39,"slopeFromMinDeviation":3.664,"allDeviations":[0,1,2,3,3,3],"lastCarbTime":1548078317000,"bwFound":false}
{"iob":0.154,"activity":0.0051,"basaliob":0.068,"bolusiob":0.086,"netbasalinsulin":0.9,"bolusinsulin":2.7,"time":"2019-01-21T17:46:25.000Z","iobWithZeroTemp":{"iob":0.154,"activity":0.0051,"basaliob":0.068,"bolusiob":0.086,"netbasalinsulin":0.9,"bolusinsulin":2.7,"time":"2019-01-21T17:46:25.000Z"},"lastBolusTime":1548078317000,"lastTemp":{"rate":3.5,"timestamp":"2019-01-21T07:50:41-06:00","started_at":"2019-01-21T13:50:41.000Z","date":1548078641000,"duration":30}}
{"delta":2,"glucose":169,"noise":1,"short_avgdelta":0.94,"long_avgdelta":0.09,"date":1548092599667}
Autosens ratio: 1.16; Adjusting basal from 1.45 to 1.65; ISF from 46.3 to 39.9; CR: 9
currenttemp: { duration: 22, rate: 4, temp: 'absolute' } lastTempAge: 236 m tempModulus: 18 m
2019-01-21T17:46:35.618Z
Checking deliverAt: 2019-01-21T17:46:35.618Z is within 1m of current time: Mon Jan 21 11:46:35 CST 2019
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"temp":"absolute","deliverAt":"2019-01-21T17:46:35.618Z","reason":"Warning: currenttemp rate 4 != lastTemp rate 3.5 from pumphistory; canceling temp","duration":0,"rate":0}
Temp refreshed: monitor/temp_basal.json: {"duration":22,"rate":4,"temp":"absolute"}
enact/smb-enacted.json: "Rate: 0 Duration: 0"
Temp refreshed: monitor/temp_basal.json: {"duration":0,"rate":0,"temp":"absolute"}
No bolus needed. Settings less than 15 minutes old. Edison on battery: 71%. pumphistory-24h refreshed
Completed oref0-pump-loop at Mon Jan 21 11:46:56 CST 2019

Again - same pattern, temp basal set, temp basal cancelled, temp basal set

Starting oref0-pump-loop at Mon Jan 21 11:47:02 CST 2019 with 7 second wait_for_silence:
Retrying without waiting for new BG
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Old pumphistory-24h, waiting for 7 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: "2019-01-21T11:47:59-06:00" is within 90s of current time: Mon Jan 21 11:48:03 CST 2019
Temp refreshed
Autotune exists! Hoorah! You can use microbolus-related features.
{"carbs":25,"nsCarbs":25,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":1.65,"maxDeviation":3.37,"minDeviation":0.13,"slopeFromMaxDeviation":-0.306,"slopeFromMinDeviation":0.939,"allDeviations":[2,0,1,2,3,3],"lastCarbTime":1548078317000,"bwFound":false}
{"iob":0.145,"activity":0.0049,"basaliob":0.065,"bolusiob":0.079,"netbasalinsulin":0.9,"bolusinsulin":2.7,"time":"2019-01-21T17:48:02.000Z","iobWithZeroTemp":{"iob":0.145,"activity":0.0049,"basaliob":0.065,"bolusiob":0.079,"netbasalinsulin":0.9,"bolusinsulin":2.7,"time":"2019-01-21T17:48:02.000Z"},"lastBolusTime":1548078317000,"lastTemp":{"rate":3.5,"timestamp":"2019-01-21T07:50:41-06:00","started_at":"2019-01-21T13:50:41.000Z","date":1548078641000,"duration":30}}
{"delta":2,"glucose":169,"noise":1,"short_avgdelta":0.94,"long_avgdelta":0.09,"date":1548092599667}
Autosens ratio: 1.16; Adjusting basal from 1.45 to 1.65; ISF from 46.3 to 39.9; CR: 9
currenttemp: { duration: 0, rate: 0, temp: 'absolute' } lastTempAge: 238 m tempModulus: 28 m
SMB disabled (no enableSMB preferences active)
Last carbs 243 minutes ago; remainingCATime: 8.7 hours; 100% carbs absorbed
Carb Impact: 1.9 mg/dL per 5m; CI Duration: 0 hours; remaining CI (~2h peak): 0 mg/dL per 5m
UAM Impact: 1.9 mg/dL per 5m; UAM Duration: 0.6 hours
minPredBG: 168 minIOBPredBG: 173 minZTGuardBG: 165 minUAMPredBG: 168 avgPredBG: 170 COB: 0 / 25
BG projected to remain above 4.8 for 240 minutes
naive_eventualBG: 163 bgUndershoot: -100 zeroTempDuration: 240 zeroTempEffect: 228 carbsReq: -74
undefined 48
2019-01-21T17:48:13.254Z
Checking deliverAt: 2019-01-21T17:48:13.254Z is within 1m of current time: Mon Jan 21 11:48:13 CST 2019
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"temp":"absolute","bg":169,"tick":"+2","eventualBG":175,"insulinReq":1.855,"reservoir":"62.3","deliverAt":"2019-01-21T17:48:13.254Z","sensitivityRatio":1.16,"predBGs":{"IOB":[169,170,170,171,172,172,173,173,173,173,173,173,173],"ZT":[169,168,167,166,166,165,165,165,165,165],"UAM":[169,170,170,170,170,170,169,169,168,168,168,168,168]},"COB":0,"IOB":0.145,"reason":"COB: 0, Dev: 0.7, BGI: -0.1, ISF: 2.2, CR: 9, Target: 4.8, minPredBG 9.3, minGuardBG 9.3, IOBpredBG 9.6, UAMpredBG 9.3; Eventual BG 9.7 >= 4.8, max_iob 2, adj. req. rate: 5.35 to maxSafeBasal: 4, no temp, setting 4U/hr. ","duration":30,"rate":4}
Temp refreshed: monitor/temp_basal.json: {"duration":0,"rate":0,"temp":"absolute"}
enact/smb-enacted.json: "Rate: 4 Duration: 30"
Temp refreshed: monitor/temp_basal.json: {"duration":30,"rate":4,"temp":"absolute"}
No bolus needed. Settings less than 15 minutes old. Edison on battery: 72%. pumphistory-24h refreshed
Pump profile refreshed; Settings refreshed; Refreshed pumphistory and meal.json
IOB: null
Completed oref0-pump-loop at Mon Jan 21 11:49:14 CST 2019
Starting oref0-pump-loop at Mon Jan 21 11:50:03 CST 2019 with 8 second wait_for_silence:
Retrying without waiting for new BG
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Old pumphistory-24h, waiting for 8 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: "2019-01-21T11:51:16-06:00" is within 90s of current time: Mon Jan 21 11:51:20 CST 2019
Temp refreshed
Autotune exists! Hoorah! You can use microbolus-related features.
{"carbs":25,"nsCarbs":25,"bwCarbs":0,"journalCarbs":0,"mealCOB":0,"currentDeviation":1.2,"maxDeviation":3.21,"minDeviation":0.13,"slopeFromMaxDeviation":-0.36,"slopeFromMinDeviation":0.413,"allDeviations":[1,2,0,1,2,3],"lastCarbTime":1548078317000,"bwFound":false}
{"iob":0.13,"activity":0.0046,"basaliob":0.06,"bolusiob":0.071,"netbasalinsulin":0.9,"bolusinsulin":2.7,"time":"2019-01-21T17:51:19.000Z","iobWithZeroTemp":{"iob":0.13,"activity":0.0046,"basaliob":0.06,"bolusiob":0.071,"netbasalinsulin":0.9,"bolusinsulin":2.7,"time":"2019-01-21T17:51:19.000Z"},"lastBolusTime":1548078317000,"lastTemp":{"rate":3.5,"timestamp":"2019-01-21T07:50:41-06:00","started_at":"2019-01-21T13:50:41.000Z","date":1548078641000,"duration":30}}
{"delta":-1,"glucose":168,"noise":1,"short_avgdelta":-0.17,"long_avgdelta":-0.13,"date":1548092899463}
Autosens ratio: 1.16; Adjusting basal from 1.45 to 1.65; ISF from 46.3 to 39.9; CR: 9
currenttemp: { duration: 28, rate: 4, temp: 'absolute' } lastTempAge: 241 m tempModulus: 29 m
2019-01-21T17:51:30.736Z
Checking deliverAt: 2019-01-21T17:51:30.736Z is within 1m of current time: Mon Jan 21 11:51:30 CST 2019
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"temp":"absolute","deliverAt":"2019-01-21T17:51:30.736Z","reason":"Warning: currenttemp rate 4 != lastTemp rate 3.5 from pumphistory; canceling temp","duration":0,"rate":0}
Temp refreshed: monitor/temp_basal.json: {"duration":28,"rate":4,"temp":"absolute"}
enact/smb-enacted.json: "Rate: 0 Duration: 0"
Temp refreshed: monitor/temp_basal.json: {"duration":0,"rate":0,"temp":"absolute"}
No bolus needed. Settings less than 15 minutes old. Edison battery at 70% is charged (>= 98%) or likely charging (60-70%). pumphistory-24h refreshed
Completed oref0-pump-loop at Mon Jan 21 11:51:50 CST 2019
Again - same pattern, temp basal set, temp basal cancelled, temp basal set
Dave Cole
@Dave9111
Jan 21 17:58
What does your pump say - is there a temp basal set or not?
renegadeandy
@renegadeandy
Jan 21 18:05
right now, no
Jon Cluck
@cluckj
Jan 21 18:05
the issue is that the last temp basal in your rig's pump history is being read as being from 4 hours ago, can you open ~/myopenaps/monitor/pumphistory-24h-zoned.json and paste the top 3-4 records?
renegadeandy
@renegadeandy
Jan 21 18:07
 {
    "_type": "TempBasalDuration", 
    "_description": "TempBasalDuration 2019-01-21T07:50:41 head[2], body[0] op[0x16]", 
    "timestamp": "2019-01-21T07:50:41-06:00", 
    "_body": "", 
    "_head": "1601", 
    "duration (min)": 30, 
    "_date": "2972075513"
  }, 
  {
    "_type": "TempBasal", 
    "temp": "absolute", 
    "_description": "TempBasal 2019-01-21T07:50:41 head[2], body[1] op[0x33]", 
    "timestamp": "2019-01-21T07:50:41-06:00", 
    "_body": "00", 
    "_head": "338c", 
    "rate": 3.5, 
    "_date": "2972075513"
  }, 
  {
    "_type": "Bolus", 
    "_description": "Bolus 2019-01-21T07:45:17 head[4], body[0] op[0x01]", 
    "timestamp": "2019-01-21T07:45:17-06:00", 
    "_body": "", 
    "programmed": 2.7, 
    "_head": "011b1b00", 
    "amount": 2.7, 
    "duration": 0, 
    "type": "normal", 
    "_date": "116d471513"
  }, 
  {
    "unknown_byte[8]": 0, 
    "_type": "BolusWizard", 
    "bg": 0, 
    "_byte[5]": 0, 
    "unknown_byte[10]": 0, 
    "_description": "BolusWizard 2019-01-21T07:45:17 head[2], body[13] op[0x5b]", 
    "timestamp": "2019-01-21T07:45:17-06:00", 
    "_body": "1990091630001b000000001b50", 
    "bg_target_high": 80, 
    "sensitivity": 22, 
    "carb_ratio": 9, 
    "food_estimate": 2.7, 
    "unabsorbed_insulin_total": 0.0, 
    "correction_estimate": 0.0, 
    "carb_input": 25, 
    "_head": "5b00", 
    "unabsorbed_insulin_count": "??", 
    "_byte[7]": 0, 
    "bolus_estimate": 2.7, 
    "_date": "116d071513", 
    "bg_target_low": 48
  },
@cluckj aha! You are right! Now why on earth is that!
Its funny, its exactly the time I arrived at my office
and this problem seems to happen when I am at the office a lot...
Jon Cluck
@cluckj
Jan 21 18:11
that's super weird lol
Dave Cole
@Dave9111
Jan 21 18:12
When's lunch? You might want to get out of the building for some time..
Jon Cluck
@cluckj
Jan 21 18:15
are there newer (than 7:50AM) records in either ~/myopenaps/monitor/pumphistory-zoned.json or ~/myopenaps/monitor/pumphistory-merged.json?
renegadeandy
@renegadeandy
Jan 21 18:18
no
thats the newest in both files
and thats the exact time i arrived at the office
07:30 -> 07:50 i was in the car (looping via bt-pan)
the bt-pan has continued to keep the rig connected with no issues throughout
Dave Cole
@Dave9111
Jan 21 18:22
So you are on the wifi at the office?
The rigs on the office wifi?
Jon Cluck
@cluckj
Jan 21 18:23
have you manually set a temp basal or bolused since you got to the office?
renegadeandy
@renegadeandy
Jan 21 18:24
No, rig nor phone is on office wifi
and no ive not basaled or bolused manually (despite being a bit high, i want to debug this issue)
Jon Cluck
@cluckj
Jan 21 18:26
can you do a tiny manual bolus, or set a manual temp basal?
either your rig isn't actually getting history from your pump, or your pump isn't logging stuff
renegadeandy
@renegadeandy
Jan 21 18:40
yep, trying it now
tiny bolus of 0.1 coming up
renegadeandy
@renegadeandy
Jan 21 18:47
that warning, I am getting, should really be discounting the warning and continuing with the basal if the last history value was > say, 15 minutes ago shouldn't it? Why would it be interested in cancelling the basal from a historical reading 4 hours ago, that behaviour doesn't make sense (Can I code a fix if people agree?)
Jon Cluck
@cluckj
Jan 21 18:48
it's not a bug; the last history record the rig has is from 4 hours ago
renegadeandy
@renegadeandy
Jan 21 18:54
yes, but clearly, there is a bug with the reason why is it 4 hours ago, my rig has been running in those 4 hours
"Warning: currenttemp rate 4 != lastTemp rate 3.5 from pumphistory; canceling temp", is still occuring
I am saying, that something is messing up the history (tiny bolus didn't help)
the rig could handle that, by ignoring the history from > say 10 minutes ago, for this scenario, it still doesn't say why the history isnt up to date, but itd at least handle it more gracefully than the loop dieing
Jon Cluck
@cluckj
Jan 21 18:56
did the tiny bolus show up in any of those pumphistory files?
Scott Leibrand
@scottleibrand
Jan 21 19:07
what does the pump's history display show (on the pump screen)?
did the tiny bolus show up in pumphistory.json with a 4 hour offset, or is it not recording it at all?
renegadeandy
@renegadeandy
Jan 21 19:27
Pumps history display shows my tiny bolus
checking history now
the tiny bolus is there
Scott Leibrand
@scottleibrand
Jan 21 19:34
with a correct timestamp, or 4h old?
renegadeandy
@renegadeandy
Jan 21 19:36
correct timestamp
"timestamp": "2019-01-21T12:41:08-06:00",
still getting - "Warning: currenttemp rate 0 != lastTemp rate 1.6 from pumphistory; canceling temp"
Checking deliverAt: 2019-01-21T19:35:58.009Z is within 1m of current time: Mon Jan 21 13:35:58 CST 2019
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"temp":"absolute","deliverAt":"2019-01-21T19:35:58.009Z","reason":"Warning: currenttemp rate 0 != lastTemp rate 1.6 from pumphistory; canceling temp","duration":0,"rate":0}
Why is it deliverAt 19:35
that looks odd
This may be to do with the fact that i recently flew from the UK -> Chicago.....so it looks like deliverAt is GMT for some reason
i did run the package reconfiguring for tz-data on the rig when i switched zones
renegadeandy
@renegadeandy
Jan 21 19:42
2019-01-21T19:35:58.009Z is within 1m of current time: Mon Jan 21 13:35:58
That statement isn't really true
Scott Leibrand
@scottleibrand
Jan 21 19:42
that's not the statement. it's "Checking whether ..."
I think we added the "whether" in dev to clarify
if you're having these kinds of issues with master, you might want to update to dev to eliminate any potential already-fixed causes
Jon Cluck
@cluckj
Jan 21 19:44
^ I think so too
renegadeandy
@renegadeandy
Jan 21 19:45
but where did it get 19:35:58 timestamp from
thats not my timestamp
im 13:35
when im in the UK, itd be 19:35
Scott Leibrand
@scottleibrand
Jan 21 19:46
Z means zulu (UTC), so it's just reporting the deliverAt in UTC
it's currently Mon Jan 21 19:50:18 UTC 2019, so that looks right
renegadeandy
@renegadeandy
Jan 21 19:47
ah ok
confusing message though
it should be timezone specific to make it easier to read
Scott Leibrand
@scottleibrand
Jan 21 19:47
^^ improved in dev
renegadeandy
@renegadeandy
Jan 21 19:47
ok...
so......
any known issues at dev?
Scott Leibrand
@scottleibrand
Jan 21 19:48
nope, just need a bit more testing before we make it a release candidate. It's better than master at this point. big difference is it uses @ecc1's Go code for pump comms instead of the old unmaintained python openaps stuff
renegadeandy
@renegadeandy
Jan 21 19:53
hmm
Ok
I'll shift over this evening
so its a case of :
cd ~/src/oref0 && git checkout dev && git pull
npm run global-install
and check preferences.
Martin Haeberli
@mhaeberli
Jan 21 19:55

freshly updated rigs - Edison/Explorer, running dev :
after boot:

bluetoothctl
Agent registered
[bluetooth]# quit
Agent unregistered

which is wrong, as this device has already been paired with a phone, which in other events I see (on other rigs):
compare:

bluetoothctl
[NEW] Controller 58:A8:39:01:0D:57 etghopenaps17 [default]
[NEW] Device C8:D0:83:89:07:A1 Eden Grown-Haeberlis iPhone 2017
[NEW] Device 40:98:AD:78:3D:57 MHiPhone
Agent registered
[bluetooth]#

other failure mode:

bluetoothctl
Waiting to connect to bluetoothd...

how am I holding it wrong?

renegadeandy
@renegadeandy
Jan 21 20:01
@scottleibrand do i need to be concerned about loosing my 'myopenaps' directory? Does anybody keep their versions of that source controlled? Might make sense
Eric
@ecc1
Jan 21 20:04
lol the whole system was based on git and caused no end of corrupt repository problems
Kevin Marshall
@ruess
Jan 21 20:04
Hey there all, can anyone tell me if it's normal to have a solid red light on at the bottom right of their HAT?
Martin Haeberli
@mhaeberli
Jan 21 20:07
@scottleibrand sorry to bother you, but I really need help with bluetooth - some rigs work, others don't; working rigs stop working (on BT) after updates sometimes. Who has mastery of this? - I’d like to get this solved.
renegadeandy
@renegadeandy
Jan 21 20:08
@ecc1 are you saying don't git control myopenaps dir?
Martin Haeberli
@mhaeberli
Jan 21 20:12
BT - the first case was fixed by a reboot. the last case was not ...
Jon Cluck
@cluckj
Jan 21 20:15
most everything in the myopenaps dir is going to be regenerated by oref0-setup and the first few loops. you might want to keep a copy of preferences.json around to crib from after upgrading
renegadeandy
@renegadeandy
Jan 21 20:16
what about autotune and smb details?
I don't want to loose that....
Jon Cluck
@cluckj
Jan 21 20:16
if you're upgrading, it'll keep autotune
renegadeandy
@renegadeandy
Jan 21 20:16
so if i switch to dev
it wont blast away my autotune?
Jon Cluck
@cluckj
Jan 21 20:28
it shouldn't, but back it up anyway..
renegadeandy
@renegadeandy
Jan 21 20:30
Ok
and everything else inside the install dir for a specific loop....is not important to be kept?
Perhaps this project needs to define a specific working directory for the bits which should be persisted
Kevin Marshall
@ruess
Jan 21 20:34
Again, would someone mind checking if they have a solid red light atop their hat rig?
Jon Cluck
@cluckj
Jan 21 20:34
@ruess that's the charging light
Kevin Marshall
@ruess
Jan 21 20:40
Ok thanks @cluckj , just trying to figure out if my rig broke via hardware or software.
renegadeandy
@renegadeandy
Jan 21 20:40
do you know if there is available LEDS which can be controlled on the edison / explorer board? Id like to make it that a green led lights up every now and again to show that the loop is still working successfully
LadenzEntrum
@LadenzEntrum
Jan 21 20:45
Hi, my pump-loop is unsuccessful with message: {"reason":"If current system time Mon Jan 21 2019 21:27:51 GMT+0100 (CET) is correct, then BG data is too old. The last BG data was read 134.4m ago at Mon Jan 21 2019 19:13:30 GMT+0100 (CET). Temp 0 <= current basal 1.45U/hr; doing nothing. "} But ns-loop is successfull every minute. glucose.json is populated with recent data. Any suggestions? Thanks, it's my first Rig, loop did not ran once yet....
renegadeandy
@renegadeandy
Jan 21 20:53
more random errors:
Starting oref0-pump-loop at Mon Jan 21 14:51:02 CST 2019 with 5 second wait_for_silence:
Waiting up to 4 minutes for new BG: glucose.json newer than pump_loop_completed
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Preflight OK. Old pumphistory-24h, waiting for 5 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. Refgrep: monitor/status.json: No such file or directory
cat: monitor/status.json: No such file or directory
/usr/local/bin/oref0-pump-loop: line 567: test: ==: unary operator expected
cat: monitor/status.json: No such file or directory
/usr/local/bin/oref0-pump-loop: line 568: test: ==: unary operator expected

cat: monitor/status.json: No such file or directory
Couldn't refresh_pumphistory_and_meal
oref0-pump-loop failed. If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.
Unsuccessful oref0-pump-loop at Mon Jan 21 14:52:30 CST 2019
Martin Haeberli
@mhaeberli
Jan 21 21:01
More BT tethering - on the one rig that still won’t tether, it’s almost as if bluetoothd is not auto-starting. What file is supposed to hold the instructions to auto-start bluetoothd?
Jon Cluck
@cluckj
Jan 21 21:24
@renegadeandy what model pump do you have?
John Sjolund
@sjolundjohn
Jan 21 21:28
I seem to be having an issue in which one of my rigs is changing the time on my pump to the wrong time. I wake up and it is 10h of my timezone. I have confirmed timezone on the rigs to be accurate. Any thoughts on how I would go ahead and troubleshoot?
renegadeandy
@renegadeandy
Jan 21 21:38
@cluckj 722
Dave Cole
@Dave9111
Jan 21 21:43
@sjolundjohn My first thought is to turn off some rigs so you can figure out which one is doing it.
Scott Leibrand
@scottleibrand
Jan 21 21:56
agreed, troubleshoot one rig at a time
also double-check the output of date on each rig
@mhaeberli unfortunately I don't think anyone is an expert on Bluetooth tethering. we have a process that works as documented, but when something goes wrong we've never really been able to troubleshoot successfully, except to start over following the steps in the docs
I've largely given up relying on Bluetooth tethering, and just use wifi tethering myself. It's less power efficient, but far more reliable once you remember to enable it.
John Sjolund
@sjolundjohn
Jan 21 22:08
I have been able to isolate to one of the rights - I will check date output. Thought when I have updated timezone it configures it correct
Have been having all kinds of strange issues - starting to wonder if it may be pump hardware related
renegadeandy
@renegadeandy
Jan 21 22:13
@cluckj do you think moving to dev would result in a more stable system for me?
Jon Cluck
@cluckj
Jan 21 22:51
@mhaeberli it's a system process, so systemctl status bluetooth will tell you what's wrong
@renegadeandy yeah, dev is refactored and rewritten
Martin Haeberli
@mhaeberli
Jan 21 23:11
@scottleibrand - thx; any suggestion where and how bluetoothd is started normally at boot; or where I can add a command to do so? (empirically, if I start it by hand, things often work afterwards) @cluckj thx - but same question. how is it started under normal circumstances?
Jon Cluck
@cluckj
Jan 21 23:14
systemctl enable bluetooth
Jon Cluck
@cluckj
Jan 21 23:20
start/stop works too, but you may have an error that's preventing it from starting
Martin Haeberli
@mhaeberli
Jan 21 23:22
@cluckj thx, but where would I do that to do it automatically at boot? What I have found on the one rig where bluetoothd is somehow not running is that something like sudo /usr/local/bin/bluetoothd --experimental & done by hand helps
Jon Cluck
@cluckj
Jan 21 23:23
enable will add it to the list of services to start on boot
Martin Haeberli
@mhaeberli
Jan 21 23:23
ok thx. but why isn’t it already enabled after usual install? I’ll give that a try though
Jon Cluck
@cluckj
Jan 21 23:25
yeah it's usually enabled during the install
gcarlson
@gcarlson
Jan 21 23:40
Hello, can I get some help with openaps troubleshooting here? I'm trying to restart my loop after about a month off, and it can't get past startup with:
Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!)
mmtune: "916.684", 5, -55 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 Mon Jan 21 15:32:09 PST 2019
Isn't 5, -55 an acceptable tuning value?