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
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
The charge point begins sending Heartbeat messages at the interval specified in the BootNotification response; the CSMS replies with currentTime to keep clocks synchronized
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
On session end, the charge point sends StopTransaction with the transactionId, meterStop, and a reason; the CSMS validates and closes the transaction
Known gotchas
OCPP 1.6J message IDs must be unique per call and are echoed back in the response; reusing a message ID before receiving its response leads to call result mismatches and can break session state
The CSMS must respond to every incoming Call within a reasonable timeout; charge points typically retry or disconnect if no CallResult or CallError is received, so async processing must still reply promptly even if work is queued
TLS configuration matters: many real-world charge points have limited root CA stores and may reject server certificates from less common CAs; use widely trusted certificates and verify the charge point's TLS behavior in testing
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp