Tandem Source Compatibility

[jwoglom]

Update: Tandem Source does not appear to break compatibility with t:connect and tconnectsync, at least as of June 2024. This means it is safe to utilize Tandem Source, and tconnectsync should still be able to successfully grab pump data and feed it into Nightscout. As always, if you experience any issues which you suspect may be related to the Tandem Source rollout, please open a new GitHub issue or reply in this thread.

Tandem sent an email today about the general availability of Tandem Source, a replacement for tconnect. At this time, I don't know how opting in to using Source might affect data appearing in tconnect, but it is extremely likely to break tconnectsync. At this time, DO NOT upgrade to Tandem Source if you'd like tconnectsync to continue to work properly. If and when tconnectsync is able to support Tandem Source, I will update this issue and release a new major version.

[MatthewMazaika]

I'm not sure when it happened, but we have been on-boarded to Tandem Source and tconnectsync is continuing to work without issue

when logging into portal.tandemdiabetes.com we go through a series of redirects before landing in the portal at source.tandemdiabetes.com/

i wouldn't consider this a 🟢 for folks to flip over, but as of today it doesn't appear that everyone will immediately stop working if they got moved to Tandem Source

[jwoglom]

Thanks for sharing @MatthewMazaika. I have been meaning to update the description that Tandem Source -- at least for now -- seems to grab from the same underlying backend as t:connect that is uploaded from the mobile apps, so tconnectsync continues to work. When I have more bandwidth, I'm hoping to add a new "Tandem Source-only" mode into tconnectsync to allow Nightscout syncing to still work even once tconnect in its entirety has been retired, using the new Tandem Source API endpoints.