Connect a charger
Point a charge point at the OCPPLab OCPP endpoint and verify BootNotification through a test session.
Use this checklist when bringing a real charge point (or a production-like simulator) onto the OCPPLab OCPP gateway.
Before you start
- Station exists in the Dashboard with a stable charge point identity
- You know the org’s OCPP endpoint URL and security profile
- Network path allows outbound WebSocket (TLS recommended)
Never paste live OCPP passwords, OCPI tokens, or client certificates into tickets, chat, or public issues. Rotate anything that may have been exposed and use Dashboard or your secret store for operational credentials.
Steps
Collect connection values
Pull identity and endpoint values from the Dashboard before you touch the station UI.
Item Source Charge point id Dashboard charger record (must match device config) CSMS / OCPP URL Charger detail in Dashboard (copy button / field on the station) Auth / certificates Org security profile (basic auth, client cert, etc.) Copy the live endpoint from Dashboard
Example hosts such as
ocpp.example.comare shape only. Open the charger in Dashboard (Managed chargers → select the station, or the create-charger success view) and copy the OCPP / CSMS URL shown for that identity. Paste that value into the station or simulator — do not invent the hostname from these docs.Configure the station
On the charger UI or config interface:
- Set protocol to OCPP JSON (1.6 or 2.0.1 as supported)
- Set the CSMS URL to the value copied from charger detail (not a docs example host)
- Apply the same security profile Dashboard expects
- Reboot or reconnect so the station opens a new WebSocket
# Shape only — paste the URL from Dashboard charger detail wss://ocpp.example.com/<env>/<charge-point-id>Verify BootNotification
Expected path:
- WebSocket connects
- Station sends
BootNotification - Central system accepts (or pending → accept after config)
- Dashboard shows the station online
If BootNotification is rejected or missing, check identity mismatch, TLS trust, and firewall rules first.
Status and heartbeat
Confirm
StatusNotification(or 2.0.1 status path) and heartbeats so the station stays green in the Dashboard after idle periods.Authorization and a test session
- Authorize with a test idTag (or remote start if enabled)
- Start and stop a short session
- Confirm the session in the Dashboard with sane meter data
Protocol references
| Version | Entry |
|---|---|
| OCPP 1.6 | Overview · Actions · Test cases |
| OCPP 2.0.1 | Overview · Actions |
The left sidebar lists Overview, Actions, and Test cases only (not every message). Open the index pages below or use ⌘K search — hit labels include the protocol version (for example · OCPP 1.6) so same-named actions stay distinct.