Hilfecenter
DE
FrançaisEnglishDeutschItalianoEspañolNederlands
Chargekeeper ↗
Startseite / bornes / OCPP Configurations

OCPP Configurations

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

This guide helps you configure specific OCPP keys to ensure the proper operation of the chargers connected to your Chargekeeper supervision. The keys listed below are drawn from the official OCPP specifications and are tailored to the operational needs of your infrastructure.

OCPP Configuration Keys

AllowOfflineTxForUnknownId

  • Description: Allows the charger to start charging sessions for unknown badges when the charger is offline.
  • Recommended value: false.
  • Impact: Setting this to true can create security risks by granting charging access to unauthenticated users.

ConnectionTimeOut

  • Description: Defines the maximum duration (in seconds) between:

The presentation of an RFID badge (or payment validation via Scan & Pay) and the connection of the charging cable to the vehicle before the authorization expires.

This key is essential for delivering a good user experience, particularly in the context of Scan & Pay, by allowing the user to complete the payment process before plugging in their vehicle.

  • Recommended value: 60.

  • Impact:

    • A value that is too low can cause the authorization to expire prematurely, forcing the user to start the process over.
    • A value that is too high can introduce unnecessary delays on very busy chargers.

HeartbeatInterval

  • Description: Maximum time interval (in seconds) between two "heartbeat" messages sent by the charger to signal its availability.
  • Recommended value: 3600 (1 hour).
  • Impact: Makes it possible to verify that the charger is online and operational.

MeterValuesAlignedData

  • Description: Types of data reported by the charger during a charging session.
  • Recommended values:
    • Energy.Active.Import.Register: Energy consumption data (Wh).
    • Power.Active.Import: Active power consumed by the vehicle (W).
    • Current.Import: Current intensity (Amperes).
    • Voltage: Voltage (Volts).
    • SoC: Battery state of charge (DC chargers only).
    • Temperature: Temperature of the charger's internal components (if supported).
  • Impact: This data allows for accurate monitoring of charging sessions.

MeterValueSampleInterval

  • Description: Frequency at which electricity meter data is reported (in seconds).
  • Recommended value: 60 (1 minute).
  • Impact: If the value is 0, consumption data will not be reported to the supervision. This will result in the absence of consumption curves in the charging sessions.

ClockAlignedDataInterval

  • Description: Defines a time interval (in seconds) at which the charger periodically sends telemetry data independently of charging sessions.
  • Recommended value: 1800 (30 minutes).
  • Impact:
    • Allows the supervision to receive essential information even when no charging session is active.
    • Ensures regular monitoring of the charger's status and its components.

Data reported by the charger via ClockAlignedDataInterval:

  • Charger internal temperature: Helps monitor overheating risks.
  • Cooling fan speed: Useful for diagnosing potential thermal issues.
  • Energy meter values:
    • kWh consumed by the charger on its main power supply.
    • kWh delivered to electric vehicles through charging sessions.

Note: An interval that is too short can generate an overload of unnecessary data and impact network performance. Conversely, an interval that is too long can delay the detection of technical problems.

StopTxnAlignedData

  • Description: Types of data collected and aligned to a specific point at the end of the transaction.
  • Recommended values:
    • Energy.Active.Import.Register: Energy consumption data (Wh).
  • Impact: Allows the total energy consumed during the charging session to be calculated accurately. This data is essential for exact billing and detailed analysis.

WebSocketPingInterval

  • Description: Time interval (in seconds) between two "pings" used to keep the WebSocket connection open.
  • Recommended value: 60.
  • Impact: Keeps the connection between the charger and the supervision stable.

Note: An interval that is too short can cause connection instability. If you observe a large number of spontaneous charger reconnections, it may be worth increasing the value of this parameter. Conversely, an interval that is too long can delay the charger's reconnection to the supervision in the event of a connection loss.

Configuration Steps

  1. Access the charger list:

    • Log in to the Chargekeeper supervision and go to the Chargers section in the main menu.

  2. Edit the relevant charger:

    • Search for and select the charger to configure from the list.
    • Click the Edit icon or the charger's name to access its settings.

  3. Access the OCPP settings:

    • Once in the charger's page, open the OCPP Settings tab.
    • You will see a list of the configuration keys available for this charger.

  4. Modify the keys:

    • Look for the keys you want to configure (for example, MeterValueSampleInterval or StopTxnAlignedData).
    • Click the current value to edit it and enter the new recommended value.

  5. Save the changes:

    • After editing the keys, click the Save button to confirm your changes.

  6. Verify that the changes are applied:

    • Chargekeeper will automatically send the new configurations to the charger. Check the communication status to make sure the changes have been taken into account.

Note

Some keys require a restart to take effect. Restart the charger if necessary.

Resources and Support

If you run into difficulties during configuration or would like additional information about a specific key, please feel free to consult:

We hope this guide helps you optimize the management of your chargers with Chargekeeper!

Chargekeeper

Energie meistern. Laden vereinfachen.

© 2026 Chargekeeper — Hilfecenter