Charger Support Second- and third-level support for EV charger makers

OCPP check

OCPP check

What does your EV charger report? Connect it to my OCPP backend for a few minutes and read status, error codes and configuration explained in plain language – free of charge, no sign-up, nothing to install.

OCPP check: what does your EV charger report?

Connect an EV charger to my OCPP backend for a test. The check reads status, error codes and configuration via OCPP and explains in plain language what is wrong – free of charge, no sign-up.

  1. Choose a charge point ID

    Use the suggested ID or enter your own, for example the serial number. The ID becomes part of the address; please do not use names or email addresses.

  2. Enter the backend address in the charger

    In the charger's web interface or app, enter this backend address: wss://charger-support.com/ocpp/<your charge point ID> – username and password may be left empty or set to anything; they are neither checked nor stored. The charger then reconnects.

  3. Read the result

    As soon as the charger is connected, the result appears here: vendor, model, firmware, status per connector and an explanation of the reported errors.

Keep the suggestion (recommended, hard to guess) or enter your own ID such as the serial number – 4 to 48 characters: letters, digits and . _ ~ -

Backend address for your charger

wss://charger-support.com/ocpp/

The address ends with your charge point ID. Encrypted connection (wss, port 443); OCPP 1.6J and 2.0.1.

Enter a charge point ID and click “Check”.

Important: the OCPP check is not a replacement for a charging backend. For the check, temporarily disconnect the charger from your production backend and re-enter the original address afterwards. Billing, load management and app-based activation do not work in the meantime. The check answers authorisation requests with “accepted” without verifying charging cards – so do not use it at publicly accessible charge points with billing.

The OCPP check is open to everyone – manufacturers, installers and private individuals. Any engagement beyond that is for businesses only (§ 14 German Civil Code). Only technical data of the charger is stored (ID, vendor, model, serial number, firmware, status, error codes, selected configuration values, meter readings) – no charging card identifiers. Deleted no later than 14 days after the last contact. Details in the privacy policy.

How the OCPP check works

  1. Choose a charge point ID

    The charge point ID is the name under which your charger registers with the backend; it becomes part of the address. Preferably keep the random suggestion – it is hard to guess, and only someone who knows the ID can retrieve the result. Your own ID (for example the serial number) is possible; do not use names, email addresses or other personal details. Allowed are 4 to 48 characters: letters, digits, dot, underscore, tilde and hyphen.

  2. Enter the backend address in the charger

    First note down your charger’s current backend address. Then, in the OCPP or backend settings of the web interface or app, enter the backend address shown above – including your charge point ID at the end. Username and password may be left empty or set to anything; they are neither checked nor stored. Save the setting and restart the charger or let it reconnect.

  3. Read the result and restore the charger

    As soon as the charger has reported, the result appears: vendor, model, firmware, status and error code per connector, selected configuration values, the last meter reading and an assessment in plain language. Afterwards, re-enter the original backend address – the check is not a charging backend.

Instructions per manufacturer

The names of the settings differ between manufacturers and firmware versions. The manufacturer’s documentation is authoritative; the following notes describe the usual route.

Webasto NEXT and Unite (Ampure, formerly Webasto Charging)

You reach the settings via the charger’s web interface – depending on the installation via the local network or via the charger’s Wi-Fi hotspot. In the backend or OCPP settings, enter the backend address shown above as the backend address and set the charge point ID to the chosen value. Username and password can stay empty. After saving, the charger reconnects; a restart helps if needed.

  • If the charger is part of a load management group with several units, connect only the leading charger (master) to the check; the others stay unchanged.
  • If the charger asks for a master password, you will find it in the installation documents – without it the settings are not accessible.
  • If the state stays at “no charger has reported yet”, check the internet connection, the charger’s clock and whether an older firmware can establish an encrypted connection (wss) to current certificates.
KEBA

The OCPP settings are in the charger’s web interface. Here, address and path are usually entered separately: as the address (host), enter only the domain from the backend address shown above – without “wss://” and without the path –, and as the path “/ocpp/” followed by your charge point ID. Enable the secure (encrypted) connection on port 443 and set the charge point ID to the chosen value. Leave username and password empty. After saving, the charger reconnects.

  • If the interface offers a field for the complete address, enter the backend address shown above there and leave path and port at their defaults.
  • If several chargers form a group (master/client), connect only the master to the check.
Alpitronic

The OCPP settings of the fast chargers are accessible via the web interface or the manufacturer’s service interface; access is usually reserved for the operator or the service partner. There, enter the backend address shown above as the backend address and set the charge point ID to the chosen value. After applying, the charger reconnects.

  • Please do not connect public fast chargers with billing to the check: authorisation requests are accepted without verification, and billing and activation do not work in the meantime.
  • Coordinate the check with the operator of the charger and plan a short maintenance window.
Ecotap

You reach the backend settings via the charger’s configuration interface. Enter the backend address shown above as the backend address and set the charge point ID to the chosen value; username and password may stay empty. Save and restart the charger if it does not reconnect on its own.

  • If the charger is connected through an operator or service partner, obtain their consent before changing the backend address.
Vestel

The OCPP settings are in the charger’s web interface. Enter the backend address shown above as the backend address and set the charge point ID to the chosen value; make sure the encrypted variant (wss) is selected if the interface asks for it. After saving, the charger reconnects.

  • Some firmware versions append the charge point ID to the address themselves. The check accepts both variants – with and without the appended ID.
  • With a Wi-Fi connection, first check whether the charger has internet access at all (for example via the status display of the interface).

Manufacturer and product names are used for descriptive purposes only; they do not imply partnership or certification unless stated.

General notes

Before switching, note down the current backend address, the charge point ID and any credentials. After the check, re-enter them; otherwise the charger stays disconnected from billing, load management and app activation.

The check answers the charger’s registration with the current time and a heartbeat interval. Timestamps from 1970 or far in the past indicate a missing time source (NTP) – the result points this out.

The connection is encrypted (wss over port 443, TLS 1.2 or newer) with a publicly valid certificate; the charger must know the certificate authority ISRG Root X1. OCPP 1.6J and OCPP 2.0.1 over TLS are supported – with or without username and password (this corresponds to Security Profile 2; credentials are not checked). Security Profile 3 (charger certificate) and unencrypted connections (ws, Security Profile 0 or 1) are not accepted. If the charger’s interface offers several variants, choose the one whose address starts with wss://.

What is stored – and what is not

  • Stored: charge point ID; vendor, model, serial number and firmware version; times of first and last contact, connection drops; per connector the status, error code, vendor code and additional text; selected configuration values; the last meter reading per connector; OCPP version and heartbeat interval.
  • Not stored: charging card identifiers (idTag/idToken), data on individual charging sessions, credentials the charger sends along. Authorisation requests are answered generically with “accepted”, without checking or storing the identifier.
  • Deleted automatically no later than 14 days after the charger’s last contact. Earlier on request – an informal email with the charge point ID is enough.
  • The service logs neither IP addresses nor charge point IDs in clear text; in the web server’s access log the ID is replaced by “-”. Details in the privacy policy.

How to read the result

  1. Charger: vendor, model, serial number and firmware as reported by the charger itself. If the block is missing, the charger has not registered yet (BootNotification).
  2. Connectors: status per connector (for example Available, Charging, Faulted) with error code and vendor code. An error code is explained in plain language, with possible causes and next steps.
  3. Configuration: selected values such as heartbeat interval, sampling interval or number of connectors – keys without credentials only. Unusual values appear in the assessment.
  4. Assessment: OK, note, attention or fault. “OK” means nothing unusual in the reported data – not that the charger is free of faults.
  5. If I do not know a code, the result says so. Feel free to send me vendor, model and code; I will add the explanation.

Limits of the check

  • The check is a diagnostic tool, not a charging backend: no billing, no load management, no activation of charging cards, not for permanent operation. Connections are limited in time and number.
  • The check writes nothing to the charger: no configuration change, no firmware update, no restart. It only reads what the charger reports or returns on request.
  • It does not replace an on-site analysis or an inspection by a qualified electrician – especially not for faults in the protective earth or residual current circuit.
  • Anyone who knows the charge point ID can retrieve the result. Therefore use the random suggestion or an ID that is hard to guess.
  • The check is open to everyone and does not create an engagement. For a more in-depth analysis on behalf of a business: contact or pilot case.

Send me your toughest open case.

Describe the failure pattern and the systems involved. You will receive an acknowledgement with follow-up questions.

Request a free initial call Submit a pilot case