-
Notifications
You must be signed in to change notification settings - Fork 0
Season Detection
Scott Gusler edited this page Feb 11, 2026
·
3 revisions
Detects if the current date falls within a specific season.
A season sensor is ON when the current date is in the selected season, OFF otherwise.
Uses meteorological seasons, which are based on temperature cycles and defined by complete calendar months.
- Select "Season Detection"
- Configure:
- Calculation Name: A friendly name
- Season: Choose spring, summer, autumn, or winter
- Hemisphere: Choose northern or southern
- Icon: Optional custom icon
Dates vary based on selected hemisphere:
- Spring: March 1 - May 31
- Summer: June 1 - August 31
- Autumn: September 1 - November 30
- Winter: December 1 - February 28/29
- Spring: September 1 - November 30
- Summer: December 1 - February 28/29
- Autumn: March 1 - May 31
- Winter: June 1 - August 31
Metorological seasons are defined by temperature cycles rather than astronomical events (equinoxes/solstices). This makes them more useful for weather, climate, and temperature-based automation. Each season spans exactly 3 months:
- More consistent meteorological data across the year
- Better alignment with temperature patterns
- Easier for climate-related automation rules
{
"type": "season",
"name": "Winter Season",
"season": "winter",
"hemisphere": "northern"
}Use in automation to adjust thermostat settings
{
"type": "season",
"name": "Time of Year Summer",
"season": "summer",
"hemisphere": "southern"
}Adjust lighting brightness based on season
automation:
- alias: "Winter heating mode"
trigger:
platform: state
entity_id: binary_sensor.winter_season
to: "on"
action:
service: climate.set_preset_mode
target:
entity_id: climate.thermostat
data:
preset_mode: heating
- alias: "Summer cooling mode"
trigger:
platform: state
entity_id: binary_sensor.summer_season
to: "on"
action:
service: climate.set_preset_mode
target:
entity_id: climate.thermostat
data:
preset_mode: cooling