Smart Thermostat Settings for September Weather

September is the month when a smart thermostat can look most suspicious. The afternoon is warm, the evening is open-window mild, and the HVAC should be doing almost nothing. Then the hallway display shows a target you did not choose, the system starts cooling before a scheduled change, or the AC runs for humidity when the room already feels close enough.

The first correction matters: a mainstream Nest or ecobee thermostat is not rewriting its schedule just because tomorrow’s weather forecast says “partly cloudy.” Weather, humidity, and grid signals are inputs to named features. Those features can still move behavior in ways that feel like drift, but the cause is usually not “the forecast changed my schedule.” It is a feature with permission to pre-condition, save energy, respond to grid events, edit a schedule during a campaign, or control indoor humidity.

The dated workaround: disable eco+ and both Smart Recovery options

If the symptom is an ecobee that appears to heat or cool toward a number different from the one you set, the most useful starting point is a status-labeled workaround, not a promise that this is permanently “the fix.” A homeowner-reproduced fix published Feb. 26, 2025 reported that disabling eco+ and both Heating Smart Recovery and Cooling Smart Recovery under Settings > Preferences stopped the unexplained temperature mismatch, with additional reader comments corroborating the behavior. Treat that as a Workaround / Confirmed-as-reproduced homeowner workaround, not as vendor-confirmed documentation.[1]

• On ecobee, check Settings > Preferences.
• Turn off eco+ if the thermostat is making savings, grid, or comfort adjustments you do not want during shoulder weather.
• Turn off Heating Smart Recovery and Cooling Smart Recovery if the system starts early to reach a scheduled setpoint before the scheduled time.
• Re-check the thermostat at the next scheduled transition rather than judging it immediately after changing the setting.

The status label is not legal padding. Thermostat apps and firmware change. A workaround reproduced in early 2025 can be exactly what a homeowner needed then and still deserve rechecking later against the current app layout and ecobee’s own documentation.

What the September forecast can influence

For September forecast swings, the useful smart thermostat settings are the ones that expose which automation is acting. A forecast can help a thermostat estimate how early to start, whether the home will coast, or how outside conditions affect comfort. That is different from the thermostat deciding that your whole schedule should be rewritten by the weather app.

That table is the difference between a thermostat being “smart” and a thermostat being annoyingly opaque. Airwave has a physical mechanism: the compressor stops, the fan uses leftover coil cooling, and the feature backs off when indoor humidity is high.[5] I may or may not want it on, but I can at least understand what it is trying to do. Silent schedule edits and pre-cooling need more scrutiny because the homeowner sees a number move before seeing the reason.

Seasonal Savings is a schedule editor, not a weather schedule

Nest Seasonal Savings deserves its own check because it can make the thermostat look like it has slowly developed a new opinion. Google describes Seasonal Savings as a campaign that makes small changes to scheduled temperatures over several days, adding up to about 2°F total. The changes are intended to be largest when people are asleep or away, and the program begins only after the thermostat starts consistently heating or cooling.[2]

In September, that timing can be awkward. A home may barely need cooling for several days, then get a warm stretch, then stop again. If Seasonal Savings appears during a period when the system has begun consistently cooling or heating, the owner may notice the setpoint has been nudged and blame the weather forecast. The better clue is in Energy History: Google says Seasonal Savings changes appear with a gold ring, and the app offers a “View changes” option.[2]

That is the kind of automation clue worth looking for before assuming the thermostat is broken. A gold-ringed schedule change is not a ghost in the hallway. It is a named feature making schedule edits.

eco+ is broader, and that is why it needs a shorter leash in September

ecobee’s eco+ bundle is not one single thermostat trick. ecobee says eco+ uses a household’s routine, comfort preferences, local weather, and grid activity.[3] That breadth is useful when the owner has agreed to it and can see it acting. It is aggravating when the house is already comfortable and the thermostat quietly behaves as if savings, grid response, and comfort preferences outrank the setpoint on the screen.

The most important September check is the eco+ status indicator on the ecobee home screen.[3] If that indicator is active while the thermostat appears to be drifting, do not start by rebuilding the entire schedule. First decide whether eco+ should be allowed to participate at all during mild shoulder-season weather.

ecobee also markets eco+ with savings claims: “up to 26%” and “$284 per year,” based on an April 2021 internal analysis.[3] Those figures may be useful as vendor context, but they do not prove that a specific September override in a specific house is acceptable. The local question is simpler: can the person paying the bill see what is acting and turn it off?

Smart Recovery is not drift if you asked for arrival on time — but it can look like drift

Smart Recovery, Pre-Heat, and Pre-Cool exist to hit a scheduled temperature at the scheduled time. The thermostat learns or estimates how the house responds and can use weather as part of that calculation, so cooling may begin before the schedule says “cool to 72” if the thermostat thinks the home needs a head start.[4]

That behavior can be perfectly reasonable in January or during a hot spell. In September, it often reads as overconfidence. The owner sees a schedule time in the app, then hears the system start earlier, and the thermostat offers less explanation than it should. If the complaint is specifically “it starts cooling before I told it to,” Smart Recovery belongs near the top of the suspect list.

The choice is not moral. Leave recovery on if arriving exactly at the scheduled setpoint matters more than avoiding early runtime. Turn it off if September comfort is loose enough that the home can arrive a little late without anyone caring. This is especially true in households where people manually adjust during shoulder weather and the schedule is more of a guideline than a contract.

Airwave and Cool to Dry: the two Nest features that need different judgments

Nest Airwave is easier to defend because the boundary is visible once you know it. Google says Airwave can turn off the compressor early and run the fan alone for 5 to 10 minutes, using residual cooling from the coil. Google also says Airwave is disabled when indoor humidity is high.[5] In a mild September cooling cycle, that can be a sensible way to coast through the last few minutes without running the compressor.

Cool to Dry is a different animal. Google’s current support documentation says Cool to Dry can use AC to reduce humidity when home humidity exceeds about 75% relative humidity, or about 65% when the home is away on Eco Temperatures for 3 days. It can cool up to 3°F below the temperature setpoint, with a 75°F floor.[6]

Those are the numbers worth using now. Older third-party threshold figures exist, but mixing vintages is how thermostat folklore starts. If a Nest is cooling below the setpoint in September and the house feels damp, check Cool to Dry against the current Google support thresholds before blaming the forecast or rebuilding the schedule.

How to tell which feature is acting

Start with the evidence that the thermostat already gives you. The fastest troubleshooting path is not a perfect September schedule. It is matching the symptom to the feature that has permission to cause it.

This is also where ordinary September advice has limited value. Yes, many homes can tolerate a wider cooling setpoint in September. Yes, a simple schedule helps. But those suggestions do not explain why the thermostat moved after you set it. If you want broader thermostat feature comparisons, the Nest Airwave and ecobee eco+ comparison is the better detour. If the problem is heat-advisory operation rather than shoulder-season drift, use the heat-advisory thermostat settings guide instead.

What to keep on, what to turn off

Keep bounded, explainable features if they serve the house. Airwave is a good example when humidity is under control because its behavior has a physical reason and a short operating window. Cool to Dry may also be worth keeping in a damp house, but only if everyone understands that the thermostat can cool below the temperature setpoint within Google’s documented limits.[5][6]

Be more skeptical of features that change the owner’s target without an obvious local action. Seasonal Savings can be fine if you watch its gold-ringed changes and accept the campaign. eco+ can be fine if the status indicator is visible and the household wants those adjustments. Smart Recovery can be fine if “arrive exactly on time” matters. The problem is not that any of these features exist; the problem is letting them explain themselves only after the homeowner has already gone looking for the cause.

If September drift is the actual complaint, disable the features most likely to create it: ecobee eco+, Heating Smart Recovery, and Cooling Smart Recovery. On Nest, inspect Seasonal Savings changes and Cool to Dry before assuming a normal schedule problem. If you are using temperature drops or recovery behavior intentionally, the temperature-drop schedule guide is a better place to tune that strategy.

About the savings claims

Vendor savings numbers belong in the background here, not in the driver’s seat. Google has claimed 3% to 5% average savings for Seasonal Savings in a company blog post, while a Nest energy-solutions page cites 5% to 10% for Seasonal Savings.[7][8] ecobee’s eco+ page claims up to 26% savings and $284 per year, based on an April 2021 internal analysis.[3]

Those are vendor claims, and the Google figures are not even identical across the cited company materials. They may help explain why the features exist. They do not settle whether a thermostat should quietly pre-cool a comfortable house on a mild September afternoon.

The practical standard is control. Keep the feature if you can see it, understand its boundary, and still want the result. Turn it off if it silently changes setpoints, recovery timing, or cooling behavior in a season when the HVAC should be boring. And keep the Feb. 26, 2025 eco+ plus Smart Recovery workaround in its proper box: useful, homeowner-reproduced, and worth rechecking whenever the app or firmware changes.

References

1. Ecobee Smart Thermostat Premium Says It’s Heating to One Temperature But Is Set on a Different One, How to Fix, Between Naps on the Porch, Feb. 26, 2025
2. Learn about Seasonal Savings, Google Nest Help
3. eco+, ecobee
4. What is Smart Recovery and how does it work, ecobee Support
5. Learn about Airwave and how to change settings, Google Nest Help
6. Learn about Cool to Dry, Google Nest Help
7. Seasonal Savings with Nest thermostats, Google
8. Energy Solutions, Nest