Connect a charge point to a Central System (CSMS) using OCPP 1.6J (JSON over WebSocket)

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

Steps

  1. On the charge point, configure the CSMS WebSocket URL in the format wss://<csms-host>/<path>/<chargepoint-id>; the charge point ID becomes the last path segment and must match what the CSMS expects
  2. After the WebSocket connection is established, the charge point sends a BootNotification request (action BootNotification, payload with chargePointModel and chargePointVendor); the CSMS responds with status Accepted and a heartbeatInterval
  3. The charge point begins sending Heartbeat messages at the interval specified in the BootNotification response; the CSMS replies with currentTime to keep clocks synchronized
  4. When a user initiates a session, the charge point sends Authorize (with idTag), then StartTransaction (with connectorId, idTag, meterStart, timestamp); the CSMS responds with transactionId
  5. On session end, the charge point sends StopTransaction with the transactionId, meterStop, and a reason; the CSMS validates and closes the transaction

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
Implement OCPP communication between a charging station and a central system, choosing between OCPP 1.6 and the message-based OCPP 2.0.1 or 2.1 depending on the hardware and CSMS you are integrating with
openchargealliance.org · 5 steps · unrated
Implement OCPP 1.6J firmware management so a CSMS can push firmware and monitor diagnostics upload status on a charge point.
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