Thermostat Automation After Checkout

Sunday at 11:01 a.m., your guest just texted ‘all locked up, thanks!’ and pulled out of the driveway. Your next booking does not start until Wednesday afternoon. For the next 76 hours, your AC is going to keep this empty 1,400 square foot condo at 71F because that is what the schedule says — unless you remember to open the Ecobee app right now and switch it to a vacant hold. You will not remember. You are about to drive 45 minutes to your kid’s soccer game.

By tonight you will have spent eight dollars cooling an empty house. By Wednesday morning you will be at thirty. Multiply that by every gap across the year and the number gets unfunny fast. The good news: a working thermostat automation after checkout setup means you never have to remember. The minute the guest walks out, the system pulls back. This guide walks through how to build it on Ecobee, Nest, and Honeywell, how to detect departure reliably, and how to handle the cleaner exception that breaks most setups.

Who this is for

This is for hosts running short-term rentals who already have a Wi-Fi smart thermostat — an Ecobee Premium, Nest Learning Thermostat, Honeywell T9, or a Z-Wave model on a SmartThings or Hubitat hub — and a calendar somewhere that knows when guests check out. It is for hosts watching their power or gas bill creep up during shoulder seasons because the home is conditioning itself nonstop between bookings.

The mechanics are the same whether your gaps are six hours or six days; only the savings differ. If you are still picking the device or the basic policy, start with the airbnb energy saving thermostat overview and then come back here for the trigger logic that actually drives the savings.

What checkout automation actually looks like

The goal is one specific transition. The instant the guest leaves — or as close to that instant as your detection lets you get — the thermostat moves from in-stay comfort to vacancy hold. In summer that means jumping from 73F up to 82-85F. In winter it means dropping from 69F down to 56-58F.

Then it stays there until 3-6 hours before the next booking, when the pre-arrival hold fires automatically and brings the home back to comfort. That is the whole loop. The interesting question is how to detect ‘the guest left’ reliably enough to trust. The setpoints themselves come from the airbnb vacant mode thermostat profiles, which spell out safe ranges by climate.

Three ways to detect checkout

Calendar-only. Your iCal feed says checkout is at 11 a.m. The automation fires at 11 a.m. exactly. Simple and reliable but ignores reality — some guests leave at 7 a.m., some linger until 12:30. You either lose energy savings or annoy guests still finishing breakfast.
Door sensor on departure. An Aqara Door & Window Sensor or Eve Door & Window on the front door reports an open-then-close event. After checkout time, if the door has not opened in 60 minutes, fire the automation. This is the sweet spot — reactive enough to catch the actual departure, conservative enough not to fire while the guest is on a beer run.
Smart lock event. A Schlage Encode, Yale Assure Lock 2, or August Wi-Fi Smart Lock can broadcast a lock event. When the guest’s code is used to lock the door from outside after checkout time, fire the automation. This is the cleanest signal but requires a smart lock you can integrate.

Most professional hosts run a hybrid. The calendar is the floor (the home can never stay in comfort mode past noon if the booking ended at 11), and the sensor is the accelerator (if the guest left at 7 a.m., move now and save five extra hours of cooling).

Building it on Ecobee with Hospitable or Touch Stay

This is the easiest path. Your property management tool (Hospitable, Touch Stay, Smartbnb, or similar) reads the iCal feed and exposes booking events as triggers. Build an Ecobee comfort setting called ‘Vacant’ with the appropriate seasonal setpoints. Then create a rule: when a booking ends, set the Ecobee to Vacant comfort with an indefinite hold.

Create a second rule: 3 hours before the next booking starts, switch to Arrival comfort. That is the whole loop, no code, fifteen minutes of setup. The arrival side is covered in detail in the airbnb welcome temperature automation guide, so you can build both halves at once.

If you want the door-sensor accelerator, add an Aqara contact sensor on the front door, expose it through HomeKit or SmartThings, and use a webhook to trigger the same Vacant transition early. The Ecobee API accepts a hold command directly if you go that route — it is a 10-line script.

Building it on Nest

Nest is harder because Google deprecated the Works with Nest API. The realistic path is Google Home routines plus Eco Temperatures. Set Eco to your vacancy setpoint (84F summer, 56F winter). Use Home/Away Assist with Wi-Fi-based phone presence detection — when no phone is on the home network for 30 minutes after checkout, the system auto-switches to Eco. Pair this with a scheduled Google Home routine 3 hours before the next booking that switches Eco off and sets the comfort setpoint.

It works but it is finicky. If you have a fleet of properties on Nest and you are doing this seriously, the right answer is a small Home Assistant install on a Raspberry Pi 4 that ingests the iCal feed and drives the thermostat through the Nest integration there. That gets you the calendar awareness Google removed.

Building it on Honeywell T9

The Honeywell T9 (and the T10 Pro) work cleanly with the Resideo Home app, which has a Smart Schedule feature plus geofencing. For rentals you do not want geofencing — you want calendar-driven holds. Use IFTTT or a Make.com scenario reading the iCal feed to send the T9 a setpoint hold via the Resideo developer API. The same scenario can fire the pre-arrival warm-up. Honeywell’s hold model is more forgiving than Nest’s, so the script is shorter.

The cleaner exception

If your cleaner shows up the same day, your thermostat automation after checkout will fight them. They will arrive to a hot or cold house, crank the thermostat to a comfortable working temperature, and your savings vanish. Two solutions.

Either build a cleaner profile (75F summer, 70F winter) that fires when the cleaner’s arrival is detected and ends 3 hours later, or set the Vacant transition to fire only after the cleaner’s completion signal — an Aqara Wireless Mini Switch they push when they leave, or a door event that comes after the cleaner-expected arrival window. The cleaner-aware schedule pattern is detailed in the smart thermostat schedule between guests writeup.

What the savings actually look like

In Phoenix in July, a 1,400 square foot condo running 73F in occupancy versus 84F in vacancy saves about 30 percent of the cooling cost during the vacant period. With a typical occupancy rate of 75 percent and average gap of 28 hours, the math works out to about 18 dollars a month in summer.

In Vermont in January, the heating savings are larger because the indoor-outdoor delta is bigger — closer to 40 dollars a month with a multi-day gap. None of this is life-changing per booking. Across a year, across multiple properties, it adds up to real money — and unlike most automation, this one literally runs while you sleep. The deeper cost-modeling lives in the airbnb utility cost reduction automation guide.

Common mistakes

Setting the vacancy too aggressive. 90F in summer means warped wood floors and a slower recovery. 50F in winter risks pipes. Stay 82-85F summer, 56-58F winter.
No fallback if the sensor fails. If the Aqara door sensor battery dies, your home stays in comfort mode forever. The calendar floor catches this — always run both.
Forgetting to fire the pre-arrival. If your automation transitions to Vacant cleanly but never transitions back, your next guest walks into an 85F house. Test both halves of the loop.
Not handling back-to-back bookings. If the gap between bookings is shorter than your pre-arrival window plus your vacant transition delay, the math breaks. Set a minimum gap of 4 hours below which Vacant just does not fire.
Ignoring humidity. In humid climates, letting indoor humidity climb above 60 percent during long vacancies creates mold risk. Set the Vacant temperature with humidity in mind, or run a separate dehumidifier on a Kasa or Wemo smart plug.

Testing the automation

Create a fake booking in your iCal that ends 30 minutes from now and starts 24 hours later.
At checkout time, watch the Ecobee or Nest app. The thermostat should switch to Vacant within minutes.
21 hours later, the pre-arrival should fire and switch to Arrival comfort.
If you have a door sensor accelerator, open and close the front door an hour before checkout time and verify the Vacant transition fires early.
Verify the cleaner exception works by simulating a cleaner arrival window with the cleaner’s smart-button push.

Once the loop runs cleanly, layer in the safety net described in the automatic thermostat reset after checkout guide so a stuck hold cannot quietly burn money for days.

Privacy notes

Disclose any sensors used — the door sensor, the smart lock, the thermostat’s occupancy sensing — in your listing and house manual. Cameras and microphones inside the living space are off-limits regardless of whether the platform technically allows them. Outdoor doorbell cameras like a Ring Battery Doorbell Plus or Google Nest Doorbell are fine when disclosed. The point of this automation is energy savings, not surveillance, and most guests are perfectly comfortable with that distinction when you are upfront about it. The privacy-safe monitoring cluster has the disclosure language platforms now expect.

Frequently asked questions

Will my AC unit be damaged by jumping from 73F to 84F?

No. AC units are designed to handle a wide range of setpoints. The compressor cycles based on temperature differential, and going to a higher vacancy setpoint just means it cycles less. The opposite — running a low setpoint constantly — is harder on the equipment.

What about pets left between bookings?

If your cleaner has a pet on site between guests — or if you have a host pet living in a separate area — build a Pets profile (76F summer, 65F winter) and use that as the ‘vacant’ setting instead. Do not let the standard vacancy setpoint apply when an animal is in the home.

How does this interact with the welcome temperature automation?

It is the other half of the same loop. Checkout automation sets Vacant; welcome temperature automation sets Arrival. Build them together and the system runs end-to-end without you. Build only one and you save energy but greet guests with an uncomfortable house, or vice versa.

What if my Wi-Fi is down at checkout time?

The thermostat keeps running its local schedule but the calendar-driven hold will not fire until the connection comes back. Most outages resolve in under an hour and the system catches up. For longer outages, the worst case is a few hours of comfort-mode cooling on an empty house — not great, not catastrophic.

Can I do this without a property management tool?

Yes — a basic Zapier flow on the iCal feed plus the Ecobee or Nest action gets you the calendar trigger. Or run Home Assistant locally with the Airbnb integration and it does the whole thing for free. The PMS path just packages it.

Next steps

Build the Vacant profile tonight, hook the calendar trigger this weekend, and add a door-sensor accelerator next month if the savings justify it. From there, the broader smart thermostats and energy automation hub connects this checkout work to your guest-comfort, welcome, and seasonal-routine layers.