Mode Schedule Force Charge only works once

[petste]

Hi,

My system has been operating a week after installation, and one of the first things I did was getting the agent to update inverter firmware since the Mode Scheduler wasn't available.

The problem is that I can't get the mode schedule to Force Charge more than once after cycling the system down and up (down: Battery, PV DC, Grid - wait until screen is blank plus some - up: Grid, PV DC, Battery). My latest try I even had two Force Charge after one another (since low tariff passing midnight), but only the first charged and the following just acted as self-use hence draining my batteries during cheap hours. Using the standard/simplified force charge is working multiple times though.

One time I was even standing looking at the inverter when it was supposed to go from self-use to force charge but it did nothing, no error messages no internal clicking, nothing.

This is probably something for support to dig into, but given the vast amount of experience in this forum it is worth seeing if someone has experienced something similar and found a way out.

Inverter is an SK-HWR-12: Version_Master 2.05, Version_Slave 1.03, Version_ARM 1.84
Batteries ECS4300 (master battery plus 3 slave batteries): Version_BMS 1.007

The notch in the SoC is where I rebooted the system, no altering of settings at all after that

Passing midnight it was up just shy over 90% SoC, but instead of continue force charge it went into self-use

Been careful not to overlap. The min SoC value of 75% in self-use is not my end game, just during testing

Standard scheduler is and were disabled

[Dave Foster]

Thanks for posting, the scheduler functions have only recently been released on the H3 series - i've checked your firmware versions and they are current.

Schedule timings and settings look fine, although I have found it is best to set FDSoC the same as your battery reserve level (not 95%), i've seen a few issues with that from time to time.

Your battery reserve capacity is very high at 75% - is that intentional ?, normally it is set the same or a little bit higher for use on EPS

[petste]

The 75% battery reserve capacity is only an artifact from previous test runs where I didn't want a period of self-use drain down batteries to 10. Also, the minSoC 20% will go to 10% once I get things to work.
My ambition is to find a good schedule time-vise (given the normal way tariffs changes over the day) and let that stay. Then using minSoC to give some room for PV depending on cloud forecast and time of year and during the day ours when tariffs usually are higher but still ok, then let minSoC down to 10 when tariffs are always high and we start to consume more power (i.e. 17-22).

I'll let FDSoC follow minSoC then just in case.

Since this then seems as a bug in the firmware for H3 rather than me doing something stupid, I'll send the issue over to support. I am new to this concept of FoxESS vs. Agent vs. Installer, would you recommend always going through my agent or directly to FoxESS support with this issue? And if going directly to FoxESS, how do I contact them correctly?

[Dave Foster]

The 75% battery reserve capacity is only an artifact from previous test runs where I didn't want a period of self-use drain down batteries to 10. Also, the minSoC 20% will go to 10% once I get things to work.
My ambition is to find a good schedule time-vise (given the normal way tariffs changes over the day) and let that stay. Then using minSoC to give some room for PV depending on cloud forecast and time of year and during the day ours when tariffs usually are higher but still ok, then let minSoC down to 10 when tariffs are always high and we start to consume more power (i.e. 17-22).

I'll let FDSoC follow minSoC then just in case.

Since this then seems as a bug in the firmware for H3 rather than me doing something stupid, I'll send the issue over to support. I am new to this concept of FoxESS vs. Agent vs. Installer, would you recommend always going through my agent or directly to FoxESS support with this issue? And if going directly to FoxESS, how do I contact them correctly?

Yes it does look like a bug, if it is re-producible it should be reported - the best way is to raise a ticket in the V2 app, click 'Me' at the bottom, then 'Contact Us', then 'Support' and you can describe the issue, attach images etc..

[petste]

Thanks Dave, I really appreciate your help!