Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong forecast/switching due to "slow" charging battery which can't absorve the pv-energy until sunset #56

Open
fabi9163 opened this issue Apr 1, 2024 · 1 comment

Comments

@fabi9163
Copy link

fabi9163 commented Apr 1, 2024

Great Script thanks a lot!
Seems there is one problem I'm not able to solve with it:

Problem

My Battery can only charge with 1,7kw, after 50% only 900W and runs multiple "battery tests" in which it doesn't charge at all (...don't ask->Senec, it's ...dahh). My PV-Power is >8kwp.

(My example is extreme, but I thing many people have more PV-Power than the battery can handle)

image

The result is that the Script thinks there's enough energy (forecast) to charge the battery later and enables additionally consumers. When it decides to force charging there's not enough time to charge the battery anymore because of the slow charging rate while theoretically there would be enough energy available.

Also in "force charging"-State much power goes to the grid cause the battery can only take <1,7kw

Idea:

Nice would be additional input-values like

  • "max. charging in kw" and
  • "actual charging power"

and some logic like:

  • independent of "force battery"-state: If actual_charging_power reaches "max. charging in kw", consumers could be enabled, right?
  • force battery-> should be triggered earlier. Maybe calculate the time between now and sunset * "max. charging in kw". If smaller than actual pv-forecast it should be another criteria to force charge, right?

Maybe someone have the same problems like me, has some other ideas or can optimize the script. Would be great :-)
If I have understand something wrong, please let me know.

Thanks!

@stefan73
Copy link
Contributor

I get your point. And i struggle to have a reasonable algo idea. The current code just checks whether the remaining predicted pv power production is larger than the missing power to reach the target SOC.
In the automation we do not know the concretely predicted pv production curve for the remainder of the day. One would have to take this curve and check how long those 1.7kW (plus maybe a margin) might still be produced as excess power.
Just assuming that there is time till sunset, will not be correct looking at typical pv production curves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants