Grid usage when the battery should be taking the load

I’ve noticed today that the grid is being used much more than it should be. Right now my home is consuming 441w of which 161w is coming from the battery and the remaining 280w is coming from the grid. The battery is at 100% and should be taking all the load.
Periodically whenever the battery drops down to 99% full it looks like more grid power is being pulled to top the battery up to 100% again.
Tariff is Octopus Go,
Charge settings are for 00:30 to 05:30
No discharge or export set,
Eco mode is on.
Winter mode is on.

Any pointers on why this might be? Thanks in advance

Here is yesterday’s battery usage pattern. It looks pretty normal. It charges overnight, then discharges during the day with a small point where it gets topped up by Solar.

Now compare it to today’s (so far) odd battery charging spikes and including after the sun has gone down.

Following up on this myself. Essentially the system is ignoring all its configuration. I set up forced discharge and export settings and they were ignored, it’s basically totally messed up for no reason as of today. No settings have changed since December.

I think I have fixed it….

Things that didn’t work…..

Restarting the inverter,
Full turn off and on,
Updating firmware,
Changing and resetting up all the settings.

The thing that fixed it was resetting the system to factory defaults. Even though according to the app the settings are exactly the same now as they were before the reset (minus the charge settings) the system is now working as expected.
I hope this helps someone else.

Carey it also looks like it started discharging before 0530, which it shouldn't have. Might behave like this if reserve was set high - as soon as it discharged below that value, it charged back up again. And the relatively flat top might have been a discharge limit. Ie as you say, lots of settings messed up.
On the remote control page, you can force the portal to read the values from the inverter - normally it just shows the values its stored values.

DD Thanks.

It seems that the reset to defaults of the values didn’t fully fix the issue. The corruption seems to be in the charge schedule.

If I turn on the charge schedule with my normal 00:30 to 05:30 in slot 1 and all the other slots empty it will immediately tries to charge the battery to 100% and then keep topping it up to 100 when it drops to 99 all day, essentially ignoring all the settings.

The problem seems to be that slots 1 to 9 contain null (as opposed to zero) values. I have had to force a charge start and end into each slot of 00:00 to 00:01 and save them one by one so the slots now have a value in them. I’ve then set them all back to 00:00 to 00:00 and it now appears to work fine.

I find it worrying that randomly one morning it can all just suddenly be messed up.

If it happens again , now that I know more about the remote control and portal I will retrieve each of the charge setting values and see which ones are broken and fix just the broken values rather than force overwriting all of them.

I now have a very similar problem which has happened over the past 2 days. I'm new to this so trying to work out if I've understood the settings properly.
I have a 13kWh AIO (firmware version 10) with Gateway. My battery seems to have gone into 'limp' mode. It's charging from solar but not discharging when needed. If the demand exceeds solar availability (washing machine and kettle on) the power is being made up from grid and not the battery.
Settings are:
Eco mode enabled
Timed charge enabled 0200 to 0500
Timed discharge enabled 0500 to 0200 - but I've also tried 0500 to 2359 and disabling this setting - it makes no difference.
Timed export enabled slot 1 0700 to 1600 export to 90%, slot 2 1600 to 1900 export to 40% - but I've also tried disabling this and it makes no difference.
Discharge power 6000w
Charge power 4960w
Reserve 4%
Winter battery conditioning not enabled
All non used slots are 0000 to 0000
I've tried resetting to defaults and then reconfiguring - it makes no difference.

What am I doing wrong? 😰

RR50 Timed discharge enabled 0500 to 0200 - but I've also tried 0500 to 2359 and disabling this setting - it makes no difference.

I'm surprised it makes no difference - setting it to 0200 to 0500, along with a timed charge of 0200 to 0500, should effectively mean that the battery never discharges. But should work correctly with 0500 to 2359, and without timed discharge. (Timed discharge has fairly limited use-cases, such as preserving battery charge for an expensive tariff period like 4pm to 7pm.)

Timed export enabled slot 1 0700 to 1600 export to 90%, slot 2 1600 to 1900 export to 40% - but I've also tried disabling this and it makes no difference.

That sounds like a problem... it would start dumping battery to grid, and as soon as it got down to 90%, inhibit discharge until 1600.

Perhaps you didn't disable both timed-discharge and timed-export together, which is why neither seemed to fix it on its own ?

How do you want the system to behave? We can suggest appropriate settings to achieve that.

Thanks for responding DD,
Just to clarify one point the timed discharge was set 0500 to 0200 - so it was the complement of the timed charge. The reason I tried 0500 to 2359 was just in case rolling over a day caused a problem.

I don't understand why an instruction to export down to 90% in a time slot would turn off discharge altogether when battery is below 90%. To my thinking, 'discharge' includes 'export' but not the other way around.
My intention was that in slot 1 (most of the day), it exported anything above 90% but still covered domestic demand - thus exporting any surplus solar but maintaining a good battery charge. Then, in the period of high grid demand, down to 40% (keeping enough battery to last through to the next charge at 0200). In truth, I planned to create more slots to cover the high demand period at a later date (once I've learned the system). Did I misunderstand how it works? And do you have any links for information that explains how it works? TIA

RR50 I don't understand why an instruction to export down to 90% in a time slot would turn off discharge altogether when battery is below 90%. To my thinking, 'discharge' includes 'export' but not the other way around.

Unfortunately, it's a common misconception that it means "discharge (at fixed power) until either the end time or 90% is reached". I guess the correct interpretation is "discharged at fixed power until the end time. If 90% is reached, that fixed power is 0W".

I use an external script to do what you're asking - disable solar charging by default, aiming to keep the SoC around 90% : if it goes above 95%, force export back to 90 ; if it goes below 85%, enable solar charging until it gets back up to 90%.

Another downside of the implementation of forced export is that it doesn't look at consumption - if the kettle goes on during a forced export at 2kW, say, then even if the consumption goes above 2kW, it won't increase the power, or go back to eco mode, or anything like that. I've yet to implement anything in my scripts to handle that case - drawing a few Wh from grid to boil the kettle is barely going to register on costs.

(sorry, yes, I misread your timed discharge setting.)