Hello Community,
I’ve been using a time-of-use controller to optimize energy usage and costs under a static pricing scheme with Octopus. However, I’ve encountered an issue where the controller seems to get stuck in self-consumption optimization mode, effectively handing over control of the ESS to the balancing with a target of 20 kW.
As a result, the system continuously discharges the ESS until it reaches the configured health reserve limit (10%). Once this threshold is reached, the time-of-use controller does not schedule any grid charging to replenish the ESS, leaving it in a persistently discharged state.
My goal is for the controller to actively manage the ESS based on its forecasting and cost-optimization logic, rather than remaining inactive after hitting the reserve limit.
Has anyone experienced similar behavior or found a way to ensure the controller resumes grid charging and maintains proper optimization after reaching the reserve threshold?
