"timestamp": "2016-03-13T19:49:51-05:00",
[report "monitor/pump-history-zoned.json"]
use = rezone
reporter = JSON
date = timestamp dateString start_at end_at created_at
adjust = missing
input = monitor/pump-history.json
device = tz
timezone = None
astimezone = True
The only place i have a TZ is here:
[report "monitor/clock-zoned.json"]
use = clock
reporter = JSON
astimezone = False
date = None
adjust = missing
input = monitor/clock.json
device = tz
timezone = PDT
I just changed it to PDT it was PST all this morning with no problems
Unknown:scripts morsen$ sudo openaps-install-udev-rules
/usr/local/bin/openaps-install-udev-rules: line 43: /etc/udev/rules.d/80-medtronic-carelink.rules: No such file or directory
failed /etc/udev/rules.d/80-medtronic-carelink.rules
/usr/local/bin/openaps-install-udev-rules: line 43: /etc/udev/rules.d/80-dexcom.rules: No such file or directory
failed /etc/udev/rules.d/80-dexcom.rules
/usr/local/bin/openaps-install-udev-rules: line 49: udevadm: command not found
@jmatheson , my hardware strategy is to hit up @eyim and ask him to tell me what to buy...but I am going to shoot for the lego style clip on hardware and most likely find a decent lipo battery to solder on. Once I have that squared away, I'll look at soldering with the Edison (and TI again). Sound decent? Anything I am missing?
I can't believe how fast development is moving. 4 months ago I was saying "Man, this is incredible! I'd love to have increased range and size (in that order) at some point" and then like a month later, both had been tackled!
Some input from an email I just got:
"The new Pi3 has of course come out to great fanfare. It's a hot item… quite literally. It runs REALLY hot! Like "singe you skin hot" in some places. This is not the case with all boards but since you are making devices that people are going to have on their person or tuck away in tight quarters you might want to take note of this.
When it comes to a DIY development board, we are big fans of the Beagle Bone. Although it is less well know we think it is far more powerful, better made and easier to incorporate into designs because of it's layout and tons of I/O capabilities. Just something to think about."
bewest@bewest-MacBookPro:~/Documents/openaps$ openaps use pump -h | grep oref0
model Get model number [#oref0] [#recommended] [#safe]
Check battery status. [#oref0]
read_bg_targets Read bg targets. [#oref0]
read_carb_ratios Read carb_ratios. [#oref0]
read_clock Read date/time of pump [#oref0]
Read insulin sensitivities. [#oref0]
Fetch the currently selected basal profile. [#oref0]
read_settings Read settings. [#oref0]
read_temp_basal Read temporary basal rates. [#oref0]
set_temp_basal Set temporary basal rates. [#oref0]
bewest@bewest-MacBookPro:~/Documents/openaps$
2164 openaps use pump set_clock --to now
2165 openaps use pump set_clock --to
2166 openaps use pump set_clock
2167 openaps use pump set_clock --to bad
2168 openaps use pump set_clock --to $(date -Iseconds)
2169 openaps use pump set_clock --to now
2170 openaps use pump set_clock monitor/clock.json
2171 openaps use pump read_clock
2172 openaps use pump set_clock --to now
2173 openaps use pump set_clock monitor/clock.json
2174 openaps use pump set_clock --to $(date -Iseconds)
2175 openaps use pump iter_pump 100
2176 openaps use pump -h
s$ openaps use pump bolus -h
usage: openaps-use pump bolus [-h] input
Send bolus command. [#warning!!!]
positional arguments:
input
optional arguments:
-h, --help show this help message and exit
Beware! This is a powerful command because it can give a lot of
insulin. Please be careful!
Not a part of oref0.
-----------------------
Requires json input with the following keys defined:
* `units` - Number of units to bolus.
Zero point one units:
{ "units": 0.1 }
Two units:
{ "units": 2 }
bewest@bewest-MacBookPro:~/Documents/openaps
openaps schedule add time-change-event "every $(dst-generate-rrule)"
or something