pirate-weather-ha: Missing properties in forecast + new weather forecasting entities

*NB: this is not really a pirate-weather-ha issue but just wanted to start the discussion here 😃

Let me start off by saying I really like pirate-weather! It has both great spatial- and temporal resolution, which is something I need for an integration I am working on. I am building a ‘local’ alternative to solcast / forecast.solar for forecasting solar PV power/energy production and I rely on accurate weather forecasts, mainly cloud cover and temperature.

I wanted to share something which will probably be useful information for the pirate-weather integration, the weather forecasting system in HA is being revamped: https://github.com/home-assistant/core/pull/75219. Here is a preview of what it looks like on the frontend side: https://github.com/home-assistant/frontend/pull/15028

My biggest problem at the moment is that there is no cloud_cover property in the weather forecast field. I have started a discussion here: https://github.com/home-assistant/architecture/discussions/905 but it seems to get no traction. My question is, would you be able to add the cloud_cover property even though the architecture discussion has not reached any kind of agreement? I don’t think it would present any major issues since this is not a core integration, but you would slightly deviate from the spec. It would be awesome to point future users of my integration to your weather integration since it will have the required cloud_cover property.

Just FYI, my alternatives are to use the weather entity state (cloudy, clear, etc.) and convert that to a cloud cover percentage, or to setup a secondary sensor entity that holds the cloud cover information. For example with pirate-weather, I could do:

sensor:
  - platform: pirateweather
    api_key: <APIKEY>
    scan_interval: '00:15:00'
    monitored_conditions:
      - cloud_cover

For the best user experience I would ofcourse highly prefer to have all this information in a single weather entity which users can configure.

Anyway, sorry for the wall of text but thanks again for the great integration!