Hi all, just wanted to seek to understand some points in the OpenAPS documentation. Specifically here: http://openaps.readthedocs.io/en/latest/docs/Resources/switching-between-DIY-systems.html
The documentation indicates that, if using Loop and OpenAPS, you must turn off Loop's ability to write to Nightscout. In my case, I have been using the Loop app and Loop watch app to enter carbs and issue bolus commands to my pump; Loop then writes that information to my Nightscout site.
When I'm at home, I switch to "open loop" mode on my phone, for Loop, so that my OpenAPS rigs at home take over.
I'm not sure I understand the warnings about suboptimal post-meal decisions after Loop writes the data to NS. Could anyone explain this to me in more detail?
anyone able to successfully get the pi0-HAT to reboot if it is plugged into a power supply? I have unsuccessfully tried
reboot and sudo shutdown -r now and sudo reboot
@cluckj ?
@scottleibrand might also be worth noting that assumptions that the code is rebooting a pi may not work if the rig is plugged into a power source. What scripts are there that have reboots associated with them? Radio errors? The setup script? and revising the docs to alert people to the need to unplug in order to reboot
actually for that matter…i can’t get it to reboot even when not plugged in, unless i physically flip the switch
I've never had a problem with
reboot
what does it do when you try?
are you implying from that link that it shuts down and doesn't start back up?
from that link it sounds like your SD card might be suboptimal. what kind are you using?
@Kdisimone - i normally
reboot now from root ,which has a # prompt. if not root, sudo reboot now should work
does not shut down at all. The rig thinks about the command for awhile…and never actually shuts down. goes back to the prompt. Never loses ssh connection
very strange. I suspect your image...
sanDisk Ultra plus 16gb
should work. pita, but may be worth rebuilding
then checking first, almost, that
sudo reboot now works
sudo reboot now does not work
i know; i’m suggesting flashing a NEW image, then making sure it works
because if something that basic isn’t working, then… i’m kinda worried
make sure it works before finishing the rest of the install.
ok, next card works before openaps install…let’s see how after goes ;)
both these cards were burned with same image, one after the other
:+1:
all of mine happily obey
sudo reboot now
actually…waiting for it to actually get back online still. it did at least break the ssh
did you change its name?
(yet)
sometimes it pays to note the ip address before reboot
because name service can take a little longer to start
i’ve been watching the router itself and connected devices
It successfully killed the ssh, but has not gotten back online
strange
and no, i did not change the name.
confirming you burned 2018-04-18 raspbian stretch lite
does it ping?
yes, using piBakery and latest raspbian lite
ok, I was using Etcher on a Mac and the above raspbian lite
how can i ping if i can’t ssh? ;)
i haven’t played with piBakery yet
in terminal you can ping FROM your Mac TO the Pi (if it’s up) even if you can’t ssh
sometimes
pi@raspberrypi:~ $ sudo bash
root@raspberrypi:/home/pi# sudo reboot now
Connection to raspberrypi.local closed by remote host.
Connection to raspberrypi.local closed.
Kathryns-iMac:~ iMac4K$ ssh pi@raspberrypi.local
^C
it was not up
do you see raspberrypi.local on your router
ping raspberrypi.local
(maybe it wont’ find the name)
on a fresh card, before you ssh pi@raspberrypi.local, try ping raspberrypi.local that will then show you the addrss
i rebooted so yes, now it is on
ok
still not working from a command line to reboot though
super strange - which precise stretch lite image are you using?
i WONDER if piBakery cooks the image differently from Etcher?
md5s:
1a741ec3b45dc7675a314d1efe2f28a8 2018-04-18-raspbian-stretch-lite.img
fc2b93c26ceeb1c54e21b285653bb106 2018-04-18-raspbian-stretch-lite.zip
(I assume they match yours)
I have a different question:
often, especially at night, sustained highs are not contained, despite SMB, etc. Unless and until in many cases, we set a temp target to 109-109 - a trick I learned from @scottleibrand some time ago, which makes it more ‘aggressive’ about bringing sugars down. so the question is: - what am I missing? what could I tune better? we’re trying to follow auto - tune suggestions to a degree, but...
max_iob at the moment is 8; I don’t remember what the relevant (723) pump maximums are set to
do you still have targets set fairly high?
target is 120
(pump target, that is)
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.9.80+ #1098 Fri Mar 9 18:51:28 GMT 2018 armv6l GNU/Linux
pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
pi@raspberrypi:~ $root@etghopenaps9:~# uname -a
Linux etghopenaps9 4.14.34+ #1110 Mon Apr 16 14:51:42 BST 2018 armv6l GNU/Linuxroot@etghopenaps9:~# cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs”
so i wonder why ‘my’ kernel is more recent than ‘your’ kernel
maybe download a new raspbian-stretch-lite image?
not that this should make a difference…
pibakery must not have updated their img fetch
:+1: seems like a likely explanation
suggestions on tuning openaps?
for “sustained” issues, and especially when we notice sustained highs, we start by adjusting the underlying basal rates for the time periods we are having problems.
figured out the reboot issue. Can’t have piBakery’s version of “reboot” in the recipe you write with. Seems as though it doesn’t execute. Leaving that out fixed things. Don’t need the updated kernel. But, easy enough to update kernel after pibakery
K yay!
@Kdisimone thx re tuning
@mhaeberli would concur re look at underlying settings if you're seeing patterns of highs
:+1:
offline atm due to dexcom tx unwarned expiry - hope to be online again in the AM; I’ll also look at autotune results again...
btw, noticed this in Loop channel ps2/rileylink_ios#402 - some more treasured Medtronic commands; don’t know if any of these do us any good… but it looked interesting
@ecc1 ^ might be interested to take a look
:+1:
@Kdisimone that might be worth us posting an issue to the pibakery repo?
and hah, pibakery is using a <4.10 kernel,
master should install just fine on it
Hi all - is anyone using the G6 with OpenAPS yet? Debating whether to order now or wait.
Hi all, I am still at loss. I have completed started my NS website from scratch, and started fresh on rig from "step 2" of installation. Autotune will not adjust carb ratios. Carbs are reporting from NS, but I am getting the following info when running autotune:
CREndIOB: 0.426 CREndBG: 133 CREndTime: Fri Jun 15 2018 03:50:04 GMT-0600 (MDT)
Ignoring 800 m CR period.
1 mealCOB: 4.4 mealCarbs: 133 basalBGI: 5.5 BGI: -2.5 IOB: 0.4 at 03:50:04 dev: 0.25 avgDelta: -2.25 csf
oref0-autotune-core autotune.2018-06-14.json profile.json profile.pump.json > ne wprofile.2018-06-14.json
CRTotalCarbs: 0 CRTotalInsulin: 0 totalCR: NaN
In better news, the NS Autotune Report (WIP site), is now showing a change in CR
@kelseyyearick that means that, based on your settings and data, carbs haven’t finished absorbing by 4am, so it can’t calculate CR.
And none of the breakfast or lunch carbs finished absorbing before the next meal either. Are any of your settings way off?
No, carb ratio is 1:5, and it should be 1:5.1 or 2. I am pregnant so I clear autotune every two weeks and run fresh and I eat a lot during the day?
@scottleibrand the last carbs I had last night were around 7:30 pm
just did a re-install of refactor; got this error message when cron was being scheduled at the end:
Would you like to remove your existing crontab first? y/[N] y
no crontab for root
no crontab for root
Dexcom G4 Share serial not provided: continuingfyi
that's not an error
it's a warning. if you don't like it, PRs welcome.
ok, thx - in my case we are set up for G5; didn’t know why a serial number would be needed for G4 share...
it's needed if you want to connect to the G4 Share receiver over Bluetooth LE
:+1: (but not so configured in this case - so I can put this on my list of PRs I ‘should’ do).
probably you'd want to add a check there to only print that if the G4 option was selected
and maybe squash the
no crontab for root messages as well by redirecting the crontab -r output to debug-only (&3 I think)
:+1:
error or not, getting this message; display stays stuck at unicorn:
2018-06-15T22:02:54.032Z
Checking deliverAt: 2018-06-15T22:02:54.032Z is within 1m of current time: Fri 15 Jun 15:02:54 PDT 2018
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"temp":"absolute","bg":169,"tick":-5,"eventualBG":108,"insulinReq":0,"reservoir":"261.1\n","deliverAt":"2018-06-15T22:02:54.032Z","sensitivityRatio":1,"COB":0,"IOB":1.419}
"COB: 0, Dev: -4, BGI: -3, ISF: 40, CR: 6, Target: 100, minPredBG 118, minGuardBG 98, IOBpredBG 98; Eventual BG 108 > 100 but Min. Delta -5.28 < Exp. Delta -3; setting current basal of 1.3 as temp. 22m left and 1.35 ~ req 1.3U/hr: no temp required"
IOB: [169,164,159,154,150,146,142,138,135,132,129,127,125,123,121,119,117,116,114,113,111,110,109,107,106,105,105,104,103,102,102,101,101,100,100,100,99,99,99,99,99,99,98]
ZT: [169,166,163,160,158,155,153,150,148,146,145,143,142,141,140,139,138,138,138,138,139,139]
No smb_enact needed. Temp refreshed: monitor/temp_basal.json: {"duration":21,"temp":"absolute","rate":1.35}
No bolus needed. Settings less than 30 minutes old. Your instance of oref0 [0.7.0-dev, 0.7.0-dev] is up-to-date.
Completed oref0-pump-loop at Fri 15 Jun 15:02:58 PDT 2018
/root/src/openaps-menu/scripts/status.js:103
var x = 2 + zero_x + Math.round(((((bg[i].date - zerotime)/1000)/60)/5));
^
TypeError: Cannot read property 'date' of undefined
at Object.<anonymous> (/root/src/openaps-menu/scripts/status.js:103:46)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:140:18)
at node.js:1043:3
Starting oref0-pump-loop at Fri 15 Jun 15:03:06 PDT 2018 with 26 second wait_for_silence:both on 0.7.0-dev and on 0.7.0-refactor
Is there any reason not to use a fast 64GB SD on pi-hat setup? Not sure if there are OS related size limits. I'll be offline a fair bit and wanted the additional storage if possible.
heh i don't think you need that much. i think we're at 2.5 of a 16GB one?
:+1: re 16 GB (I’m running 32GBs, but can’t imagine coming close…)
so what am I missing that breaks the status.js script?
@mhaeberli is there anything weird going on in your
monitor/glucose.json?
not that I can see; tail contains, for example:
{
"direction": "Flat",
"trend": 4,
"dateString": "2018-06-15T11:43:00-07:00",
"sgv": 149,
"device": "share2",
"date": 1529088180000,
"_id": "5b2408f2c385302cef5d3dca",
"type": "sgv",
"glucose": 149
}head contains:
{
"direction": "Flat",
"trend": 4,
"dateString": "2018-06-15T15:17:54-07:00",
"sgv": 154,
"device": "share2",
"date": 1529101074000,
"_id": "5b243b56c385302cef600d46",
"type": "sgv",
"glucose": 154
},
maybe delete these and wait for fresh ones to come in via share?
@mhaeberli yes, that one is a TypeError ;-)
I wonder if you have a record in glucose.json without a
date field
based on grep | wc ; 38 records with { ; 38 records with date field
i’m not a .js wiz; is there a print i can add to the status.js file around the error at line 103 that would show me more?
fwiw, the current data has big gaps in it; it started only around 11:45 this morning after a day offline, and lost another 1/2 hour in the middle...
console.error(bg[i]) would print each bg record
k I’ll try that and report learnings...
{ direction: 'FortyFiveUp',
trend: 3,
dateString: '2018-06-15T11:52:55-07:00',
sgv: 164,
device: 'share2',
date: 1529088775000,
_id: '5b240b4ac385302cef5d6e96',
type: 'sgv',
glucose: 164 }
{ direction: 'FortyFiveUp',
trend: 3,
dateString: '2018-06-15T11:47:56-07:00',
sgv: 157,
device: 'share2',
date: 1529088476000,
_id: '5b240a1ec385302cef5d5bd5',
type: 'sgv',
glucose: 157 }
{ direction: 'Flat',
trend: 4,
dateString: '2018-06-15T11:43:00-07:00',
sgv: 149,
device: 'share2',
date: 1529088180000,
_id: '5b2408f2c385302cef5d3dca',
type: 'sgv',
glucose: 149 }
undefined
/root/src/openaps-menu/scripts/status.js:104
var x = 2 + zero_x + Math.round(((((bg[i].date - zerotime)/1000)/60)/5));
so it’s like the tail of the value has an undefined stuck in it...
tail -2 /root/myopenaps/monitor/glucose.json | od -x -a
0000000 2020 0a7d 0a5d
sp sp } nl ] nl
0000006
ok
I bet it's the gaps
I think I can fix that...
k
:muscle:
@cluckj if you want to send me version to test somehow, let me know and i can try it
what are the records around:
{ direction: 'Flat',
trend: 4,
dateString: '2018-06-15T11:43:00-07:00',
sgv: 149,
device: 'share2',
date: 1529088180000,
_id: '5b2408f2c385302cef5d3dca',
type: 'sgv',
glucose: 149 }
(it's from the previous day, right?)
no; all from today.
today is the 15th here.
CGM transmitter broke yesterday and began running again just about 5 hours ago
hang on a minute for neighbor records
lol, I mean the record prior to the 11:43 one
{
"direction": "FortyFiveUp",
"trend": 3,
"dateString": "2018-06-15T11:52:55-07:00",
"sgv": 164,
"device": "share2",
"date": 1529088775000,
"_id": "5b240b4ac385302cef5d6e96",
"type": "sgv",
"glucose": 164
},
{
"direction": "FortyFiveUp",
"trend": 3,
"dateString": "2018-06-15T11:47:56-07:00",
"sgv": 157,
"device": "share2",
"date": 1529088476000,
"_id": "5b240a1ec385302cef5d5bd5",
"type": "sgv",
"glucose": 157
},
{
"direction": "Flat",
"trend": 4,
"dateString": "2018-06-15T11:43:00-07:00",
"sgv": 149,
"device": "share2",
"date": 1529088180000,
"_id": "5b2408f2c385302cef5d3dca",
"type": "sgv",
"glucose": 149
}
]
so 11:43 is the FIRST (or LAST) record depending on how you view it...
oh
is there something obviously wedged someplace?
at the risk of being an idiot, is there a way of easily trapping the excption that bg[i] is somehow undefined and just skipping the rest of the code in the if statement?
yes, just wrap it in an
if (bg[i]) { ... } block
I'm actually not sure why that's breaking if all the records have a date field
@cluckj @scottleibrand thx
the enumerator is returning ‘undefined’ at the last i of bg[i]
note the code reads:
for (var i = 0; i <= numBGs; i++) {
but maybe should read:
for (var i = 0; i < numBGs; i++) {
?
i’ll try that, too
yeah, that should fix it
hmm yeah
by the way, IF that solves it, I don’t know why it works at all even if data is more complete
or maybe ++i
I wonder if it normally doesn't use the whole glucose.json file?
so it only errors when there are fewer records that can be displayed on the screen?
no, it usually doesn't :)
yeah
dumb q - is array zero indexed or 1 indexed
k < vs <= did NOT fix per logs
changing per scott to ++i
(or I can hit it with the hammer of guarding fully against undefined…)
it does sound like it's incrementing past where it should
:+1:
like it's going for bg[39].date?
when there are only 38
:+1: running regression will report
if that doesn't work, try taking out the if statement that does
numBGs++
I added some diagnostic code; note numBGs is 72, but bg len is 50
numBGs:72
len bg:50
so maybe enumerate to min(numBGs, bg.length)?
hmm
Hello, I have a question about iob, can Anyone help to clarify? If iob is nagative, is that means some base basal missed previously? If iob is very big And bg keep high not going down, is that means base basal is too low? so base basal is very important in closed loop, And also we can set our base basal more accurate than pump, since it can be dynamic adjusted. Is my understanding correct?
@mhaeberli yeah...if bg.length < numBGs, set numBGs = bg.length?
console.error("numBGs:" + numBGs)
console.error("len bg:" + bg.length)
// for (var i = 0; i < numBGs; ++i) {
var iterMax = Math.min(numBGs, bg.length)
for (var i = 0; i < iterMax; ++i) {
console.error(i)
console.error(bg[i])
var x = 2 + zero_x + Math.round(((((bg[i].date - zerotime)/1000)/60)/5));
or, without debugging:
var iterMax = Math.min(numBGs, bg.length)
for (var i = 0; i < iterMax; ++i) {
var x = 2 + zero_x + Math.round(((((bg[i].date - zerotime)/1000)/60)/5));
can I put that back in YOUR lap to PR? confirmed that this fixed it.
yep
(via regression)
:+1: :clap: thx SO much!
no, thank YOU
:-)
this is a nice bug
:+1:
does it also work with
for (var i = 0; i <= iterMax; ++i) {
(<=)
i’ll try and report
thanks, it'll miss a BG record if it's just <
usually you sohudl use
< if your array is 0 based... i think the joke goes something like: there are 2 hard programming errors: "off by one errors"
lol okay
~ 5 minutes to ‘proof'
you can call the script directly from the commandline if you want
good point, but, if you appreciate the reference to Arlo Guthrie, Alice’s Restaurant, “ill just wait for the tune to come around here again on the guitar…"
@mhaeberli and @danamlewis Hahah, thanks!