Alfen · OCPP 1.6J

Not hardware-validated by 22togo Last verified 2026-11-12

Alfen Eve Single S-line

Connect an Alfen Eve Single S-line 22 kW three-phase charger to 22togo over OCPP 1.6J.

22 kW 3-phase 1 × Type 2 OCPP 1.6J

The Eve Single S-line uses the Alfen web interface. Configure the CSMS URL, Charge Point Identity, and Back office authorization Key in Connectivity → Network Profile 1 with Security Profile 2, then restart and verify.

Before you start

  • A 22togo station record with its exact identity (Charge Point ID) and OCPP auth token.
  • The OCPP server URL shown in the 22togo app for that station (including identity path).
  • The charger installed, powered, and connected to the local network (Ethernet).
  • A computer with web browser on the same network, or the ALFEN Config Tool.

Settings to enter

Use these values when configuring the charger's OCPP backend.

Setting Value Notes
Protocol OCPP 1.6J Select OCPP 1.6 JSON.
CSMS URL wss://<ocpp-host>/<identity> Use the exact URL from the 22togo app. Must include the identity path segment.
Charge Point Identity <identity> Must match the 22togo station identity exactly.
Authorization Key <ocpp_auth_token> Enter the per-station auth token from 22togo in the 'Back office authorization Key' field.
Security Profile 2 - TLS with Basic Authentication Select Security Profile 2 for wss:// connections with Basic Auth.
Network Ethernet (DHCP or Static) Alfen Eve chargers use wired Ethernet. Configure IPv4 before OCPP.

Setup steps

Follow the steps in order. Restart the charger after changing backend settings.

  1. 1

    Access the Alfen web interface

    1. Connect your computer to the same Ethernet network as the charger.
    2. Find the charger’s IP address (default: DHCP, check router or use ALFEN Config Tool).
    3. Open browser to http://<charger-ip>. 4. Log in with installer credentials (default: username installer, password alfen or on label).

    Alfen Eve chargers do not have Wi-Fi — they use wired Ethernet only. The ALFEN Config Tool (Windows) can also discover and configure the charger via USB or network.

  2. 2

    Configure network settings

    1. Go to Connectivity → General → Network Profile 1.
    2. Set IPv4 Configuration to DHCP (or Static IP with your network details). 3. Apply and verify the charger has internet access.

    If using Static IP, ensure DNS and gateway are correct for internet access.

  3. 3

    Configure OCPP backend

    1. Go to Connectivity → General → Network Profile 1.
    2. In CSMS URL, enter the full 22togo WebSocket URL including identity path (e.g., wss://ocpp.22togo.com/CHG-001).
    3. Set Security Profile to 2 - TLS with Basic Authentication.
    4. In Back office authorization Key, enter the OCPP auth token from 22togo.
    5. In Charge Point Identity, enter the exact station identity from 22togo. 6. Click Save.

    The ‘Back office authorization Key’ field is the OCPP auth token. Security Profile 2 enables Basic Auth over wss://.

  4. 4

    Restart and verify

    1. Reboot the charger (power cycle or via System → Reboot).
    2. After reboot, check Status → OCPP — should show ‘Connected’ with OCPP 1.
      1. In 22togo app, station should show ‘Online’.

    If connection fails, verify CSMS URL (including identity path), identity, and auth token. Check OCPP log in the web interface.

Charger capabilities

What this model supports with 22togo over OCPP.

  • OCPP 1.6J

  • Ethernet only

    Wired Ethernet only; no Wi-Fi or 4G on Eve Single models.

  • Web & Config Tool commissioning

  • Authorization Key (Basic Auth)

  • Smart charging profiles

  • MID meter support

Frequently asked questions

What distinguishes the S-line from Pro-line?

The S-line is the standard home model with MID meter. The Pro-line adds a display and additional connectivity options. OCPP setup is identical.

Does the S-line have a display?

No. The S-line has LED status indicators only. The Pro-line includes a touchscreen display.

Can I use a CT clamp with the S-line?

Yes. The S-line supports external CT clamp for load balancing. Configure in the web interface under External Devices.

Sources

These steps are based on public vendor documentation.