search

victronenergy / dynamic-ess

MIT License
76 stars 5 forks source link

[Bug]: Table shows different trg SOC compared to graph V0.1.2 #59

Closed LecramRed closed 9 months ago

LecramRed commented 9 months ago

Contact Details

info@redupsell.nl

VRM / Site iD

345657

Country / region

Netherlands (nl)

B max

24

TB max

No response

FB max

No response

TG max

No response

FG max

No response

Battery costs

No response

Buy price

No response

Sell price

No response

feed-in possible

None

feed-in possible

None

What happened?

The table says at 12 and 1AM 13%. The graph shows 33% at 12AM and 34% at 1AM.

image

image

Relevant log output

No response

Screenshots

![DESCRIPTION](LINK.png)
SimonYoungtree commented 9 months ago

I have the same problem. Also the order 12AM (This is mid-day) and then 1AM (correct). This probably will mean that the system will start dumping to the grid at mid night, while it should not do anything (It should stay at ~42%)

Screenshot 2023-09-13 220401 Screenshot 2023-09-13 220707

dirkjanfaber commented 9 months ago

Good find. This is a bug in the table. The actual schedule does contain the values that are in the graph. (You can check that by logging in via ssh and starting dbus-spy to check the inserted schedule under com.victronenergy.settings Settings/DynamicEss/Schedule/*/Soc).

This will be fixed with the next update.

Edit: did not mean to close the issue (as it has not been resolved yet); pressed the wrong button.

LecramRed commented 9 months ago

The graph is a better scheme than the table. So it is good that the graph is the right one.

LecramRed commented 9 months ago

It is now 00.30 and unfortunately, dess took the table data to discharge to 13%. So not the graph, but the table was leading. The graphs are still showing 48 hrs, despite a new day. The current day is the data from yesterday. It seems that it relies on yesterday's data, rather than today's data. So something is going wrong here.

LecramRed commented 9 months ago

The context flow dess still contains 48 hrs data at 1.08 am

LecramRed commented 9 months ago

I just deleted flow.dess manually, disabled and enabled the tab, and it is 24 hrs of data again. So it still does not refresh the old flow.dess automatically

dirkjanfaber commented 9 months ago

Thanks for staying up that late. I probably need to that for the next few days too to make sure that I can pinpoint where exactly it goes wrong. On another site I noticed it going wrong from midnight until 6 minutes after midnight. Then the schedule was 24 hours again and everything worked as it should.

dirkjanfaber commented 9 months ago

This should be fixed by switching to version 0.1.3. Note that you also need to re-import the flow as the code of the prepare dess variables function changed.