Is it safe/sensible to update the battery SoC target via a HA automation to control charge/discharge?

[amkurtis]

I'd like to set a HA automation to set the SoC target (ie. 100% or 25% as charge vs discharge respectively) by updating the current timeslots SoC based on grid export.

Is it safe to do this? Will frequent writes cause overly excessive wear on any internal flash memory?

I'm trying to get my battery to charge if I'm exporting to the grid and it's not at 100%, as my solar is on a separate grid-tied inverter. I'd like it to still discharge to a minimum SoC to cover import. I understand this is the Sunsynk behaviour if the solar strings are connected directly, but they're not in this case. It only charges using any export if the SoC is greater than the current value.

[f1wade]

you can also turn the timer off, and it will charge the battery, I think at full battery charge current.
At least for me that works.

but may be good to test it.

I can't comment on the excessive wear on internal memory, as I don't know how the inverters made / works.
but it should be able to handle something like that in my opinion.

[amkurtis]

Thank you!

I could do that based on automation if export exceeds max charge current to avoid grid import. The nice thing about the system mode is it balances the battery current against export if grid is not ticked to still charge up.

I might be overthinking it. The HA plugin for my EV Charger came with some warnings about the best method of controlling charge current through automations to avoid excessive wear, but it might be the idiosyncrasies of that particular device.

[kellerza]

Should be safe to change settings - see #142