Implement the OCPP 2.0.1 Reservation functional block so a CSMS can reserve and cancel a charging connector.

domain: openchargealliance.org · 5 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗

Verified steps

  1. Confirm the charging station reports Reservation feature support via its device model (ReservationCtrlr component/variables).
  2. Send ReserveNowRequest from the CSMS with id, expiryDateTime, idToken, and optionally an evseId to target a specific connector.
  3. Handle the ReserveNowResponse status (Accepted, Faulted, Occupied, Rejected, Unavailable) to confirm whether the reservation was placed.
  4. Send CancelReservationRequest with the reservationId to release a reservation before it's used or expires.
  5. Rely on the charging station's automatic-release mechanism to free the connector if the driver doesn't show up by expiryDateTime.

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
Configure an OCPP 2.1 CSMS to handle V2G bidirectional power transfer sessions using the BidirectionalChargingParameters functional block
openchargealliance.org · 6 steps · unrated
Implement the OCPP 2.0.1 TransactionEvent lifecycle for charge-point-to-CSMS session and metering reporting
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