I will contact Tidepool to discuss this and hopefully we can get interested people testing it soon. Overall it is looking good and a very worthy addition to xDrip in my opinion as this is something I would rate as an urgent priority for the community.Īs far as I understand it, the next steps would need to be Tidepool agreeing that it would be possible for the api to be utilized by xDrip users. 2021 Debut author Nicole Willson is another person Id like to meet in real life. It seems to take about 1 second to upload an entire days worth of data. To avoid problems with duplicated data I went with a completely linear upload strategy from oldest to newest never repeating the same uploaded time segment. It uses the data pulled from AAPS to upload the dynamic basal rate information. It supports CGM data from all collectors, manual and automated synced blood test data, treatment items entered in xDrip or via Nightscout or from any followers or pump synchronization. I am fairly confident it will be possible to modify this very quickly as required. I've implemented it to be as modular and adaptable as possible in terms of the data structures, rest-api endpoints and the message sequence, bearing in mind the expectation that the api may be subject to change. So I have a working implementation for xDrip+ written now (many thanks to for the proof-of-concept c# example tool and Tidepool for access to the api)
0 Comments
Leave a Reply. |