EV Admin

Connecting a station over OCPP

Set the central system URL in the charger and it shows up in the admin panel and on the map.

Charger setup

  1. Central system (CSMS) URL. wss://ev-admin.net/ocpp/<station ID> — a secure connection. For chargers without TLS there is a plain ws:// on a dedicated port (by arrangement).
  2. Protocol version. Subprotocols: ocpp1.6, ocpp2.0.1, ocpp2.1. The charger picks its own; the server replies with the same subprotocol.
  3. Station identity. The last path segment (Charge Point ID). It must match the station record in the admin panel.
  4. Authentication. Basic Auth (station ID + password) or an IP allow-list — depending on the station settings in the panel.
  5. Check. After connecting, BootNotification appears in the OCPP log and the station in the online list.

Example (OCPP 1.6J)

[2, "19223201", "BootNotification", {
  "chargePointVendor": "Vendor",
  "chargePointModel": "Model-22kW"
}]

wss://ev-admin.net/ocpp/STATION-001   (Sec-WebSocket-Protocol: ocpp1.6)

Old and new addresses

While moving from the previous server, stations may stay on the old address: both domains accept connections, so the migration happens without downtime.

Supported messages

BootNotification, Heartbeat, StatusNotification, Authorize, StartTransaction, StopTransaction, MeterValues, DataTransfer; from the central system — RemoteStartTransaction, RemoteStopTransaction, Reset, ChangeConfiguration, GetConfiguration, UnlockConnector, TriggerMessage and more. For 2.0.1/2.1 — TransactionEvent, RequestStartTransaction, RequestStopTransaction and so on.