Start with the site's energy flows
A battery installation may include grid import and export, solar generation, battery charging and discharging, and building loads. Draw those measurement points before selecting hardware. Otherwise it is easy to count the same energy twice or mistake a site total for the battery's own output.
Use the ZEM electricity-monitoring family where independent electrical measurements are needed. Select the configuration and current transformers against the current datasheet and the installation requirements; do not infer billing or settlement approval from an accuracy class alone.
Combine metering with battery telemetry
An external electricity meter measures electrical flow. It does not, by itself, provide battery state of charge, internal temperatures, alarms or operating limits. Those values need a supported interface to the battery system or its controller.
Edge can bring supported equipment readings into the same workspace as EpiSensor measurements. For the specific battery model and firmware, agree the interface, register or API mapping, units, update intervals and permissions. A shared protocol name does not establish that every telemetry point or command is supported.
The ZGW-20 Gateway hosts the site system. Its communications options and any additional interfaces should follow the equipment and network requirements, not a fixed example bill of materials.
Make the charts useful
Compare battery power and state of charge with solar output and site import/export in the Edge Data workspace. Agree which power sign means charging and which means discharging. Check timestamps and measurement boundaries before calculating throughput or comparing energy totals.
For an efficiency comparison, define the measurement period and include the relevant auxiliary consumption and change in stored energy. Label calculated values so operators know how they differ from readings supplied by the battery.
Define control responsibilities
Edge supports configured local automation and partner integrations. Review the ZDR demand-response family where its monitoring and control functions fit the project. The battery's internal protection and management functions remain the responsibility of the battery system; site-level commands are not a replacement for them.
Agree allowed operating modes, limits, command acknowledgement, local overrides and loss-of-connection behaviour. Verify the physical response, not just a successful API request.
Connect a wider service when needed
A third-party platform is optional for using Edge's local tools. If the project needs portfolio optimisation or market participation, define that service with the provider and qualify the complete integration.
Browse battery manufacturers in the directory, read the VPP integration guide, or discuss a BESS project. A manufacturer profile is useful context, not confirmation that a particular battery is already integrated.