Upcoming changes: OCPP 2.0.1 configuration key handling

Improved OCPP 2.0.1 configuration variable naming

We have improved how OCPP 2.0.1 charger configuration variables are named and stored on the platform. The new naming format accurately represents all addressing dimensions defined in the OCPP 2.0.1 specification, making configuration management more reliable and unambiguous.

What was the issue?

Previously, configuration variable names were built by joining parts with underscores (e.g. Default_EVSE_Power, EVSE_L1_FuseRating). This format was ambiguous and there was no way to distinguish between a component instance and a variable instance, and EVSE/connector information was not encoded in the name at all. This could lead to incorrect configuration values being sent to chargers, especially for chargers with multiple EVSEs or connectors.

What has changed?

The new format uses distinct delimiters for each part of the variable address, making every configuration key unambiguous:

The new format encodes the component name, component instance, EVSE ID, connector ID, variable instance, and variable name all in a single readable key.

Do I need to do anything?

No action is required. Migration happens automatically the next time a charger reports its configuration (via NotifyReport or GetVariables). In practice, all actively connected chargers will migrate on their next boot notification cycle. Setting configuration values via Connect or API works with both old and new format keys during the transition period.

We will also update your existing configuration templates using the old-style keys automatically, and you don’t need to do anything.

If you have any questions regarding this change, feel free to contact us at our Service Desk or at support@emabler.com