FoxESS Community - Owners & Installers Forum

Hi

I've got a H1 G2 5KW inverter, connected to HA using an Elfin EW11 and the HACS ModBus adapter (https://github.com/nathanmarlor/foxess_modbus).

I've setup an automation to control the Min & Max SoC of my ECS2900 batteries based on the electricity rate from Octopus (IOG). This works fine for the Max SoC, but the Min SoC seem to be exhibiting some odd behaviour... When viewing in HA the Min SoC gets set but then reverts to the original value (10%) within a couple of seconds, as shown in the history:

I'm unsure whether the stat change is actually applied to the inverter and then overridden by something else (perhaps the mode scheduler?), or whether the change in HA is as a result of an internal 'variable' being set in the ModBus and the value is never actually changed on the inverter (and the value then appears to be 'reset' the next time the state is read from the inverter.

Has anyone come across this behaviour, or have a similar automation working for a H1 G2 inverter?

Any help or advice appreciated

You're going to need to provide an example please, I've read it twice and I'm not following. What I can confirm is that I have a number of H1 gen2 working fine with HA.

Have you tried the number.min_soc_on_grid? rather than number.min_soc? min_soc_on_grid works fine on the KH as a way to control the minimum charge limit (I'm using it for the 'freeze charge' and 'hold charge' modes on predbat).

Oh I have no idea, I prefer to setup my own automation in HA over PredBat

Will wrote: Sun Apr 13, 2025 7:26 pm Oh I have no idea, I prefer to setup my own automation in HA over PredBat

Just to make life difficult for myself I do it both ways

Started off with my own scheduler based on target SoCs throughout the day but running predbat in the background in read-only mode (so that it only monitors and does not control the system), let predbat control things during March with mine turned off, back on mine for control now now and predbat is read-only again.

The main reason is that I wanted to be able to run predbat is so that I have the ability to jump to a more complex tariff if necessary. For a simple tariff like E-on Next Drive, my own scheduler can control it exactly the way I want.