Bug or feature? Charging behavior when reaching the minimum SoC

[AlphaZuluNRW]

Hello everyone,

Over the winter, I set the storage systems so that the minimum state of charge (SoC) is 20%. So far, it has worked like this: the systems (2 x Hyper 2000 and 1 x SolarFlow 800 Pro) discharge to 20% and then switch to standby.

After that, the charge level kept decreasing until some batteries were down to 1%. Then, at some point, they would recharge until they reached 20% again. Currently, one Hyper 2000 system shows 4%, the other 7%. The 800 Pro behaved the same way. This can't be how it's supposed to work, because what's the point of the 20% minimum?

All three systems are charged via grid electricity when there is a surplus of solar power. Currently, this is naturally not the case because there is no surplus.

Today, a firmware update for the 800 Pro was released. At the same time, I also decided to update the integration to the latest version. Everything seems to be working as usual, but there is one change:

The 800 Pro, which was at about 10% at the time of the firmware update, immediately started charging up to 20%. I then lowered the limit to 10%, and lo and lo and behold, the charging process stopped and power was fed into the grid until presumably 10% had been reached. After that, I raised the limit back to 20%, and it charged to 20%. Later that day, the system discharged again to 19%. Just now, I happened to notice that it was charging again, and now it's showing 20%.

However, the two Hyper 2000s are still showing "almost empty."

Ultimately, the "new" behavior of the 800pro is exactly what was desired, because I only introduced the 20% limit for the winter, as I wanted to prevent the storage from being discharged below 10%, which it is currently doing anyway...

Is this an integration issue or a firmware problem?

[MacdiverOne]

It‘s the Firmware. My 3 SF800 Pro (2 x controlled by Zendure-HA, 1 x standalone without Zendure-HA-control) behave identical since the last update… Don‘t call it „quick-and-dirty-ZENKI-AI-winter-survival-fix“ 🙈

[Zen4712]

Recharging - this is a firmware "bug". ;-)
My Hypers started charging in the past at 0 % and 1 minute after. Did not like this beaviour, because its too late, at about 2,80V/cell.
They did not start charging just some percentage below the Hyper min limit, only at 0%.
But chargung SF800 via AC now just below its "min limit" is wasting money.

Please go to github: "/surfer1264/Zendure-Stuff" and read his wiki for the SoC at the lower right corner. => "zum Wiki AB2000"
=> The SoC value is not worth its value!
The SoC value is valid only if you have reached 100% at the same day before! For all days without 100% it is an estimate only.
"minVol" (resting state) is the only value which represents the correct SoC for the accumulator !

After that, the charge level kept decreasing until some batteries were down to 1%.

In addition to the SoC "failure" the power consumption of an AC device (Hyper/Solarflow Pro) itself is approximately 10W.
=> 24h*10W = 0,24kWh taken from solar power or the battery.

[AlphaZuluNRW]

Is it possible to trigger a charging process via Home Assistant based on the cell voltage? My two HyperX batteries are approaching 1% in one or two days.

For example, one could set the lower limit for SOC to 10%, but only start charging when the cell voltage reaches a certain value.

For the SF800 Pro, this would need to be configured so that the minimum SOC is set there, preventing it from interfering automatically.

[Zen4712]

Of course you can charge one Hyper manually via HA. You have to set up the Zendure Manager and you have to set the fuse group to "none" for one hyper, if you want to charge the other hyper only.
Look at //discussions/772 to the end of the post. Sepp2812 has developed a solution for this in HA via NodeRed after harrymayr implemented "PR #899".