zevOS

01Features · Operations

Fix it before you drive out to it

The cost of a charging network is not the hardware; it is the van. Every fault that can be diagnosed and cleared from a desk is a site visit you did not pay for. zevOS turns the OCPP diagnostics and firmware primitives into an operations workflow your team can run without touching the protocol.

Remote diagnostics & OTA

  • On-demand log pull

    Diagnostics

  • Scheduled OTA rollout

    Firmware

  • Coded and grouped

    Faults

Capabilities

What this gives you

01

On-demand diagnostics

Request a diagnostics bundle from any charger and collect it at your endpoint. Upload progress is tracked so your team knows whether the charger is slow or simply not responding.

  • GetDiagnostics with upload status tracking
  • Retrieve logs for a specific time window
  • Attach the bundle to the incident record automatically
02

Firmware over the air

Schedule a firmware update for one charger or a whole model cohort, with a retry policy and a window that avoids your busy hours. Status transitions are recorded end to end.

  • UpdateFirmware with retry count and retry interval
  • Roll out by model, by site or by explicit selection
  • Downloading → Installing → Installed status trail per unit
  • Abort and re-attempt without losing the audit history
03

Fault codes in plain language

OCPP status notifications arrive as vendor error codes. zevOS decodes them into readable faults, groups repeated occurrences, and shows the sessions that were affected — so you can tell a genuine hardware failure from a driver who unplugged early.

  • Standard OCPP error codes mapped to human descriptions
  • Vendor error codes preserved alongside the mapping
  • Repeat-fault grouping to spot the failing unit in a cluster
04

Reset ladder

Availability change, soft reset, hard reset, connector unlock — the standard escalation, in order, from the dashboard, with the charger response recorded at each step.

Questions

What operators ask about this

Does OTA work on OCPP 1.6 chargers?

Yes. UpdateFirmware and GetDiagnostics are part of the OCPP 1.6J firmware-management profile. OCPP 2.0.1 chargers additionally support the newer log and firmware status reporting, which zevOS uses when available.

Where do diagnostics files go?

To an upload endpoint you control, referenced in the OCPP request. The resulting bundle is linked to the charger record so the operations team can find it later.

See remote diagnostics & ota working

A walkthrough against your own chargers and tariffs, rather than a demo tenant with tidy data.