Evidence-reviewed compatibility

Check how a charger behaves before rollout.

Review anonymized production observations and controlled OCPP 1.6J test results. Evidence applies to the observed model, firmware, configuration, network path, and conditions—it is not OCPP certification.

Run a private charger testRead the test process

Observed in production

Model-level operational evidence reviewed on 14 August 2026. Counts are rounded down and require observations from at least three chargers.

EVLY ALL CHARGE

100+ chargers · 2,000+ completed sessions · 1,700+ metered sessions

  • Accepted OCPP 1.6J boot and recent online-state evidence
  • Completed charging sessions with transaction-scoped energy readings
  • Remote start, remote stop, configuration, and Smart Charging responses observed
Review ALL CHARGE evidence

Teltonika TeltoCharge EVC12100

10+ chargers · 400+ completed sessions · 300+ metered sessions

  • Accepted OCPP 1.6J boot and recent online-state evidence
  • Completed charging sessions with transaction-scoped energy readings
  • Remote-start response observed on production installations
Review TeltoCharge EVC12100 evidence

MENNEKES AMTRON 4Business

10+ chargers · 300+ completed sessions · 200+ metered sessions

  • Accepted OCPP 1.6J boot and recent connector-status evidence
  • Completed charging sessions with transaction-scoped energy readings
  • Availability-command response observed; other commands remain unclassified
Review AMTRON 4Business evidence

CTEK CS Connected v2

5+ chargers · 1,300+ completed sessions · 800+ metered sessions

  • Accepted OCPP 1.6J boot and recent online-state evidence
  • Completed charging sessions with transaction-scoped energy readings
  • Remote-start and remote-stop responses observed
Review CS Connected v2 evidence

Schneider Electric SE Charge Pro

5+ chargers · 40+ completed sessions · 30+ metered sessions

  • Accepted OCPP 1.6J boot and recent online-state evidence
  • Completed charging sessions with transaction-scoped energy readings
  • Configuration, remote control, and charging-profile responses observed
Review SE Charge Pro evidence

GreenMotion Omnibox

3+ chargers · 160+ completed sessions · 90+ metered sessions

  • Accepted OCPP 1.6J boot and operational status evidence
  • Completed charging sessions with transaction-scoped energy readings
  • Configuration and availability-command responses observed
Review Omnibox evidence

evtrip OCPP

3+ chargers · 60+ completed sessions · 50+ metered sessions

  • Accepted OCPP 1.6J boot and operational status evidence
  • Completed charging sessions with transaction-scoped energy readings
  • Configuration, remote-start, and remote-stop responses observed
Review evtrip OCPP evidence

Webasto AC Live

3+ chargers · 150+ completed sessions · 100+ metered sessions

  • Accepted OCPP 1.6J boot on multiple installations
  • Completed charging sessions with transaction-scoped energy readings
  • Command capabilities remain unclassified until directly observed or tested
Review Webasto AC Live evidence

Controlled test results

Only results with reviewed evidence and explicit publication permission belong in this directory.

What the isolated test can observe

A result is marked verified only when the expected protocol response and resulting behavior are present in bounded evidence.

OCPP connection

WebSocket negotiation and an accepted BootNotification.

Online monitoring

Heartbeat evidence that supports online-state monitoring.

Connector monitoring

Valid physical connector status messages.

Charging sessions

Observed StartTransaction-to-StopTransaction lifecycle.

Energy readings

Usable transaction-scoped energy-register samples.

Remote control

Confirmed remote start and stop with expected state changes.

Smart Charging

Temporary profile, composite-schedule query, and automatic clear.

Configuration

A correlated standard GetConfiguration response.

Availability

Temporary connector unavailability followed by restoration.

DLM prerequisites

Charger-side profile behavior only; not the site-level algorithm.

How a result reaches the directory

Publication is a separate review step after the private diagnostic.

  1. 1. Test with permissionThe owner supervises the charger or safe test load and confirms every hardware-affecting stage.
  2. 2. Review the evidenceEVCharge checks model, firmware, conditions, capability states, findings, and restoration status.
  3. 3. Approve publicationOnly the agreed model-level summary is published. Ownership tokens, passwords, identifiers, and raw private evidence stay private.