FoxESS Community - Owners & Installers Forum

I'd suggest - at least once a week, make sure you hit 100%. At least once a month, make sure you hit 10% (i.e., down to the reserve).

I set up an automation to do it for me. Many people will just hit these limits routinely as a result of their charging / discharging schedules.

It was about 5 days I think, but it is going to vary depending on how many tickets that they have in the queue, and whether that is all working days or includes a weekend / holiday / etc.


Note that the peak rate consumption won't get to exactly zero, unless you set it to some absurd level like ...

You need to check it via a separate CT clamp or (ideally) from the smart meter itself. The inverter's CT will appear to be unchanged, at +10W import or whatever, but the readings will be biased by the compensation figure in the direction of forcing export. So for example, the inverter's CT is ...

Somewhere buried away in the system the clocks have not moved forward.


I think (not 100% sure) that the mode scheduler is driven from the cloud, not locally on the inverter. So if the time on the Fox cloud hasn't been adjusted, then it'll be off, regardless of what the inverter's time is set ...

Generally people just use the default range 10% - 100% (since it is 90% DoD). The warranty will cover you for 6000 full 10%-100% cycles (EC/EQ) for 12 years, or 4000 cycles (EP) for 10 years with the extended warranty, and you should have at least 80% capacity remaining after doing that.

If you are ...

Yeah. A pity that particular paper did not model 20-80 charging as one of the scenarios, but some other papers do cover it. High cell temperatures, high SoC ranges, high charge rates, etc all have an effect over the years.

Do you have more details on setting up Home Assistant to work with the 485 messages?



* This is my system, installed in January, including the RS485/MODBUS adaptor, home assistant, and the plug: https://imgur.com/a/18OpA4d
* This is the interface software ('integration') which you install into ...

Presumably the agreement with the DNO is that export cannot exceed 100kW?

If the export limit is an issue, perhaps increase battery capacity & ensure that there is enough space in the morning, so that any overflow can be stored rather than clipped?

Here's what the meter compensation setting will look like - inverter's sensor.grid_ct figure compared to a Shelly CT. -30 set at 15:47:50. The inverter CT still registers +10W import, but the system is actually now exporting a small amount rather than importing a small amount. Of course it is the ...

Here's the result of my calibration automation - I got brave and set it to 100%, and it reached it OK. This is with top calibration interval at 7 days, bottom calibration interval 28 days, charge current 2.7A via number.force_charge_power (600W on an EC4300-H4) >= 97% SoC. I guess the previous time ...

Sounds like Will has already tested it (no issues), so I have edited my support ticket, since I'd prefer not to take the risk if it isn't necessary

@Dave

Noticing the new manager version v1.39 mentioned above, do you need that tested for the integration? I'm on v1.37 which seems stable, but I could ask them for an upgrade if it is needed. I don't know what the changes are. I wonder if it might contain any of the recent H3 pro register gain ...

You'll find the forecast gradually gets more accurate as time goes by. So if you fancy making the automation a bit more complex/intelligent, you could query it 3 times - once at the start of the charging period, once 1/3 of the way through it, and once 2/3 of the way through it. Then adjust the ...

That's great, thank you.

I have adjusted the charge rates appropriately. Currently it does the bottom calibration at the same interval as top calibration, so I'll also split that out into another setting rather than sharing it.

I drive my battery relatively hard (about the equivalent of 1.3 full ...

Have you tried Solcast? The instructions are in the predbat documentation. It's quite a bit more accurate than the others, from what I can see.

From Solcast, the single figure will be in sensor.solcast_pv_forecast_forecast_today or sensor.solcast_pv_forecast_forecast_tomorrow.


solcast_vs ...

- but make sure you charge to 100% regularly (at least weekly, preferably more often) and give them a bit more time at the top of the charge by reducing the charge rates,



I set my KH7 (EC4300-H4) to do it every 10 days - sounds like I need to adjust this down to a week. I set up my calibration ...

If the voltage tolerance can't be adjusted, there might be another option - I've heard of something called a 'household voltage optimiser' which can adjust the incoming grid voltage if it is persistently too high or too low. I have no idea how much it would cost, or if it would help in this scenario ...

Thanks for reply. No I don't have a battery at present, but may consider upgrading in future. When I looked at the battery option it seemed to push back the break even point by several years. I can see the prices of batteries online seem to be about half the price that the installer was quoting as ...

I have spent hours trying to wrap everything in {{}} or {%%}

It depends on what you are trying to do. For example, if you wanted to modify the number rather than use it directly. The simple case is just to look at the entity directly


conditions:
- condition: numeric_state
entity_id: sensor ...

First set up your input_number:

Settings, devices & services, then select the 4th tab (helpers), click 'create helper', scroll down to 'number', click on that, then pick a name, type in the minimum and maximum values, and the step size (for example, for 0.0% to 100.0% in steps of 0.1%, do 0, 100, 0 ...

Could you use an input_number template helper as the input?

Many thanks

I have asked FoxESS if these are the latest versions but no response so far.

Manager versions from 1.33 onwards expose the BMS registers, the bms_cell_temp_low sensor is particularly useful if your system can get cold in winter.

Just had mine updated today as BMS info is now available via Modbus

I believe that this is the firmware version which includes the setting for grid pressure. I got this update in early Jan (accidentally rather than deliberately, I was actually after a battery firmware update, but it's probably a ...

I've been throttling charging via the number.force_charge_power (which is in kW rather than amps, and obviously affects the system only when it is in force charge mode).

Is it better to do it via number.max_charge_current instead?

Are these two throttles independent (i.e., will it be the lower of ...