---
title: 'Battery Comparison'
description: Side-by-side battery comparison for several nodes — a summary table and mini discharge charts to verify batch consistency or find an outlier.
section: AI Analytics
weight: 8
related:
  - ai-analytics/node-reports/battery-forecast
  - ai-analytics/fleet-reports/fleet-battery-forecast
---

import Alert from '@/components/docs/Alert.astro';

The report places the batteries of several metering nodes (from 2 to 5) side by side on one page: a summary table and mini discharge charts next to each other. It lets operations quickly see whether the devices behave the same or one of them stands out from the group.

Typical tasks:

- check the uniformity of a batch — do nodes from one delivery discharge the same way;
- find an anomalous node in a group — one discharged noticeably faster than the rest;
- compare buildings with identical metering devices.

<Alert type="tip">
For a single-node breakdown with a service-life forecast, use the [Battery Forecast](/en/platform/v3/ai-analytics/node-reports/battery-forecast) report.
</Alert>

## What it shows

For each selected node, a summary-table row and a mini chart of the charge history are built. The charts stand next to each other so the comparison is clear.

| Column | What it means |
|---|---|
| Node | metering node number |
| First / Last | charge at the start and end of the period |
| Minimum / Maximum | the lowest and highest value over the period |
| Average | the average charge level over the period |
| Drop, % | how much the charge fell from start to end — the main indicator for comparison |

Below the table, the report flags the node that discharges noticeably faster than the others — for example, a node that discharges twice as fast as the rest, which may point to a modem anomaly or a higher load.

## How it's calculated

The list of node numbers is parsed from a comma-separated string. For each number the report finds the metering device and loads the battery voltage history from the communication-session log (records of the device coming online, from which the charge readings are taken).

Then for each history simple indicators over the period are computed: first and last value, minimum, maximum, average and the drop percentage. For each series a checksum (a data fingerprint) is computed. If the fingerprints of two nodes match, this signals that the same device was accidentally entered twice on input — the data turned out identical.

## Run parameters

| Parameter | Default | Meaning |
|---|---|---|
| Node numbers | required | a comma-separated list of node numbers, e.g. `868, 700, 5690` |
| Period from | one year ago | start of the history window |
| Period to | yesterday | end of the history window |

<Alert type="note">
Enter exactly the metering node number — the number from the node page address on the IIoT Platform — not the internal device number.
</Alert>

## How to read it

- Look first at the **Drop, %** column: for uniform nodes the values should be close. A node that stands out sharply is a candidate for a check.
- **Mini charts** show the discharge character: a flat line, a step or an acceleration. Compare the shape, not just the final figures.
- If two nodes have **fully matching data** (the same fingerprint), most likely the number was mistyped on input — recheck the list.
- Node selection is **manual only**: the report does not guess nodes of one batch on its own. Take the numbers from your list or export.
- The minimum for comparison is **2 nodes** (for one, use Battery Forecast); the maximum is **5 nodes** per page, otherwise the charts read poorly.

## Related reports

- [Battery Forecast](/en/platform/v3/ai-analytics/node-reports/battery-forecast) — a detailed single-node breakdown with a service-life forecast.
- [Fleet Battery Forecast](/en/platform/v3/ai-analytics/fleet-reports/fleet-battery-forecast) — an overview of battery state across the whole fleet.