Forecast.solar integration - make the PV power and energy forecast production datapoints accessible

Hello Everybody,

It would be nice if via the Forecast.solar integration we could somehow (maybe as attributes of existing sensors?) have access to the granular data made available through the API calls, Public subscription at least (as its features are in common to any subscription plans), that would cover the forecast datapoints for:

  • watts
  • watt_hour
  • watt_hour_period
  • watt_hour_day

These are available through the API call but not via the integration (which is great as fully integrated with the Energy dashboard).
Making these datapoints available would make a big difference as in this way you are able to optimize the workflows and rely on a single process/access point to get the data and any other service can rely on what is retrieved via the integration, with no need to duplicate requests and use resources.
Below an example of what you get via the API call, Public plan.
Thank you!

curl https://api.forecast.solar/estimate/:lat/:lon/:dec/:az/:kwp
{
   "result":{
      "watts":{
         "2023-10-03 07:23:46":0,
         "2023-10-03 08:00:00":531,
         "2023-10-03 09:00:00":1127,
         "2023-10-03 10:00:00":2327,
         "2023-10-03 11:00:00":3359,
         "2023-10-03 12:00:00":4030,
         "2023-10-03 13:00:00":4232,
         "2023-10-03 14:00:00":4126,
         "2023-10-03 15:00:00":3850,
         "2023-10-03 16:00:00":2967,
         "2023-10-03 17:00:00":1756,
         "2023-10-03 18:00:00":754,
         "2023-10-03 19:00:00":330,
         "2023-10-03 19:01:38":0,
         "2023-10-04 07:25:00":0,
         "2023-10-04 08:00:00":502,
         "2023-10-04 09:00:00":1302,
         "2023-10-04 10:00:00":2268,
         "2023-10-04 11:00:00":3131,
         "2023-10-04 12:00:00":3778,
         "2023-10-04 13:00:00":4178,
         "2023-10-04 14:00:00":4030,
         "2023-10-04 15:00:00":3748,
         "2023-10-04 16:00:00":2857,
         "2023-10-04 17:00:00":1690,
         "2023-10-04 18:00:00":714,
         "2023-10-04 18:59:47":0
      },
      "watt_hours_period":{
         "2023-10-03 07:23:46":0,
         "2023-10-03 08:00:00":160,
         "2023-10-03 09:00:00":829,
         "2023-10-03 10:00:00":1727,
         "2023-10-03 11:00:00":2843,
         "2023-10-03 12:00:00":3695,
         "2023-10-03 13:00:00":4131,
         "2023-10-03 14:00:00":4179,
         "2023-10-03 15:00:00":3988,
         "2023-10-03 16:00:00":3409,
         "2023-10-03 17:00:00":2362,
         "2023-10-03 18:00:00":1255,
         "2023-10-03 19:00:00":542,
         "2023-10-03 19:01:38":4,
         "2023-10-04 07:25:00":0,
         "2023-10-04 08:00:00":146,
         "2023-10-04 09:00:00":902,
         "2023-10-04 10:00:00":1785,
         "2023-10-04 11:00:00":2700,
         "2023-10-04 12:00:00":3455,
         "2023-10-04 13:00:00":3978,
         "2023-10-04 14:00:00":4104,
         "2023-10-04 15:00:00":3889,
         "2023-10-04 16:00:00":3303,
         "2023-10-04 17:00:00":2274,
         "2023-10-04 18:00:00":1202,
         "2023-10-04 18:59:47":356
      },
      "watt_hours":{
         "2023-10-03 07:23:46":0,
         "2023-10-03 08:00:00":160,
         "2023-10-03 09:00:00":989,
         "2023-10-03 10:00:00":2716,
         "2023-10-03 11:00:00":5559,
         "2023-10-03 12:00:00":9254,
         "2023-10-03 13:00:00":13385,
         "2023-10-03 14:00:00":17564,
         "2023-10-03 15:00:00":21552,
         "2023-10-03 16:00:00":24961,
         "2023-10-03 17:00:00":27323,
         "2023-10-03 18:00:00":28578,
         "2023-10-03 19:00:00":29120,
         "2023-10-03 19:01:38":29124,
         "2023-10-04 07:25:00":0,
         "2023-10-04 08:00:00":146,
         "2023-10-04 09:00:00":1048,
         "2023-10-04 10:00:00":2833,
         "2023-10-04 11:00:00":5533,
         "2023-10-04 12:00:00":8988,
         "2023-10-04 13:00:00":12966,
         "2023-10-04 14:00:00":17070,
         "2023-10-04 15:00:00":20959,
         "2023-10-04 16:00:00":24262,
         "2023-10-04 17:00:00":26536,
         "2023-10-04 18:00:00":27738,
         "2023-10-04 18:59:47":28094
      },
      "watt_hours_day":{
         "2023-10-03":29124,
         "2023-10-04":28094
      }
   },
   "message":{
      "code":0,
      "type":"success",
      "text":"",
      "pid":"xxxxxx",
      "info":{
         "latitude":degrees_here,
         "longitude":degrees_here,
         "distance":0,
         "place":"address_here",
         "timezone":"Europe/Rome",
         "time":"2023-10-03T14:26:42+02:00",
         "time_utc":"2023-10-03T12:26:42+00:00"
      },
      "ratelimit":{
         "period":3600,
         "limit":12,
         "remaining":2
      }
   }
}

Thank you but there are some aspects that make some people (like me) prefer to use Forecast.solar.
Unluckily Solcast would not work as a workaround.

Just out of curiosity, what makes you prefer Forecast.solar? I use Solcast and haven’t used Forecast.solar, so I wouldn’t know.

The limited number of API calls per day for new users; this also led the developer to modify the custom component and remove the automatic data pull.
Other reasons may be HA out-of-the-box support, forecast precision, geographic data availability, integration with other “services” and so on.

2 Likes

Sorry , i didn’t understand that it already was an “available” integration in HA, guess it makes a FR’s more appropriate , than just another Custom Component :slight_smile:

1 Like