EV chargers with OCPP: the brands in our database
An EV charger with OCPP can talk to any backend that speaks the same protocol, so you choose the software that manages it, and you can change that choice later. A charger without OCPP talks only to its maker's cloud. Plugchoice, a free OCPP backend, keeps a database of chargers with a source for every figure. The table below lists every brand in it whose AC chargers list OCPP.
What OCPP on a charger means
OCPP, the Open Charge Point Protocol, is the open standard of the Open Charge Alliance for the conversation between a charger and the software that manages it: the back office, also called the CSMS or OCPP backend. Over that connection the charger reports its status and every charging session, and the backend starts and stops sessions, checks charge cards, updates firmware and sets how much power the charger may draw.
Because the protocol is open, the backend is not tied to the hardware. You can connect the same charger to an energy supplier's platform, a fleet operator's billing system or a free backend such as Plugchoice, and switch when one stops fitting.
Which OCPP version you need
- OCPP 1.6J is the version almost every charger on the market speaks. The J stands for JSON over a WebSocket. Most backends run on it, including Plugchoice.
- OCPP 2.0.1 adds a device model, stronger security profiles and better smart charging. More new chargers list it, often together with 1.6J.
- OCPP 2.1 builds on 2.0.1 with bidirectional charging and more energy management. Few chargers list it so far.
A charger that lists both 1.6J and 2.0.1 runs one of them at a time, chosen in its configuration. The full message sets are in our OCPP 1.6J reference and OCPP 2.0.1 reference.
Chargers with OCPP, by brand
In our charger database, 263 AC chargers from 80 brands list OCPP. 52 of them also list OCPP 2.0 or later.
| Brand | Models with OCPP | OCPP versions | On Plugchoice |
|---|---|---|---|
| ABB | 1 of 1 | 1.6 | |
| ABL | 6 of 9 | 1.5, 1.6 | Supported |
| AgeVolt | 4 of 4 | 1.6 | Supported |
| Alfen | 8 of 8 | 1.6, 2.0, 2.0.1 | Confirmed |
| Amina | 1 of 2 | 1.6 | Supported |
| Amperfied | 6 of 12 | 1.6 | Supported |
| Anker | 1 of 2 | 1.6 | Supported |
| BENY | 8 of 10 | 1.6 | |
| Blink Charging | 7 of 13 | 1.6, 2.0, 2.0.1 | |
| char.gy | 3 of 5 | 1.6 | Supported |
| Charge Amps | 4 of 4 | 1.6 | Confirmed |
| ChargePoint | 5 of 6 | 1.6, 2.0.1 | |
| Circontrol | 3 of 3 | 1.6, 2.0.1 | Supported |
| Circutor | 3 of 3 | 1.6, 2.0 | |
| CTEK | 4 of 6 | 1.5, 1.6, 2.0.1 | Supported |
| Dahua | 3 of 5 | 1.6 | |
| DBT | 1 of 1 | 1.6 | Supported |
| DEFA | 2 of 8 | 2.0.1 | Supported |
| Delta | 1 of 1 | 1.6, 2.0 | |
| Easee | 7 of 7 | 1.6 | Confirmed |
| eCharge Hardy Barth | 2 of 2 | 1.6 | Supported |
| Elecq | 2 of 2 | 1.6, 2.0.1 | Confirmed |
| EN Plus | 8 of 9 | 1.6, 2.0.1 | |
| Enelion | 3 of 4 | 1.6, 2.0.1 | Confirmed |
| Ensto | 4 of 6 | 1.6 | Supported |
| eTreego | 2 of 2 | 1.6, 2.0.1 | Supported |
| Etrel | 3 of 5 | 1.6, 2.0, 2.0.1 | Supported |
| EVBox | 6 of 6 | 1.6, 2.0.1 | Supported |
| EvoCharge | 3 of 3 | 1.6 | |
| Fronius | 4 of 8 | 1.6 | |
| GARO | 3 of 8 | 1.5, 1.6 | Supported |
| Gewiss | 3 of 3 | 1.6 | |
| go-e | 8 of 8 | 1.6 | Supported |
| Grasen | 2 of 4 | 1.6 | Supported |
| Growatt | 4 of 5 | 1.6 | Confirmed |
| Hager | 3 of 8 | 1.6 | Supported |
| Huawei | 2 of 2 | 1.6 | |
| Hyundai Kefico | 1 of 1 | 1.6 | |
| Ingeteam | 2 of 2 | 1.6, 2.0.1 | Supported |
| Injet | 6 of 6 | 1.6 | |
| Juice Technology | 1 of 3 | 1.6 | |
| KEBA | 2 of 3 | 1.6 | |
| Legrand | 1 of 3 | 1.6 | Supported |
| LEKTRI.CO | 1 of 2 | 1.6 | Supported |
| Leviton | 1 of 6 | 1.6, 2.0.1 | |
| Lite-On | 4 of 4 | 1.6, 2.0.1 | |
| Loop Global | 3 of 3 | 1.6 | |
| Luobinsen | 1 of 2 | 1.6 | Supported |
| MENNEKES | 6 of 12 | 1.6 | |
| MOON | 1 of 1 | 1.6, 2.0.1 | Supported |
| Morek IT OÜ | 2 of 3 | 1.6, 2.0 | |
| myenergi | 1 of 2 | 1.6 | Confirmed |
| NRGkick | 5 of 5 | 1.6 | Supported |
| Ocular | 3 of 3 | 1.6, 2.0, 2.0.1 | Supported |
| openWB | 3 of 4 | 1.6 | Supported |
| Orbis | 5 of 6 | 1.6 | Supported |
| Peblar | 4 of 4 | 1.6 | Confirmed |
| Phihong | 4 of 6 | 1.6 | |
| Phoenix Contact | 4 of 5 | 1.6 | Supported |
| Power Electronics | 2 of 2 | 1.6 | Supported |
| Ratio | 6 of 17 | 1.6 | Confirmed |
| Rheinmetall | 1 of 3 | 1.6 | |
| Scame | 4 of 4 | 1.6 | Supported |
| Schneider Electric | 7 of 10 | 1.5, 1.6, 2.1 | Confirmed |
| Siemens | 1 of 2 | 1.6 | |
| Sigenergy | 2 of 2 | 1.6 | |
| Silla Industries | 2 of 4 | 1.6 | |
| SMA | 1 of 5 | 1.6 | |
| Smappee | 4 of 4 | 1.6 | Supported |
| Sungrow | 1 of 2 | 1.6 | Supported |
| Technagon | 6 of 6 | 1.6 | Supported |
| Teison | 3 of 3 | 1.6, 2.0.1 | Supported |
| Teltonika Energy | 5 of 5 | 1.6 | |
| Tesla | 2 of 2 | 1.6 | Supported |
| Valeo | 3 of 3 | 1.6 | Supported |
| Vestel | 4 of 4 | 1.6 | |
| Viessmann | 2 of 3 | 1.6 | Supported |
| Webasto | 3 of 4 | 1.6 | Confirmed |
| Zaptec | 1 of 3 | 1.6 | Confirmed |
| Zerova Technologies | 2 of 3 | 1.6 |
A brand that is missing here can still speak OCPP. The list holds what we could check against a public source, such as a datasheet or the maker's own page. Each brand links to its models, with the source of every figure.
The status column shows the best status of the brand's models on Plugchoice. Confirmed means we tested a model with Plugchoice; supported means it connects through standard OCPP. DC fast chargers and every other model are in the charger database.
How to check whether your charger speaks OCPP
- Look for "OCPP" on the datasheet or the product page, with a version number.
- Open the charger's configuration, usually in the installer app or the charger's web page. A charger with OCPP has a field for the backend address, a URL that starts with
ws://orwss://, often labelled OCPP server, central system or backend URL. - Check the firmware. Some home models talk only to their maker's cloud by default and get OCPP through a firmware update or an installer setting.
With that field you can point the charger at another OCPP backend. How to change your charger's OCPP backend URL walks through it.
Connecting an OCPP charger to Plugchoice
Plugchoice is a free OCPP backend for chargers with OCPP 1.6J, with a web portal and an app, and no fee per charger. You register, enter the Plugchoice WebSocket URL in the charger and it shows up in your account. Smart Charging, such as load balancing on the main fuse or charging on a dynamic tariff, is a paid module per charger.
The Plugchoice OCPP proxy also relays the charger's connection to a back office you already use, for billing or for an energy supplier, so you keep both.
Frequently asked questions
Do all EV chargers support OCPP?
No. Most chargers for businesses and public sites do. Among home chargers, many do, but some only talk to their maker's own cloud, or get OCPP later through firmware.
Is OCPP 1.6J or 2.0.1 better?
OCPP 2.0.1 is newer and more capable, but 1.6J is what nearly every backend and charger speaks today. For a home or business charger, OCPP 1.6J is enough to choose your backend freely.
Can one charger have two back offices?
Not with a direct connection: a charger opens one OCPP connection, to one backend. An OCPP proxy relays that connection, so several back offices can work with the same charger.
Sources
- Open Charge Alliance, Open Charge Point Protocol: the versions and their specifications.
- Plugchoice charger database: every model in the table, with the source and date of each figure.
How we report: Editorial policy | Corrections | Authors
The Plugchoice newsletter
News and guides on EV charging by email. You can unsubscribe at any time. Privacy policy