Connecting as a CPO
Register as a Charge Point Operator
To obtain control of Enua Charge Points via OCPP, you have to be registered as a Charge Point Operator (CPO). A CPO is an entity listed in the Enua Cloud to whom charge point data and control can be directed. There is an onboarding process to become an operator, which is free of charge. To start the process, send an email to contact@enua.io and we will get in touch.
Once you are a registered CPO, you will be listed in the Enua Installer App so electricians can select you at the point of installation. Charge Points then automatically route their data to you.
How the connection works
Each Enua charger connects to your CSMS as a standard OCPP-J WebSocket client (wss://). Enua opens and
maintains the connection on behalf of the charger; your CSMS acts as the server. The charger's OCPP identity is
its Charging Station serialNumber (the Enua Wallmount serial number — see
Architecture & Topology).
During onboarding you provide, and we jointly confirm, the connection parameters:
| Parameter | Description |
|---|---|
| CSMS endpoint | The wss:// URL of your CSMS. May include the charger identity in the path. |
| OCPP version | ocpp2.0.1 or ocpp1.6, negotiated as the WebSocket subprotocol. |
| Credentials | A per-charger identity and password, sent as HTTP Basic authentication on the WebSocket upgrade request. |
Authentication
Enua authenticates to your CSMS using HTTP Basic authentication over TLS — the Authorization: Basic header
on the WebSocket upgrade request, carrying the charger identity and its password. This corresponds to OCPP
Security Profile 1/2.
Note
Security Profile 3 (mutual TLS with client certificates) and OCPP certificate management are not currently supported. See Deviations from the Standard.
Connection and boot handshake
Once the WebSocket is established, the charger boots onto your CSMS by sending a BootNotification. Your CSMS
replies with an interval and a status; on Accepted the charger begins its normal Heartbeat and
StatusNotification traffic.
sequenceDiagram
participant CS as Enua Charging Station
participant CSMS as Your CSMS
CS->>CSMS: WebSocket upgrade (wss, Basic auth, subprotocol ocpp2.0.1/ocpp1.6)
CSMS-->>CS: 101 Switching Protocols
CS->>CSMS: BootNotification
CSMS-->>CS: BootNotificationResponse {status: Accepted, interval, currentTime}
CS->>CSMS: StatusNotification (Available)
loop every <interval> seconds
CS->>CSMS: Heartbeat
CSMS-->>CS: HeartbeatResponse {currentTime}
end
The messages exchanged during and after boot are described in Provisioning.