[VRM - Bug]: ‘course-correction’ logic somewhere within the hour

[pokeplayer2]

Contact Details

No response

VRM portal ID

b827eb6ff17f

Country / region

Germany (de)

B max

26

TB max

6.5

FB max

7

TG max

30

FG max

30

Battery costs

0,02

Buy price

p+0.217+0.0161

Sell price

0,115

feed-in possible

yes

feed-in control

yes

What happened?

Battery discharge only with 2,5 kW if discharge is allowed, why we do not discharge with the need power? At this moment was 5,5KW needed and the rest comes from grid. :-( Grid is mostly expensive here and when the battery has enough power, why should we limit the discharge power?

When did it happen?

14/10/2023 09:50

Screenshots

![DESCRIPTION](LINK.png)

[pokeplayer2]

[KajLehtinen]

The way Dynamic ESS works currently is that it sets a target SoC and aims for that during the current hour, if the consumption is more than estimated it will consume from grid, and if its lower it will sell back to grid if allowed.

/Kaj

[pokeplayer2]

I don't like it as it end in a situation where you buy power at totally wrong time or sell to grid, which I only like to do when the battery is 100% full. At that moment was the battery ~ 83 %, no need to buy power from grid. A half-hourly recalculation can compensate the inaccuracy of the system and if electricity is cheap on the stock exchange, the battery should be charged to 100% if the solar no in the position to fill the battery.

[pokeplayer2]

and again power from grid and battery over 80%

[pokeplayer2]

23:00 - 00:00 was grid used ... 15/10/2023

[dirkjanfaber]

There was an inaccuracy in forecasts, so in hindsight the battery could have discharged more than it did. Note that hindsight clarity is always easy. Determining what to do based on the knowledge of the present is less simple. At the moment we don't offer ‘course-correction’ logic somewhere within the hour. We are researching if there is a good way to do this, but we decided to put it to lower priority to focus on more pressing matters first. I don't mind leaving this issue open, but it won't get much further attention for a while.

[pokeplayer2]

I have no problem with the long runner, ;-) important is that the solution is in future more agile and the limits have to be removed and minimum for charging.

[dirkjanfaber]

With the 0.1.10 version we've introduced restrictions that are followed during the scheduled hour. See the restrictions section in the README.

At the moment the logic only sets the 2 or 0 value, If that is not enough, you can add some extra logic to the flow by injecting the needed restriction, based on the information available.

[dirkjanfaber]

Can you try again with running version 0.0.14 with firmware 3.30~7 (or above when released)? This adds extra strategies for not blaming the wrong forecasts on the grid all of the time.

Closing this issue. Please re-open a new issue if the problem persists.