search

victronenergy / dynamic-ess

MIT License
76 stars 5 forks source link

[Bug]: Could not create a feasible schedule #32

Closed andressade closed 9 months ago

andressade commented 11 months ago

Contact Details

No response

VRM / Site iD

285851

Country / region

Estonia (ee)

B max

7.5

TB max

2

FB max

2

TG max

0.72

FG max

2

Battery costs

0.04

Buy price

(p+0.0044+0.0394)*1.2

Sell price

p-0.0075

feed-in possible

yes

feed-in possible

yes

What happened?

After enabling Dynamic ESS node the error "Could not create a feasible schedule" will be displayed. Api info output shows http 500 "Internal Server Error"

Relevant log output

No response

Screenshots

andressade commented 11 months ago
image
dirkjanfaber commented 11 months ago

Have you set the location in the VRM for the site?

andressade commented 11 months ago

Yes, I have indeed set the location in the VRM for the site

khostri commented 11 months ago

Last time I got this message I have noticed that accidentally in configuration node there was one number deleted from siteID. So site Id was incorrect (probably as I have written comment.)

andressade commented 11 months ago

SiteID seems right to me

image
Mableeker commented 11 months ago

Same sort of situation here, small difference that in node-red flow it shows ok, but in the dashboard is says 'could not create a feasible schedule', although the graphs show a good schedule but the multiplus doesn't obey the schedule. Settings are not set...image

mrstackit commented 11 months ago

I have the same issue in the flow and ui shows: Could not create a feasible schedule. I have do the initial Setup today and after a few hours this problem.

I have test it again and i can see it runs a few hours without error and setting a schedule but then the error ist there again.

mpvader commented 11 months ago

We're looking into this (Ali is)

PoolsideKelbi commented 11 months ago

Hey @mrstackit, thanks for reporting this error.

This issue should be solved now. The low value of TG_max made it difficult for Dynamic ESS to schedule the rest of the day. But now it should be able to deal with values such as these.

Please give it a check and in the case that it works, feel free to close the issue :)

mrstackit commented 11 months ago

Hey @PoolsideKelbi thanks for your reaction,

In the flow everything looks fine in the UI (dashboard the message is still there) even after restarting the flow. I activated the flow again at the weekend and just let it run. However, since 1 p.m. today, I have noticed strange behavior. The day was well planned until 1 p.m. Then it was somehow rescheduled and it suddenly started charging at 25 cents kWh, which made no sense. Also visible in the screenshots. No loading was planned there before 1 p.m. At 25 cents kWh it makes no sense to charge the battery if the most expensive price is around 30 cents. I am not the first person to report the bug, my settings in the flow are different:

Country: Germany B max: 2.4 TB max: 1.2 FB max: 1.2 TG max: 0 FG max: 10

Should I open a new bug for this?

grafik grafik

mrstackit commented 11 months ago

Today again at 2pm fg_max is set at price 0,24 € kWh at SOC is on 90%. Thats bad. Prices in the evening max 0,32 € for two hours. Can you tell me why he suddenly sets fg_max even though it's not worth it? How is it calculated when the battery is charged from the grid?

dirkjanfaber commented 9 months ago

We've just published a new release, that is more incorporated into the Venus OS and follows the target SOC instead of setting a setpoint and a less than ideal way of idling the battery.

As this uses a different approach, you will need to:

More information can be found in the release notes and README.md