Add a standardised way to handle forecasting sensor data as part of HA core

HA has a solid way to store historic sensor data, using the recorder and long term statistics, but what about forecasting sensor data? I think it would be a great addition if there would be a standardised way to handle forecast throughout all of HA. Think about the UI showing graphs with forecasted energy prices, automations that can anticipate on forecasted precipitation

Some added benefits if forecast would be part of HA:
An automation could close the awning 5 minutes before it starts to rain
Appliances could start on the cheapest time of the day based on dynamic energy prices.

Data I’m thinking about that could include forecasts:
Dynamic energy prices
Weather
Traffic
Fuel prices
Energy consumption
Tides
Upcoming song/Playlist

I am aware some integrations already implement some kind of forecasting, like the weather platform which has the weather.get_forecasts action, the sun integration which has various solar related forecasts as separate sensors available and the Nord Pool integration which has the dynamic energy prices for the day stored in a state attribute.

This already sums up 3 different ways forecasts are currently implemented, using an action, separate sensors or as state attribute and maybe different other approaches are also in use that I haven’t seen.

That is now handled terribly and needs an easier way. Expecting new users to create triggered template sensors to be able to use forecast data is asking too much.

+1

Just wanted to add that the Tibber integration uses a tibber.get_prices action to get energy price forecast

Also, there already is a discussion on the subject on the HA architecture GitHub: