OCPP Backend Integration

Not yet reviewed

The content in this section is currently under review.

Intro

Learn more about configuring the communication between the Charging Station and the Backend.

Benifits of a Backend

A Backend provides a centralized platform for

• payment processing
• monitoring the occupation status of Charging Stations
• and much more

Before you begin

Make sure that

• a network connection is in place
• an active subscription to a Backend provider is set up
• the Charging Station is registered inside the Backend Dashboard
• for public charging infrastructure, a Charge Point ID per Charging Station is set up through an energy code provider

Configuration steps

There are two steps to connect a Charging Station to a Backend:

1. Enabling the network connection to the Backend through the Internet
2. Configuring the Backend through the Backend Dashboard

Part 1: Configuring the Charge Controller

1. Apply the following configuration:

Location in Dashboard	Parameter	Value	Info
BACKEND > Connection	Connection Type	Set this to the connection type used to access the Internet. Not set up yet? Read this guide
BACKEND > OCPP	OCPP ChargeBoxIdentity (ChargePointID)	See here for more info	ChargeBoxIdentity/ChargePointID = EVSE ID
BACKEND > OCPP	OCPP Mode	Set this to the latest mode supported by your Backend provider
BACKEND > OCPP	WebSockets JSON OCPP URL of the Backend	Set this to the URL of your Backend Example: ws://backend:8080/OCPPJProxy/v16/)

Issuing EVSE IDs

Private infrastructure

For private charging infrastructure operators, the EVSE ID (Electric Vehicle Supply Equipment ID)s can be set freely and no registration is required.

Public and semi-private infrastructure

Public and semi-private infrastucture operators need to apply for an EVSE ID (Electric Vehicle Supply Equipment ID) through an EVSE ID provider:

Region	EMA ID provider
DE	Energie Codes & Services GmbH (BDEW)
AT	Smart Mobility Power GmbH

info

Check with your country's

After registering for an EMA ID (E-Mobility Account Identifier), you can assign Charging Stations EVSE ID (Electric Vehicle Supply Equipment ID)s (ChargePointIDs). This is required to connect to your Backend.

Part 2: Configuring the Backend

1. Log into your Backend Dashboard
2. According to your Backend provider's guide, register the Charge Controller via its OCPP ChargeBoxIdentity (ChargePointID)

Part 1: Configuring the Charge Controller

1. Apply the following configuration:

Location in Dashboard	Parameter	Value
BACKEND > Connection	Connection Type	Set this to the connection type used to access the Internet. Not set up yet? Read this guide
BACKEND > OCPP	OCPP ChargeBoxIdentity (ChargePointID)	TODO:
BACKEND > OCPP	OCPP Mode	Set this to the latest mode supported by your Backend provider
BACKEND > OCPP	WebSockets JSON OCPP URL of the Backend	Set this to the URL of your Backend Example: ws://backend:8080/OCPPJProxy/v16/

Part 2: Configuring the Backend

1. Log into your Backend Dashboard
2. According to your Backend provider's guide, register the Charge Controller via its OCPP ChargeBoxIdentity (ChargePointID)

Tested Backends

These Backends are proven to work well with our Charge Controllers:

• Allego
• Chargecloud
• Datek
• Eluminocity
• e-regio
• eugebau
• garo
• hastobe
• ib-Aarau (Eniwa)
• Inselwerke
• Lancaster
• sleep and charge
• Stuttgart Gmbh
• Berlin Vattenfall
• Werke Schussental GmbH
• Virta
• Rostock
• PIONAG