v0.9.8

• fix: update sleep events if their duration changes (#92) - thanks @maz!
• Environment variable to ignore Nightscout connection errors added (NS_IGNORE_CONN_ERRORS=true)
• Additional unit tests added.

Full Changelog: v0.9.5...v0.9.8

v0.9.5: Fix profile syncing

• Resolves a bug where, after the t:connect login session expired, profile synchronization would sometimes stop working
• Update Readme.md for non-WSL Windows installation by @jwalberg (#77)

Full Changelog: v0.9.4...v0.9.5

v0.9.3: Bugfix

• Resolves synchronization bug for extended boluses which are not complete (#76)

Full Changelog: v0.9.2...v0.9.3

v0.9.1: Synchronize profiles with Nightscout

New: with the PROFILES synchronization feature, now ensures that the pump's profile settings match in Nightscout, and resolves differences accordingly.

Full Changelog: v0.8.10...v0.9.1

v0.8.10

Adds additional logging in --check-login

Full Changelog: v0.8.9...v0.8.10

v0.8.9

Fix bug which crashed tconnectsync when an extended bolus was cancelled without a timestamp (#73)

Full Changelog: v0.8.8...v0.8.9

v0.8.8

Resolves timestamp issues with Nightscout (#71)

Full Changelog: v0.8.7...v0.8.8

v0.8.7

What's Changed

• Fix "Unknown therapy event type: Basal" due to new event types being added to Tandem APIs
• Moved remaining logger.warn() statements to logger.warning() by @jyaw in #58

Full Changelog: v0.8.5...v0.8.7

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