You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today DPL started discharging though the start threshold wasn't met (by far) yet. I had no other way to stop it then by increasing the stop voltage above the current voltage and then again put the old value back again.
I only recently switched from SoC start stop to voltage based stop. With SoC I didn't have an issue almost a year long, it never started discharging before the SoC start value was reached.
Did anybody observe this behavior as well?
I had the Start Threshold at 55.5V (yeah, wanted to fully charge once) and stop at 51.2V. The value was at that moment 51.46V. No way somehow 4Vs more were reported by the inverter.
To Reproduce Bug
30-1-25 Don't know yet, it just happened out of nowhere.
31-1-25 Again it started just by itself... which way can I log such that I can find out why it starts?
Expected Behavior
Discharging starts only when the voltage threshold has been reached.
Install Method
Pre-Compiled binary from GitHub releases
What git-hash/version of OpenDTU-OnBattery?
205.01.23
What firmware variant (PIO Environment)?
generic_esp32s3_usb
Relevant log/trace output
Anything else?
I'm curious whether anyone else also observed this issue, probably then we'll have a chance chasing the cause down.
Please confirm the following
I believe this issue is a bug that affects all users of OpenDTU-OnBattery, not something specific to my installation.
I have already searched for relevant existing issues and discussions before opening this report.
I have updated the title field above with a concise description.
I have double checked that my inverter does not contain a W in the model name (like HMS-xxxW) as they are not supported.
The text was updated successfully, but these errors were encountered:
I have "Use battery at night even if only partially charged" ... so probably it's a feature, not a bug, right?
Probably it's a good idea to have a "I" with the remark: "Discharging starts though Start Threshold has not been reached, but stops at the Stop Threshold".
I had interpreted as "use the battery at night as well".
Yeah... So we'll keep this open and add a tooltip as you suggested, with a similar text. I will adjust the issue title accordingly.
schlimmchen
changed the title
[Bug] DPL starts discharging before Voltage Start Threshold has been met
Add tooltip for "Use battery at night even if only partially charged" to further reduce confusion
Feb 1, 2025
What happened?
Today DPL started discharging though the start threshold wasn't met (by far) yet. I had no other way to stop it then by increasing the stop voltage above the current voltage and then again put the old value back again.
I only recently switched from SoC start stop to voltage based stop. With SoC I didn't have an issue almost a year long, it never started discharging before the SoC start value was reached.
Did anybody observe this behavior as well?
I had the Start Threshold at 55.5V (yeah, wanted to fully charge once) and stop at 51.2V. The value was at that moment 51.46V. No way somehow 4Vs more were reported by the inverter.
To Reproduce Bug
30-1-25 Don't know yet, it just happened out of nowhere.
31-1-25 Again it started just by itself... which way can I log such that I can find out why it starts?
Expected Behavior
Discharging starts only when the voltage threshold has been reached.
Install Method
Pre-Compiled binary from GitHub releases
What git-hash/version of OpenDTU-OnBattery?
205.01.23
What firmware variant (PIO Environment)?
generic_esp32s3_usb
Relevant log/trace output
Anything else?
I'm curious whether anyone else also observed this issue, probably then we'll have a chance chasing the cause down.
Please confirm the following
The text was updated successfully, but these errors were encountered: