This page is also available in French. Switch to French

This page is also available in Spanish. Switch to Spanish

OCPP 1.6 vs 2.0.1: what actually changes

OCPP 2.0.1 is not a setting you switch on: it is not backward compatible with 1.6, and it changes how chargers are secured, how they report sessions and how they are configured (OCPP 2.0.1 Part 0, §2). Here are the differences, from the Open Charge Alliance documents, and what they mean when you buy chargers.

The differences at a glance

  • Age

    1.6: released in October 2015; edition 2 of 2017 merged the errata without changing any message. · 2.0.1: introduced in 2020, replacing OCPP 2.0; its edition 3 was approved as an IEC standard, IEC 63584, in 2024. (OCPP 1.6, §3.1; OCPP 2.0.1 Part 0, §1.1; Open Charge Alliance)

  • Compatibility

    1.6 to 2.0.1: not backward compatible. In practice, a charger and its software must speak the same version on each link; management software can support both, and a 1.6 charger moves to 2.0.1 only if its maker offers the firmware. (OCPP 2.0.1 Part 0, §2)

  • Transport

    1.6: OCPP-J, JSON over WebSocket, or OCPP-S, SOAP. · 2.0.1: JSON over WebSocket only; WebSocket compression is required on the server and optional, but recommended, on the charger. (OCPP 1.6, §3.2; OCPP 2.0.1 Part 0, §2.7.2; Part 4, §3.3)

  • Structure

    1.6: six feature profiles, of which only Core is required. · 2.0.1: 16 functional blocks of use cases and requirements, from Security to Data Transfer. (OCPP 1.6, §3.3; OCPP 2.0.1 Part 0, §3.1, §3.2)

  • Security

    1.6: security profiles, secure firmware updates and a security event log come from a separate white paper, for OCPP-J only. · 2.0.1: part of the specification. (OCA white paper, §1, §1.4; OCPP 2.0.1 Part 0, §2.3)

  • Sessions

    1.6: StartTransaction, StopTransaction, MeterValues and StatusNotification. · 2.0.1: one TransactionEvent message for everything transaction-related; StatusNotification only reports connector availability. (OCPP 2.0.1 Part 0, §2.2.1)

  • Configuration

    1.6: configuration keys, read and changed with GetConfiguration and ChangeConfiguration. · 2.0.1: no configuration keys; the Device Model's variables are read and set with GetVariables and SetVariables, with inventory and monitoring on top. (OCPP 1.6, §5.3, §5.8; OCPP 2.0.1 Part 0, §2.1; Part 2, §1.28, §1.57)

  • Smart charging

    1.6: limits sent to the charger in charging profiles. · 2.0.1: adds direct input from an energy management system, local controllers and input from the car over ISO 15118. (OCPP 1.6, §3.13; OCPP 2.0.1 Part 0, §2.4)

    What smart charging is
  • ISO 15118 and Plug & Charge

    1.6: no ISO 15118 messages; an application note adds Plug & Charge through DataTransfer, without ISO 15118 smart charging. · 2.0.1: supports ISO 15118, with Plug & Charge and smart charging that takes input from the car. (OCA application note, §1.1, §1.3; OCPP 2.0.1 Part 0, §2.5)

    How Plug & Charge works
  • Connector status

    1.6: nine connector statuses. · 2.0.1: five connector statuses, plus a separate charging state reported during a session. (OCPP 1.6, §7.7; OCPP 2.0.1 Part 2, §3.16, §3.23)

    Both status lists, side by side
  • Drivers

    1.6: designed mainly for drivers who authorize with an RFID card. · 2.0.1: adds authorization by payment terminal, smartphone or local mechanical key, messages on the charger's display, the driver's preferred language, and tariff and cost on the display before, during and after charging. (OCPP 2.0.1 Part 0, §2.6)

Security: from add-on to requirement

OCPP-J 1.6 leaves security either to the network or to TLS, with the charger logging in by HTTP Basic authentication (OCPP-J 1.6, §6).

The Open Charge Alliance later brought the security of OCPP 2.x to 1.6 in a white paper, Improved security for OCPP 1.6-J. It adds a secure setup of the link to the server, security events and logging, and secure firmware updates, and it covers OCPP-J only, not SOAP (OCA white paper, §1, §1.4). Edition 4 is dated 5 February 2026.

Both documents define the same three security profiles: 1, unsecured transport with Basic authentication; 2, TLS with Basic authentication; 3, TLS with client-side certificates, where the charger also proves its identity with a certificate (OCA white paper, §2.1; OCPP 2.0.1 Part 2, A §1.3).

Both documents also say that profile 1 belongs only on trusted networks, for instance where a VPN links the charger and the server, and both highly recommend a profile with TLS in the field (OCA white paper, §2.1; OCPP 2.0.1 Part 2, A §1.3). The difference is status: running 2.0.1 without security is possible, but it is not considered a valid OCPP 2.0.1 implementation (OCPP 2.0.1 Part 2, A §1.3). On 1.6, the white paper itself is optional, so ask whether the firmware implements it.

Sessions and offline charging

In OCPP 1.x, a session is reported across four messages.

OCPP 2.0.1 unifies them into TransactionEvent, while StatusNotification remains only for connector availability (OCPP 2.0.1 Part 0, §2.2.1).

In 1.x the server created the transaction ID. In 2.0.1 the charger creates it, which helps sessions that start offline, and every message of a transaction carries a sequence number, so the server can check that none is missing (OCPP 2.0.1 Part 0, §2.8.2; Part 1, §7.3). A charger can also mark events that happened while it was offline (OCPP 2.0.1 Part 0, §2.8.4).

Some messages were renamed for clarity. RemoteStartTransaction became RequestStartTransaction, because it was always a request: with no cable plugged in, no transaction can start (OCPP 2.0.1 Part 0, §2.8.1).

Configuration and monitoring: the Device Model

On 1.6, the server works with a list of configuration keys, each a key and a value.

One of them, SupportedFeatureProfiles, tells it which feature profiles the charger supports (OCPP 1.6, §5.8, §9.1.29).

On 2.0.1, a charger describes how it is built as components, such as a connector, a token reader or a display, each with variables that can be read, set and monitored for changes (OCPP 2.0.1 Part 1, §4.1, §4.2). The Open Charge Alliance names inventory reporting, better error and state reporting, better configuration and customizable monitoring as the gains, aimed at operators who manage chargers from several makers (OCPP 2.0.1 Part 0, §2.1).

Makers decide how much detail they publish through the Device Model (OCPP 2.0.1 Part 0, §2.1), so two 2.0.1 chargers can still differ in what you can see remotely.

Which version should you ask for?

Funding rules are one answer.

The US minimum standards for NEVI Formula Program projects and other publicly accessible chargers funded under Title 23 require OCPP 2.0.1 (23 CFR 680.108). Our post on OCPP in 2027 covers the California and New York rules.

For new chargers, we suggest asking for 2.0.1 on the exact model and firmware you buy: security is part of the specification, and Plug & Charge with ISO 15118 smart charging needs it (OCA application note, §1.3).

For chargers you already run on 1.6, there is no need to replace working hardware. Ask the maker whether a firmware update to 2.0.1 exists for your model, and meanwhile ask your software provider which security profile each charger uses.

What to ask a charger maker

  • Which version?

    Which OCPP version does this exact model run, with which firmware: 1.6J or 2.0.1? Is a firmware update from 1.6 to 2.0.1 planned for it?

  • Which profiles?

    On 1.6, which feature profiles does it list in SupportedFeatureProfiles (OCPP 1.6, §9.1.29)?

  • Which security profile?

    On 1.6J, does the firmware implement the Improved security white paper, and which of its three profiles? On 2.0.1, which of the three security profiles does it support (OCPP 2.0.1 Part 2, A §1.3)?

  • Has it been tested?

    Is this model on the Open Charge Alliance list of products that passed its certification program, and with which certification profiles? For OCPP 2.0.1, the Core profile is mandatory; Advanced Security, Smart Charging and ISO 15118 Support are optional (Open Charge Alliance, Certification OCPP 2.0.1).

And OCPP 2.1?

OCPP 2.1 was released in January 2025.

It builds on 2.0.1, and application logic developed for 2.0.1 continues to work in 2.1. OCPP 1.6 has different application logic and is not compatible with 2.1 (Open Charge Alliance, 2025). In practice, a charger on 2.0.1 is the shorter step to 2.1.

How it works in Kinethra

Three chargers of three makers (a DC fast charger, a charger on a post and a slimmer one on a post), each on its own locked data line marked with its OCPP version, 1.6, 2.0.1 and 1.6; the three lines run side by side, never merging, each to its own server cabinet of the platform. The card reads OCPP 1.6 and 2.0.1, chargers of any manufacturer; secured: WSS, a key per charger.
0212Available12 1.62.0.11.6 OCPP1.62.0.1Chargers of any manufacturerSecuredWSS · A key per charger
  • Both versions

    Connect Business works with OCPP 1.6 and 2.0.1 chargers from any manufacturer.

  • Version per charger

    The charger list in Connect Business shows each charger's OCPP version.

  • Own key, secure channel

    Every charger has its own unique OCPP authentication key and talks to the platform over a secure WebSocket channel (WSS).

  • Plug & Charge

    Kinethra supports Plug & Charge (ISO 15118) with compatible chargers and vehicles.

  • OCPP 2.1

    OCPP 2.1 support is in development.

  • No new chargers

    OCPP chargers move to Connect Business without being replaced.

Sources

  1. Open Charge Alliance (2017). Open Charge Point Protocol 1.6, edition 2, with OCPP-J and OCPP-S (opens in a new tab). OCPP 1.6 §3.1 Edition 2, §3.2 Document structure, §3.3 Feature Profiles, §3.13 Smart Charging, §5.3 Change Configuration, §5.8 Get Configuration, §7.7 ChargePointStatus, §9.1.29 SupportedFeatureProfiles; OCPP-J 1.6 §6 Security; accessed 2026-10-26.
  2. Open Charge Alliance (2026). Improved security for OCPP 1.6-J, edition 4 (opens in a new tab). dated 2026-02-05; §1 Scope, §1.4 OCPP-J Only, §2.1 Security Profiles; accessed 2026-10-26.
  3. Open Charge Alliance (2020). Using ISO 15118 Plug & Charge with OCPP 1.6, v1.0 (opens in a new tab). §1.1 Reason for this Application Note, §1.3 About this Application Note; accessed 2026-10-26.
  4. Open Charge Alliance (2025). OCPP 2.0.1 Edition 4, Part 0 – Introduction (opens in a new tab). §1.1, chapter 2 New functionalities (§2.1–§2.8), §3.1 Overview of Specification Parts, §3.2 Functional Blocks; accessed 2026-10-26.
  5. Open Charge Alliance (2025). OCPP 2.0.1 Edition 4, Part 1 – Architecture & Topology (opens in a new tab). §4.1 Components, §4.2 Variables, §7.3 Transaction IDs; accessed 2026-10-26.
  6. Open Charge Alliance (2025). OCPP 2.0.1 Edition 4, Part 2 – Specification (opens in a new tab). A. Security §1.3 Security Profiles; §1.28 GetVariables, §1.57 SetVariables; §3.16 ChargingStateEnumType, §3.23 ConnectorStatusEnumType; accessed 2026-10-26.
  7. Open Charge Alliance (2025). OCPP 2.0.1 Edition 4, Part 4 – OCPP-J Specification (opens in a new tab). §3.3 WebSocket Compression (required for the CSMS, optional and recommended for the Charging Station); accessed 2026-10-26.
  8. Open Charge Alliance (2026). Open Charge Point Protocol (opens in a new tab). OCPP 2.0.1 introduced in 2020; edition 3 approved as IEC 63584 in 2024; page date not stated; accessed 2026-10-26.
  9. Open Charge Alliance (2025). OCPP 2.1 is now available (opens in a new tab). published 23 January 2025; compatibility with 2.0.1 and 1.6; accessed 2026-10-26.
  10. Open Charge Alliance (2026). Certification OCPP 2.0.1 (opens in a new tab). certification profiles: Core mandatory; Advanced Security, Smart Charging, ISO 15118 Support optional; page date not stated; accessed 2026-10-26.
  11. eCFR (2023). 23 CFR 680.108, Interoperability of electric vehicle charging infrastructure (opens in a new tab). §680.108(b); applicability per 680.100 and 680.102; accessed 2026-10-22.

Talk to us about your chargers

What happens next

  1. Tell us about your network.
  2. Meet a Kinethra specialist.
  3. Get your chargers live on Kinethra.
  • 40,000+ chargers onlineOn the Kinethra platform.
  • OCPP 1.6 and 2.0.1Kinethra works with OCPP chargers from any manufacturer.
  • No commission on charging revenueKinethra takes none.
  1. 01Contact
  2. 02Business
  3. 03Request

Step 1 of 3

We use your details to answer your request. See our Privacy Policy for details.