Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Talk Directly to Dexcom Cloud #50

Open
wesbland opened this issue May 9, 2015 · 9 comments
Open

Talk Directly to Dexcom Cloud #50

wesbland opened this issue May 9, 2015 · 9 comments

Comments

@wesbland
Copy link

wesbland commented May 9, 2015 •
edited by bewest
Loading

I just started up with Nightscount with my Dexcom G4 Share. I'm wondering if anyone has started looking into having the Pebble app speak directly to the Dexcom cloud (pulling over the parsing code from the cgm-remote-monitor repo).

The website can still provide the historical data and trends, but the watch doesn't really need to go through the website (which for me is extremely flakey because of Azure), when it can just query the last datapoint directly from the Dexcom servers and get all of the information it needs for the watchface (Dexcom provides the raw value, trending direction, time, etc.).

For some people, this is enough since we can use the Dexcom device itself to get more long term trends and it would be a more reliable way of getting the data than going through the website.

I've started taking a look at this, but I work in High Performance Computing in C all day so getting up to speed with user facing APIs and Javascript with JSON objects will take me a bit of time, so it will be a while before I can get a PR together.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/13952534-talk-directly-to-dexcom-cloud?utm_campaign=plugin&utm_content=tracker%2F2453141&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2453141&utm_medium=issues&utm_source=github).
@hackingtype1
Copy link
Contributor

I have this working, a bit rough, but it works just fine. Newer version
will support this, I'll try to post code soon.

On Saturday, May 9, 2015, Wesley Bland [email protected] wrote:

I just started up with Nightscount with my Dexcom G4 Share. I'm wondering
if anyone has started looking into having the Pebble app speak directly to
the Dexcom cloud (pulling over the parsing code from the
cgm-remote-monitor repo).

The website can still provide the historical data and trends, but the
watch doesn't really need to go through the website (which for me is
extremely flakey because of Azure), when it can just query the last
datapoint directly from the Dexcom servers and get all of the information
it needs for the watchface (Dexcom provides the raw value, trending
direction, time, etc.).

For some people, this is enough since we can use the Dexcom device itself
to get more long term trends and it would be a more reliable way of getting
the data than going through the website.

I've started taking a look at this, but I work in High Performance
Computing in C all day so getting up to speed with user facing APIs and
Javascript with JSON objects will take me a bit of time, so it will be a
while before I can get a PR together.

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

@wesbland
Copy link
Author

wesbland commented May 9, 2015

Awesome. If you want a tester, point me at the repo and I can give it a shot.

On May 9, 2015, at 6:00 PM, John Costik [email protected] wrote:

I have this working, a bit rough, but it works just fine. Newer version
will support this, I'll try to post code soon.

On Saturday, May 9, 2015, Wesley Bland [email protected] wrote:

I just started up with Nightscount with my Dexcom G4 Share. I'm wondering
if anyone has started looking into having the Pebble app speak directly to
the Dexcom cloud (pulling over the parsing code from the
cgm-remote-monitor repo).

The website can still provide the historical data and trends, but the
watch doesn't really need to go through the website (which for me is
extremely flakey because of Azure), when it can just query the last
datapoint directly from the Dexcom servers and get all of the information
it needs for the watchface (Dexcom provides the raw value, trending
direction, time, etc.).

For some people, this is enough since we can use the Dexcom device itself
to get more long term trends and it would be a more reliable way of getting
the data than going through the website.

I've started taking a look at this, but I work in High Performance
Computing in C all day so getting up to speed with user facing APIs and
Javascript with JSON objects will take me a bit of time, so it will be a
while before I can get a PR together.

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

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

@hackingtype1
Copy link
Contributor

Will do, right now it's hard coded to my son's data, will add a config page
and clean up some animations I was toying/learning with and it'll be good
to go.

On Saturday, May 9, 2015, Wesley Bland [email protected] wrote:

Awesome. If you want a tester, point me at the repo and I can give it a
shot.

On May 9, 2015, at 6:00 PM, John Costik <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

I have this working, a bit rough, but it works just fine. Newer version
will support this, I'll try to post code soon.

On Saturday, May 9, 2015, Wesley Bland <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

I just started up with Nightscount with my Dexcom G4 Share. I'm
wondering
if anyone has started looking into having the Pebble app speak
directly to
the Dexcom cloud (pulling over the parsing code from the
cgm-remote-monitor repo).

The website can still provide the historical data and trends, but the
watch doesn't really need to go through the website (which for me is
extremely flakey because of Azure), when it can just query the last
datapoint directly from the Dexcom servers and get all of the
information
it needs for the watchface (Dexcom provides the raw value, trending
direction, time, etc.).

For some people, this is enough since we can use the Dexcom device
itself
to get more long term trends and it would be a more reliable way of
getting
the data than going through the website.

I've started taking a look at this, but I work in High Performance
Computing in C all day so getting up to speed with user facing APIs and
Javascript with JSON objects will take me a bit of time, so it will be
a
while before I can get a PR together.

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

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

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

@hackingtype1
Copy link
Contributor

Super simple, but here's where I'll start - will get it working for current
& new pebbles, stay tuned.

On Saturday, May 9, 2015, John Costik [email protected] wrote:

Will do, right now it's hard coded to my son's data, will add a config
page and clean up some animations I was toying/learning with and it'll be
good to go.

On Saturday, May 9, 2015, Wesley Bland <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

Awesome. If you want a tester, point me at the repo and I can give it a
shot.

On May 9, 2015, at 6:00 PM, John Costik [email protected]
wrote:

I have this working, a bit rough, but it works just fine. Newer version
will support this, I'll try to post code soon.

On Saturday, May 9, 2015, Wesley Bland [email protected]
wrote:

I just started up with Nightscount with my Dexcom G4 Share. I'm
wondering
if anyone has started looking into having the Pebble app speak
directly to
the Dexcom cloud (pulling over the parsing code from the
cgm-remote-monitor repo).

The website can still provide the historical data and trends, but the
watch doesn't really need to go through the website (which for me is
extremely flakey because of Azure), when it can just query the last
datapoint directly from the Dexcom servers and get all of the
information
it needs for the watchface (Dexcom provides the raw value, trending
direction, time, etc.).

For some people, this is enough since we can use the Dexcom device
itself
to get more long term trends and it would be a more reliable way of
getting
the data than going through the website.

I've started taking a look at this, but I work in High Performance
Computing in C all day so getting up to speed with user facing APIs
and
Javascript with JSON objects will take me a bit of time, so it will
be a
while before I can get a PR together.

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

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

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

@robertlevy
Copy link

+1

@hackingtype1
Copy link
Contributor

It's been working well, b&w code is getting wrapped up now. Hope to have it
up for folks to test out this weekend.

On Thursday, May 21, 2015, Robert Levy [email protected] wrote:

+1

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

@wesbland
Copy link
Author

Any news? Anything we can do to help? I'm happy to dig into the code if it would be helpful.

@hackingtype1
Copy link
Contributor

Hi! Sorry, it's out and you can find it here:
http://www.nightscout.info/wiki/labs/pebble-pebble-time-watchface-wshare-support

On Thursday, June 11, 2015, Wesley Bland [email protected] wrote:

Any news? Anything we can do to help? I'm happy to dig into the code if it
would be helpful.

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

@wesbland
Copy link
Author

That's the best kind of response. "It's already done. Go try it out!"

On Thu, Jun 11, 2015 at 1:31 PM, John Costik [email protected]
wrote:

Hi! Sorry, it's out and you can find it here:

http://www.nightscout.info/wiki/labs/pebble-pebble-time-watchface-wshare-support

On Thursday, June 11, 2015, Wesley Bland [email protected] wrote:

Any news? Anything we can do to help? I'm happy to dig into the code if
it
would be helpful.

—
Reply to this email directly or view it on GitHub
<
https://github.com/nightscout/cgm-pebble/issues/50#issuecomment-111232798>

.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wesbland @robertlevy @hackingtype1