#Hourly forecast data

1 messages · Page 1 of 1 (latest)

viscid iris
#

Looking at my solar charts, i can see that the Forecast.Solar integration gives some level of detail on the forecasted production. It looks like the integration provides hourly data. But the sensor entities it provides only give you few specific windows into that data (today, today remaining, this hour, next hour etc).

Is it possible to retrieve the actual hourly data, for use in for example automations? I'm thinking of maybe using that to automatically generate a plan for when to use what devices

hollow crypt
#

Yes, look at the action it makes available

viscid iris
#

theres an action? i cant seem to find it in my install, the docs, or the source

#

i might be blind tho 😄

hollow crypt
#

Uh yeah I can't find it either but there should be something because the energy dashboard uses it

#

@brittle shuttle should know?

brittle shuttle
#

Forecasts is not exposed as an action, though I saw once someone working on a PR for it to add a get_forecast action.

brittle shuttle
hollow crypt
#

Energy dashboard i mean

brittle shuttle
#

websocket

#

the communication between frontend and backend is much more extensive than just the limited set of actions that are exposed to users.

hollow crypt
#

I thought it used the action over websocket

brittle shuttle
#

Nah there's an api called energy/solar_forecast. It's not an action.

#

someone could make one though if they wanted.

#

back when this was designed we didn't have actions that could return data like we do now

hollow crypt
#

unfortunately then I don't see any simple way to get the forecast data out of the forecast.solar integration

#

maybe an action that calls the websocket API? ugly though

brittle shuttle
hollow crypt
brittle shuttle
#

oh that's an interesting angle

viscid iris
#

i have a working changeset on my machine with an implementation of a get_hourly_forecast action. showed the openweathermap integration and the forecast_solar integration to claude through copilot and it produced sth that worked and looked pretty good

#

but i'm not a python dev, so i dont have the toolchain local to make it past the git commit hooks. they should work in the devcontainer, but that runs quite slow because i instinctively mounted instead of cloning. but i'll have another look at it tomorrow, shouldnt be too hard to get it through and actually push the changes to my fork