v0.8.5: Stops unnecessary data uploads from occurring to Nightscout

This release includes a bugfix which, in certain situations, would result in unnecessary repeated data uploads to Nightscout. If your Nightscout instance stores event timestamps in isoformat with a space between the date and the time instead of a T (e.g. 2022-10-01 22:27:10-04:00 instead of 2022-10-01T22:27:10-04:00), then tconnectsync would upload all of the past day's basal and bolus information rather than only the delta between the most recently uploaded data from tconnectsync. As far as I can tell, this caused minimal impact as these events contained identical data at identical timestamps, and either Nightscout or Mongo deduplicates the data and continues to function properly.

Per #47, some users' Nightscout instances do indeed have proper isoformat timestamps, so tconnectsync now checks Nightscout for both formats of timestamps before returning that no previous bolus/basal objects exist in NS.

Full Changelog: v0.8.4...v0.8.5

v0.8.3: Fix Nightscout date parsing and unknown therapy events

What's Changed

• Update README.md by @t1diotac in #50
• Replace hand-rolled date format with isoformat(). by @rstutsman in #51
• Handle unknown therapy event error when running ciq_therapy_event.py by @jyaw in #54
• Handle unknown therapy event error when running ciq_therapy_event.py by @jyaw in #53
• fix unknown therapy event error in ciq_therapy_event.py by @jyaw in #55

New Contributors

• @t1diotac made their first contribution in #50
• @rstutsman made their first contribution in #51
• @jyaw made their first contribution in #54

Thanks for your help!

Full Changelog: v0.8.2...v0.8.3

v0.8.2: WS2 API connection timeout, check-login fixes

• Fixes to --check-login (#46)
• Adds timeout to WS2 API endpoints

Full Changelog: v0.8.1...v0.8.2

v0.8.1: Improve reliability for bolus synchronization

• Removes use of the WS2 therapytimeline csv endpoint which was causing major synchronization problems due to unreliability (#43)

Full Changelog: v0.7.2...v0.8.1

v0.7.2: Reliability improvements

• Support HTTP/HTTPS/SOCKS proxies
• Drop Python 3.6 support (requests no longer supports 3.6)
• Tandem HTTP 403 workarounds

Full Changelog: v0.7.1...v0.7.2

v0.7.0: fix Tandem Android API connection

Fixes #38 which, due to changes on Tandem's side, prevented tconnectsync from connecting to Tandem's servers.

Prior releases are likely to be broken by Tandem's changes, so please upgrade.

v0.6.5: remove IOB as default feature, autoupdate refactoring

Breaking change: The IOB synchronization feature was disabled by default, because it is not being utilized in the Nightscout UI at this time and is only available through the Nightscout API. It can be re-enabled with the --features flag.

Full Changelog: v0.6.4...v0.6.5

v0.6.4

• autoupdate: reset API connection when event index change is recorded but no data is found, potential fix for #11
• secret: use TZ to infer TIMEZONE_NAME if set
• check: add additional output to --check-login

Full Changelog: v0.6.3...v0.6.4

v0.6.3: support basal rate change suspension event

Full Changelog: v0.6.2...v0.6.3

v0.6.2

• When loading a .env file, explicitly looks for $HOME/.config/tconnectsync/.env if a .env file doesn't exist in the current directory.
• Allows environment variables to have higher precedence over .env file contents
• Fixes a bug relating to in-progress extended boluses.

Full Changelog: v0.6.0...v0.6.2