No forecast attribute on weather entities despite supported_features: 3 (DWD, OWM, Met.no)

Configuration
1

Hi everyone,

I’m running Home Assistant (2025.5.3) and noticed that none of my weather entities provide a forecast attribute – even though supported_features: 3 is set, which (to my understanding) should include forecast support.

Here are some examples from my setup:

:sunny: DWD (weather.ort)

state: sunny
temperature: 19.6
supported_features: 3
# → No `forecast` attribute present

:sunny: OpenWeatherMap (weather.openweathermap)

state: sunny
temperature: 22
apparent_temperature: 21.8
supported_features: 3
# → No `forecast` attribute present

:sunny: Met.no (weather.forecast_home_2)

state: sunny
temperature: 20.1
supported_features: 3
# → Again, no `forecast` attribute

:mag: However, when I call the service weather.get_forecasts manually for these entities (via Developer Tools → Services), I do get valid forecast data returned in the response (e.g., hourly or daily data with temperature etc.).

:question:My questions:

  • Shouldn’t this forecast data be automatically exposed in the weather entity (as the forecast attribute)?
  • Or is this new behavior in recent Home Assistant versions?
  • Is there a reason why I need to call the service explicitly every time?
  • Any known workaround to access this data via template or automation logic?

I’d appreciate any insights. My main goal is to use forecast temperatures in automations (like shading), but this issue seems more fundamental.

Thanks!

2

Not if it’s unnecessary and possibly detrimental. As I understand it, large attributes like forecast, calendar events, and others were contributing a significant amount of bloat to the database and having negative effects on overall efficiency.

Define “recent”… The forecast attribute was deprecated in core 2023.9 and removed from the state object of weather entities six months later in 2024.3.

Some weather provider integrations made the choice to move the sub-attributes of forecast into distinct sensors that users can enable as desired; others did not. Check the Entities menu to see if your weather provider integration has already created sensors that you just need to enable. If your provider integration did not, you can use weather.get_events in trigger-based Template sensors, as shown in the examples on the Weather integration page.

At this point there are dozens, if not hundreds, of posts on these forums covering different ways to use the action and manipulate the response data… do a search for weather.get_events.

1 Like