Optimisation's scope and limitations

Export limits and G100 restrictions

Currently, optimisation does not take export limits or G100 constraints into account when planning battery behaviour.

This means if a system has a cap on how much power it can export to the grid—such as a DNO-imposed export limit or a G100-compliant inverter—the optimisation engine is not aware of this restriction. As a result, it may assume it can export more than the system is physically allowed to, leading to decreased performance and reduced savings.

Support for export-limited systems is something we aim to improve in the future, but for now, optimisation assumes full export capability unless otherwise limited by manual settings or battery constraints.

Octopus Power-Ups

Octopus Power-Ups offer consumers free electricity during special events, but they require manual opt-in and do not change the live tariff rate. Since our optimisation engine relies on real-time tariff data—and Octopus does not currently provide Power-Up information via API—the system is unaware of these events and won’t optimise around them.

Read more about Power-Ups here: type: embedded-entry-inline id: 4QyHTNCyy3Ca4ubFo4xZO9

GivEnergy GivBack Events

GivBack events involve GivEnergy taking control of the battery to participate in grid flexibility schemes. Using these events alongside Zoa’s optimisation is not recommended, as the two systems can conflict. While it’s possible to manually switch optimisation off for a GivBack event, doing so may disrupt the strategy and result in reduced savings or missed opportunities.