Skip to content

Add template weather forecast documentation#42524

Merged
c0ffeeca7 merged 3 commits into
home-assistant:currentfrom
Petro31:add-weather-forecast-info
Dec 12, 2025
Merged

Add template weather forecast documentation#42524
c0ffeeca7 merged 3 commits into
home-assistant:currentfrom
Petro31:add-weather-forecast-info

Conversation

@Petro31
Copy link
Copy Markdown
Contributor

@Petro31 Petro31 commented Dec 11, 2025

Proposed change

Add template weather forecast documentation

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

  • Link to parent pull request in the codebase:
  • Link to parent pull request in the Brands repository:
  • This PR fixes or closes issue: fixes #

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

@Petro31 Petro31 requested a review from a team as a code owner December 11, 2025 18:25
@home-assistant home-assistant Bot added the current This PR goes into the current branch label Dec 11, 2025
@netlify
Copy link
Copy Markdown

netlify Bot commented Dec 11, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 8bf458f
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/693b0c9b15dfcd000808e99a
😎 Deploy Preview https://deploy-preview-42524--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Comment thread source/_integrations/template.markdown
@home-assistant home-assistant Bot marked this pull request as draft December 12, 2025 05:54
@home-assistant
Copy link
Copy Markdown

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@c0ffeeca7 c0ffeeca7 marked this pull request as ready for review December 12, 2025 11:59
Copilot AI review requested due to automatic review settings December 12, 2025 11:59
@home-assistant home-assistant Bot requested a review from c0ffeeca7 December 12, 2025 11:59
Copy link
Copy Markdown
Contributor

@c0ffeeca7 c0ffeeca7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @Petro31 👍

@c0ffeeca7 c0ffeeca7 merged commit 02e228a into home-assistant:current Dec 12, 2025
11 checks passed
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds documentation for the Template Weather Forecast feature, explaining how to properly structure weather forecast data for the three supported forecast types: hourly, daily, and twice daily. The documentation describes the expected data format and timing requirements for each forecast type.

  • Adds a new "Weather forecast data" section explaining how forecast templates should structure their data
  • Documents requirements for hourly (24 data points starting from current hour), daily (midnight-based increments), and twice daily (12-hour period) forecasts
  • Includes information about the mandatory is_daytime field for twice daily forecasts


The `hourly` forecast should contain 24 dictionaries, where each dictionary represents a specific hour within the next 24 hour period. The `hourly` data should start at the current hour and end 24 hours from that point. The `datetime` in each dictionary should represent the start of the hour in your local timezone.

#### Daily Weather Forecast
Copy link

Copilot AI Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The heading uses title-style capitalization ("Daily Weather Forecast") but should use sentence-style capitalization according to the documentation standards. It should be "Daily weather forecast".

Suggested change
#### Daily Weather Forecast
#### Daily weather forecast

Copilot uses AI. Check for mistakes.

The `daily` forecast should contain dictionaries, where each dictionary represents a specific day within any desired timeframe. The `daily` data should start at midnight tonight and end on the last day of your desired timeframe, incrementing 1 day at a time. The `datetime` in each dictionary should represent midnight for each night in your local timezone.

#### Twice Daily Weather Forecast
Copy link

Copilot AI Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The heading uses title-style capitalization ("Twice Daily Weather Forecast") but should use sentence-style capitalization according to the documentation standards. It should be "Twice daily weather forecast".

Suggested change
#### Twice Daily Weather Forecast
#### Twice daily weather forecast

Copilot uses AI. Check for mistakes.

#### Hourly Weather Forecast

The `hourly` forecast should contain 24 dictionaries, where each dictionary represents a specific hour within the next 24 hour period. The `hourly` data should start at the current hour and end 24 hours from that point. The `datetime` in each dictionary should represent the start of the hour in your local timezone.
Copy link

Copilot AI Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The phrase "24 hour period" should be hyphenated when used as a compound adjective. It should be "24-hour period".

Suggested change
The `hourly` forecast should contain 24 dictionaries, where each dictionary represents a specific hour within the next 24 hour period. The `hourly` data should start at the current hour and end 24 hours from that point. The `datetime` in each dictionary should represent the start of the hour in your local timezone.
The `hourly` forecast should contain 24 dictionaries, where each dictionary represents a specific hour within the next 24-hour period. The `hourly` data should start at the current hour and end 24 hours from that point. The `datetime` in each dictionary should represent the start of the hour in your local timezone.

Copilot uses AI. Check for mistakes.

#### Twice Daily Weather Forecast

The `twice_daily` forecast should contain dictionaries, where each dictionary represents a specific 12 hour period within any desired timeframe. The `twice_daily` should start at the closest 12 hour period and end on the last 12 hour period of your desired timeframe. The `datetime` in each dictionary should represent midnight or noon for each day in your local timezone. Keep in mind, `is_daytime` is mandatory in every dictionary output to `twice_daily` forecasts.
Copy link

Copilot AI Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The phrase "12 hour period" should be hyphenated when used as a compound adjective. It should be "12-hour period".

Suggested change
The `twice_daily` forecast should contain dictionaries, where each dictionary represents a specific 12 hour period within any desired timeframe. The `twice_daily` should start at the closest 12 hour period and end on the last 12 hour period of your desired timeframe. The `datetime` in each dictionary should represent midnight or noon for each day in your local timezone. Keep in mind, `is_daytime` is mandatory in every dictionary output to `twice_daily` forecasts.
The `twice_daily` forecast should contain dictionaries, where each dictionary represents a specific 12-hour period within any desired timeframe. The `twice_daily` should start at the closest 12-hour period and end on the last 12-hour period of your desired timeframe. The `datetime` in each dictionary should represent midnight or noon for each day in your local timezone. Keep in mind, `is_daytime` is mandatory in every dictionary output to `twice_daily` forecasts.

Copilot uses AI. Check for mistakes.

#### Twice Daily Weather Forecast

The `twice_daily` forecast should contain dictionaries, where each dictionary represents a specific 12 hour period within any desired timeframe. The `twice_daily` should start at the closest 12 hour period and end on the last 12 hour period of your desired timeframe. The `datetime` in each dictionary should represent midnight or noon for each day in your local timezone. Keep in mind, `is_daytime` is mandatory in every dictionary output to `twice_daily` forecasts.
Copy link

Copilot AI Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are two spaces between sentences in this line. According to the style guide, only one space should be used after periods. The double space appears after "desired timeframe." and before "The datetime".

Suggested change
The `twice_daily` forecast should contain dictionaries, where each dictionary represents a specific 12 hour period within any desired timeframe. The `twice_daily` should start at the closest 12 hour period and end on the last 12 hour period of your desired timeframe. The `datetime` in each dictionary should represent midnight or noon for each day in your local timezone. Keep in mind, `is_daytime` is mandatory in every dictionary output to `twice_daily` forecasts.
The `twice_daily` forecast should contain dictionaries, where each dictionary represents a specific 12 hour period within any desired timeframe. The `twice_daily` should start at the closest 12 hour period and end on the last 12 hour period of your desired timeframe. The `datetime` in each dictionary should represent midnight or noon for each day in your local timezone. Keep in mind, `is_daytime` is mandatory in every dictionary output to `twice_daily` forecasts.

Copilot uses AI. Check for mistakes.

{% endconfiguration %}

### Weather Forecast data
Copy link

Copilot AI Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The heading uses title-style capitalization ("Weather Forecast data") but should use sentence-style capitalization according to the documentation standards. It should be "Weather forecast data".

Suggested change
### Weather Forecast data
### Weather forecast data

Copilot uses AI. Check for mistakes.

The weather forecast options should return a list of dictionaries, where each dictionary contains [forecast information](https://www.home-assistant.io/integrations/weather/#action-weatherget_forecasts) for the current timeframe. The data is slightly different for each forecast type: `hourly`, `daily`, and `twice_daily`.

#### Hourly Weather Forecast
Copy link

Copilot AI Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The heading uses title-style capitalization ("Hourly Weather Forecast") but should use sentence-style capitalization according to the documentation standards. It should be "Hourly weather forecast".

Suggested change
#### Hourly Weather Forecast
#### Hourly weather forecast

Copilot uses AI. Check for mistakes.
Raraph84 pushed a commit to Raraph84/home-assistant.io that referenced this pull request Dec 13, 2025
@github-actions github-actions Bot locked and limited conversation to collaborators Dec 13, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

current This PR goes into the current branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants