The irritation
In Arizona, getting into a parked car can mean waiting through an intensely hot cabin. I kept forgetting to start the climate system before leaving for calendar events.
ProductRetiredRetired
Calendar Climate Keeper
A retired Arizona-heat automation that used Google Calendar and the Tesla Fleet API to pre-cool the cabin before a scheduled departure.
- Current state
- Retired — Retired
- Jack’s role
- Concept, Calendar automation, Vehicle API integration
- Find it in the workshop
- Archive Yard · Calendar-linked car remote
Built because…
The real build story.
What I built
I connected Google Calendar and Tesla through official OAuth, calculated departure time from the event location, traffic, and a five-to-thirty-minute cooling offset, then scheduled Fleet API climate commands and push notifications from a small PWA.
The hard part
Events move or disappear, cars sleep, GPS goes stale, daylight saving changes, Tesla commands cost money, and duplicate webhooks cannot be allowed to leave the climate running for hours.
Under the casing
Proof, not decoration.
Build evidence02 items
- Google Calendar events translated into scheduled cabin pre-cooling
- Tesla Fleet API vehicle control documented in the preserved public article
- Node.js
- Express
- Go
- Google Calendar API
- Tesla Fleet API
- Neon Postgres
- Heroku
- PWA
Scope of work
What I owned.
- Concept
- Calendar automation
- Vehicle API integration
No victory-lap math
Outcome and lesson.
Where it landed
The app launched at $3.99 per month, but limited adoption and persistent bugs made it unreasonable to maintain. I sunset Calendar Climate Keeper in September 2025.
What stayed
The automation solved my very specific problem, but a working personal convenience is not automatically a sustainable subscription product.
Field notes
This project has a physical address.
In the playable workshop, Calendar Climate Keeper lives in the Archive Yard as a calendar-linked car remote. You can inspect it without unlocking anything.