PV output clipping during strategy set forced charge

Post Reply
Riverman
Posts: 2
Joined: Tue Mar 05, 2024 6:41 pm

Just joined Octopus Flux but waiting for export to be set up. I have been charging my batteries (8.6 KWh H1) by force charging to 100% until last night, but because a decent amount of sun was forecast today I reduced the charge time to leave space. The forecast changed and there was no sun, so I set the strategy to force charge just after lunch to avoid importing at the premium rate between 4 and 7p.m. The Fdpower was set as advised by the installer at 600W. However the sun did come out and the panels were producing >2 KWh all this PV output was clipped. Can anyone suggest a strategy to avoid clipping in this circumstance.
Dave Foster
Posts: 1294
Joined: Thu Oct 13, 2022 7:21 pm

The Force Charge and Force Discharge functions, do not allow the use of solar generation, all PV generation is suspended when they are used. - FoxESS are aware of this and have said that a firmware update will be released to correct this, but no date has been given.

The only charge method that currently supports PV generation are the ‘old’ charge periods - but to use these you must disable the scheduler and any schedules or it will clear them.

If in the schedules you set the work mode to self-use it will prioritise output as follows ‘House Load’ > ‘Battery’ > ‘Feedin’ which would charge your battery but obviously not as much when charging.
calum
Posts: 398
Joined: Fri Feb 24, 2023 11:00 am
Location: Stockport

Dave Foster wrote: Wed Mar 06, 2024 7:30 am The Force Charge and Force Discharge functions, do not allow the use of solar generation, all PV generation is suspended when they are used. - FoxESS are aware of this and have said that a firmware update will be released to correct this, but no date has been given.
This is one of those things where it's just staggering that it made it past even the most basic of QA.
H1-3.7 / 6xHV2600 / 14x400W / RS485 Modbus->HA
FoxESS Modbus HA Integration
Contact Fox here
octonaut
Posts: 1
Joined: Wed Oct 04, 2023 7:05 pm

Dave Foster wrote: Wed Mar 06, 2024 7:30 am The Force Charge and Force Discharge functions, do not allow the use of solar generation, all PV generation is suspended when they are used. - FoxESS are aware of this and have said that a firmware update will be released to correct this, but no date has been given.

The only charge method that currently supports PV generation are the ‘old’ charge periods - but to use these you must disable the scheduler and any schedules or it will clear them.

If in the schedules you set the work mode to self-use it will prioritise output as follows ‘House Load’ > ‘Battery’ > ‘Feedin’ which would charge your battery but obviously not as much when charging.
Do you know if this been addressed by firmware update(s) yet? I have Manager 1.70 on H1-5.0-E in the UK. It works okay to use the 'old' grid charge periods but switching between these and the otherwise more flexible Mode Scheduler is cumbersome. Since going over to Octopus Agile I sometimes find myself wanting to top up the battery at cheaper times during the day but don't want to waste the sun power in the process.
H1-5.0-E / Fox Cube ECS4300H-H3 12.44kWh / 12 x 455W
Dave Foster
Posts: 1294
Joined: Thu Oct 13, 2022 7:21 pm

octonaut wrote: Mon May 06, 2024 1:04 pm Do you know if this been addressed by firmware update(s) yet? I have Manager 1.70 on H1-5.0-E in the UK. It works okay to use the 'old' grid charge periods but switching between these and the otherwise more flexible Mode Scheduler is cumbersome. Since going over to Octopus Agile I sometimes find myself wanting to top up the battery at cheaper times during the day but don't want to waste the sun power in the process.
Yes it has for the H1, if you upgrade to Manager 1.71 and Master 1.64 it will use solar generation instead of disabling it :)
reef
Posts: 107
Joined: Sat Sep 09, 2023 10:06 am
Location: East Yorkshire

Sorry to bump an old thread, but I've requested a firmware update on my H1 to solve this PV clipping issue and they have updated the Manager to 1.74 but left the Master 1.63 for some reason? Is the fix in the manager version or are both required to be updated?

What's the latest Master version. Is it 1.65?
Dave Foster
Posts: 1294
Joined: Thu Oct 13, 2022 7:21 pm

Yes latest is 1.65 and i’m pretty sure you need both updated (at least to 1.64) - but double check on your app what the firmware versions are, home assistant sometimes doesn’t report the latest version untill it’s been restarted.
reef
Posts: 107
Joined: Sat Sep 09, 2023 10:06 am
Location: East Yorkshire

Yes, the v2.0 app and home assistant after a restart both show v1.63 still. I've sent them an email asking for the update to v1.65. I'm not sure why they only updated the one.
reef
Posts: 107
Joined: Sat Sep 09, 2023 10:06 am
Location: East Yorkshire

I can confirm that the fix does not work without the update of the master version. Hopefully they reply to my email!
Post Reply