I have been getting an intermittent problem where a timed charge that has been set doesn’t get actioned. I’ve traced this through the logs to a very specific set of weird circumstances.
On the days the timed charge failed to be actioned my battery SoC was always at 4% or less (not sure how it quite regularly gets down to 2%, 1%, or even 0% but maybe that’s another issue?) AND battery discharge power happened to be set to zero to prevent discharge at cheaper periods earlier in the day. Battery charge power was always at 2600.
I tested this to confirm, and when battery discharge power is changed up to maximum 2600 the timed charge then starts up. It may be coincidence, but this didn’t happen before a battery firmware upgrade on 27 October.
It seems very illogical that discharge power would interfere with charging, but I use automation software to maximise benefits from Octopus agile, and this set of circumstances can crop up regularly, and prevents charging.
Is anyone else experiencing this, or is it just my system, and is there anything I can do?