Heat advisory? These smart thermostat settings save energy
During a heat advisory, cooling should stay safe without spiking the bill. Get exact Nest and ecobee setpoints for home, sleep, and away — plus which smart features to enable, disable, or opt out of.
Set these numbers first
If you opened a weather alert and searched for smart thermostat settings for heat advisory energy saving, start with a schedule instead of hunting for one magic temperature: about 78°F when people are home, about 82°F for sleep, and about 85°F when the house is empty. Keep a lower cooling floor around 72°F for manual overrides and pre-cooling, and use a lower away ceiling—about 80°F, not 85°F—where pets, older adults, infants, medical conditions, or heat-sensitive rooms are part of the house agreement.
| Situation | Setpoint | What to watch |
|---|---|---|
| Home and awake | About 78°F | Use this as the normal Heat Advisory baseline, then adjust for health, humidity, and room-by-room comfort. |
| Asleep | About 82°F | Only use this if everyone still sleeps safely; bedrooms that run hot should stay lower. |
| Away | About 85°F | Use occupancy-based Eco/away behavior, but do not let a pet room or vulnerable space sit this high. |
| Pets or health concerns | No higher than about 80°F | Treat this as a conservative ceiling, especially in sunny rooms or closed-off spaces. |
| Pre-cool or manual override | Do not chase below about 72°F | A brief pre-cool can help before the peak window; overcooling usually just moves the bill earlier. |
| Automation safety limit | Enable a high-temperature Safety Temperature limit | On Nest, cooling Safety Temperatures are off by default and must be turned on separately. |

The 78°F home target lines up with the commonly cited summer air-conditioning baseline, and the sleep and away numbers follow the same pattern: a modest rise while sleeping and a larger setback when the house is empty. Consumer Reports describes the Department of Energy-style summer approach as 78°F at home, with higher settings while asleep or away, and notes the rule of thumb that each degree above 72°F can save up to roughly 3% on cooling costs.[1] The Department of Energy separately gives the broader setback rule: setting the thermostat back 7–10°F for 8 hours a day can save up to about 10% a year on heating and cooling, with real results depending on the home and climate.[2]
That is enough precision for tonight, but not enough trust for the whole season. A smart thermostat should be allowed to help only inside visible boundaries: a schedule you can read, an Eco/away mode you understand, a safety limit that prevents overheating, and a clear opt-out path for any program that changes setpoints for you.
Why a Heat Advisory still leaves room for energy saving
A Heat Advisory is serious. It means dangerous heat is expected, but the National Weather Service distinguishes it from higher-tier alerts such as an Excessive Heat Warning, where conditions are expected to be more severe.[3] That distinction matters for thermostat advice. During an advisory, the goal is not to shut cooling off or prove how much heat the household can tolerate. It is to keep cooling active, raise setpoints only where the house can safely absorb it, and prevent the most expensive afternoon hours from turning into a panic override.
The schedule works because it gives each part of the day a different job. The 78°F home setting protects normal living spaces. The 82°F sleep setting asks for savings only after the sun is lower and activity drops. The 85°F away setting lets the house drift while nobody is there, but not so far that the system has to claw back from an oven-like indoor temperature. If the alert escalates, use the more conservative Excessive Heat Warning playbook instead.
The weak part of any savings formula is the house itself. The 3%-per-degree and 10%-per-year numbers are rules of thumb, not guarantees. A shaded, well-insulated home with predictable occupancy can usually make better use of setbacks than a leaky house with west-facing glass, a struggling AC, or someone home all day. Recovery behavior also matters: if the system runs flat out for hours after a deep setback, the bill may not improve much, and comfort certainly will not.
Set the schedule before you trust the automation
Build the thermostat’s normal cooling schedule first. On a typical workday, that usually means 82°F overnight if bedrooms stay safe, 78°F before the household wakes, 85°F after the last person leaves, and 78°F again before the first person returns. If a room has a pet, a crib, a medical device, or a person who cannot easily adjust the thermostat, use the lower ceiling for that room’s reality rather than the optimistic away number.
Do not create a schedule that depends on someone remembering to rescue the house later. A smart thermostat is useful here because it can repeat the same modest pattern every day of the advisory. It is less useful when the schedule is vague and every afternoon turns into a manual argument between comfort, cost, and the app.
| Time block | Copyable Heat Advisory setting | Adjustment rule |
|---|---|---|
| Wake / morning at home | 78°F | Lower only if bedrooms or main rooms are already too warm. |
| Midday away | 85°F | Use 80°F instead for pets, vulnerable people, or rooms that heat unevenly. |
| Return home | 78°F | Start recovery before arrival if your thermostat supports predictable occupancy or pre-cooling. |
| Sleep | 82°F | Keep bedrooms lower if sleep quality or health risk changes. |
Nest settings: Eco is useful, Safety Temperatures need a real check
For Nest, the Heat Advisory setup has three separate pieces: your schedule, Eco Temperatures, and Safety Temperatures. They are not the same control, and treating them as one is how a house ends up hotter or colder than anyone expected.
Use Eco Temperatures as an away setback, not as permission to overheat the house
Google documents Nest cooling Eco Temperatures as a selectable range from 76°F to 90°F.[4] For this playbook, that range is wider than you need. Set cooling Eco near the away target—about 85°F for an empty house, or about 80°F where pets or heat-sensitive occupants are part of the plan. A 90°F Eco setting may be available in the app, but availability is not the same thing as a good Heat Advisory setting.
Nest can also take time to switch into Eco after everyone leaves. Google says automatic Eco behavior may wait up to about 2 hours after departure before changing modes.[4] That delay is not a defect; it is meant to avoid false away decisions. But it means short errands should not be counted as a guaranteed 85°F setback. If the house is empty for only a brief window, the thermostat may correctly decide that comfort stability is worth more than a tiny setback.
Turn on Safety Temperatures instead of assuming they are already protecting you
Nest Safety Temperatures deserve their own check because Google says cooling Safety Temperatures are off by default.[5] That is the kind of default that matters during a Heat Advisory. If Eco, a schedule, or a utility event lets the house drift too warm, the safety setting is the backstop that tells the thermostat to cool again.
Keep two different limits straight. The 72°F number in this playbook is a lower cooling floor for pre-cooling and manual overrides; it keeps the system from being driven unnecessarily cold in the name of savings later. Nest’s cooling Safety Temperature, by contrast, is a high-temperature protection limit. Set that high limit according to the safest room in the house, not the toughest adult in the house. If pets or health concerns make 85°F too high, the safety limit should reflect that.
Review Seasonal Savings and utility events before the advisory peaks
Nest Seasonal Savings is worth reviewing rather than blindly accepting during a Heat Advisory. Google describes Seasonal Savings as a feature that makes small schedule adjustments, with about a 2°F total change being the solid figure across its documentation.[6] A small change may be harmless on a mild week and irritating during an advisory if it lands in a bedroom or a pet room. If the thermostat starts changing its own setpoints, check whether Seasonal Savings or a utility program is active before assuming the device is malfunctioning.
Demand-response programs can also adjust cooling during peak grid events. They may be useful, and they may come with incentives, but the household still needs an exit path. Before the next hot afternoon, find where the event appears in the Nest app or thermostat, confirm whether you can opt out of a single event, and decide who in the house is allowed to make that call. If setpoints are already moving unexpectedly, use the separate guide to thermostats changing their own settings during a heat wave.
ecobee settings: let pre-cooling help, but watch event adjustments
For ecobee, the useful Heat Advisory pattern is similar: schedule first, occupancy behavior second, event programs third. Set the comfort schedule around 78°F home, 82°F sleep, and 85°F away, then use Smart Home/Away or Eco-style occupancy behavior only if it keeps returning to those visible setpoints.
ecobee’s Community Energy Savings program is more explicit about peak events than many generic smart-thermostat features. ecobee says the program may pre-cool the home before an energy event, then adjust the thermostat by 1–4°F for a few hours during the event. It also describes opt-out behavior and utility rewards of up to $125 where available.[7]
That design can fit a Heat Advisory if the boundaries are visible. A pre-cool from 78°F down toward the mid-70s before the peak window is very different from discovering at 5 p.m. that the house has been nudged warmer than a bedroom, pet area, or home office can tolerate. If Community Energy Savings is active, check the event notice before the hottest part of the day, not after someone complains.
Do not add equipment-threshold tweaks just because they sound advanced. The available ecobee material for this article supports the documented event behavior—pre-cooling, 1–4°F adjustments, opt-out, and reward framing—not a verified set of cooling equipment thresholds. Leave compressor and staging details alone unless you have model-specific documentation or an HVAC technician’s instruction.
Pre-cooling should be modest and scheduled
Pre-cooling is useful during a Heat Advisory when it is small, timed, and reversible. The practical version is to cool the house a little before the hottest or most expensive window, then let the thermostat rise back to the normal home setting instead of forcing the AC to fight peak conditions from behind.
For most homes using this playbook, pre-cooling means temporarily dropping from 78°F into the 75–76°F range before the peak window, then returning to 78°F while occupied or to the away setting if the house is empty. Do not pre-cool below about 72°F unless there is a specific health or comfort reason. Below that, the thermostat is often just buying a colder hour with a longer runtime, not creating a smarter advisory plan.
If your utility event or thermostat program handles pre-cooling automatically, do not duplicate it with a second manual drop. One pre-cool is a plan; two overlapping pre-cools are a good way to make the house too cold early and still uncomfortable later.
Use realistic savings expectations
The credible savings anchor is not the largest number on a thermostat product page. ENERGY STAR says certified smart thermostats save users an average of about 8% on heating and cooling bills, or roughly $50 per year, based on EPA-analyzed field data.[8] That average is a better planning number than assuming every Heat Advisory schedule will produce a dramatic bill drop.
Manufacturer savings claims can run higher, including “up to 26%” language used in smart-thermostat marketing.[9] Treat that as a ceiling under favorable conditions, not a promise for an occupied house during dangerous heat. A household that lowers the pet room ceiling to 80°F is making the right call even if it gives back some theoretical savings.
Demand-response savings belong in their own bucket. They can reduce load during specific grid events and may bring bill credits or rewards, but that is not the same as saying the thermostat will cut every cooling bill by the same percentage. For a Heat Advisory, the win is narrower and more dependable: avoid unnecessary runtime when nobody is home, avoid overcooling before bed, and avoid unexplained setpoint changes that make someone override the system angrily.
Before the next advisory event, check four things
- Schedule: 78°F home, 82°F sleep if safe, 85°F away only for an actually empty house.
- Safety limits: keep manual cooling and pre-cooling from dropping below about 72°F, and enable a high-temperature Safety Temperature or equivalent protection so automation cannot let the house overheat.
- Eco/away behavior: confirm Nest Eco Temperatures or ecobee occupancy behavior returns to the setpoints you chose, not a forgotten summer experiment.
- Setpoint-changing programs: review Nest Seasonal Savings, utility demand-response events, and ecobee Community Energy Savings notices before the hottest part of the day.
During a Heat Advisory, the best thermostat move is not a heroic setpoint. It is a bounded schedule with automation under supervision.
References
- Best Setting for Your Central Air Conditioning — Consumer Reports
- Home Upgrades — U.S. Department of Energy
- Understanding Heat Alerts — National Weather Service
- Learn about Eco Temperatures and how to change settings — Google Nest Help
- Learn about Safety Temperatures and how to change settings — Google Nest Help
- Learn about Seasonal Savings — Google Nest Help
- Community Energy Savings — ecobee
- ENERGY STAR Smart Thermostats — ENERGY STAR
- Smart Thermostats — ecobee
