get more data from share API

[bewest]

• figure out what data is available
• decide which data to get
  • create way to get data
  • do something with the data

CC. @channemann

[bewest]

Needs this first: #15

[bewest]

Also, no sense in reverse engineering. Let's see if our blooming relationship/partnership with Dexcom can help us out here. Which data would we like to do something with? Let's ask Dexcom a well framed question about that data.

[channemann]

I'm most interested in a simple tool that can download just timestamp / glucose for all records in the database of a given user (or, perhaps, the last n records). IF things like sensor starts and stops, calibration events, and error events (out of range, ???, etc) are available, those would be nice-to-haves.

[alexandre-normand]

I'd be interested in hearing what other APIs you find out. I'm thinking of changing https://github.com/alexandre-normand/glukloader to get the data from the share API now that I have a G5 but I'd be losing the event data and the calibration data unless I find APIs that allow me to get that data too.

[bewest]

@alexandre-normand: Very good to hear from you. @StephenBlackWasAlreadyTaken did some work documenting endpoints here: https://gist.github.com/StephenBlackWasAlreadyTaken/adb0525344bedade1e25. Have you tried pairing to G5 directly? See https://github.com/loudnate/xDripG5 for more info on G5 direct.

[alexandre-normand]

Pairing the G5 directly would be nice longer term (glukloader could become its own iOS app with better integration for context data (insulin, meals, etc.)) but I'll probably go with something quick to get things working again with glukit. The glucose readings is still the only essential piece of data and it's enough to get things functional again.

Thanks for your continuing your awesome work, @bewest :)