Skip to content

TimeTree Calendar 2.0.1

Choose a tag to compare

@acdcnow acdcnow released this 08 Oct 07:41
· 8 commits to main since this release
1dc5ae7

What's Changed

  • fix(export): resolve recurring event duplication, target switch false conflicts, and occurrence state mismatch by @rutj87 in #10

New Contributors

Full Changelog: 2.0.0...2.0.1

TimeTree Calendar 2.0.1
First stable release of the 2.0.x line — the complete rework of the integration. It
promotes the two pre-releases (2.0.0-beta.1, 2.0.0-beta.2) to a normal release.
There are no functional changes to the integration compared to 2.0.0-beta.2.

Highlights
All calendars of your account — select any number during setup; each one becomes
its own calendar.* entity and its own device.
Complete event import — chunked sync, recurring events expanded into single
occurrences (EXDATE/RDATE/COUNT/UNTIL), correct exclusive all-day end,
negative timestamps, labels, attendees, optional comments and memos.
Create, update and delete events from Home Assistant — the full browser payload,
a fresh CSRF token and a browser-shaped TLS fingerprint via curl_cffi.
Export / sync loop to any calendar entity (for example Google Calendar) with a
selectable interval, window, one-way (export_only) or two-way mode and a dry run.
Conflict management — policies manual, source_wins, target_wins and
newest_wins; pending conflicts surface in a sensor, a notification and the
timetree_conflict_detected event and are resolved with timetree.resolve_conflict /
timetree.resolve_all_conflicts.
New services — timetree.refresh_now, timetree.export_now,
timetree.list_conflicts, timetree.resolve_conflict,
timetree.resolve_all_conflicts and timetree.get_event.
Fixed
The reported issues #1–#6: recurring events breaking month views, the
create_event keyword mismatch, 422 responses on writes, all-day off-by-one,
missing labels and stalled views.
Plus the recurring-event analysis from #7.
See the changelog
for the full, per-change list.

Upgrade notes
Requires Home Assistant 2026.9 or newer.
The integration is now hub-style: one config entry holds the account
(e-mail/password) and the selected calendars. Old 1.x config entries are migrated
automatically.
curl_cffi is installed as a requirement. Reading works without it; writes may be
refused by TimeTree's anti-bot layer.
Nothing is written to a second calendar until the export loop is enabled in the
options — the default is disabled with the manual conflict policy.
License
Starting with this release the project is licensed under the GNU General Public
License v3.0 (GPL-3.0-only). It was MIT before.

Documentation
README
CHANGELOG
Wiki —
Architecture Design Document, Software Design Document and Workflow Diagrams