can keep glucose from going over 8.5 with that
and because my doctor uses this with the same AAPS setup, says it's very nice and has similar battery life compared to my now-broken pebble2
and I found one from amazon with a cheap price
it's quite nice actually, and I can get the battery to last 6-7 days
I just like how the vivoactive looks and it does what I want
this still probably breaks in 1-2 years and I need to buy a new one
but I like this watch so far
After some digging, it seems to be related to Chrome's application cache. Firefox and Edge don't have the problem. With Chrome, a hard reload isn't enough; you have to go into Dev Tools > Application > Clear storage > Make sure 'Application cache' is checked > Clear site data.
Hi, general/data model question: why Nightscout Careportal always show entry of BGV (glucose field in json) together with treatments? it is even by various clients (like:NSClient/AAPS) that while entering Careportal treatments not only show BGV entry, but when changing time of event they even search for BGV for that speciffic moment in past and make it in-sync with BGV from then? At the same time, not all entries have glucose field.
Due to the Gitter Client being broken on Android and iOS, we're moving the discussion to Discord - see you on other side of the fence: https://discord.gg/zg7CvCQ
If someone is interested i have developed a windows taskbar app that shows the latest values from the nightscout api, screens: http://eyeone.be/NightscoutTaskbarApp/TaskbarApp.JPG
If interest i can share on github
Hello!
What could be the reason?
Log a Treatment => Submit Form
Request URL: https://url.com/api/v1/treatments/
Request Method: POST
Status Code: 404 Not Found
Error POST
ENABLE=careportal,iob
SHOW_PLUGINS=careportal,iob
No error
ENABLE=careportal
SHOW_PLUGINS=careportal
Or are you talking about a variable in a file my.env?
I am looking for some help on how to setup cgm monitor in my linux box. I did the mongo and node setup. The server seems to be up. I do not have a test device.
Also is there an API document for building wearable clients ?
@fclingen Dexcom isn't going to be able to help with that. Try to keep the xDrip app alive as much as you can (don't force-quit it, make sure background processes are allowed to run, reduce battery-saving settings, return to the app more frequently during the day). Is about all you can do.
Another option is to use the official Dexcom app (uploading to NS via the Share bridge) and also use xdrip-js in Alternate Channel mode emulating a receiver (or do the same with xDrip+, if it supports it). If you then have problems with the official app, you can report that to Dexcom and ask for a replacement transmitter if appropriate.
(He's referring to this, if you haven't found it already: https://www.reddit.com/r/diabetes/comments/c00wgk/oc_build_your_own_dexcom_app_update_bugfixes_and/)
Still not exactly officially supported by Dexcom, but if you don't mention its true nature they won't know the difference.
Brand new to this community. If anyone else is looking into why azure deploy doesn't work, my notes so far are: ARM templates were not wired up properly, using the free tier results in out of memory exceptions, heapdump fails to build at deploy time due to some missing C header files, and some of the module versions in package.json and npm-shrinkwrap.json seem to be incompatible or irrelevant in azure environment. Make sure to add IP addresses the azure web app is using to the IP whitelist on the mongodb side or it will timeout. Also some of the documentation screenshots are out of date, and constructing mongodb connection strings as documented doesn't seem to work (although using the connection string provided at mongodb.com at time of setup does). Some really rough changes that seem to get deploy working on Azure are here: https://github.com/nightscout/cgm-remote-monitor/compare/master...opengtd:master
We're all over on Discord now; if you're looking to chat about this, probably not going to get much of a response here.