Flix6x
commented
2 days ago If you want the scheduler to take into account the opportunity of buying less from the grid, shouldn't you be telling the scheduler that it should take into account the forecasted inflexible consumption/production happening on your grid connection? That is, I was expecting to see the --inflexible-device-sensor option (like in Toy example II) set to the sensor ID that records the forecasted inflexible power on the grid connection.
Ragnar-the-mighty
The storage schedule can not optimize for self use. I.e charge from battery instead or buying from grid and discharge for self use instead of selling to the grid. Here is an example showing that the storage schedule does not come up with the most economical schedule. Sorry, this is a long explanation.
Assumption We have a price difference between buy and sell prices We have local production We have have a battery We have a forecast for the grid connection.
Modify toy example 2 to show the issue Start with the toys account as described in the documentation Toy example Add sensors Buy energy price (we use the existing price sensor for sell price)
Grid connection
Load data, sell prices
Load Buy prices:
Use your buy sensor id in the command below
Load Grid forecast
Use your own grid sensor id in the command below
Make a schedule, use your buy sensor id in the command below
You should now have a schedule like this
Take a look at discharge at 02:00 notice that the buy prices at 01:00 and 03:00 are higher than the sell price at 02:00. Discharging the battery at 01:00 and 03:00 hours so we avoid buying is more economical than to discharge everything at 02:00. Result from current scheduler
The optimal schedule result should be
The same is true for the charging time period at 12:00. The optimal schedule should spread out the charging to take advantage of the solar production and avoid selling solar energy at low prices.