Dexcom utility for switching between mg/dl and mmol/l about nightscout.github.io

[jasoncalabrese]

@lixgbg, has already done lots of work for this in https://github.com/lixgbg/dexcom-uploader and https://github.com/lixgbg/cgm-remote-monitor

[ELUTE]

You can switch your website to mmol by using the rebased/mmol branch instead of master.

[brianhanifin]

There is a new settings interface on the website, the code is currently at rebased/settings.

[ELUTE]

Everything switched really well!

A few items...
Must set and save switch to mmol in all browsers. Just an item to note.

When saving the settings in Firefox I get the attached error. Settings are saved anyway.

On Jul 22, 2014, at 9:45 PM, Brian Hanifin [email protected] wrote:

There is a new settings interface on the website, the code is currently at rebased/settings.

—
Reply to this email directly or view it on GitHub.

[brianhanifin]

Thank you for helping test these updates!

I have made a lot of improvements today. I have fixed the Firefox issue, and I fixed a bunch of issues with mobile browsers (e.g. buttons and form fields were too small). Would you please update your site?

https://github.com/nightscout/cgm-remote-monitor/tree/rebase/settings

[ELUTE]

Deployment keeps failing:

Error: The process cannot access the file 'D:\home\site\wwwroot\node_modules\mongodb\node_modules\bson\ext\win32\ia32\bson.node' because it is being used by another process.
An error has occurred during web site deployment.
Kudu Sync to Target failed

I assume this is because I have two sites in azure…

My BG delta is also not changing… the + or - does but not the 0.0 bit

On Jul 24, 2014, at 2:17 AM, Brian Hanifin [email protected] wrote:

Thank you for helping test these updates!

I have made a lot of improvements today. I have fixed the Firefox issue, and I fixed a bunch of issues with mobile browsers (e.g. buttons and form fields were too small). Would you please update your site?

https://github.com/nightscout/cgm-remote-monitor/tree/rebase/settings

—
Reply to this email directly or view it on GitHub.

[brianhanifin]

Can you go back to the master branch for now?

I think bson.node was added by @bewest. Maybe he can shed some light.

[jasoncalabrese]

I think this is a npm problem with supertest, when I deployed last night I had to remove that dependency

[ELUTE]

I have two sites, one for testing so no big deal.

The bg delta was in my pebble code and was dividing twice I believe I have resolved that bit.

[bewest]

The bson.node error is an azure bug, I've been exchanging emails with the azure folks who confirmed it this morning. It seems to only happen when using two sites. The suggest stopping/sync/starting any trouble some sites.

[bewest]

She's depending on mmol support not in master. Stopping the site should allow it to deploy if this error persists. (Believe stop, sync, start should work.)

[bewest]

The tests are using supertest to do the test, but should only be installed during devel, the npm install --production prevents devDependencies from being installed.

[ELUTE]

stop sync start did not work

Still cannot load it

On Jul 25, 2014, at 3:16 PM, Ben West [email protected] wrote:

The tests are using supertest to do the test, but should only be installed during devel, the npm install --production prevents devDependencies from being installed.

—
Reply to this email directly or view it on GitHub.

[bewest]

@ELUTE this is now an option per browser or per server. For server side, set the DISPLAY_UNITS environment variable to mmol. Azure this is in "app settings":

[bewest]

Sorry, that last comment is in the wrong thread. The latest change to deploy.sh should fix this, I believe.

[ELUTE]

Is it possible to ensure that the error codes are being scaled too? Right now they are coming in mg/dL which I think will cause problems when we are trying to add error icons etc.

On Jul 27, 2014, at 6:56 PM, Ben West [email protected] wrote:

Sorry, that last comment is in the wrong thread. The latest change to deploy.sh should fix this, I believe.

—
Reply to this email directly or view it on GitHub.

[jasoncalabrese]

Would be nice to let the pebble js do the unit conversion
On Jul 27, 2014 6:59 PM, "ELUTE" [email protected] wrote:

Is it possible to ensure that the error codes are being scaled too? Right
now they are coming in mg/dL which I think will cause problems when we are
trying to add error icons etc.

On Jul 27, 2014, at 6:56 PM, Ben West [email protected] wrote:

Sorry, that last comment is in the wrong thread. The latest change to
deploy.sh should fix this, I believe.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#21 (comment)
.

[brianhanifin]

What do you mean by scaled? Do you want a number to be larger our smaller
on the website?

[jasoncalabrese]

scaled = converted to mmol, if we do the conversion in the pebble js the alerts can stay the same

[ELUTE]

All numbers are divided by 18 to go from mg/dL to mmol... That is great. But the error codes (1-12) that the Dex puts out if there is a problem need to be divided by 18 as well.

Does that make sense?

Sent from my iPhone

On Jul 27, 2014, at 11:06 PM, Brian Hanifin [email protected] wrote:

What do you mean by scaled? Do you want a number to be larger our smaller
on the website?
—
Reply to this email directly or view it on GitHub.

[jasoncalabrese]

I think what I want:
The pebble endpoint would the return the same exact data for the bg/delta no matter what the units setting is, but then also includes the units setting. The pebble code would use the units setting when building the message to send from the js to the c code just change the bg and delta, https://github.com/nightscout/cgm-pebble/blob/master/src/js/pebble-js-app.js#L108

[whooze]

I know this topic has been dead for a while, but DISPLAY_UNITS should be good to have in the installation guide so people know about this feature

[psonnera]

Addressed in documentation.
https://nightscout.github.io/nightscout/new_user/#step-4-fork-and-deploy-cgm-remote-monitor