Add visibility and wind direction to weather template

[avee87]

Proposed change

Currently weather template doesn't support these attributes. They are useful, for instance, when you want to create a weather entity from multiple sources and show them in a rich weather card.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml
weather:
  - platform: template
    name: Composite Weather
    condition_template: "{{ states('weather.home') }}"
    temperature_template: "{{ states('sensor.outdoor_temperature') | float}}"
    humidity_template: "{{ states('sensor.outdoor_humidity') | float }}"
    pressure_template: "{{ states('sensor.outdoor_pressure') | float }}"
    forecast_template: "{{ state_attr('weather.home', 'forecast') }}"
    visibility_template: "{{ state_attr('weather.home', 'visibility') }}"
    wind_bearing_template: "{{ state_attr('weather.home', 'wind_bearing') }}"
    wind_speed_template: "{{ state_attr('weather.home', 'wind_speed') }}"

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Add new variables to weather template home-assistant.io#16851

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[homeassistant]

Hi @avee87,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[probot-home-assistant]

Hey there @PhracturedBlue, @tetienne, mind taking a look at this pull request as its been labeled with an integration (template) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[dgomes]

LGTM

[dgomes]

#47736 is more extensive then this PR, we should focus in a single one

[dgomes]

Can we close this one then ?

[avee87]

Closing in favour of #47736