01Features · Operations
Every charger, every connector, one control room
A charge point is only an asset while it is answering. zevOS keeps a live WebSocket session with every charger on your network, tracks each connector through its state machine, and gives your operations team the same commands the manufacturer gave their own engineers — without a laptop at the kerb.
Charger management
OCPP 1.6J + 2.0.1
Protocols
Sub-second, typical
Command round-trip
Tracked live
Connector states
Capabilities
What this gives you
Onboard a charger in minutes
Create the station, give it an OCPP identity, and point the charger at your endpoint. The first BootNotification registers the model, firmware and connector layout automatically, and the charger appears on the dashboard as it comes up.
- Per-charger OCPP identity with rotating credentials
- Auto-discovery of connector count, type and rated power
- Bulk import for rollouts, with a dry-run before commit
- Site, sub-site and connector hierarchy that mirrors the real world
Remote commands that actually land
Every OCPP call is issued from the dashboard, queued against the live session, and logged with the charger response. If the charger is offline the command is held and reported, not silently dropped.
- RemoteStartTransaction / RemoteStopTransaction
- UnlockConnector, Reset (soft and hard), ChangeAvailability
- GetConfiguration / ChangeConfiguration with a diffable view
- TriggerMessage for on-demand status and meter values
A message log you can debug from
Every OCPP frame in both directions is stored against the charger with its timestamp, payload and result. When a charger misbehaves at 2am, the evidence is already collected.
- Full request/response payloads, searchable per charger
- Filter by action, direction, result or time window
- Correlate a driver complaint to the exact frame sequence
Configuration you can hold steady
Read a charger’s configuration keys, compare them to your standard, and push corrections. Drifted heartbeat intervals and wrong meter-value sampling are the two quiet causes of most billing disputes — both are visible here.
Specifications
The technical detail
The things a procurement team or an integration partner will ask for, stated plainly.
- Transport
- WebSocket (wss), OCPP-J subprotocol negotiation
- Versions
- ocpp1.6, ocpp2.0.1
- Authentication
- Per-charge-point identity, TLS, optional basic auth
- Heartbeat
- Configurable interval with offline detection
- Message log retention
- Configurable per tenant
Questions
What operators ask about this
Do I need a specific charger brand?
No. zevOS speaks OCPP, so any charger with a compliant OCPP 1.6J or 2.0.1 implementation can connect. Vendor quirks are handled with per-model profiles rather than by locking you to a brand.
What happens when a charger loses connectivity?
The session drop is recorded, the charger is marked offline, and its connectors stop accepting new sessions. Queued commands surface as pending rather than failing silently, and any transaction the charger buffered locally is reconciled when it reconnects.
Can I group chargers by site or by team?
Yes. Stations belong to sites, and station groups control which staff members can see or operate which chargers. Owners always see everything; restricted staff see only their groups.
Related
Works closely with
Remote diagnostics & OTA
Pull logs, read diagnostics, push firmware and clear faults remotely — so a truck roll is the last resort, not the first.
Uptime & incident management
Connectivity monitoring, fault grouping and uptime reporting per charger, per site and per contract.
Smart charging & load management
Per-connector power limits, default charging profiles and site-level load sharing — enforced on the charger, not just on paper.
See charger management working
A walkthrough against your own chargers and tariffs, rather than a demo tenant with tidy data.