Followed the energy setup ‘wizard’ after update to 2021.8.0. Got everything sorted OK, except the solar data doesn’t seem to be fully working. The data is present in the energy dashboard’s top chart (and production values match the data from the system itself), but not the second one.
I’m wondering if it’s because of another error I’m seeing from the forecast.solar integration:
Retrying setup: Rate limit for API calls reached. (error None)
Appreciate any guidance or pointers.
I have the same issue. I am based in Sydney.
When I try to call their API directly I get the following reponse:
$ curl https://api.forecast.solar/estimate/-33.6/151.1/25/25/5000
{"result":null,"message":{"code":5,"type":"error","text":"No solar data available for location -33.6, 151.1 - Please check your location on https://re.jrc.ec.europa.eu/pvg_tools/en/#MR","info":null,"ratelimit":{"period":3600,"limit":12,"remaining":11}}}
And when I then look at that EU website mentioned in the response, the unfortunate truth may be that there is simply no data available on this end of the continent:
yup I have been getting this too - in Brisbane - the forecast.solar website shows prediciton locations on the work map for Aus. I had similar problems in the July 21 release when the integration was released.
That’s great to hear - do you have a link to that workmap page? I found an issue tracker, but it is short and doesn’t mention coverage.
I think that there is more to this than lack of coverage, I am also in Sydney. I subscribed to the Forcast.Solar Personal Service to get an api key (it’s a 14 day trial so easily cancelled). I ran the same curl command but inserted the api key and this was returned: -
{"result":{"watts":[],"watt_hours":[],"watt_hours_day":[]},"message":{"code":0,"type":"success","text":"","info":{"latitude":-33.6,"longitude":151.1,"place":"2159 Berrilee, New South Wales, AU","timezone":"Australia/Sydney"},"ratelimit":{"period":3600,"limit":60,"remaining":31}}}
I still have an error message in the integration section of HA though this time it says: -
Retrying setup: 'list' object has no attribute 'items'
Hmm, not sure where that got me really.
Problem is the limit of request in time. doing the same request by nodered you will see taht after 11 times, in the 12 system blocks. 12 in 3600
Hi,
had a Working Integration with this with two Roofs (East and West). After the last Update i have the same error. I am in Germany.
Greetings, Jochen
Hi, I got the same error and I’m wondering if can we use a different API with the new Energy Management dashboard, such as solcast api or pvgis api they gives better prediction.
Here’s the error i got from forecast.solar :
Logger: homeassistant.components.forecast_solar
Source: helpers/update_coordinator.py:147
Integration: Forecast.Solar (documentation, issues)
First occurred: 11:04:23 (7 occurrences)
Last logged: 11:08:20
Unexpected error fetching forecast_solar data: Rate limit for API calls reached. (error None)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 147, in _async_update_data
return await self.update_method()
File "/usr/local/lib/python3.9/site-packages/forecast_solar/__init__.py", line 138, in estimate
data = await self._request(
File "/usr/local/lib/python3.9/site-packages/forecast_solar/__init__.py", line 118, in _request
raise ForecastSolarRatelimit(data["message"])
forecast_solar.exceptions.ForecastSolarRatelimit: Rate limit for API calls reached. (error None)
Having the same error, I also use the Solcast, but what makes the forecast.solar so nice is the highest Peak sensor, which I’m using in my automations.