Meter Values
Source: OCPP 2.0.1 Part 2 — Specification (Edition 2, 2022-12-15) — Section 1.32 (Messages); Use Case J01 — Sending Meter Values not related to a transaction (Functional Block J. MeterValues)
Overview
The Charging Station sends MeterValuesRequest to deliver one or more sampled meter readings not related to a transaction. For meter values inside a transaction, the CS uses TransactionEvent instead (use case J02).
NOTE (from spec): This message might be removed in a future version of OCPP — it will be replaced by Device Management Monitoring events (
NotifyEvent).
Each meterValue element contains a timestamp plus one or more sampledValue entries (measurand, context, location, phase, unit, format, signature for signed metering).
Sequence Diagram
Charging Station ──── MeterValuesRequest ────▶ CSMS
(evseId, meterValue[])
Charging Station ◀─── MeterValuesResponse ──── CSMS
Initiator
Charging Station → CSMS
Fields
| Field Name | Field Type | Card. | Description |
|---|---|---|---|
| evseId | integer (>= 0) | 1..1 | Required. EVSE of the Charging Station. 0 (zero) designates the main power meter. |
| meterValue | MeterValueType | 1..* | Required. The sampled meter values with timestamps. |
No fields are defined.
Examples
{
"evseId": 0,
"meterValue": [
{
"timestamp": "2026-04-27T12:34:56Z",
"sampledValue": [
{
"value": 12500.0,
"context": "Sample.Periodic",
"measurand": "Energy.Active.Import.Register",
"unitOfMeasure": { "unit": "Wh" }
}
]
}
]
}{}Schema
Source:
schemas/MeterValuesRequest.json,schemas/MeterValuesResponse.json(OCPP 2.0.1 FINAL)