You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tidepool's PC uploader obtains pump data from the pump. However, the uploader requires connecting the pump via USB to a computer running the Tidepool uploader.
A Tidepool uploader that obtains the pump data from tconnect would avoid the wait and hassle of connecting via USB.
The endstate would be an automatic uploader.
Would this be a totally new tool 'tconnectsync-to-Tidepool' or an additional capability of tconnectsync?
The text was updated successfully, but these errors were encountered:
Related to #33 -- it's debatable whether a multi-data platform approach is best for tconnectsync to move towards. I found a project https://github.com/skalahonza/TidepoolToNightScoutSync which looks like it might only synchronize in the other direction.
Speaking as the maintainer of the project, I'd be willing to consider supporting both nightscout as well as systems like tidepool but it would require some rearchitecting of the code as well as significantly more testing. On a ~6 month time span, I could see it potentially happening. There are enough things to improve with the current featureset first :)
This one is less important to us than SugarMate. The endo uses Tandem's reports but would use TidePools reports if they were available. TidePool reports are more for settings analysis (like Dexcom Clarity) than for daily monitoring. Having tconnectsync support would eliminate the need for hooking the pump up to the computer once a week. On iOS, TidePool has an uploader that pulls data from Apple Health. Since Dexcom writes BG to Apple Health getting the data to TidePool is effortless. Tandem doesn't write anything to Apple Health so that option doesn't work. I don't think Android users have any automated ability with TidePool since there is nothing equivalent to Apple Health. They have to use the computer uploader.
Tidepool's PC uploader obtains pump data from the pump. However, the uploader requires connecting the pump via USB to a computer running the Tidepool uploader.
A Tidepool uploader that obtains the pump data from tconnect would avoid the wait and hassle of connecting via USB.
The endstate would be an automatic uploader.
Would this be a totally new tool 'tconnectsync-to-Tidepool' or an additional capability of tconnectsync?
The text was updated successfully, but these errors were encountered: