Strange Battery Behaviour

[spiral]

Participated in an Axle grid event last night which discharged my battery to the 10% min soc.
By this morning the battery had dropped to 5%.
Once solar started to be generated, 100% of my solar went into charging the battery and 100% of my home use came from the grid.
I thought this must be a quirk of the battery being below 10% but on checking the battery later (when at 16%) I noticed this was still occurring.
I thought I'd try and force the state to end by setting my max soc at 17%. Sure enough when 17% soc was achieved, the battery stopped charging but solar generation went to 0 and 100% of home use was still coming from the grid.
On returning the max soc back to 100% the problem resumed where it left off i.e. 100% solar generation going to battery, 100% of home use coming from grid.
How do I get the battery to start being used by the home again?

[spiral]

Just uploaded a screenshot to summarise the behaviour

[MaterialBarracuda48]

What occurs if you switch work modes?
If this does not change things, you may have to restart your system.

[spiral]

I've done both of those to no avail.
I have a g100 state 3 message on the inverter that won't go away. I've contacted my installer who after walking me through a reboot (again) has advised me that Fox need to reset this error remotely as he doesn't have access to the settings required so now I need to wait for him to contact Fox and Fox to action it.
At least I'll probably have a full battery at the end even if my Axle event proves to be cost neutral.

[spiral]

All up and running correctly now which leads me onto this question.
If operators and installers cannot access this menu setting to fix the problem, what happens if Fox go bust. Would that leave me with a system that doesn't work with no way of fixing it.
More likely though is my installer packs up their business (having made a tidy profit out of installations) and Fox won't deal with me directly because my installer has informed me should this occur again, I still need to go through him.

It does beg the question as to why Fox would want to get involved in day to day maintenance though.

[MaterialBarracuda48]

There is a factory reset menu IIRC, odds are this would get you working again if there was a duff setting.
TBF, Fox have been around for a fair while, though with any kit, there's always a chance they go belly up, or any other company too.

[Dave Foster]

If you go into your inverter settings at the front panel, there is an on-line menu option that has a G100 sub-menu and you can reset the error there.

[spiral]

I did google the error and attempt to fix it as per the response but I couldn't locate the menu item although the answer I saw only told me to locate the g100 sub menu in settings with no mention of the online menu option. I'll take another look in the morning but if I can reset it, it begs the question as to why my installer said he would need to contact Fox as that menu item was hidden from him.
I assumed it was a feature that fox had removed access to and I was looking at an old method of fixing it.

[spiral]

Just to confirm as per Dave's suggestion, I did locate the G100 sub menu under settings-on grid-g100 para and there is a reset option within it. Hopefully now I know where it is, I'll never need to use it.

[spiral]

Not being quite sure what caused this my installer suggested not discharging to 10% so I contacted Axle to be informed that they have no setting for this and their schedule overrides any minimum SOC set up by the end user stopping at a manufacturers safe level.
Their solution is to adjust the discharge levels in order to not fully drain the battery.

[spiral]

For the past couple of days (I think since this lock up issue occurred but cannot be 100% certain) I get a 40004 loading error when entering the dashboard on a pc.
It only remains for about half a second, then disappears. Data seems to be reading correctly and I can set up schedules which also seem to work OK.
Presumably because the message only appears briefly, whatever communication error it sees is correcting itself within that time. Is that assumption correct as everything appears to be behaving normally otherwise.