Implement OCPP 1.6 or 2.0.1 charge-point-side messaging so a charging station can communicate with a central system (CSMS)
domain: openchargealliance.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Pick a protocol version — OCPP 1.6 JSON is still the most widely deployed, while 2.0.1/2.1 add smart charging, security profiles, and device management — based on what your target CSMS or charge point vendor supports.
Open a WebSocket connection from the charge point to the CSMS URL, using the charge point's identity in the URL path and negotiating the ocpp1.6 or ocpp2.0.1 subprotocol.
Implement the boot sequence: send BootNotification on startup, Heartbeat on the configured interval, and StatusNotification whenever a connector's state changes.
Implement transaction messages (Authorize, StartTransaction/TransactionEvent, MeterValues, StopTransaction) so the CSMS can bill and track charging sessions.
Handle remote-triggered messages from the CSMS (RemoteStartTransaction/RemoteStopTransaction, ChangeConfiguration, Reset) since OCPP is bidirectional over the same WebSocket.
Test against an open-source or vendor sandbox CSMS before connecting to a production network, since correct spec implementation doesn't guarantee interoperability.
Known gotchas
OCPP 1.6 and 2.0.1 are not wire-compatible — a charge point speaking 1.6 JSON cannot talk to a CSMS that only implements 2.0.1, despite similar message names.
OCPP defines the charge-point-to-CSMS protocol only; it says nothing about payment or roaming between networks — that's what OCPI is for.
Formal certification/interoperability testing through the Open Charge Alliance is a separate, often paid process from simply implementing the spec correctly.
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?