Implement the OCPP 2.0.1 TransactionEvent lifecycle for charge-point-to-CSMS session and metering reporting

domain: openchargealliance.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Adopt OCPP 2.0.1's unified TransactionEvent message instead of 1.6's separate StartTransaction/StopTransaction/MeterValues calls
  2. Send TransactionEvent with eventType Started, Updated, or Ended over the OCPP WebSocket connection to the CSMS
  3. Populate triggerReason (e.g. CablePluggedIn, Authorized, MeterValuePeriodic, EVDeparted) to explain why the event fired
  4. Embed meterValue arrays (e.g. energy.active.import.register, power, current, SoC) directly inside the TransactionEvent payload
  5. Have the CSMS return idTokenInfo authorization status on the Started event before energy delivery proceeds

Known gotchas

Related routes

Implement OCPP 1.6 or 2.0.1 charge-point-side messaging so a charging station can communicate with a central system (CSMS)
openchargealliance.org · 6 steps · unrated
Integrate vehicle-side EV charging telemetry into a fleet management system via OCPP 2.0.1 transaction event data
openchargealliance.org · 6 steps · unrated
Connect a charge point to a Central System (CSMS) using OCPP 1.6J (JSON over WebSocket)
openchargealliance.org · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans