Which heat-wave thermostat features actually save energy?
A comparison of heat-wave saving features in smart thermostats and hubs — Nest Airwave, ecobee eco+ Time of Use, Sensi demand response, and the Home Assistant route — covering how each feature actually works, what wiring, utility enrollment, and cloud access it requires, and which rate plan and setup each one fits. Vendor savings figures are labeled as marketing claims, not bill math.
Last updated
During an extreme heat wave, “smart home energy saving” can mean four very different things. A thermostat might squeeze a few more minutes out of a cold evaporator coil. It might move compressor runtime away from a pricey afternoon rate window. It might let a utility make a temporary setpoint adjustment during a grid event. Or it might give you enough hooks to build your own cooling rules in a hub. Those are not interchangeable tips; they reduce different things, require different permissions, and disappoint for different reasons.
The distinction matters because cooling is no longer a small background load on the worst days. The IEA reports that space cooling can exceed 70% of peak residential demand on extremely hot days in parts of the U.S. and the Middle East, and roughly 50% in Texas on the warmest days. That is grid context, not a promise that any one home will cut its bill by the same proportion. It does explain why thermostat features that trim or shift cooling get so much attention during heat waves. [1]

The four heat-wave saving routes are doing different jobs
| Route | What it actually does | What it needs | When it helps | When it disappoints |
|---|---|---|---|---|
| Nest Airwave | Turns the compressor off slightly before the target temperature, then runs the fan for about 5–10 minutes to use residual cold left in the coil. It only activates when indoor humidity is low. [2] | A compatible Nest setup controlling cooling and fan operation; no utility enrollment for Airwave itself. | Dry heat, homes where fan-only residual cooling can finish the cycle without making the room clammy. | Humid heat waves, homes where stopping the compressor early leaves comfort behind, or cases where fan-only runtime is not useful. |
| ecobee eco+ Time of Use | Pre-cools or shifts cooling around time-of-use pricing. ecobee publishes claims of up to 23% more cooling savings for Time of Use in a third-party summer 2020 U.S./Canada study, and up to 26% annual heating and cooling savings versus a fixed 72°F hold; those are vendor-published marketing claims, not bill math for every home. [3] | An ecobee platform setup, a meaningful TOU rate, enough comfort headroom to cool earlier, and tolerance for cloud-assisted optimization. | Homes on real TOU pricing that can hold a cooler temperature long enough to coast through part of the expensive window. | Flat-rate plans, leaky or poorly insulated homes, occupants who dislike pre-cooling, or climates where the house gains heat too fast. |
| Utility demand response through Sensi or Nest-style programs | Allows temporary event-time thermostat adjustments after program enrollment, typically with opt-out or override available. Sensi describes the model as utility demand-response enrollment with customer participation choices, while ENERGY STAR’s smart thermostat criteria require demand-response capability while preserving consumer override. [4][5] | An eligible thermostat, a participating utility program, account enrollment, and usually cloud/program connectivity. | Grid-stress events where reducing or delaying AC load helps the utility manage peak demand. | If you want guaranteed bill savings without enrolling, dislike event adjustments, or expect certification criteria to define exactly how every utility program behaves. |
| Home Assistant route | Lets you build your own cooling logic using thermostat integrations, weather inputs, rate sensors, automations, and local or cloud devices. | A maintained hub, integrations that expose the controls you need, reliable sensors or rate data, and willingness to own the logic. | Tinkerers who want explicit rules, local fallbacks where supported, and visibility into what changed and why. | Anyone expecting a packaged rebate program, automatic utility coordination, or zero-maintenance heat-wave optimization. |
That table is the useful buying filter. If the feature does not match your humidity, rate plan, wiring, cloud tolerance, and utility-program comfort, the advertised “saving” label is doing too much work.
Airwave is the most mechanical trick — and humidity is the catch
Airwave is easy to picture because it is not a pricing strategy or a utility program. In a normal cooling cycle, the compressor chills the evaporator coil, and the indoor fan moves air across that coil. Airwave tries to stop the expensive part — the compressor — a little early, then keeps the fan moving air across the still-cold coil for roughly 5–10 minutes. If the leftover cooling is enough to finish the job, compressor runtime goes down. [2]

The humidity condition is not a footnote. Google says Airwave only turns on when indoor humidity is low. That is mechanically sensible: once the compressor stops, the system is no longer actively dehumidifying, and blowing air over a wet coil in sticky weather can feel worse even if the temperature number looks close. In a dry heat wave, Airwave may be a low-friction setting worth enabling. In a humid heat wave, it may simply stay inactive or be much less useful. [2]
Airwave also should not be confused with demand response or time-of-use optimization. It does not need a utility event to matter, and it does not know whether 4 p.m. power costs more than 10 a.m. power. It is a compressor-runtime feature. If your bill problem is a high on-peak retail rate, Airwave may help a little at the margin, but it is not designed to move cooling out of that rate window.
eco+ Time of Use is real only if the rate plan is real
ecobee’s eco+ Time of Use feature belongs in a different category. The point is not leftover coil cooling; it is retail timing. If power is cheaper before the afternoon peak, the thermostat can cool the house earlier and reduce cooling during the expensive window. That can lower cost even if total cooling energy does not fall much. In some houses, it may even use more total energy while still reducing on-peak cost; whether that is worthwhile depends on the rate spread and comfort trade-off.

This is where vendor percentages are easy to misuse. ecobee says eco+ Time of Use can deliver up to 23% more cooling savings, based on a third-party summer 2020 study of U.S. and Canadian homes, and also says its thermostats can save up to 26% annually on heating and cooling compared with a fixed 72°F hold. Those are vendor-published claims. They are useful as marketing context, but they do not tell you what a flat-rate customer, a renter in a hot upstairs unit, or a house with weak insulation will see on a specific July bill. [3]
The feature needs several assumptions to line up:
- The home must actually be on a time-of-use rate where afternoon or evening cooling costs meaningfully more.
- The thermostat must have enough comfort headroom to cool earlier without making the house uncomfortably cold.
- The building must hold temperature reasonably well after pre-cooling; otherwise the compressor may still run hard during the peak window.
- The occupants must be comfortable with the platform making cloud-assisted timing decisions rather than only following a fixed local schedule.
That last point is not a moral issue; it is a dependency issue. If you bought a smart thermostat because you want the platform to optimize around rates, eco+ Time of Use is exactly the kind of packaged feature to inspect. If you bought one because you want predictable local behavior during the hottest week of the year, the same feature may feel too opaque.
Pre-cooling is conditional, not folklore
The broader pre-cooling debate shows why TOU features deserve conditional language. NPR reported in July 2025 that utilities disagree on pre-cooling and supercooling: Arizona Public Service endorses it, Georgia Power frames it as dependent on home efficiency, and Exelon warns that aggressive supercooling can cost more. [7]
Tucson Electric Power gives a concrete TOU-style protocol: set the thermostat 3 degrees lower for three hours before its 3–7 p.m. on-peak window, then raise the setting during peak. That is a rate-window strategy, not a universal “run the AC more because it is hot” rule. [8]
If you want the longer savings-claim reconciliation — what thermostat percentages compare against, and why “savings” often changes meaning between runtime, demand, and dollars — use our separate guide to heat-advisory smart thermostat savings. This article’s job is narrower: choosing the feature whose assumptions match your house.
Demand response is about event-time load, not automatic bill math
Demand response is the feature category that most often gets blurred into general thermostat savings. It deserves its own lane. In a demand-response program, you enroll with an eligible utility or program partner, and during certain grid events the thermostat may make temporary temperature adjustments. Sensi’s demand-response FAQ describes customer enrollment and participation choices, including the ability to opt out of events. ENERGY STAR’s smart thermostat criteria likewise require demand-response capability while preserving consumer override. [4][5]
Those consent and override details belong before rebate talk. A heat-wave event is exactly when comfort is most sensitive: an upstairs bedroom, a poorly insulated rental, or a home with medical cooling needs is not the same as a shaded, tight house with spare thermal mass. A reasonable grid program should make the trade clear, let the customer say yes knowingly, and preserve the ability to override.
The evidence for demand response is also measured differently. Google says Nest demand-response events across five U.S. utilities from 2020 to 2022 averaged about 1.06 kW of load reduction per enrolled thermostat per event, with setpoint adjustments of up to 4°F. That is event-time demand reduction. It should not be converted into a generic annual bill-savings number for a household. [6]
This is why a Sensi-style utility enrollment and a Nest/Google demand-response result should be read as grid-facing value first. You may receive a program incentive, and your utility may design rates or rewards around participation, but the core mechanical effect is temporary reduction or delay of cooling load during events. If you are not willing to enroll, connect the account, and tolerate event adjustments with override rights, demand response is not your heat-wave saving route.
Home Assistant gives you the logic, and also the maintenance burden
Home Assistant appeals to a different buyer. Instead of accepting Airwave, eco+, or a utility program as packaged behavior, you can build rules around weather forecasts, indoor temperature, humidity, occupancy, electricity price sensors, solar production, or whatever your integrations expose. That flexibility is useful when you want to know exactly why the setpoint changed.
It is not a magic local replacement for utility-integrated demand response. If the thermostat integration is cloud-based, your automation still inherits that dependency. If a utility program requires a specific thermostat enrollment, a local hub does not automatically make your DIY rule eligible for the same rebate or grid dispatch. If your rate data, weather trigger, or device integration breaks, you are the support desk.
The Home Assistant route fits people who would rather maintain a transparent system than accept a vendor’s black-box timing. For copyable heat-wave automations, use the separate guide to timing smart home cooling for heat waves. If your automations depend on weather triggers, it is also worth checking which local weather data sources are reliable enough for control decisions rather than just dashboard decoration.

Which feature fits your heat-wave setup?
Start with the constraint that actually applies to your home.
- If your heat is mostly dry and you want a low-friction compressor-runtime trick, Nest Airwave is the cleanest fit to try. Watch comfort and humidity rather than expecting a dramatic bill change.
- If you are on a meaningful time-of-use rate and your home can hold temperature after pre-cooling, ecobee eco+ Time of Use is the platform feature to examine. On a flat rate, its main billing logic largely disappears.
- If you are willing to enroll with a utility and accept temporary event adjustments with override rights, demand response is the grid-facing route. Judge it by program terms and event comfort, not by generic thermostat savings claims.
- If you want custom rules, visible logic, and control over dependencies, Home Assistant is the flexible route. Buy it for configurability, not because it erases every cloud, utility, or maintenance requirement.
The best heat-wave thermostat feature is not the one with the biggest advertised percentage. It is the one whose assumptions match the home’s wiring, rate structure, humidity, cloud tolerance, and comfort with utility participation.
References
- How can energy efficiency alleviate rising heatwave-driven electricity demand — IEA, 2024
- Learn about Airwave and how to change settings — Google Home/Nest Help
- 5 ways to save energy this summer — ecobee
- Demand Response FAQs — Sensi/Copeland
- Smart Thermostats Key Product Criteria — ENERGY STAR
- One click away: your home's thermostat can save energy and the grid — Google Sustainability
- Heat, air conditioning, forecast: supercooling, precooling — NPR, July 2025
- Pre-Cooling Your Home in the Summer — Tucson Electric Power
Known issues with this device / protocol
Spec-version history
For active regressions on this protocol, see Update Watch.
No linked Update Watch entries yet.
