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 https://github.com/jwoglom/tconnectsync/issues/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**: https://github.com/jwoglom/tconnectsync/compare/v0.8.4...v0.8.5