Thanks for the hint. These parameters are really new. I performed calls with each of them and checked the results.
time & time-tz
are just delivering timestamps in different formats. This shouldn’t be changed by the user. The binding is handling current timestamps in the correct way and it shall not guess around which format is delivered
Just delivering zero values before and after sunset / sundawn. Binding is already handling this properly
For each plane you need to specify Kilowatt Peak kwp in configuration. Your inverter can’t handle that? Then please reduce what your inverter can handle or am I wrong?
This will jeopardize the calculated values. I you start forecast from e.g. 12:00 the today channel, which shall deliver the total daily forecast, is missing the morning hours.
This parameter is valid! It really delivers different forecast values. Then you would have the possibility to tweak these parameters to get best possible forecast for your system.
My proposal is to add 2 config parameters for morning / evening damping.
The other options will result in errors in the binding calculations plus they don’t have any effect on the forecast values.
Yes, the damping parameter(s) are the most interesting ones. The inverter parameter is clipping the peak energy to the max inverter power. I have confirmed that the estimated peak values are reduced to the inverter value. So it might be useful for specific setups.
first of all, thanks for your work at this and also your other bindings.
As Solcast has daily rate limits for the API, it is required to set the refresh interval to 120 min for two sites, which is quite a long time.
I just had a idea how the limited number of API requests might be used more efficient: don’t or far less request the API at night (at least one request during night to get todays forecast would be required) and use those „saved“ requests to refresh more often during day.
Please let me know what you think about that idea.
120 mins should be fine, remember it’s a free service, if you want more, go pay for it.
Real weather doesn’t change drastically within this time (or that’s in the forecast already), though so the benefit is rather theory than real.
That might be true, if it is, forget about that idea. Then forecast updates every 2 hours are good.
I don’t know if much shorter periods would be sensible as the forecast provider might not update the forecast in this period.
This - of course - was to “spend” the free api calls at day time only
Not sure though, if this really improved the prediction for a certain point in time. But if there is any value in increasing the update frequency at day time, this could be an option…
I’m in the process of implementing Solcast.
Solcast offers the service to improve the prediction through a back channel (powerItem).
Unfortunately, I can’t get any further with the configuration because I don’t know how to specify the “powerItem” parameter:
powerItem needs to be configured with the item name, which reports the power value for this particular sc-plane - in your case homeSouth. If you’ve only one plane as configured above the inverter value is fine.
powerUnit can be set to auto-detect if a valid QuantityType is delivered. Otherwise set it to kW for Kilowatt or W for Watt. Note: The W is upper case and your config contains kw - both lower case.
Switch on DEBUG level and you’ll see the calculations each 15 minutes in the traces.
I would say there is nothing wrong. It is a prediction based on different data. So this means it is not 100 % accurate, also it is not real time. There is scatter to the data of your plant.
Or what did you expect?
Select the Item in the Web UI, then under the metadata section, Add Metadata, select State Description.
A popup will open, this allows you to configure the state description metadata. Fill %.2f W into the pattern field, and save it.
Explanation of %.2f W:
%2.f tells openHAB to display the state as a floating point number with two digits after the point
Adding W as unit makes openHAB convert the state from kW to W
Check first the response in Channel raw. You’ll find it in fs-plane thing after activating Show advanced checkbox. Here you’ll see the direct json response from forecast.solar. Cross check the time the first values are reported.