foxess_em icon indicating copy to clipboard operation
foxess_em copied to clipboard

Charge current too low when battery is already charged

Open markmtb opened this issue 9 months ago • 0 comments

Version of the custom_component

1.9.1

Configuration

FoxESS - Modbus via TCP 1.11.1 HA version 2024.5.1 (Docker)

Describe the bug

The scenario described below has occurred a few times in the last month now. I suspect it'll happen more often as we move into spring and then summer.

My off-peak tariff currently ends at 0830 each morning, which is more than 3 hours after sunrise.

On sunny mornings, I am generating an excess of PV power by 0800 and it's all being fed into the grid, because foxess-em appears to have left the "max charging current" value at 1 A. The battery is already at the SoC that foxess-em is targetting for the start of my peak-rate tariff, and the charge period has been disabled by foxess-em. foxess-em will reset the maximum charge current to 35 A at 0830 each morning and this is when I stop feeding the grid and start charging the battery.

Once the targetted SoC has been reached and grid charging has been disabled, would it make sense to reset the maximum charge current then instead of waiting until the end of the offpeak tariff?

If I manually change the maximum charge current setting back to 35 A at 0800 then the excess starts charging the battery again, but I don't want to have to do this every morning.

markmtb avatar May 07 '24 16:05 markmtb