Skip to content

Commit

Permalink
Update forecasts.md
Browse files Browse the repository at this point in the history
Not sure how solar.forecast is implemented in EMHASS, but actually the free tier is 12 API calls per hour, not per day.
So, depending on the implementation, feel free to reject this PR.
Cheers!
  • Loading branch information
g1za authored May 16, 2024
1 parent 0fbf9a6 commit c2cdce5
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/forecasts.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ For example:
curl -i -H "Content-Type:application/json" -X POST -d '{"solcast_rooftop_id":"<your_system_id>","solcast_api_key":"<your_secret_api_key>"}' http://localhost:5000/action/dayahead-optim
```

A third method uses the Solar.Forecast service. You will need to set `method=solar.forecast` and use just one parameter `solar_forecast_kwp` (the PV peak installed power in kW) that should be passed at runtime. This will be using the free public Solar.Forecast account with 12 API requests per day and 1h data resolution. As with SolCast, there are paid account services that may results in better forecasts.
A third method uses the Solar.Forecast service. You will need to set `method=solar.forecast` and use just one parameter `solar_forecast_kwp` (the PV peak installed power in kW) that should be passed at runtime. This will be using the free public Solar.Forecast account with 12 API requests per hour, per IP, and 1h data resolution. As with SolCast, there are paid account services that may results in better forecasts.

For example, for a 5 kWp installation:
```
Expand Down

0 comments on commit c2cdce5

Please sign in to comment.