Skip to main content
NestGrid logoNestGrid

How to Set Your Smart Thermostat for Las Vegas Extreme Heat

Exact, copyable smart thermostat settings for Las Vegas extreme-heat stretches: pre-cool to 74–76°F before the NV Energy 1–7 PM peak window, drift to 80–81°F through peak, and recover at night. The recipe covers the specific setpoints, schedule, and platform toggles for Nest, ecobee, and Honeywell, with dated verification notes.

For a Las Vegas extreme-heat stretch, the smart thermostat setting that usually matters most is not a single “78°F” number. It is the timing: cool the house before the expensive, brutal part of the afternoon, then let it coast instead of asking the compressor to win a losing fight against west sun at dinner.

Use this as the default recipe to try first: pre-cool to 74–76°F before the NV Energy summer peak window, let the house drift to 80–81°F through peak, return to 78°F when occupied after peak, and sleep at 74–76°F if the bedrooms need it. The Cooling Company recommends the same basic Las Vegas pattern — 74–76°F from about 11 AM–1 PM, 80–81°F from 1–7 PM, 78°F after 7 PM, with 74–76°F for sleep — and frames 78°F home, 85°F away, and 74–76°F sleep as a local summer baseline.[1]

Illustration of a summer day cooling schedule with pre-cool, drift, and recover stages

The copyable Las Vegas extreme-heat schedule

TimeCooling setpointWhat the thermostat is doing
Occupied morning78°FNormal occupied comfort setting before the pre-cool begins.
About 11 AM–1 PM74–76°FPre-cool before the afternoon peak window. Use 74°F only if the system can reach it without running nonstop for hours.
About 1–7 PM80–81°FLet the house drift. The goal is to reduce peak-window compressor runtime, not to make the hallway feel perfect at 4:30 PM.
After 7 PM while occupied78°FRecover after peak. If recovery takes too long, start by checking whether the house actually hit the pre-cool target.
Sleep74–76°FUse the bedroom comfort number your household can sleep with; do not let an unused hot room control the whole house overnight.
Away85°F, unless it blocks pre-coolingReasonable away limit, but disable or adjust away/eco behavior on extreme-heat days if it prevents the 11 AM pre-cool.

The rate window is the part to verify before relying on exact cents. Secondary summaries of NV Energy time-of-use periods describe summer peak as weekdays from June 1 through Sept. 30, about 1:01 PM to 7 PM, with one Solar Optimum tariff summary listing roughly $0.389/kWh peak and $0.095/kWh off-peak.[2] The Cooling Company’s 2026 Las Vegas figures are lower — about $0.18–$0.22 peak versus $0.09–$0.12 off-peak — which is enough discrepancy to treat the schedule as sound logic, not a substitute for checking the current NV Energy tariff before relying on exact bill math.[1]

If your house is occupied during the day, do not make the peak setting punitive. An 80–81°F drift is already a compromise. If you have medical needs, small children, heat-sensitive pets, or an upstairs bedroom that becomes unsafe, comfort and safety overrule the recipe. The useful version of this schedule is one the house can actually ride through.

Why a flat 78°F often fails here

A flat 78°F setting sounds neat because it is easy to remember. In a Las Vegas heat wave, it can put the compressor’s hardest work right into the highest-load hours. By 3 or 4 PM, the attic, stucco, windows, and west-facing rooms are all giving heat back to the house. The thermostat is not deciding thrift in a vacuum; it is deciding when to run a real air conditioner against a real building.

Pre-cooling moves some of that work earlier. The house starts the peak window with cooler walls, cooler furnishings, and more margin before the hallway reaches 80°F. Letting the setpoint rise during peak then gives the compressor permission to stand down instead of cycling hard at the most expensive and least forgiving time of day.

That does not make the schedule magic. Cooling below 78°F still uses energy, and The Cooling Company gives a rough Las Vegas cost sensitivity of about 3–4% more cooling cost for each degree below 78°F.[1] The point is to choose when those lower degrees happen. For a broader savings reality check, compare this kind of heat-advisory recipe with measured and claimed savings in our guide to smart thermostat heat-advisory savings.

Nest: make Eco and learning behavior obey the schedule

On a Nest thermostat, enter the schedule first, then audit the features that can quietly change what you thought you entered. The schedule itself is simple: add a late-morning cooling event at 74–76°F, a 1 PM event at 80–81°F, a 7 PM event at 78°F, and a bedtime event at 74–76°F.

  • Set the 11 AM pre-cool event to 74–76°F. Use 76°F first if your system struggles, then lower only if the house reaches the target before 1 PM.
  • Set the 1 PM peak event to 80–81°F. This is the drift setting; do not pair it with another automation that immediately pulls the house back to 78°F.
  • Set the 7 PM occupied event to 78°F. If your household needs dinner cooler, use 77°F after peak rather than fighting for it during peak.
  • Set the sleep event to 74–76°F, preferably based on bedroom comfort rather than a hot hallway.

The first Nest setting to check is Eco Temperature. Google lists the cooling Eco Temperature range as 76–90°F, and Nest can switch to Eco when it thinks the home is away.[3] That is useful on ordinary days. On a Las Vegas peak day, it can ruin the pre-cool if the thermostat decides the house is away at 11 AM and holds 85°F instead of pulling down to 74–76°F.

There are two clean ways to handle that. If someone or pets need the house pre-cooled, turn off automatic Eco/away behavior for the extreme-heat stretch. If the house is truly empty and you mainly care about cost, leave Eco on and accept that you are not running this pre-cool recipe that day. The frustrating middle is thinking you scheduled a pre-cool while Eco is vetoing it.

Airwave is usually less dangerous to the plan. Google describes Airwave as turning off the compressor while continuing the fan for about 5–10 minutes, and says it disables itself when indoor humidity is high.[4] In dry Las Vegas conditions, leaving Airwave on is reasonable if the rooms still feel comfortable. If the house feels warmer or clammy during monsoon moisture, turn it off for a day and compare recovery.

Sun hitting the thermostat is a different problem. Google’s Sunblock feature is not available on the standard Nest Thermostat.[5] If afternoon sun lands on the device, do not expect a schedule tweak to fix bad temperature sensing. Shade the thermostat, close the window covering, or plan for relocation. A thermostat reading the wall wrong will make every recipe look worse than it is.

ecobee: Comfort Settings are the recipe; eco+ is the possible override

ecobee is powerful enough to run this schedule cleanly and powerful enough to outsmart it. Build the recipe with Comfort Settings first. ecobee describes Activities and Comfort Settings as the named temperature and fan settings used by the schedule, which is exactly the structure you want here.[6]

ecobee Comfort SettingCool setpointScheduled time
Home78°FOccupied morning and after 7 PM
Pre-Cool74–76°FAbout 11 AM–1 PM
Peak Drift80–81°FAbout 1–7 PM
Sleep74–76°FBedtime through wake
Away85°FOnly when it will not block needed pre-cooling

After the Comfort Settings are on the calendar, decide whether eco+ Time of Use is helping or interfering. ecobee says eco+ can use Time of Use to pre-cool or pre-heat around higher electricity prices and claims additional cooling savings of 7–26% for Time of Use customers.[7] That is a vendor savings claim, not a promise for one Las Vegas house, and it should not be treated as proof that the thermostat picked the right comfort tradeoff for your rooms.

If you want manual control, disable eco+ Time of Use during the test week and let your own 11 AM, 1 PM, 7 PM, and bedtime schedule run. If you want ecobee to optimize around rates, leave eco+ on but check the actual setpoint on the thermostat during the 1–7 PM window. The important test is not whether eco+ sounds efficient. It is whether the displayed cooling target is still the one you intended.

Also check Smart Recovery. When recovery is enabled, ecobee can start cooling before the next scheduled Comfort Setting so the home reaches the target by the scheduled time. That can be comfortable at 7 PM, but it can also start compressor runtime before the peak window has ended if the thermostat is trying to arrive at 78°F right at 7 PM. ecobee’s threshold settings are where advanced staging, temperature correction, and related control behavior live, and third-party walkthroughs commonly point users to disabling Smart Recovery and eco+ when they want strict setpoint control.[8][9]

Finally, do not mistake the setpoint for an exact on/off line. ecobee’s threshold documentation covers temperature differential behavior, and the common cooling expectation is that a thermostat may wait about 1°F above the cooling setpoint before calling for cooling unless thresholds are changed.[8] So a 78°F setting may behave more like “cool when the sensed temperature rises to about 79°F.” That is normal control logic, but it matters when someone is staring at the app wondering why the AC is not running at 78.4°F.

If you are comparing Nest Airwave, ecobee eco+ Time of Use, and demand-response behavior side by side, the deeper feature breakdown belongs in our heat-wave thermostat feature comparison. For this recipe, the rule is simpler: either let ecobee optimize and verify the result, or turn the optimizers off and run the schedule exactly.

Honeywell Home: keep the fan boring unless you have a reason

On Honeywell Home thermostats, the schedule is usually the least dramatic part. Program the same four cooling targets: 74–76°F before peak, 80–81°F during peak, 78°F after 7 PM, and 74–76°F for sleep. Then look at fan mode before you start hunting for clever settings.

  • Use Auto as the default fan mode. The fan runs with cooling calls and shuts off when the cooling call ends.
  • Use Circ only if you are trying to mix air between rooms or floors. Honeywell describes Circ as running the fan about 35% of the time, or about 20 minutes per hour, minus time the heating or cooling system already ran.[10]
  • Avoid continuous On as the default summer answer. It can make some rooms feel more even, but it also adds fan heat and can work against dehumidification during muggy monsoon periods.

In very dry weather, Circ can be useful for a stuffy upstairs landing or a bedroom that lags behind the hallway thermostat. During humid spells, especially after storms, Auto is the safer starting point. If the house feels sticky after the compressor shuts off, stop circulating air over a wet coil and go back to Auto.

If the house still will not recover

The first diagnostic is not in the app. At 12:45 PM, check whether the home actually reached 74–76°F. If it did, the drift plan has a fair chance. If it did not, the schedule is asking for stored cooling the house never received.

What you seeMost useful checkLikely next move
The thermostat never reaches 74–76°F before 1 PMConfirm filters, supply airflow, closed blinds, and whether an eco/away feature blocked pre-cool.Use 76°F as the pre-cool target, start a little earlier, or have the AC/envelope checked if it still cannot pull down.
The house is fine downstairs but bedrooms are hotLook at sensor participation, room exposure, and whether the upstairs is controlling the whole system.Use bedroom sensors for Sleep, not necessarily for the 1–7 PM peak period.
The compressor starts before 7 PM even though peak drift is scheduledCheck Smart Recovery, eco+ Time of Use, adaptive recovery, demand-response enrollment, and active holds.Disable the feature for the test week or move the recovery target later.
The app says 78°F but cooling does not start immediatelyCheck temperature differential/deadband behavior.Do not chase decimal readings; adjust the setpoint only if comfort is consistently off.
Rooms feel humid or stale after fan-only operationCheck whether Fan On or Circ is running too much during humid weather.Return to Auto and compare for a day.

Two-story Las Vegas homes need special restraint. Local cooling guidance commonly focuses on upstairs heat gain, room imbalance, and the usefulness of zoning or remote sensing for stubborn second floors.[11] Remote sensors can help the thermostat understand where people actually are, but one west-facing bedroom can also drag the whole system into a long afternoon run. During the peak drift period, let the main living area coast if it is safe. At night, shift attention to occupied bedrooms.

Blinds, exterior shade, attic heat, duct leakage, and AC condition decide whether this recipe feels calm or barely adequate. If the home stalls at 79°F before peak even with a clean filter and closed shades, do not keep lowering the pre-cool target and blaming the thermostat. A control system cannot make an undersized, poorly charged, or badly ducted system behave like a bigger one.

What to watch during the first three days

Give the schedule a short, boring test before you judge it. The thermostat history is more useful than the sales screen. You are looking for three things: whether the system reaches pre-cool, how far the house drifts by 7 PM, and whether a smart feature changed the target without asking.

  1. Day 1: Use 76°F for pre-cool, 81°F for peak drift, 78°F after 7 PM, and your normal sleep setting. This is the cautious version.
  2. Day 2: If the house reached 76°F before 1 PM and stayed tolerable through peak, keep it. If west-facing rooms were still climbing hard, try 75°F pre-cool or start the pre-cool earlier.
  3. Day 3: Check runtime and comfort, not just the bill estimate in the app. If recovery starts before 7 PM, hunt for Smart Recovery, eco+ Time of Use, adaptive recovery, demand-response, or a hold.

Do not tune every number at once. If you lower the pre-cool, change the fan mode, turn on a utility feature, and move the bedtime setting on the same day, you will not know which change helped. The clean test is one schedule, one set of overrides, and one honest look at whether the house reached the target before peak.

Savings claims belong in the background

This recipe can reduce peak-window runtime. Whether it lowers your total bill depends on your actual tariff, insulation, AC condition, occupancy, solar gain, and how low you pre-cool. A house that pre-cools easily to 76°F and drifts slowly is a good candidate. A house that needs nonstop cooling from 10 AM onward to touch 76°F may simply be moving a lot of runtime earlier.

That is why the cents matter but should not be over-sold. The secondary NV Energy summaries support the peak-shifting logic, yet their listed rates differ enough that the exact bill math needs current verification.[1][2] Vendor claims need the same discipline. ecobee’s 7–26% Time of Use cooling-savings claim may be relevant if you let eco+ manage the schedule, but it is still a vendor claim and not a guarantee for a stucco house with an upstairs bonus room.[7]

The practical win is narrower and more useful: fewer hopeless compressor calls during the late-afternoon peak, a clearer bedtime recovery, and fewer surprises from thermostat features that were trying to be helpful. If you want a device-by-device savings comparison beyond this recipe, use the separate guide to smart-home cooling device savings rather than turning this schedule into a fake ROI calculator.

The boundary of the recipe

For Las Vegas extreme heat, the default smart thermostat recipe is: 74–76°F before peak, 80–81°F from roughly 1–7 PM, 78°F after peak when occupied, and 74–76°F at night. It works best when the AC can actually hold the pre-cool and the thermostat is not allowed to “optimize” over the user’s plan.

Before treating the numbers as final, verify the current NV Energy time-of-use window and rates, confirm Nest Eco, ecobee eco+/Smart Recovery, Honeywell fan behavior, and any demand-response settings are not overriding the schedule, and watch whether the home reaches 74–76°F before peak. If it cannot, the next answer is not another app toggle. It is airflow, shade, ducts, insulation, refrigerant charge, capacity, or expectations.

References

  1. Best Thermostat Settings for Las Vegas — The Cooling Company
  2. What Are Nevada Energy Peak Hours for TOU Rates? — Solar Optimum
  3. Learn about Eco Temperatures and how to change settings — Google Nest Help
  4. Learn about Airwave and how to change settings — Google Nest Help
  5. Learn about Sunblock and how to change settings — Google Nest Help
  6. What are Activities and Comfort Settings? — ecobee Support
  7. eco+ — ecobee
  8. Threshold settings for ecobee thermostats — ecobee Support
  9. How to Stop an Ecobee Smart Thermostat from Overriding Temperature Settings — Between Naps on the Porch
  10. 7-Day Programmable Thermostats — Honeywell Home
  11. How to Keep Your Two-Story House Cool in Las Vegas — NRS Vegas

Related reading

Feedback / Question

Did a step not work as written? Let us know so it can be corrected.

Blogarama - Blog Directory