Can apps get real-time estimated glucose values (EGVs) with the Dexcom API?
Currently, the Dexcom API offers EGV data on a three-hour delay. The Dexcom API is intended for software developers to retrieve retrospective CGM data and CGM-derived metrics for use in software applications. Real-time treatment decisions should not be made based on the data displayed to the end user, and the delay helps clarify this. Dexcom settled on the three-hour delay after consultation with FDA.
probably the wrong forum for this. I have already emailed Dexcom. Delay is average 3.5 hours because … But if you USB tether to Dexcom Clarity then you can get real-time. We are here, with openaps, of course making treatment decisions based on real-time EGVs via Share most frequently. But I would also like real-time calibrations - because then can auto-remind to calibrate when needed...
what page did you see that on? I missed it when reviewing their API docs.
perhaps https://gitter.im/nightscout/decoding-dexcom would be a good place to discuss further?
predCIs: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
remainingCIs: 0 0 0 0 0 0 0 0 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0
.1 0.1 0.1 0.1 0.1 0.1 0.1 0 0 0 0 0 0 0 0 0
cd ~/myopenaps && rm -rf .git
That will remove the directory and it will be rebuilt by the cron. If that (the rebuild) doesn’t happen automatically, then I would remove the openaps directory too and run the script fresh cd && ~/src/oref0/bin/oref0-setup.sh
cd && rm -rf myopenaps
to remove to the myopenaps directory
\
shaped predCI curve (the first line) vs. remainingCI that isn't projected to absorb over ~4h and is being projected as part of the /\
shaped remainingCI curve
smb_verify_status || ( sleep 30 && smb_verify_status ) ) && gather
root@binky:~# ifconfig
bnep0 Link encap:Ethernet HWaddr 98:4f:ee:04:1c:ca
inet6 addr: fe80::9a4f:eeff:fe04:1cca/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:67 (67.0 B) TX bytes:276 (276.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:85 errors:0 dropped:0 overruns:0 frame:0
TX packets:85 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12012 (11.7 KiB) TX bytes:12012 (11.7 KiB)
usb0 Link encap:Ethernet HWaddr 02:00:86:27:c3:e5
inet addr:10.11.12.13 Bcast:10.11.12.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr 78:4b:87:ac:5a:e8
inet addr:192.168.1.12 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::7a4b:87ff:feac:5ae8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:409243 errors:0 dropped:0 overruns:0 frame:0
TX packets:419070 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:128221700 (122.2 MiB) TX bytes:53393204 (50.9 MiB)
root@binky:~# ip -4 -o addr show dev bnep0 | awk '{split($4,a,"/");print a[1]}'
root@binky:~#
So I'd use
"curve": "rapid-acting"
For Novolog, or is that for Fiasp?