Content of the Article
- General information about the connection
- Configuration options
- OCPP Endpoints
- Ports
- About public and private auth URL security – BASIC AUTHORISATION
- BASICAUTH Password
General Information
This article describes the basic configuration to connect a charging station to be.ENERGISED.
You can configure your charging station using the accessible OCPP endpoints. This configuration allows you to connect to the be.ENERGISED back office using SIM card(s) or VPN certificate(s) provided by ChargePoint.
For the connection to be.ENERGISED, we currently support websocket connections based on the current OCPP specifications. A connection via SOAP is currently only supported via the OCPP Broker. In the long term, however, SOAP will be completely eliminated.
In the following article, we will discuss the configuration of the charging station for the connection to be.ENERGISED.
Configuration options
Communication protocols:
- HTTP and HTTPS for SOAP
- WS and WSS for Websocket/JSON
Based on the communication protocol configuration, the connection is made via TCP connections or WebSocket connections based on TCP/UDP. In principle, we provide encrypted endpoints for all configurations. It is recommended to use the TLS secured connections (HTTPS / WSS) even in protected networks.
Client name:
- "INSTANCE": Each client has their own subdomain (slug) that is used for the domain name.
- The client’s name is assigned by ChargePoint and cannot be changed.
Connectivity types:
To connect a charging station, we provide dedicated endpoints based on the required security levels of data communication and support from the charging station. The choice of endpoints affects the configuration of your charging station.
- Private - Secure unencrypted connection in a protected APN/VPN network via SIM cards
- Privatessl - Secure encrypted connection in a protected APN/VPN network via SIM cards
Please note that for this connection type your station must have the necessary SSL certificate to be able to set up an encrypted connection (for example DigiCert). In this context, we would like to point out that you are responsible for the validity and updating of the certificates yourself. Therefore, make sure that the certificates at your charging stations are always up-to-date. |
-
Privateauth - Private Authentication - Encrypted connection in a protected APN/VPN network with additional Basic Authentication to identify the charging station.
- Public - Encrypted connection over the Internet in conjunction with Basic Authentication. (More information on Basic Authentication can be found her) If charging stations are connected via a public communication channel, this configuration is the only connection option.
OCPP Endpoints
Based on your instance, we provide the following endpoints:
Connection type |
Protocol |
Protocol Version |
|
Private |
SOAP |
OCPP 1.5 |
http://INSTANCE.private.ocpp-broker.com/ocpp/cp/soap/15/CHARGE_POINT_ID |
|
|
OCPP 1.6 |
http://INSTANCE.private.ocpp-broker.com/ocpp/cp/soap/16/CHARGE_POINT_ID |
|
Websocket |
OCPP 1.5 |
ws://INSTANCE.private.ocpp-broker.com/ocpp/cp/socket/15/CHARGE_POINT_ID |
|
|
OCPP 1.6 |
ws://INSTANCE.private.ocpp-broker.com/ocpp/cp/socket/16/CHARGE_POINT_ID |
|
|
OCPP 2.0.1 |
ws://INSTANCE.private.ocpp-broker.com/ocpp/cp/socket/201/CHARGE_POINT_ID |
Privatessl |
SOAP |
OCPP 1.5 |
https://INSTANCE.privatessl.ocpp-broker.com/ocpp/cp/soap/15/CHARGE_POINT_ID |
|
|
OCPP 1.6 |
https://INSTANCE.privatessl.ocpp-broker.com/ocpp/cp/soap/16/CHARGE_POINT_ID |
|
Websocket |
OCPP 1.5 |
wss://INSTANCE.privatessl.ocpp-broker.com/ocpp/cp/socket/15/CHARGE_POINT_ID |
|
|
OCPP 1.6 |
wss://INSTANCE.privatessl.ocpp-broker.com/ocpp/cp/socket/16/CHARGE_POINT_ID |
|
|
OCPP 2.0.1 |
wss://INSTANCE.privatessl.ocpp-broker.com/ocpp/cp/socket/201/CHARGE_POINT_ID |
Privateauth |
SOAP |
OCPP 1.5 |
https://INSTANCE.privateauth.ocpp-broker.com/ocpp/cp/soap/15/CHARGE_POINT_ID |
|
|
OCPP 1.6 |
https://INSTANCE.privateauth.ocpp-broker.com/ocpp/cp/soap/16/CHARGE_POINT_ID |
|
Websocket |
OCPP 1.5 |
wss://INSTANCE.privateauth.ocpp-broker.com/ocpp/cp/socket/15/CHARGE_POINT_ID |
|
|
OCPP 1.6 |
wss://INSTANCE.privateauth.ocpp-broker.com/ocpp/cp/socket/16/CHARGE_POINT_ID |
|
|
OCPP 2.0.1 |
wss://INSTANCE.privateauth.ocpp-broker.com/ocpp/cp/socket/201/CHARGE_POINT_ID |
Public |
Websocket |
OCPP 1.5 |
wss://INSTANCE.public.ocpp-broker.com/ocpp/cp/socket/15/CHARGE_POINT_ID |
|
|
OCPP 1.6 |
wss://INSTANCE.public.ocpp-broker.com/ocpp/cp/socket/16/CHARGE_POINT_ID |
|
|
OCPP 2.0.1 |
wss://INSTANCE.public.ocpp-broker.com/ocpp/cp/socket/201/CHARGE_POINT_ID |
Please replace the word "INSTANCE" and "CHARGE_POINT_ID" as follows:
INSTANCE You can easily insert your instance name in the link to the backend. Access to the backend: https://example.beenergised.cloud/. Here you can enter your instance by taking the value AFTER "https://" and BEFORE ".beenergised.cloud/". In this case the INSTANCE is called "example".
CHARGE_POINT_ID Replace the CHARGE_POINT_ID with a unique station name. The chargepoint identity must not contain spaces, special characters (e.g.: +*!#) and letters not known in English (e.g.: ä, ö, ü, ß). The exception is the underline character (_), which can be used. Please also note the character limitation of 45 characters! A CHARGE_POINT_ID is required to identify the station and must therefore be unique. Newer station models often add this automatically. If this is the case, the CHARGE_POINT_ID in the URL can be ignored -> Please ask the respective manufacturer for information about this. |
Ports
For private connection variants, please enter port "80".
e.g. ws://INSTANCE.private.ocpp-broker.com:80/ocpp/cp/socket/15/CHARGE_POINT_ID
Port "443" must be used for all public and secure variants.
About the security of the Public and Private authentication-URL - BASIC AUTHENTICATION
As already described above, you have different variants of broker connection to our be.ENERGISED back office to choose from.
One of them is the public connection (public), which allows you to connect stations to be.ENERGISED that do not communicate via our internal VPN. For this, the charging station must support BASIC AUTHENTICATION. Please contact your hardware manufacturer for more information!
If you have any questions about this connection variant, please contact a sales representative or our ChargePoint be.ENERGISED support team.
The "privateauth" variant also offers you the option of additionally protecting the connection between the back office and the charging station with a username and password. Your charging station must also support BASIC AUTHENTICATION for this.
BASICAUTH Password
You can find your BASICAUTH password in your be.ENERGISED instance.
Please go to Settings/System settings/OCPP Security Settings.
Here you can view your password and also add new BASICAUTH passwords.
If you do not find the item OCPP Security Settings under Settings/System settings, then the right for this user group has not yet been enabled.
To do this, go to User management/Groups/Overview and click on the Groups icon and then the Rights button for the relevant group. Under the tab Settings you will find the item OCPP Security Settings. Set this to YES and the right is then activated for the respective user group.
For more information on rights management please have a look at this article.
Version: 2023-11-03 16:19:14 UTC