OKā¦so I posted my message, had a shower, and when I came back it had magically sorted itself out - all the data is there now and everything is nicely added up! So very cool.
Butā¦this morning my forecast was goneā¦and it turns out that I have exhausted all of my API calls alreadyā¦in one hour it went for 14 remaining to 0ā¦so how do I limit the calls? One per hour would be ampleā¦and since there are two account counting independently that should ensure I never run outā¦
Is it just me or has the Solcast forecast disappeared with the latest beta of HA? If I go to configure the Energy dashboard and click on the Forecast Production button next to my panels, it now offers me only the opportunity to manually configure parameters for a Forecast.Solar forecast and Solcast is no longer visible. Iāve removed and re-added the Solcast integration, but no effect.
Restarted multiple times. Deleted, re-downloaded, re-added Solcast. Still doesnāt show up when trying to add a forecast to panels in the energy dashboard.
So forecast is working better for meā¦but now I have a couple of questions:
Controlling polling
It looks like Iām polling when it is dark and the panels have already stopped producingā¦it doesnāt poll in the dead of night (much) but is there a way to set start and end times for polling?
API call consumption
Per poll it sometimes consumes 4 API callsā¦and other times it seems to chew through 10ā¦my poll count from yesterday (per interval) comes back as:
46, 42, 34, 30, 26, 18, 14, 10, 2, -6
Meaning the API calls per hour were:
4, 4, 8, 4, 4, 8, 4, 4, 8, 8
A restart of HA could account for an extra polling cycle but I didnāt restart it that oftenā¦?
API counts for multiple accounts
I have two accounts with SolCast as I have two systems, each with two strings facing N/E and N/Wā¦which means that I have 50 API calls per account or a total of 100 calls. The API count tracker doesnāt consider this when ticking off the remaining calls so I get negative API counts remaining once I get past the halfway point (I start at 50, and end on -40ish). This is a minor bug that should be easy to fix by setting the API call starting value equal to the 50 x the number of accounts provided.
Logger: custom_components.solcast_solar.solcastapi
Source: custom_components/solcast_solar/solcastapi.py:127
Integration: Solcast PV Forecast (documentation, issues)
First occurred: 11:20:57 AM (1 occurrences)
Last logged: 11:20:57 AM
Solcast http_data error: Traceback (most recent call last): File "/config/custom_components/solcast_solar/solcastapi.py", line 386, in http_data found_data = [d for d in _data if d['period_end'] == item['period_end']] File "/config/custom_components/solcast_solar/solcastapi.py", line 386, in <listcomp> found_data = [d for d in _data if d['period_end'] == item['period_end']] KeyError: 'period_end'
Hi @gerasalus - Would it be possible to see your completed code for this Actual vs Forecasted graph? Have been trying to get mine working, but having some issues.
Iāve had issues with zero values a few times since id updated to the 3.0.30 update (was was using 3.0.3 beta prior). Sometimes it clears if you go into the following starting at the main menu on the side:
settings/devices and services
then scroll to the solecist integration.
Click on the three little dots, and then click reload.
@anon7821378 thanks for including the detailed forecasts at 30 minute resolution, I had a separate REST call which I no longer need to use and will reduce my API calls. Thanks.
Upstream (Solcast) seem to provide their 30 minute forecasts in kW - forecast power during the period.
Your integration seems to be providing the 30 minute pv_forecasts in kWh (which is half the kW value as it is only for half an hour) - forecast energy during the period
Both of course are correct, just different ways of measuring.
I just wanted to make sure I understood your integration.
Thanks oziee for the great integration and further support. The automation script here didnāt work for me. Trying a bit further I landed on updating the action as follows:
alias: Solcast_update
description: New API call Solcast
trigger:
- platform: time_pattern
minutes: "0"
seconds: "0"
condition:
- condition: sun
before: sunset
after: sunrise
action:
- service: solcast_solar.update_forecasts
data: {}
mode: single
And the last pulled is Yesterday, which is not true as I use automation to call Solcast forecast update service. You see API used is 5, pulled every hour since sunrise, until sunset.
18 of my 22 panels face north (81%).
The other 2 pairs face east and west.
I only have 1 rooftop site setup in solcast and that does the job.
Here is my solcast settings