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.
Stay informed with the latest trends, insights, and developments in the electric vehicle charging industry.
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.
Why hotels increasingly offer EV charging, how to design it as an amenity, and the patterns that distinguish good from bad implementations.
The four OCPI tariff dimensions in depth: ENERGY, TIME, FLAT and PARKING_TIME, how step_size rounding works, and how restrictions gate each one.
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.
How the major EV charging networks in North America and Europe actually differ, and how to check coverage, pricing, and reliability yourself.
The CSMS is the back-end that operates a fleet of EV chargers. Here is what it does, how it fits in the stack, and how to choose one.
How money actually flows in OCPI roaming: the fees, the settlements, and how to think about the economics of cross-network charging.
How to test an OCPI implementation properly: mocks, schema validation, partner-style fixtures, and the operational tests that catch real bugs.
Run a complete OCPI 2.2.1 flow in a sandbox: credentials handshake, Locations, Sessions, Commands and CDRs, with no roaming partner needed.
Copy-paste OCPI 2.2.1 request examples: real Locations, Sessions, and CDR JSON payloads, with the HTTP method, endpoint path, and headers for each.
A step-by-step OCPI integration test workflow: handshake, versions, module smoke tests, and error handling, so nothing surprises you on go-live day.
How to plan a long EV trip: tools, charger selection, time budgeting, contingencies, and the small details that make the difference.
Standing at a charger wondering if your plug fits? Three things decide it: connector, power level, and authorization. Includes a free checker tool.
Work out EV charging time from battery size, charger kW, and your start and end SOC, plus the DC taper that flat division misses. Free tool inside.
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.
Common OCPI integration mistakes and pitfalls (pagination, idempotency, timestamps, status codes) and the concrete fix for each, from real builds.
How long it takes to charge an EV, from Level 1 to 350 kW DC fast: real charging times, the one formula that predicts any session, and the taper trap.
How OCPI security and authentication really work: bearer tokens, TLS, mTLS, the threat model, and a checklist to keep tokens from leaking.
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.
What OCPI 3.0 is positioned to change: bidirectional sessions, CDRs, tariffs, and grid services, plus how to prepare while running 2.2.1 today.
The features OCPI 2.3.0 adds: the Payments module, AFIR-ready pricing, the Parking object, North American tax support, and who should upgrade.
OCPI 2.2 vs 2.2.1 differences explained: the exact fields and enums 2.2.1 changed, what stayed the same, and whether you need to migrate.
How the OCPI HubClientInfo module lets a hub publish its connected parties, with worked PUT/GET examples, the four status values, and the gotchas that bite.
What an EV charging roaming hub is, how it solves the N-by-N problem, how hub pricing is structured, and when direct peer-to-peer wins instead.
CCS, NACS, CHAdeMO, Type 2, J1772: the 6 EV charging connectors, where each is used in North America and Europe, and which one your EV needs.
OCPI 2.1.1 to 2.2 migration in the order to actually do it: what changed, the Credentials handshake to fix first, and how to upgrade without breaking partners.
How OCPI ChargingProfiles lets an eMSP shape power on a live session: the fields, a full worked round trip, and the gotchas that quietly break it.
When to roam through a hub, when to build direct peer-to-peer integrations, and what the tradeoffs cost you in practice.
Before any data can flow between an eMSP and a CPO via OCPI, they have to negotiate. The Credentials and Versions modules are the handshake.
How eMSPs trigger start/stop/reserve actions on CPO stations via OCPI. The Commands module is what makes "Start Session" buttons in apps work.
How the OCPI Tariffs module models EV charging prices: per-kWh, per-minute, time-of-use and idle fees, with annotated JSON and step_size gotchas.
The OCPI Locations module explained: the Location/EVSE/Connector data model, push updates, evse_id format, and the gotchas that get objects rejected.
How eMSPs grant customers access to CPO stations via tokens, and how CPOs validate those tokens without ever seeing the underlying customer.
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.
CDRs (Charge Detail Records) are the final, immutable billing records exchanged via OCPI after a session completes. Here is how they work.
How CPOs stream live session data to eMSPs over OCPI: when a session starts, how much energy has flowed, and how status changes get pushed.
The three power tiers in EV charging: what each one is for, how fast each charges, and how the connectors map to each level.
CPOs operate the charging stations. eMSPs own the customer relationship. The split is the foundation of how the EV charging industry actually works.
kW is power (rate); kWh is energy (quantity). The distinction matters for chargers, batteries, and specs. The practical version.
Every OCPI release from 2.1.1 through 2.3.0, plus the 3.0 preview: what each version changed, and which one a new integration should target.
OCPI vs OCPP: one connects charging networks, the other a station to its operator. Plus OICP and ISO 15118, and which layer each lives at.
EV charging means refilling an electric vehicle's battery from an external source. The practical version every owner and professional should know.
OCPI (Open Charge Point Interface) is the protocol that lets one charging network accept another network's customers. What it is and how it works.
What this site is, what we publish, and how to get the most out of it: a quick orientation for new readers.