Program Event Reports
Read the results of program events — energy delivered, device participation, and fleet health
Program Event Reports is where you see what happened during and after a program event — how much energy moved, which devices responded, and whether the fleet is healthy. The shared reports experience covers batteries, chargers, EVs, and thermostats; this page focuses on the battery reports view, but most concepts apply across device types.
The reports answer three questions, one per tab:
- Event Performance — How much energy did the program deliver, and when?
- Device Participation — Which enrolled devices actually took part in a given event, and how much did each contribute?
- Program Health — Are the enrolled devices online and responding reliably over time?

Key concepts to read first#
These conventions apply across every report. Understanding them up front prevents most of the confusion customers run into.
Two energy metrics: Net at Meter vs. Battery#
Battery reports can show energy two different ways, switched with the Energy Metric toggle (Net at Meter / Battery). They answer different questions and are meant to differ:
- Net at Meter (default) — the net energy exchanged between the whole site and the grid, measured at the site's grid connection (via the system's gateway/meter). Because it is a net, whole-site figure, it reflects everything behind the meter — solar, household loads, and every device at the site — not the battery alone. So you may occasionally see unexpected or opposite values: e.g. if solar is charging the battery while it discharges, or the home is consuming what the battery delivers, the meter number can differ from — or even oppose — what the battery by itself is doing.
- Battery — the energy that actually left the battery's cells, derived from the battery's state-of-charge. This is per-battery (no whole-site mixing) and is the more direct read of "what this battery delivered." Because it is measured at the battery, it is gross of inverter/round-trip conversion losses, so it generally reads a little higher than the grid figure.
The Energy Metric toggle appears only for battery programs/events that actually report state-of-charge data; for everything else, reports show the Net at Meter figure.
Export vs. import direction#
Grid energy has a direction. Throughout the reports:
- ↑ Exported to grid — the site sent energy out to the grid (typically battery discharge). Shown in orange/amber.
- ↓ Imported from grid — the site pulled energy in from the grid (typically battery charging). Shown in blue.
When the Battery energy metric is selected, the same colors describe the battery directly: orange/amber = discharged (energy out of the battery), blue = charged (energy into the battery).
All times are shown in your local time#
Timestamps and time windows display consistently in your local browser time zone across every report and filter. If you operate a program in another region, convert the event's scheduled hours to your local time when reading the charts — for example, an event scheduled 6–9 PM Pacific appears as 8–11 PM for a viewer in Central time.
Event phases: charge, idle, discharge#
A single event can contain multiple phases. A typical battery event charges the batteries first, holds (idle), then discharges during the target window. Two terms matter when reading totals:
- Discharge window — only the portion of the event when devices were asked to discharge to the grid.
- Entire event — the full event, including the charge-up and idle phases.
Several views let you toggle between these two scopes, which changes the kWh totals you see.
Where to find the reports#
Open a program from the dashboard and select Reports. You can also reach a single event's report from Program Events → Event Details → View report.
At the top of the Reports page you'll find three shared controls:
- Program selector (top right) — choose which program you're reporting on.
- Date range — Last 24h, Last 7d, Last 30d, or a custom range via the calendar.
- Asset type — Battery, Charger, EV, or Thermostat. Reports are scoped to one asset type at a time.
Tab 1 — Event Performance#
This tab summarizes all events in the selected date range and asset type.
Summary metrics#
| Metric | What it means |
|---|---|
| Events Completed | Number of program events that finished in the selected range. |
| Devices Enrolled | Devices signed up to the program that were eligible to participate. |
| Devices Participated | Of the enrolled devices, how many actually took part in at least one event. |
| Success Rate | Share of dispatched commands the fleet completed successfully across the range. |
Headline card#
| Card | What it means |
|---|---|
| Net Grid Energy / Battery Output (all events) | Total energy across every event in the range. The card follows the Energy Metric toggle: Net at Meter shows net energy exchanged with the grid (labelled "Net Grid Energy", e.g., 2,449.9 kWh in the sample); Battery shows energy delivered from the batteries (labelled "Battery Output"). |
| Average Peak kW per Event | The average across events of each event's single highest-throughput hour (≈ the peak hourly kW). Also follows the Energy Metric toggle — peak grid throughput under Net at Meter, peak battery discharge under Battery. |
Reading the Event Energy Comparison chart#
The Energy Comparison view shows energy (kWh) per hour across events as a color-coded grid. Each row is one event; each column is an hour of the day; the final column is that event's total energy in kWh.
How to read a cell:
- Cell fill color shows the energy direction for that hour — amber/orange for energy exported to grid (or, under the Battery metric, discharged from the battery), blue for energy imported from grid (charged), grey for no data.
- The colored bar on the left edge of a cell shows the command that was active that hour — orange for a discharge command, blue for a charge command, grey for idle.
- Color intensity reflects the magnitude — darker cells moved more energy.
For battery programs with state-of-charge data, the Energy Metric toggle (next to the Customize hours button) switches the whole chart — cells, totals, and color scaling — between Net at Meter and Battery.
By default the chart spans the full program window. Use the Customize hours button to narrow the view to specific hours (for example, just the discharge window).
Reading tip: A row that is mostly blue on the left (early hours) then amber on the right (later hours) is the normal shape of a battery event: charge up first, then discharge to the grid during the target window.
Tab 2 — Device Participation#
This tab breaks a single event down device by device: who took part and how much each one contributed. Pick the event from the Event dropdown, then filter by status, asset type, manufacturer, or member name.
Summary cards#
- Enrolled — devices signed up for the program at the time of the event.
- Participated — devices that responded and took part (shown with a percentage of enrolled).
- Did not participate — enrolled devices that did not take part.
The device table#
| Column | What it means |
|---|---|
| Device | The device manufacturer and model (e.g., Tesla Powerwall 3, FranklinWH aGate X). |
| Member | The customer / site owner the device belongs to. |
| Status | Participated or Did not participate for this event. |
| kWh → grid | Energy this device contributed during the selected scope. The header changes with the Energy Metric toggle — "kWh → grid" for Net at Meter, "Battery kWh" for Battery. A dash (—) means no measurable energy was recorded. |
| Resp time | How long the device took to acknowledge the dispatch command, in seconds. Long values indicate a slow-to-respond device. |
Two toggles (top right of the table) control this column:
- Energy Metric: Net at Meter / Battery — which energy source to show (see Two energy metrics above). Appears only when the event has batteries reporting state-of-charge.
- Show kWh Totals for: Discharge Window / Entire Event — the time scope: the discharge window only, or the full event (charge + idle + discharge). See Event phases above.
The two combine — e.g. Battery × Discharge Window shows each battery's discharge during the discharge phase only.
Tab 3 — Program Health#
This tab is about reliability over time rather than the energy outcome of a single event. Choose a window (Last 30 / 60 / 90 days, or custom) and filter by status, asset type, manufacturer, or member.
Summary cards#
- Total devices — devices in the program for the window.
- Online / Offline — current connectivity of those devices.
- Needs attention — devices flagged with one or more issues (see thresholds below).
The fleet health table#
| Column | What it means |
|---|---|
| Status | The device's current connectivity (Online / Offline). This reflects the live state of the device and is independent of how it performed in any program event. |
| Success rate | Share of commands the device completed successfully over the window. |
| Avg response time | Average time the device took to acknowledge commands, in seconds. |
| Issues | Why a device is flagged "needs attention." Common values are Long response times and Low success. |
The Event Details page#
Reached from Program Events, this page describes one specific event. The View report button takes you to the Reports tabs filtered to this event.
Actions#
Each event lists its phases as numbered Actions, each with a time window and status. For example:
| # | Phase | Window | Status |
|---|---|---|---|
| 1 | Charge | 2 PM – 4 PM | Completed |
| 2 | Idle | 4 PM – 6 PM | Completed |
| 3 | Discharge (min reserve 20%) | 6 PM – 10 PM | Completed |
"Min reserve" is the floor the battery is told not to discharge below, protecting the customer's backup capacity.
Headline metrics#
- Enrolled Sites — sites participating in this event.
- Overall Response Rate — share of enrolled sites/devices that acknowledged the dispatch.
The site table#
| Column | What it means |
|---|---|
| Site | The participating site address. |
| Device | The device at that site. |
| Response | A bar and percentage showing how fully the device responded to the dispatch (0% = no response, 100% = full). |
| Grid Energy | Net energy exchanged with the grid, with a direction arrow: ↑ exported to grid, ↓ imported from grid. A dash (—) means no net grid energy was attributed for this window — for example, the device didn't report, had no measurable net flow, or its charge and discharge netted out. |
Quick glossary#
| Term | Definition |
|---|---|
| Program event | A scheduled dispatch window during which the program sends commands to enrolled devices. |
| Action / phase | A segment of an event — charge, idle, or discharge — each with its own time window. |
| Discharge window | The portion of an event when devices were asked to discharge to the grid. |
| Entire event | The full event including charge-up and idle phases. |
| Net grid energy / Net at Meter | The net energy exchanged between the whole site and the grid, measured at the site's grid connection (via the system's gateway/meter). Net and whole-site, so it includes solar, loads, and all devices — not the battery alone. In raw data, positive values indicate energy imported from the grid (↓), and negative values indicate energy exported to the grid (↑). The UI displays energy delivered to the grid (exported) as the primary "delivered" metric with an upward arrow (↑), consistent with program goals. |
| Battery (energy metric) | Energy delivered from the battery's cells, derived from state-of-charge. Per-battery, and gross of conversion losses (so usually a bit higher than the grid figure). |
| Energy Metric toggle | Switches battery reports between the Net at Meter and Battery figures above. Shown only when batteries report state-of-charge. |
| Exported to grid (↑) | Energy the site sent to the grid — usually battery discharge. Shown amber. |
| Imported from grid (↓) | Energy the site drew from the grid — usually battery charging. Shown blue. |
| Participation | Whether an enrolled device took part in a given event. |
| Success rate | Share of commands a device or fleet completed successfully. |
| Response time | Time between a command being sent and the device acknowledging it. |
| Needs attention | A device flagged for one or more issues: Low success (command success rate below 85% over the window), Long response times (average acknowledgement time over 120 seconds), or Offline > 7 days. |
| Min reserve | The battery state-of-charge floor a discharge action will not go below. |