Not respecting Max SoC / I'm doing something wrong

Post Reply
cpwood
Posts: 4
Joined: Sat Sep 21, 2024 3:48 pm

I'm using the nathanmarlor/foxess_modbus integration and have an automation that takes a target SoC number value that's configured on a dashboard slider, sets the Max SoC on the inverter and then enables charge period 1 between 03:00 and 04:59. If I set the slider to 70%, for example, it still charges to 100%. Connection is via RS485 and Waveshare adapter.

H1-6.0-E-G2
Master: 1.21
Slave: 1.02
ARM: 1.32

The automation is configured as follows:
Automation.png
I can see from the sensor history that the Max SoC does indeed change from 100% to 70% for the duration of the charge period:
Max SoC.png
But here is the reported Battery SoC for the same period:
Battery SoC.png
My expectation is that it would charge to 70% SoC and go no further. Can somebody tell me if I'm missing something obvious here, either in my configuration or understanding?

Really appreciate your help!

Chris
Dave Foster
Posts: 1234
Joined: Thu Oct 13, 2022 7:21 pm

I think this is an issue with older firmware on the G2, for both the G2 and KH the inverter didn't respect maxSoC when charging from grid (as it is supposed to) which was corrected recently in a firmware update.

You are on old firmware, the latest being Master 1.27 and Manager (ARM) 1.44 - ask your installer or email Fox service with your serial number and ask for the inverter to be updated to the latest firmware version.
Post Reply