sudo /usr/local/bin/bluetoothd --experimental
@CaptainBalou to do it "properly" from the CLI without copy-paste you'll want to clone the repo, set up your own repo as your git remote on the rig, push to there, and then PR.
Thanks Scott. I understood. So I can send my changes up to my repo. But then I have to PR those changes again to the community, right? So I cannot get around using the github website, correct?
mealCarbs
at zero at around 11:30 am, and then the carbs from every meal are added to mealCarbs
until it hits 209 and stays there until midnight. It looks like the mealCOB
never hits zero before the next meal so all of the meals coalesce into one. Does this mean that autotune only tunes CR over this time (11:30 to midnight)? Is this the expected behaviour? Our kid's meals weren't particularly close over the day. There were also a few periods of lost data overnight (Dex question marks) - would that play havoc with the autotune algorithm?
IOB 4.89 > max_iob 4
The IOB amount was correct, but those were manual boluses and there were no SMBs and hardly any high-temping in the hours before. From my understanding max_iob should still only take IOB from high-temping and SMBs into account.
{
"enteredBy": "DoButton",
"eventType": "Temporary Target",
"reason": "Low Treatment",
"carbs": 5,
"targetTop": 110,
"targetBottom": 110,
"duration": 45,
"insulin": null
},
$ iconv -f ascii -t ascii
<paste text to be checked here>
CTRL-D