OCPP Reservation: How Reserving a Charger Actually Works
The ReserveNow and CancelReservation flow, how chargers handle the user-facing reservation experience, and the operational subtleties.
23 articles in this category
The ReserveNow and CancelReservation flow, how chargers handle the user-facing reservation experience, and the operational subtleties.
How LocalAuthList lets a charger authorize users when the back-end is unreachable. The patterns that work and the trade-offs that come with them.
Copy-paste OCPP-J JSON examples for BootNotification, Heartbeat, StatusNotification, StartTransaction, MeterValues and more, with the wire frame explained.
How OCPP handles firmware updates: the messages, the lifecycle, the security, and the operational reality of pushing updates to chargers in production.
See exactly why a charge point gets a Rejected or Pending BootNotification: reproduce it live in a browser, read the frames, and fix each cause.
OCPP 2.0.1's device model is a richer way to represent what a charger is and what it can do. How it works and why it improves on 1.6.
Walk the OCPP boot handshake, station id, and subprotocol, then connect a virtual charge point to your CSMS live over wss://, in the browser, no hardware.
TransactionEvent replaces 1.6's StartTransaction, MeterValues, and StopTransaction with one unified message. How it works and why the change matters.
How Heartbeat keeps an OCPP connection alive, what happens when it fails, and the connection-recovery patterns that make production deployments robust.
When a user starts charging via their phone app, the back-end sends RemoteStart to the charger. Here is how the message works and where it goes wrong.
A practical guide to the OCPP errors you actually see in production: what each one means, what causes it, and how to fix it.
MeterValues carries the energy data that drives billing and analytics. What it contains, how often it should fire, and where it goes wrong in production.
How OCPP smart charging works: profiles, schedules, stacking, and the operational realities of controlling charger power output via OCPP.
OCPP defines three security profiles ranging from basic to mutually-authenticated TLS. What each profile actually requires and which to use in production.
A practical guide to testing and simulating an OCPP charge point in software, with no charger and no lab. Build a real integration test suite for your CSMS.
StatusNotification carries every connector state change. The state machine, the transitions that matter, and what operational dashboards depend on.
An honest, verified rundown of free OCPP simulators and charge-point emulators: SteVe, CitrineOS, EVerest, MicroOcpp, and which one fits your test.
The two messages that bracket every charging session in OCPP 1.6, how they relate to billing, and how 2.0.1's unified TransactionEvent changes the model.
A free online OCPP simulator to watch charging-station and CSMS messages flow frame by frame: BootNotification, Authorize, TransactionEvent, and more.
The full OCPP message flow for a charging session, in order: boot, status, authorize, transaction start, MeterValues, stop. Plus a live simulator to replay it.
The OCPP BootNotification message explained: every field in 1.6 and 2.0.1, what Accepted/Pending/Rejected mean, and the failure modes that cause outages.
OCPP 1.6 vs 2.0.1 vs 2.1 compared: transaction model, security, device model, and V2G, plus which version to pick for a new deployment and how to migrate.
OCPP is how a charging station talks to its back-end. What it is, the messages it carries, how a session flows, and how 1.6, 2.0.1 and 2.1 differ.