Stop using ws2 therapytimeline endpoint

[jwoglom]

WS2 therapytimeline is currently used to fetch CGM, IOB, bolus, and NON-ControlIQ basal data. The WS2 therapytimeline API endpoint is excruciatingly slow to respond to queries at times -- Tandem's API frontend sometimes returns http 500's since it times out querying its backend. It can sometimes take multiple minutes to get a response as it refuses to return results entirely. The end data also needs to be heavily processed.

Equivalent data should exist in the ControlIQ therapy_events endpoint, which contains at least Basal, Bolus, and CGM data.

[PorkShoulderHolder]

Oh perhaps this is related to my issue #44 - does this endpoint not have any basal data in it if ControlIQ is being used?

[jwoglom]

Replied on #44 -- I'm hoping to fully deprecate the use of the ws2 endpoint in tconnectsync because it's incredibly unreliable and is currently a blocker to faster synchronization.

[vin]

Maybe they've changed the API? tconnectsync stopped working for me since a few days ago. In my logs:

2022-08-09T07:21:56.693554+00:00 app[scheduler.7767]: 2022-08-09 07:21:56 INFO     Downloading t:connect CSV data
2022-08-09T07:21:58.159347+00:00 app[scheduler.7767]: 2022-08-09 07:21:58 WARNING  No last CGM reading is able to be determined
2022-08-09T07:21:58.272982+00:00 app[scheduler.7767]: 2022-08-09 07:21:58 INFO     Last Nightscout basal upload: 2022-08-06T21:04:52+00:00
2022-08-09T07:21:59.510176+00:00 heroku[scheduler.7767]: Process exited with status 0
2022-08-09T07:21:59.191385+00:00 app[scheduler.7767]: 2022-08-09 07:21:59 INFO     Last Nightscout bolus upload: 2022-08-06T20:56:52+00:00
2022-08-09T07:21:59.313728+00:00 app[scheduler.7767]: 2022-08-09 07:21:59 INFO     Last Nightscout iob upload: 2022-08-06T14:30:40-07:00
2022-08-09T07:21:59.313771+00:00 app[scheduler.7767]: 2022-08-09 07:21:59 INFO     No IOB events present from API: skipping
2022-08-09T07:21:59.313822+00:00 app[scheduler.7767]: 2022-08-09 07:21:59 INFO     Wrote 0 events to Nightscout this process cycle

When I use the chrome network tools visiting tconnect.tandemdiabetes.org I see in my therapytimeline responses there's no readingData or bolusEvents. I see: basal, events, pumpFeatures, softwareUpdates, suspensionDeliveryEvents.

Also in chrome inspector I do see bolus data and EGV events under in therapyevents events.

[jwoglom]

This has been achieved in the latest release of tconnectsync (v0.8) which removes use of the ws2 therapytimeline / csv endpoint for fetching bolus and cgm data. It is still being used for pump_events and iob. This should greatly improve the reliability of tconnectsync. #45 will track removing these remaining uses