This page is also available in French. Switch to French

This page is also available in Spanish. Switch to Spanish

MeterValues missing or wrong: what it means and what to do

Missing meter values are not an OCPP error code. Start with the configuration: a MeterValueSampleInterval of 0 means no sampled data is sent at all (OCPP 1.6, §3.16.1).

What it means

OCPP 1.6 has two kinds of reading.

Sampled data shows the progress of a session and is set by MeterValuesSampledData and MeterValueSampleInterval. Clock-aligned data is for billing at fixed times and is set by MeterValuesAlignedData and ClockAlignedDataInterval, where 900 means every 15 minutes (OCPP 1.6, §3.16.1, §3.16.2).

Readings may arrive in MeterValues during the transaction, inside StopTransaction, or both. If StopTxnSampledData and StopTxnAlignedData are empty, StopTransaction carries no meter values in transactionData, though it still sends the final meterStop reading (OCPP 1.6, §3.16, §3.16.5, §6.49).

If a ChangeConfiguration lists even one measurand the charger does not support, the charger answers Rejected and changes nothing (OCPP 1.6, §3.16.4).

In OCPP 2.0.1

Transaction meter values travel in TransactionEvent, which replaces StartTransaction, StopTransaction and the transaction MeterValues of OCPP 1.6 (OCPP 2.0.1 Part 0, §2.2.1).

The sampled-data settings are TxUpdatedMeasurands and TxUpdatedInterval on the SampledDataCtrlr component (OCPP 2.0.1, Referenced Components and Variables, §2.7.10, §2.7.11).

Energy missing between sessions

All Register values for one transaction must increase monotonically (OCPP 1.6, §7.31).

The specification also recommends reporting register values exactly as read from the meter, not reset to zero at the start of each transaction. Then the server can check that each session starts at the reading where the previous one ended on the same connector, and spot energy lost to a hardware fault, wiring error or fraud (OCPP 1.6, §7.31).

Likely causes

MeterValueSampleInterval is 0, or the measurand you expect is not in MeterValuesSampledData (OCPP 1.6, §3.16.1).

A configuration change was Rejected because it listed a measurand the charger does not support, so the old settings stayed (OCPP 1.6, §3.16.4).

The charger was offline. It queues periodic and clock-aligned MeterValues during a transaction and sends them when the connection returns, so they arrive late (OCPP 1.6, §3.7).

First three checks

  • 1.

    Read MeterValueSampleInterval and MeterValuesSampledData with GetConfiguration (OCPP 1.6, §5.8).

  • 2.

    Look for the values in the StopTransaction transactionData.

  • 3.

    Check for offline gaps in the same window, then ask for fresh values with TriggerMessage MeterValues (OCPP 1.6, §5.17, §7.32).

What to do

  • Safe remote action

    Change the configuration to measurands the charger supports. If it answers Rejected, remove them one at a time to find the unsupported one (OCPP 1.6, §3.16.4).

  • Dispatch when

    Register values go backwards during a transaction, which the specification does not allow (OCPP 1.6, §7.31): see PowerMeterFailure.

  • Do not

    Do not bill a session whose register values go backwards until someone has reviewed it.

What to tell the customer

"Live charging data didn't reach us during your session, but the charger records the final energy reading, and it will appear in your history."

A detection rule to start from

Status Charging without MeterValues for longer than MeterValueSampleInterval plus a margin you choose, while other messages arrive: open a meter-configuration ticket.

A session that starts at a different register value from where the last one ended on the same connector: flag it for billing review.

Sources

  1. Open Charge Alliance (2017). Open Charge Point Protocol 1.6, edition 2 (opens in a new tab). §3.7 Transaction-related messages, §3.16 Metering Data, §5.8 Get Configuration, §5.17 Trigger Message, §6.49 StopTransaction.req, §7.31 Measurand, §7.32 MessageTrigger; accessed 2026-10-22.
  2. Open Charge Alliance (2025). OCPP 2.0.1 Edition 4, Part 0 – Introduction (opens in a new tab). §2.2.1 One message for all transaction related functionalities; accessed 2026-10-22.
  3. Open Charge Alliance (2025). OCPP 2.0.1 Edition 4, Part 2 – Specification (opens in a new tab). Referenced Components and Variables §2.7.10, §2.7.11 (SampledDataCtrlr); accessed 2026-10-22.

Talk to us about your chargers

What happens next

  1. Tell us about your network.
  2. Meet a Kinethra specialist.
  3. Get your chargers live on Kinethra.
  • 40,000+ chargers onlineOn the Kinethra platform.
  • OCPP 1.6 and 2.0.1Kinethra works with OCPP chargers from any manufacturer.
  • No commission on charging revenueKinethra takes none.
  1. 01Contact
  2. 02Business
  3. 03Request

Step 1 of 3

We use your details to answer your request. See our Privacy Policy for details.