How to Integrate OCPP Smart Sockets with Your CSMS Platform-OCPP Knowledge-OCPP Smart Socket & Two-Wheeler Charging Station Manufacturer

How to Integrate OCPP Smart Sockets with Your CSMS Platform

Step-by-step guide to integrating OCPP 1.6J smart sockets with a CSMS: WebSocket endpoint, charge box identity, authorization, metering configuration and acceptance testing.

Products and Services

Review relevant products, system options, application guidance, project support, and pre-sales or after-sales services.

Information for Selection

Compare the application scenario, functional requirements, installation environment, interfaces, communication method, quantity, and project schedule.

How Information Is Verified

Confirm model numbers, technical parameters, certifications, delivery terms, and compatibility against current product documents and agreed project requirements.

Key Takeaway

Step-by-step guide to integrating OCPP 1.6J smart sockets with a CSMS: WebSocket endpoint, charge box identity, authorization, metering configuration and acceptance testing.

Why it mattersUse the article to identify the technical, market or project decision affected.

Check the evidenceFollow named standards, tests, product documents and dated primary sources.

Before actingVerify the current rule, jurisdiction, certificate scope and project conditions.

How to Integrate OCPP Smart Sockets with Your CSMS

Connecting an OCPP 1.6J smart socket to a charging platform (CSMS) is a well-defined engineering task. Here is the checklist our integration engineers use, and the one we recommend to every operator.

Step 1 — Gather Endpoint Parameters

CSMS WebSocket URL (wss://.../ocpp or similar path)
ChargeBoxId / charge point identity (unique per device, e.g. WANLIN002-XXXX)
Auth credentials (HTTP Basic or security profile per your platform)
OCPP version + profile selection (1.6J, JSON)

Step 2 — Provision the Socket

Set the central system URL, ChargeBoxId and credentials either via the device configuration interface or remotely through platform provisioning. On Wanlin sockets these are standard OCPP 1.6 configuration keys (CentralSystemURI, ChargeBoxIdentity, AuthorizationKey), changeable remotely after first connection.

Step 3 — Bring the Device Online

The socket connects over 4G Cat.1 (no site Wi-Fi needed), opens the WebSocket and sends a BootNotification. Accept it and the CSMS registers the device, its firmware version and its connector inventory (WANLIN-002 reports connectors 0/1/2; WANLIN-010 reports 0/1–10).

Step 4 — Configure Operations

Authorization: choose platform auth (Authorize request per session), local whitelist (Local Authorization List, 500 cards) or both.
Metering: set MeterValues sampling and confirmation intervals; Wanlin reports 0.001 kWh resolution for billing.
Smart charging: push ChargePointMaxProfile for site limits and TxProfile for per-session/per-socket schedules.
Heartbeat & status: tune HeartbeatInterval and confirm per-connector StatusNotification handling.

Step 5 — Acceptance Test

Run one full session end-to-end: scan/card authorize → StartTransaction → MeterValues streaming → StopTransaction → invoice on platform. Then test the failure paths: kill the network mid-session (session must continue and back-fill), pull overload (per-socket protection + Faulted status on that connector only), and push an OTA firmware update.

Conclusion: with a compliant 1.6J device, integration is configuration, not development. Wanlin provides the configuration key list, message examples and joint debugging support for the WANLIN-002/010 so your CSMS integration typically completes within days.