Startseite / Technische Konfiguration / Connect a charging station / Connect/Migrate an EvBox charging station

Connect/Migrate an EvBox charging station

Aktualisiert am 09. Juli 2026
Dieser Artikel ist noch nicht auf Deutsch verfügbar. Es wird die English-Version angezeigt.

This procedure describes step by step the migration of an EVBox BusinessLine G3/G4 charging station
from the Everon platform (or another) to Chargekeeper supervision.


1. Preparation before migration

1.1 Preliminary checks

  • Access to the Everon console with configuration rights.
  • Charging station visible and online in Everon.
  • Serial number and EVB-P identifier recorded (as well as the security code for connection with EvConnect)
  • Firmware up to date.
  • Inform the customer of the temporary service interruption.

1.2 Information to collect

  • APN used (e.g. everon.m2m).
  • OCPP version (1.6J).
  • Chargekeeper backend URL (e.g. wss://ocpp-j.service-evse.com/chargekeeper).
  • List of charging stations to migrate.

2. Adjusting the configuration in Everon

2.1 Disabling EVBox/Everon-specific functions

In the Everon console, open the charging station record:
Functions / Features tab, then Configuration.
Set these fields to false:

  • Auto-start charging: prevents automatic startup without authentication
  • evb_SerialAsConnectorID: removes the connector identifier based on the serial number
  • evb_ResumeAfterReset: prevents automatic resumption after restart
  • evb_ConnectorList: disables the internal EVBox connector list
  • evb_EVBFunction: disables Everon/EVBox internal functions
  • evb_DebugValues: stops sending debug values
  • evb_ConnectionInfo: stops sending Everon network info

2.2 Updating the OCPP backend (key evb_Network)

This is the master key used by EVBox to configure the APN, the OCPP URL, the protocol version and the port.

It groups together several values separated by commas:

APN_NAME, APN_USER, APN_PASS, SERVER_URL, OCPP_VERSION, SERVER_PORT

Example value adapted to Chargekeeper:

everon.m2m,x,**********,ws://ocpp-j.service-evse.com/chargekeeper,1.6J,80
  • everon.m2m: SIM APN (change it if you use your own APN).
  • x: APN user field (change it if you use your own APN).
  • ****: masked APN password (change it if you use your own APN).
  • ws://ocpp-j.service-evse.com/chargekeeper: Chargekeeper WebSocket URL.
  • 1.6J: OCPP version.
  • 80: port (use 443 with wss://).

⚠️ Do not modify evb_ServerURL alone:
this key is a mirror. Only updating evb_Network
actually reconfigures the OCPP connection.

Once evb_Network has been modified, send the configuration to the charging station from Everon.


3. Switching over to Chargekeeper

3.1 Restarting the charging station

Restart the charging station (via Everon or a brief power cut) to apply evb_Network.

3.2 Deactivation on the Everon side

Deactivate the station in Everon once the connection to Chargekeeper is confirmed.

3.3 Configuring access on Chargekeeper

In order to allow charging on the station after it connects to your Chargekeeper supervision, it is also important to remember to configure:

  • Company + zone,
  • Users,
  • User groups,
  • Tariff(s) corresponding to these zones and groups.

4. Post-migration checks

  • Verify that the charging station appears on the Chargekeeper side.
  • Check the reception of OCPP messages: BootNotification, Heartbeat, StatusNotification.
  • Run a test charging session and verify that the meterValues are correctly reported.

5. Quick checklist

  • Preparation (APN, credentials, Everon access)
  • Disabling EVBox/Everon functions
  • Updating evb_Network
  • Restart
  • Deactivation on the Everon side
  • Chargekeeper checks
  • Monitoring