Xdrip: Push CGM data to Diabetes:M app

[TecMunky]

Diabetes:M for Android now exposes API which allows third party apps to communicate with Diabetes:M app directly. The third party apps can open Log Entry form and also push data to Diabetes:M for Android after explicit permission from the user. Developers, who are interested to integrate their apps with Diabetes:M for Android app, can get more information at https://github.com/sirmamedical/diabetes-m-addon-example.

I am willing to try my hand at this effort. If I do this I will need some help. This will be the first time I would contribute directly to any project.

My specific concerns for contributing:
Would I be stepping on an existing maintainer, or parallel activity?
What would I need to know before contributing a patch?
Would this patch fit with the current project roadmap without issues or concerns?

Once I get working code into my current build, how do I create a pull request that only includes the code changes for this patch without including other changes I have made to my build that are unrelated to this patch? Do I create a fork and/or branch explicitly for this patch? Right now I have not forked the app - I sync changes from the master branch to my local build (VCS Update) - I never sync up (VCS Commit).

A brief summary of how to create, test, and commit changes to a fork, and how to create a patch and pull request to the project, would be helpful.

-- I think I should create a fork, then a branch of that fork, then make code changes to test on a test bed (separate phone/cgm) to test my changes. Once I have working code successfully executing the patched code, then I am not sure how to proceed to get the patch tested by others, and finally integrated into the master branch of the original project. I suspect I should create a branch in the original code, apply and commit the changes there, get that branch tested by others, then create a pull request - is this correct?

Please direct me to where to find any documents, procedures, or other information sources I need to read/review.

Thanks

[doc77]

That would be awesome. A couple years ago I asked the developer of Diabetes:M if Dexcom direct upload was in his list of project updates. He replied that he could not afford the FDA hurdle. An open source solution would be great!

[TecMunky]

I have decided I will begin the preliminary work - a proof of concept - that CGM data can be successfully pushed to diabetes:m - if successful, we can discuss further the plan for integration.

[TecMunky]

I am ready to start trying to push data to diabetes:m app.

I need a suggestion about where to put the call to the new code to push Sensor Data as it comes in. For this first implementation, and for proof of concept, I only intend to push current data as it comes in from the sensor.

[kskandispersonal]

You could have a look at UtilityModels/UploaderQueue and add a new route for diabetes:m. The data actually gets sent by MongoSendTask.doInBackground(), so you'll need to add a circuit for diabetes:m, and then perform your new send method.

[dideldum]

Is there any action undertaken regarding this?
As a user of Diabetes:M and XDrip+ I would apreciate the data connection from XDrip+ to Diabetes:M.

[TecMunky]

I started work on this a while back, but then got really busy at my real
job. Been out of town a lot. I think I'm close, but don't know when I'll be
able to get back to it. I'm hoping to have it finished by the end of the
year, maybe sooner

On Oct 22, 2017 14:13, "dideldum" [e-mail] wrote:

Is there any action undertaken regarding this?
As a user of Diabetes:M and XDrip+ I would apreciate the data connection
from XDrip+ to Diabetes:M.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NightscoutFoundation/xDrip/issues/128#issuecomment-338501596,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACLc7a_zHyWYlqKF1FHN0IrQl9UBfTfmks5su5PngaJpZM4NvAAG
.

[jpsfs]

Hi!

@TecMunky do you have any news on this feature?

Best,

[filipedanunes]

Any development? Thanks!

[chuckgit99]

Any updates on this? Xdrip + diabetes:m = awesome.

[TecMunky]

I'm sorry - I thought I had updated this thread.

I abandoned this project for the simple reason that the diabetes:m crew/app won't allow data closer than 15 minutes to be used or displayed. That makes the diabetes:m app useless for CGM data.

[tolot27]

@TecMunky Please can you give a reference to "the diabetes:m crew/app won't allow data closer than 15 minutes to be used or displayed"?

[TecMunky]

@TecMunky Please can you give a reference to "the diabetes:m crew/app won't allow data closer than 15 minutes to be used or displayed"?

I searched through my old emails, and nothing is there anymore. I probably deleted the relevant emails at some point while cleaning up old stuff.

You can go to their example code and contact them from there:
https://github.com/sirmamedical/diabetes-m-addon-example

I think I even tried to manually enter data that was close together, and the app would not display any data that was closer than 15 minutes to a prior data point.

I abandoned the project when I was told by the diabetes:m team that they had no intention of displaying data closer than 15 minutes. They were somewhat adamant about that, as I recall.

Perhaps someone else can get them to move on this. I have lost all interest in dealing with them, or pursuing this any further.

I closed this issue once. I won't close it again.