Home assistant changed weather forecasts from attributes to a service reply.

[stovedoctor]

Sept 2023 Ha announced that the use of weather attributes will be depreciated in March of 2024 I did not have time to fix this issue until now.
Weather forecast service

If you use the old way of using the weather attributes in a template they would no longer work.

OLD WAY

 - obj: "p5b51" # Forecast time +8h
      properties:
        "text": >
          {%- if not is_state('weather.barb_s_place_hourly','unavailable') %}
          {%- set update = states('sensor.date') %}
          {%- set midnight = now().replace(hour=0, minute=0, second=0, microsecond=0).timestamp() %}
          {%- set event = as_timestamp(strptime(state_attr('weather.barb_s_place_hourly','forecast')[8]['datetime'], '%Y-%m-%dT%H:%M:%S%z', default='2020-01-00T00:00:00+00:00')) %}
          {%- set delta = ((event - midnight) // 86400) | int %}
          {%- if delta == 0 %}
          Today
          {%- elif delta == 1 %}
          Tomorrow
          {%- endif %}
          {{- event | timestamp_custom(" %-I %p") }}
          {%- endif %}

    - obj: "p5b52" # Forecast temp +8h
      properties:
        "text": "{{ state_attr('weather.barb_s_place_hourly','forecast')[8]['temperature'] if not is_state('weather.barb_s_place_hourly','unavailable') else '-' }}"

    - obj: "p5b53" # Forecast condition +8h
      properties:
        "src": >
          {%- if not is_state('weather.barb_s_place_hourly','unavailable') %}
          L:/w-32-{{ state_attr('weather.barb_s_place_hourly','forecast')[8]['condition'] }}.png
          {%- endif %} 

Solution:

Create a Hourly weather sensor.
sensor.weather_hourly

This does not work for accuweather I needed to use the Meteorologisk institutt (Met.no) integration.
just for less confusion i created a new weather service called home forecast
then created new sensor sensor.weather_hourly in my template.yaml

hourly forecast sensor

#weather forcast hourly sensor 
- trigger:
    - platform: time_pattern
      minutes: /1

    - platform: homeassistant
      event: start
  action:
    - service: weather.get_forecasts
      data:
        type: hourly
      target:
        entity_id: weather.home
      response_variable: hourly

  sensor:
    - name: Weather Hourly
      state: "{{ states('weather.home') }}"
      attributes:
        temperature: "{{ state_attr('weather.home', 'temperature') }}"
        dew_point: "{{ state_attr('weather.home', 'dew_point') }}"
        temperature_unit: "{{ state_attr('weather.home', 'temperature_unit') }}"
        humidity: "{{ state_attr('weather.home', 'humidity') }}"
        cloud_coverage: "{{ state_attr('weather.home', 'cloud_coverage') }}"
        pressure: "{{ state_attr('weather.home', 'pressure') }}"
        pressure_unit: "{{ state_attr('weather.home', 'pressure_unit') }}"
        wind_bearing: "{{ state_attr('weather.home', 'wind_bearing') }}"
        wind_speed: "{{ state_attr('weather.home', 'wind_speed') }}"
        wind_speed_unit: "{{ state_attr('weather.home', 'wind_speed_unit') }}"
        visibility_unit: "{{ state_attr('weather.home', 'visibility_unit') }}"
        precipitation_unit: "{{ state_attr('weather.home', 'precipitation_unit') }}"
        forecast: "{{ hourly['weather.home'].forecast }}"    

New yaml for plates for +8 hour data to be displayed. basicly replace all weather.barb_s_place_hourly' with sensor.weather_hourly

yaml

    - obj: "p5b51" # Forecast time +8h
      properties:
        "text": >
          {%- if not is_state('sensor.weather_hourly','unavailable') %}
          {%- set update = states('sensor.date') %}
          {%- set midnight = now().replace(hour=0, minute=0, second=0, microsecond=0).timestamp() %}
          {%- set event = as_timestamp(strptime(state_attr('sensor.weather_hourly','forecast')[8]['datetime'], '%Y-%m-%dT%H:%M:%S%z', default='2020-01-00T00:00:00+00:00')) %}
          {%- set delta = ((event - midnight) // 86400) | int %}
          {%- if delta == 0 %}
          Today
          {%- elif delta == 1 %}
          Tomorrow
          {%- endif %}
          {{- event | timestamp_custom(" %-I %p") }}
          {%- endif %}

    - obj: "p5b52" # Forecast temp +8h
      properties:
        "text": "{{ state_attr('sensor.weather_hourly','forecast')[8]['temperature'] if not is_state('sensor.weather_hourly','unavailable') else '-' }}"

    - obj: "p5b53" # Forecast condition +8h
      properties:
        "src": >
          {%- if not is_state('sensor.weather_hourly','unavailable') %}
          L:/w-32-{{ state_attr('sensor.weather_hourly','forecast')[8]['condition'] }}.png
          {%- endif %}

sources
Weather forecast service
HA dev Weather forecasts

https://community.home-assistant.io/t/petition-dont-delete-the-forecast-attribute/609298?u=rod_poplarchick

Unsure How To Use Hourly Forecast Information (Since 2024.3.0) #112628

[jazzmonger]

What a royal PITA. All that work on my forecast page down the drain.
Can you expand on this? I'm lost...
i created a new weather service called home forecast --- HOW???
then created new sensor sensor.weather_hourly in my template.yaml

[stovedoctor]

The solution yaml that you put in your home assistant config file or your template.yaml file if you have your templates out of your configuration.yaml

So you would replace your old weather.myweather_hourly
With the
New
Sensor.myweather

[stovedoctor]

So you replace your old {what ever is was named}
Weather.mystation_hourly
With the newly created
Sensor.myweather_hour
{what ever you choose to name}

[jazzmonger]

"i created a new weather service called home forecast "

HOW do you create a new service?? Im Still lost... all I've been able to do is pull from a different sensor

    - obj: "p1b17" # Current weather condition
      properties:
         "text": "{{state_attr('weather.weather_home','description')}}"

It's not nearly as comprehensive as the old text I got from NWS though.

[jazzmonger]

I can see the old description from NWS if I call the service.

so that would then go into a new template sensor? So it's not a "new service". It's creating a new sensor by calling a service.

how frigging convoluted and unnecessary. I really don't understand why they made this change.

[stovedoctor]

The old way puts strain on HA database and API calls

There are several other threads on GitHub and HA forums that explain better than I can but I will try to follow up with more info when I'm in a computer.
Read the comments for some great info.
My forum thread
https://community.home-assistant.io/t/update-from-using-weather-attributes-with-the-new-service-weather-get-forecasts/702736?u=rod_poplarchick

Another good one.
https://community.home-assistant.io/t/how-to-migrate-from-weather-integration-approach-to-new-weather-get-forecast-service/619481?u=rod_poplarchick

Get hub. There are several answers in the comments.

home-assistant/core#112583

[GregWoods]

now I know why my entire home heating system has been acting screwy. It's been stuck on a 14.2 deg C forecast.
I nearly boiled to death.
But I know I've only got myself to blame for not reading the release notes properly. No more regular updates for me :(

[fvanroie]

This will be more helpful when posted on the HA threads. We don't have any influence on which functionality they implement or deprecate... I have seen a lot of people being impacted by this change.