-
Notifications
You must be signed in to change notification settings - Fork 67
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
[Request] AC charger: Implement DC/Battery stop SoC #754
Comments
Quick question for my understanding: What are you using for charging? |
There is no "stop charging". There is only "start discharging", or in other words "start using the battery for energy production". I don't understand what you are asking for. What should happen if the newly proposed "Battery SoC - Stop charging" threshold is reached? |
Is this about the Huawei charger? |
Yes, after reaching the "Battery SoC - Stop charging" threshold it should stop charging... Currently there are two SoC values: stop discharge, start again discharging. For example 15% (stop) and after reaching 20% allow discharging again. The third value would be the upper level to stop charging, like 90% or 95%. Yes my setup is a HM, Huawei, Pylontech setup. |
I think this is completed with #848, which will be included in the next release. Please re-open this issue if I got it wrong. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns. |
Is your feature request related to a problem? Please describe.
Currently stopping of the charging is defined by voltage. As both the start and stop threshold conditions are defined in SoC %s, adding a target to stop charging would make sense.
Describe the solution you'd like
Adding Battery SoC - Stop charging.
To avoid confusion: best rename
a) Battery SoC Stop threshold to Battery SoC - Stop discharging
b) Battery SoC - Start charging to Battery SoC - Allow discharging
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: