This page is also available in French. Switch to French

This page is also available in Spanish. Switch to Spanish

OtherError and InternalError: what they mean and what to do

InternalError: "Error in internal hard- or software component". OtherError: "Other type of error. More information in vendorErrorCode" (OCPP 1.6, §7.6).

What it means

The clue is in vendorErrorCode and info; in OCPP 2.0.1, in techCode and techInfo (OCPP 1.6, §6.47; OCPP 2.0.1, §2.22).

Likely causes

Almost anything: the code itself says little until you read the vendor detail.

First three checks

  • 1.

    Read vendorErrorCode and info before you do anything else: for OtherError, the specification itself points there (OCPP 1.6, §7.6).

  • 2.

    Look the code up in the manufacturer's documentation for that model and firmware version. The specification leaves the meaning of vendorErrorCode to the vendor (OCPP 1.6, §6.47).

  • 3.

    Same code on the same model, firmware version or site? Group the events before you contact the manufacturer.

What to do

  • Safe remote action

    At most one remote reset, if the manufacturer allows it. Start with Soft: a Hard reset is "a last resort solution" where queued information "might get lost" (OCPP 1.6, §5.14).

  • Dispatch when

    The error comes back after the reset, or the vendor code points to a hardware fault. Contact the charger manufacturer with the vendorErrorCode, the model and the firmware version.

  • Do not

    Do not dispatch before reading the vendor code, and never automate a reset loop.

What to tell the customer

"Your charger reported an internal error.

We've restarted it remotely and will arrange a repair with the manufacturer if the error returns."

A detection rule to start from

When the error code is OtherError or InternalError and the vendorErrorCode is not in your dictionary: open a "new vendor code" ticket and add the code to the dictionary after diagnosis.

What industry data shows

A 2024 NREL report cites 2023 network-monitoring data from one charging network company: internal station faults and errors made up 38% of the causes of no-charge events in that data (NREL, August 2024, Table 4).

These are the network's categories, not OCPP error codes.

Sources

  1. Open Charge Alliance (2017). Open Charge Point Protocol 1.6, edition 2 (opens in a new tab). §5.14 Reset, §6.47 StatusNotification.req, §7.6 ChargePointErrorCode; accessed 2026-10-22.
  2. Open Charge Alliance (2025). OCPP 2.0.1 Edition 4, Part 2 – Specification (opens in a new tab). §2.22 EventDataType (techCode, techInfo); accessed 2026-10-22.
  3. National Renewable Energy Laboratory (2024). Impact of Electric Vehicle Charging Station Reliability, Resilience, and Location on Electric Vehicle Adoption, NREL/TP-5R00-89896 (opens in a new tab). §2.2.3 Top Causes of No-Charge Events, Table 4 (p. 9); accessed 2026-10-22.

Talk to us about your chargers

What happens next

  1. Tell us about your network.
  2. Meet a Kinethra specialist.
  3. Get your chargers live on Kinethra.
  • 40,000+ chargers onlineOn the Kinethra platform.
  • OCPP 1.6 and 2.0.1Kinethra works with OCPP chargers from any manufacturer.
  • No commission on charging revenueKinethra takes none.
  1. 01Contact
  2. 02Business
  3. 03Request

Step 1 of 3

We use your details to answer your request. See our Privacy Policy for details.