OCPP API Docs¶
Purpose¶
OCPP documentation covers Open Charge Point Protocol message schemas and package behaviour used by BetterFleet charger connection services. It is the main protocol reference for charger boot, authorization, transactions, metering, configuration, diagnostics, availability, reservations, and OCPP 1.6J or OCPP 2.0.1 message handling.
OCPP is the protocol between charging stations and the central charging-management system. In BetterFleet, charging stations open outbound WebSocket connections to Vemo Connect / bf-manage-connect, which acts as the CSMS boundary and brokers decoded charger events and commands to downstream services.
What This Covers¶
- Connection model: outbound WebSocket or secure WebSocket from charger to central system.
- Charger identity: charge point ID or charging station ID in the WebSocket path.
- OCPP 1.6J structure: charge point plus connectors,
StartTransaction/StopTransaction,MeterValues,Authorize, andStatusNotification. - OCPP 2.0.1 structure: charging station, EVSE, connector, device model,
TransactionEvent, reports, variables, and richer monitoring. - Remote operations: start or stop transaction, unlock connector, reset, change availability, set charging profiles, firmware and diagnostics flows.
- Security: Basic Auth, TLS, optional client certificates, and OCPP 2.0.1 certificate-management messages.
- Offline behaviour: buffered transactions and meter values that replay when a charger reconnects.
BetterFleet Interpretation¶
Use OCPP when the question is about charger connectivity, session lifecycle, charger status, metering, charger commands, or charger protocol compatibility. OCPP is closest to live charger operations; product concepts such as charging sessions, connector availability, remote start, remote stop, and fault handling often trace back to OCPP message flows.
The generated docs are the right place for exact protocol message support and schema behaviour. BFDev docs should explain how bf-manage-connect, bf-manage-core, depot simulation, and product surfaces use those protocol events.
Published Documentation¶
- Public docs: https://evenergi.gitlab.io/vemo/packages/vemo-ocpp-core
- Support microsite public wrapper:
bf-support-microsite/public/docs/ocpp.html - Source path:
packages/vemo-ocpp-core
Related BetterFleet Areas¶
bf-manage-connectbf-manage-corebf-depot-sim- Charger control
- Smart charging protocol interoperability
Chatbot Retrieval Terms¶
OCPP, OCPP 1.6J, OCPP 2.0.1, charge point, charger, connector, BootNotification, Authorize, StartTransaction, StopTransaction, TransactionEvent, MeterValues, StatusNotification, ChangeAvailability, configuration, diagnostics.
Notes¶
- Use the public generated docs for schema-level protocol details.
- For BetterFleet connection lifecycle and service ownership, start with
bf-manage-connectand the Manage internal diagrams.