OCPP
Connect and operate charge points over OCPP 1.6 and 2.0.1 with the GridOS gateway.
The GridOS OCPP gateway terminates charge-point WebSockets, normalizes session lifecycle, and feeds Dashboard and downstream systems.
Versions
| Version | Notes |
|---|---|
| OCPP 1.6 | Widely deployed JSON variant; BootNotification, Start/StopTransaction, MeterValues |
| OCPP 2.0.1 | Device model, improved security, transaction events, richer configuration |
Many fleets run a mix of 1.6 and 2.0.1. GridOS is built for that mixed reality rather than forcing a single-version cutover on day one.
Operator path
Connect a charger
Register identity and point the station at GridOS — Connect a charger.
Simulate a full session
Drive boot through stop without hardware — Simulating a charger.
Point at your CPMS
Wire WebSocket URL, subprotocol, and security profile — Connecting to your CPMS.
Protocol reference
OCPP 1.6
- Overview
- Actions — all 39 messages, one page each
- Test cases — 178 OCTT compliance cases
OCPP 2.0.1
- Overview
- Actions — message reference by functional block
- Test cases — Part 6 style compliance cases
Security
Prefer TLS-backed endpoints and the highest security profile your hardware supports. Document per-fleet exceptions — weak profiles should be intentional and time-bounded.
The left sidebar lists Overview, Actions, and Test cases only (not every message). Open the index pages below or use ⌘K search — hit labels include the protocol version (for example · OCPP 1.6) so same-named actions stay distinct.
See also
- GridOS product — Dashboard and platform architecture
- Architecture — how the gateway fits the product
- OCPI — roaming sessions that often originate from OCPP charge data