OpenAPS Prefs: { warn: 30, urgent: 60, enableAlerts: true }
in the logs with the settings it sees
openaps use latest-treatments shell
it craps out with no JSON object. not sure where that is supposed to come from
openaps latest-ns-treatment-time
this is what my report looks like
[report "monitor/latest-treatments.json"]
device = latest-treatments
use = shell
reporter = text
and then my device is
[device "latest-treatments"]
vendor = openaps.vendors.process
extra = ini/latest-treatments.ini
and then my ini is
[device "latest-treatments"]
fields =
cmd = nightscout
args = latest-openaps-treatment $NIGHTSCOUT_HOST
and then in my env $NIGHTSCOUT_HOST is set properly
format-latest-nightscout-treatments = ! bash -c "nightscout cull-latest-openaps-treatments monitor/pump-history-zoned.json monitor/model.json $(openaps latest-ns-treatment-time) > monitor/upload-treatments.json"
And thanks for reporting this. This is the kind of thing we really want to get fixed ASAP to be as safe as possible when it matters most.
Done
In particular, where it affects us is if it has low temped him for a while maybe 2 hours and has significant negative iob then it will try to give him extra insulin to counteract that when in reality it doesn't need to. I had hoped the auto sensitivity stuff would help but I didn't find that
sudo easy_install -ZU openaps
to update it?
@jasoncalabrese :+1:
@TC2013 I opened nightscout/cgm-remote-monitor#1545 that I hope will fix the NS OpenAPS alarms you're getting. Also gets rid of the really noisy units warnings.
openaps use latest-treatments shell
return for people?
pand