These are chat archives for nightscout/intend-to-bolus
service stop cron && killall -g oref0-pump-loopfirst?
already in useerror
Here's my preferences.json:
I ran the autotune command in the docs and it said:
Couldn't download ns-treatments.json
cat preferences.json | jq .to double check format of preferences
openaps pump-loop, which you shouldn't do.
When I try to do tab complete on oref0<tab>, I get:
mmtune: "916.636", 0, -99is that normal? Or should I be looking for a pump replacement?
added process://ns/nightscout/ns NIGHTSCOUT_HOST API_SECRET /usr/local/bin/nightscout: line 338: json: command not found close failed in file object destructor: sys.excepthook is missing lost sys.stderr Traceback (most recent call last): File "/usr/local/bin/openaps-import", line 89, in <module> app( ) File "/usr/local/lib/python2.7/dist-packages/openaps/cli/__init__.py", line 51, in __call__ self.run(self.args) File "/usr/local/bin/openaps-import", line 77, in run candidates = json.load(args.input) File "/usr/lib/python2.7/json/__init__.py", line 291, in load **kw) File "/usr/lib/python2.7/json/__init__.py", line 339, in loads return _default_decoder.decode(s) File "/usr/lib/python2.7/json/decoder.py", line 364, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode raise ValueError("No JSON object could be decoded") ValueError: No JSON object could be decoded Could not run nightscout autoconfigure-device-crud
The medtronic enlite appears it would cost about £2520/year ($3323 USD)
The G5 appears it would cost about £3402/year ($4487 USD) (excluding introductory discount on first pack and no receiver).
I have found with using my Libre that the readings are usually no more that 0.3mmol/L (5mg/dL) different once calibrated within Xdrip - using the Libre reader I would agree the values can be much larger
Invalid Datestring itself doesn't come directly from any of the oref0 code
Yes I thought that but I cannot see where it comes from. And I have no idea how to fix this lack of knowledge. ;-)
jq .instead. The latest oref0 0.5.5 release does the latter, but if you're already on that perhaps a spot was missed.
Hi - I am thinking of doing a big update of my Rigs - being on Fiasp the 0.6.0 algorithm is very attractive. Any comments on a) when to go about doing this. IE is it soon to move out of dev so I should wait?
Additionally, and insights or readings I should review before digging in? Thanks in advance!
"dateString": "2017-10-10T19:20:02+02:00", "sgv": 101, "date": 1507641602674, "device": "medtronic-600://6212-1079976", "_id": "59dcc9988552191d7a7a4ae8",
"_id": "59dcc9988552191d7a7a4ae8", "date": 1507641602674, "dateString": "Tue Oct 10 15:20:02 GMT+02:00 2017", "device": "medtronic-600://6212-1079976",
date(for localtime) and
date -u(for UTC)? are those both right?
carb ratio turned out to be ~14. First day the autotune results are really close to pump values:
Parameter | Pump | Autotune ------------------------------------- ISF [mg/dL/U] | 126.000 | 128.142 Carb Ratio[g/U]| 14.000 | 14.205
Results of today:
oref0_temp_target.pythat can read/write the temp target from the command line. i'm thinking of including an option that will also look back in the pump history and in case a (large) meal bolus has been done can set a activity temp target. i don't want to rely on iftt stuff
"enableSMB_with_COB"=falsewith this CR will fix it without any temp targets.
"enableSMB_with_temptarget"to see, if that fixes the fast falling bg's during activity. will report back. out for now.