These are chat archives for nightscout/intend-to-bolus
openaps report add enact/enacted.json JSON pumpbuilding set_temp_basal enact/suggested.json, and then updated your enact code to do
openaps report invoke enact/enacted.jsoninstead of the
openaps use pumpbuilding set_temp_basal
grep -q duration enact/suggested.json && echo true || echo false
grep -q duration enact/suggested.jsonshould prevent it from trying to enact that particular suggested.json. the
assert durationerror you go indicates it did try to enact something, though, so I'm having you check the logic of that code with simple true / false output
sudo chown -R pi.pi ./and I there is no sudo anywhere, everytime the loop runs it generates reports that are root. I'm considering a fresh start. Is that too drastic/unnecessary?
preflight = ! bash -c "rm -f monitor/clock.json && echo -n \"PREFLIGHT \" 2>/dev/null && openaps report invoke monitor/clock.json 2>/dev/null >/dev/null && grep -q T monitor/clock.json && echo OK 2>/dev/null || ( mm-stick warmup || oref0-reset-usb; echo FAIL 2>/dev/null ; exit 1 )"following a suggestion I saw here. Apparently clock is better than model to check communications. Whenever I had problems with model it was related to the range of the carelink stick.
?units=mg/dLto your NS endpoint, hmmm
mm-format-ns-treatmentsshould handle this maybe
treatments.json, you can do