OCPP 2.0.1 Updates*

eDRV continues to update their APIs and WebHooks for OCPP 2.0.1. This page contains key updates to APIs and Webhooks.

📘

Limited to Development Environment

These updates are currently available only in the DEVELOPMENT environment. Please contact the eDRV team for access or further information.

Updates to key APIs

The following endpoints now support new parameters:

• POST /v1.1/chargestations/{id}/connectors
  ➤ Now supports: evseId of a connector.
  ➤ If the evseId is not specified it defaults to 1
• PATCH /v1.1/connectors/{id}
  ➤ Now supports: evseId of a connector
• GET /v1.1/chargestations
  ➤ Reports evseId of the connector as chargestation[id].connectors[id].evseId
• GET /v1.1/chargestations/{id}
  ➤ Reports evseId of the connector chargestation.connectors[id].evseId
• POST /v1.1/chargestations/{id}/set_charging_profile
• POST /v1.1/chargestations/{id}/clear_charging_profile
  ➤ Both set and clear supports 1.6 style compatibility. Developers can call this API with connectorId as before.
  • eDRV assumes the requestedconnectorId is the same as evseId for OCPP 2.0.1 Chargestations.
  • Supports a new value for chargingProfilePurpose = ChargingStationMaxProfile

Updates to key Webhooks

❗️

Integration Note

The data structure changes in these Webhook events will impact existing 1.6J based integrations.

The following Webhook events have been updated for OCPP 2.0.1:

• chargestation.connector_status.updated
  • ➤ Now includes: evseId of the connector as chargestation.connectors[id].evseId
  • ➤ Includes the raw OCPP StatusNotificationRequest message as chargestation.connectors[id].raw_message
• session.updated
  • ➤ A new field called session.metrics.chargingState reports the state of the charging process (e.g. Charging, SuspendedEV etc) when reported in a transactionEvent message. These were previously communicated in 1.6 via chargestation.connector_status.updated
  • ➤ A new field called session.metrics.chargingStopReason reports the OCPP TriggerReason at the end of a charging session i.e. (TransactionEvent.eventType = Ended). 201 is a lot more verbose and defines many reasons for e.g. remote stop, cable disconnection, EV communications lost etc. For a full list of reasons please see: (see 3.82. TriggerReasonEnumType)
  • ➤ Includes the raw TransactionEvent message sent by the Chargestation as session.raw_transction_event
• Synthetic Webhook chargestation.connector_status.updated for backward compatibility for StatusNotification states
  • If a change in the current transactionInfo.chargingState is detected, then eDRV will synthetically trigger a Webhook eventchargestation.connector_status.updated. This allows applications that rely on legacy OCPP 1.6 Webhooks to continue to function with limited changes.
  • OCPP 2.0.1 ChargingState is mapped to the connector.status as follows
    • Charging, SuspendedEV, SuspendedEVSE are mapped unchanged
    • EVConnected is mapped to Preparing
    • Idle is reported as Available
  • In order to enable this, the org admin must set the include_artificial_status_notification_for_201 flag in organization settings (via the admin panel)