pv forecast with scrapper and generic pv panel and inverter

[scruysberghs]

@davidusb-geek
For my use case(s) and I guess for many users it would be nice to use scrapper (pvlib + ClearOutside) PV predictions in emhass but instead of having to find an exact (or close enough) matching panel and inverter type in the pvlib database just use a generic panel and inverter size like they do in solcast and solar.forecast and in the home assistant energy dashboard. I see that pvlib supports this notion of a generic system using pvwatts. Is this something you have looked at before? Would you accept a PR that allows sizes in Watt instead of the text string with the exact models?

[davidusb-geek]

Hi, this can be an option. I'm aware of the pvwatts possibility.
Yes of course, we can accept a PR for this. It will be a simpler way to setup. We can keep the advanced setup and propose a simplified setup with your proposition

[scruysberghs]

I left the path to use pvlib from within emhass and have now switched to using /~https://github.com/rany2/ha-open-meteo-solar-forecast integration from within Home Assistant.
The results are very accurate, you can setup multiple strings/inverters and add them together, and also use the same values in the energy dashboard in Home Assistant. No problems with limited api calls and having to setup solar prediction for HA and emhass separately ...

Template to pass the next pred_horizon number of half hour blocks to the mpc (or day ahead) optimizer:

{% set now = now() %}
              {% set today_data = state_attr('sensor.energy_production_today', 'watts') %}
              {% set tomorrow_data = state_attr('sensor.energy_production_tomorrow', 'watts') %}
              {% set combined_data = 
                  (today_data | dictsort | selectattr('0', '>=', now.isoformat()) | list) 
                  +
                  (tomorrow_data | dictsort | list)
              %}
              {% set sorted_data = combined_data | sort(attribute='0') %}
              {% set next_24h = sorted_data | selectattr('0', '<', (now + timedelta(hours=24)).isoformat()) | list %}
              "pv_power_forecast": [{{states('sensor.sec_pac_solar') | int(0)}},{% for i in range(2, pred_horizon*2, 2) %}{{ ((next_24h[i][1] + next_24h[i + 1][1]) / 2) | round(0) }}{{ ", " if not loop.last else "" }}{% endfor %}],

[davidusb-geek]

Very nice solution using that custom integration

[scruysberghs]

is see openmeteo has made it into emhass... great.
I do feel that it is a little wastefull to pull solar predictions in emhass while almost everyone is also pulling in the same solar predictions into Home Assistant directly for the energy dashboard. I always try to avoid pulling the same remote datasource twice. I guess passing solar predictions from HA as runtime parameters might be too far fetched for most users but maybe a weather_forecast_method called "home assistant" that uses data from the sensor(s) created by the open meteo solar integration in HA that are set in the energy dashboard?
Or the other way around, and have emhass pull the openweather api with the inverters and strings that are defined in the config, but post the attibutes in sesnor.p_pv_forecast in a way that the sensor can also be used in the energy dashboard in Home Assistant?