Viva EV Charger Admin

-

Chargers Online

-

In Use (active sessions)

- kW

Power In Use (live draw)

- kWh

Energy Today

Sites

Fleet Availability (90 days)

Active Sessions

Remote Start

Remote Stop

System (DB overrides config.json)

Essential boot settings (mysql, ports, adminSecret) remain in config.json.

General
Availability Targets

Auth window (seconds)

Session reopen window (hours)

Reported timestamp age limit (hours)

Phantom-transaction grace (seconds)

Idle SoC threshold (%)

Idle SoC high multiplier

MeterStart backward tolerance (%)

Meter sample interval — active (seconds)

Meter sample interval — idle (seconds)

Heartbeat interval (seconds)

Heartbeat request when stale (seconds)

CSMS pokes only chargers that have gone quiet (no Heartbeat for > N s), with a per-charger cooldown. 0 disables it. Floored at 15s.

SoC-aware load balancing

When capacity is shared, favour vehicles below the SoC threshold and taper those above it. Every connected vehicle still keeps a 6 A minimum. Only applies where the charger reports State of Charge.

Enable SoC-aware balancing

SoC threshold (%)

Low-SoC boost (×)

Dynamic power sharing: when on, idle/suspended chargers release all but a 6 A reserve to actively-charging chargers, and contended chargers ramp up over a redistribution tick. Per-charger priority weight applies regardless. Default off keeps the legacy event-driven behaviour.

Enable dynamic power sharing

Enable demand-following reclaim

Demand-following: under contention, trim each charger's offer toward its actual draw + one step and re-pool the freed capacity to chargers still ramping (and reclaim on taper). Downward-only — never offers above the capacity limit. Default off; validate on the DC charger test.

Power sharing owns the session limit (trial)

Session limit ownership: when on, power sharing sends its allocation as the TxProfile of each connector with a live transaction, replacing the remote-start profile and capped at the session's permit. When off, it keeps its standing TxDefaultProfile and re-sends each session's own TxProfile at the lower of its cap and the allocation. Default off.

Enable per-connector power sharing

Per-connector sharing: allocate and send a SetChargingProfile to EACH active connector of a multi-connector charger (almost always DC) independently, instead of one charge-point-wide limit. Σ(connectors) stays within the charge point's max power (optionally each connector capped by its own rating). Default off; validate on real DC hardware. When off, multi-connector chargers receive a single charge-point-wide (connector 0) limit.

Enable departure-aware smart charging

Uses ISO 15118 NotifyEVChargingNeeds (battery capacity, target SoC, departure time) to cap a charger DOWN to the power it needs to hit its target by departure (+15% margin), freeing capacity for contended chargers; releases to the 6A floor once the EV reaches its target. Downward-only — never above the limit. Default off; validate on the DC charger test.

Reset charger between sessions

At session end, send ClearChargingProfile for that connector to wipe the custom limits this CSMS pushed (power sharing / pacing), restoring the charger to its standard state so the next session never inherits a stale limit. Connector-scoped (won't disturb another active connector). Default off; validate on the DC charger test.

Redistribution tick (s)

Min profile change (W)

Profile emission churn guard: a recomputed limit within this many watts of the last sent profile is not re-sent. Drift accumulates against the last sent value, so real changes still go out.

OCPI credential routing rules: when on, per-partner routing rules (eMAID + RFID; exact/glob/regex, configured on each partner's Routing tab) resolve the owning partner up front and skip the sequential partner authorize fan-out. Supersedes the legacy eMAID issuer-prefix routing. Default off — with no custom rules, behaviour matches the legacy 1:1 prefix routing.

Enable OCPI credential routing rules

Enable legacy eMAID issuer routing

Legacy 1:1 eMAID issuer-prefix routing. Ignored when the credential routing rules above are enabled.

Enable ISO 15118 autocharge

Master switch for autocharge. A plug-in is auto-started only when this is on AND the vehicle (EVCCID/eMAID) is enrolled with autocharge enabled.

"Move vehicle" notification at session stop

When a session stops on a site with client paid-access hours configured, notify the customer (webhook / SMS / email fallback) to move their vehicle, including the access window. Only fires for sessions with a linked End User or notification override.

Blackout notifications for live sessions

On sites with an OCPI blackout schedule: warn customers with a live session 15 minutes before a blackout starts, and again when it begins. Webhook / SMS / email fallback; once per session per event.

Trust charger-asserted authorization

For chargers that authorize a plug-in locally (cached auth / autocharge / local list) and send Started(triggerReason=Authorized) with no preceding Authorize or idToken (e.g. Kempower). When on, such a start is trusted and a session is formed. Trade-off: weak credential attribution — enable only where the charger is the authorization authority.

Kempower plug-first operator-bind

Kempower-only. A plug-first station starts the transaction at cable-plug and re-presents the vehicle's MacAddress/EVCCID — not the operator's idTag — so a manual/OCPI/webhook remote start can't authorize it and the charge ends DeAuthorized at 0 Wh. When on, an operator remote start on a Kempower binds to the connector so the next plug-first Authorize there is Accepted. Unknown plug-ins with no pending operator start still get Invalid.

Kempower plug-first re-arm

Only acts when the station accepts a start but echoes an already-ended transaction (the latched bay). Default Off. Validate on a bench charger before enabling.

Enforce API-key scopes

When on, destructive routes (/remote/reset|configuration|force-stop|force-end-session, /firmware*) require the API key to hold the specific scope (remote:control / firmware:write); admin is a superset. Provision each key's scopes BEFORE enabling — legacy api keys lose destructive access. Off = legacy role-based gating (no change).

Date-time format

Tokens: DD MM YYYY HH mm ss

Date-only format

Time-only format

RFID Canonical Format

Webhook RFID Format

Webhook URL

Webhook timeout (ms)

Webhook fallback to DB

Email host

Email port

Email secure

Email on unauthorised credential attempts

Unauthorised alert dedupe window (minutes)

Settlement queue-drain wait (minutes)

Alarm debounce window (minutes)

Critical alarm re-notification (minutes)

Alarm escalation threshold (occurrences)

Alarm trigger log retention (days)

Alarm retention (days)

Alarm trigger log cap (rows per alarm)

Banned credential enforcement

Idle energy-drift detection (power theft)

Idle energy-drift threshold (Wh/day)

Email user

Email pass

Email from name

Email from address

Email alert to

National dashboard enabled

ND access

ND display password

ND layout

Map basemap

CARTO Basemaps API key

Removes the "API key required" watermark from the three CartoDB basemaps. Get one free at carto.com/basemaps/apikey. OpenStreetMap and OpenTopoMap need no key.

Redis buffer enabled

Redis flush interval (ms)

Charger registry require registration

End-user API enabled (port 3001 — required for client frontend)

End-user API rate limit

Requests per minute per IP. Blank = 60; 0 = no limit. Applies without a restart.

Client Frontend Base URL

The public address printed in every bay-code QR. Admin only.

Default Brand

Client-frontend brand for bay codes whose site sets none

Billing & Display

Currency

Default Rate Card

Third-party monthly fee mode

How recurring third-party (roaming) monthly fees are counted.

Allow cost display (master)

Each charger must also enable cost display individually.

Default cost vendor ID OCPP 1.6 DataTransfer vendorId preset

Default cost message ID

Default cost message template Placeholders: {cost}, {costCents}, {energyKwh}, {unitRate}, {unitRateSuffix}, {chargePointId}, {transactionId}

Charger screen messages

Allow display messages (master)

Default plug-in auto-push

Mid-session price-change notice

Enable price-change notice

On chargers without live cost display, warn at session start when a time-of-use rate boundary lies ahead.

Notice horizon (hours) Only boundaries within this window after session start trigger the notice.

Notice text Vendor config groups can override this per vendor.

Default vendor ID

Text message ID

QR message ID

Clear message ID

Default plug-in text template

Default QR URL template Placeholders: {bayCodeUrl} (recommended: the connector's printed bay code), {chargePointId}, {connectorId}, {clientFrontendBase}. Blank = no plug-in QR. The old {clientFrontendBase}/charge/… default is read as {bayCodeUrl}: the client frontend has no /charge/ page.

Force stop unavailable (s)

Logging & Debug

Log level

JSON logs

Include stack traces

Debug mode

Debug health checks

Firmware base URL

Firmware allowed hosts

Comma-separated host allowlist for UpdateFirmware download URLs. Blank = derive from the firmware base URL.

PnC DataTransfer vendor allowlist

Comma-separated ISO-15118 DataTransfer vendorId allowlist for Plug&Charge. Blank = allow all (current behaviour). Set it to restrict PnC authorization/autocharge to known vendors.

Default diagnostics collector

The default for chargers with no per-charger override (set per charger on the Charge Point edit screen). HTTP/FTP upload to this CSMS (file appears in the request row); FTP suits OCPP 1.6 chargers that only upload via FTP (port/PASV range live in config.json; switching needs an OCPP restart). External sends a URL to the charger verbatim — the file lands on a third-party server and is NOT retrievable here; the External URL is configured per charger.

HTTP base URL

This CSMS's public http(s) origin for the built-in HTTP collector. Blank = derive from the charger's connection (its host and port are honoured — useful behind a firewall/port-forward).

FTP base URL

Host (and optional port) of the FTP collector — may differ from the HTTP host. Blank = the charger's connect host with the FTP listener port from config.json. The port in this URL is honoured when set.

Max upload (MB)

Upload link TTL (min)

Colour bands for the availability day-strips on the dashboard and site cards. A day is green at or above the green target, orange at or above the orange target, and red below it. Each cell is also shaded from the bottom to show that day's utilisation.

Green target (%)

Orange target (%)

Overall SLA target (%)

System-restart maintenance window (seconds)

Applies only to chargers that were connected when the service stopped, and only while they are still missing. Maintenance minutes are excluded from availability, the same as a scheduled out-of-service window.

SMS Gateway Providers

Configure ordered SMS gateway providers for failover. Providers are tried in order; first successful send wins.

Tip: click Edit to open provider settings in a modal.

Authorisation Policy

Webhook Auth Providers

Configure webhook endpoints for RFID/credential authorization. Providers are tried based on the selected policy.

Dashboard display

Settings for the public dashboard at /dashboard

EV Screens (ESP32 Displays)

Manage charger-mounted ESP32 display screens. Pending screens show an eight-character hex registration code on the screen itself: enter it below (either case) to adopt and link to a charger. A screen bound to its device key shows its code only on the screen, never here.

Adopt a Screen

Asks the charger to upload its diagnostics file (OCPP 1.6 GetDiagnostics, 2.0.1/2.1 GetLog). The charger uploads asynchronously to this server; status updates and the downloadable file appear below once received.

From (optional)

To (optional)

Requested	Action	Status	File
No diagnostics requests yet.

Site Screen Configuration

WiFi credentials, API keys, and URLs pushed to screens at a site.

All DB Settings

Edit any key-value setting. system_settings and dashboard_settings combined.

Source	Key	Value	Actions

Charger Boot Configuration

OCPP configuration keys pushed to chargers on connect. Group configs by charger type (e.g. Default, Schneider, Dahua). Use {brand_name}, {site_name}, {charge_point_id} as placeholders.

Vendor Config Groups

Per-vendor bundles of charger display and rate configuration, assigned per charger on the charger's edit form. Resolution order: per-charger override (mode enabled) → vendor group (mode inherit) → system defaults → built-in defaults. Each capability picks its own delivery: auto (protocol default), datatransfer (OCPP 1.6 vendor DataTransfer), setdisplaymessage (OCPP 2.x), or none. Rate-via-SetConfiguration is independent of the display, for vendors whose screens read pricing from a configuration key.

Dashboard Configs (Multi-Brand)

Configure multiple national dashboards. Each has a URL like /dashboard/slug.

End Users

–

Charge Credentials

–

Unassigned Credentials ›

–

Show archived

Auto Charge

Enrolled Credentials

Every credential that auto-starts a session on plug-in (autocharge enabled). Unassigned = not linked to any End User profile — it still auto-starts, but appears on no profile page; use Assign to attach it.

Sightings Log

Every plug-in that reported an EVCCID/eMAID, with the autocharge decision. Started = we auto-started it; Observed = the charger authorised the vehicle itself. Use “Enroll” on an unenrolled sighting to add it as an autocharge credential.

Banned Credentials

Power Limit Hierarchy (Sites)

Site → Meter → Cabinet group → Charger group → Charger. Limits flow from top.

Power Sharing & Metering Hierarchy

Edit Sites & Meters

Top-down power stack: grid limit → site meter (live import) → cabinet → charger group → charge point → connector. Per charger: Capacity (nameplate rating) · Offered (power currently granted — the live load-management allocation, or full capacity when nothing is throttling) · Draw (actual consumption). The gap Offered−Draw is reclaimable headroom that can be redistributed. Chargers throttled by load management (Suspended EVSE) are flagged.

Offered — power granted to the charger (live allocation, or full capacity when un-throttled) Actual draw ↻ reclaimable — Offered − Draw: offered but unused, redistributable (N−1) Throttled Load-managed (SuspendedEVSE) Per-site bar — each coloured segment is a charger's live allocation against the grid limit (not nameplate sum); the matching dot sits beside that charger's name. Colours are per-site (reused across sites). Units: kW, and A/phase where voltage & phases are known.

Loading hierarchy…

Charger Groups

Power sharing and map overlay. Assign chargers via charge point edit.

API Keys

DB-backed keys for API auth. Store new keys securely; they are shown only once.

OCPI Admin Suite

Single control centre for OCPI settings, partners, bookings, payment terminals, attempts, and diagnostics.

OCPI Settings (Routing Identity)

OCPI enabled

Party ID

Country Code

Party Name

Base URL Your OCPI base URL (e.g. https://cms.example.com)

OCPI protocol log level Writes OCPI request/response protocol logs to logs/ocpi/.

Enforce pre-authorization amount (PTP)

Stops a partner-started session before its cost exceeds the rate card's OCPI pre-authorize amount (set per rate card under Rate Cards). Protects revenue when the payment terminal holds a fixed amount — e.g. Nayax. Sessions on rate cards without a pre-authorize amount are unaffected.

OCPI Partner Liveness & Sync Defaults (Global)

Periodic GET /versions probe per OCPI HubClientInfo "still alive" pattern. Per-partner values override these defaults.

Loading liveness status…

Enable liveness checks

Interval (seconds) OCPI spec recommends starting at 300 (5 min).

Timeout (ms)

Failures before OFFLINE

CDR resend rides on the probe: a partner's undelivered CDRs are re-sent when its probe comes back CONNECTED, when you ping it by hand, or on the floor below while it stays CONNECTED. Turning liveness off turns automatic resend off with it.

CDR resend floor (minutes) Between two automatic sweeps of a partner that stayed CONNECTED.

Failed sweeps before stopping Past this only a reconnect or a manual ping re-arms the partner.

CDR resend horizon (days) Older undelivered CDRs are left for an operator.

Full sync interval (hours) Re-pushes all Locations + Tariffs to every push partner. 0 = disabled.

Token retention (days) Delete cached eMSP tokens this many days after they become invalid (revoked by push or dropped from a pull sync). Valid tokens are never deleted. 0 = keep forever.

Token audit retention (days) How long per-token audit entries (push/pull/sweep/prune actions) are kept. 0 = keep forever.

Status resync interval (s) Fallback EVSE-status sync: re-PUTs Locations (live EVSE statuses) to push partners, healing missed pushes and partner-side staleness. 0 = disabled; minimum effective interval is 60 s (values 1-59 are rounded up); 300 recommended. (Connector ocpp_status has its own resync below.)

Suppress duplicate status pushes

Enabled

Skip an EVSE/connector status PATCH when the partner already acked the same status. Stops a same-status StatusNotification burst (e.g. Preparing→Charging×3, all → CHARGING) from emitting identical PATCHes that partners like Nayax debounce and drop. Re-assertions (offline, reconnect, resync) always send. Recommended ON with a non-zero resync interval.

Connector status cooloff (s) Min spacing between per-connector ocpp_status pushes (nayax_ptp only). Bursts coalesce to the latest status, flushed once per window, so Nayax can process each update. 0 = disabled; 10 recommended.

Connector status resync interval (s) Periodic heartbeat that re-asserts every online connector's ocpp_status to nayax_ptp partners — heals updates Nayax acked but silently dropped (which drift detection can't see). 0 = disabled; min effective 60 s; 120 recommended.

Session update interval (s) Min seconds between Session cost pushes during charging (event-driven; bounded below by the charger's metering interval).

Pending session timeout (s) After a partner START_SESSION is accepted, how long to wait for the driver to plug in before pushing the session as INVALID (releases the partner's bay). Set above your slowest charger's ConnectionTimeOut.

Pending session retention (days) Delete the record of a partner-started session that stayed PENDING or ended INVALID this many days after its last change. Partners read these back with GET /sessions until then. 0 = keep forever.

OCPI Profile Defaults (Global)

Applied when site or charge point fields are blank. Charge point overrides site; site overrides global.

Default time zone

Default operator name

CPO website

Operator BusinessDetails contact, advertised in Credentials & Location.operator.

CPO logo URL

CPO logo thumbnail URL

Logo width (px)

Logo height (px)

Sub-operator name

Optional sub-operator advertised in Location.suboperator.

Energy supplier name

Energy product name

Terms & conditions URL

Tariff alt URL

Human-readable tariff page advertised in Tariff.tariff_alt_url.

Energy is green / renewable

Default tariff IDs

Default parking type

Default parking restrictions

OCPI Partners

Hub-reported connection status of OCPI parties (read-only; populated when a hub pushes ClientInfo to our HubClientInfo receiver).

OCPI Token Cache (Read-Only)

CPO-side cache of tokens received from eMSPs, used by the cache-first authorization branch. UIDs and contract IDs are masked.

The outbound bearer token we present to this eMSP (admin-only). Editing above replaces it; leave blank to keep this value.

Authorization token encoding Auto sends Authorization: Token base64(token) for OCPI 2.2/2.2.1/2.3.0 and the raw token for 2.1.1, per spec §1.1.2 — the right form for conformant partners without intervention. Inbound requests are accepted in both raw and Base64 form regardless. Use Force raw only for a 2.2+ partner that rejects Base64, or Force Base64 for a 2.1.1 partner that requires it.

Inbound spec compliance Everything this partner sends us (tokens, commands, credentials, charging profiles) is validated against the OCPI spec (field lengths, enums, country/language codes, timestamps, URL/body id match). Normal keeps accepting non-compliant payloads but logs each violation to the protocol log — safe for live integrations. Strict rejects them with OCPI 2001 Invalid or missing parameters + HTTP 400 naming the offending fields. Run a new partner on Normal, review the logged violations, then enforce Strict.

Allow API access before credentials handshake (manually-keyed partner)

Per OCPI, a partner's registration token (token A) is valid only for the versions and credentials modules — functional modules answer 401 until the credentials handshake completes. Tick this ONLY for a partner whose tokens were exchanged manually and will never handshake. Partners that existed before this feature are ticked automatically (grandfathered); untick once a partner's handshake is confirmed.

Register pushes our credentials to the partner's /credentials endpoint (POST, falls back to PUT) using the token above, then stores their returned token and discovered receiver URLs. Reset returns the partner to "not registered" (their next POST re-registers) and issues a fresh inbound token to share out-of-band — the recovery path when token exchange goes bad.

Enabled

Rate Card (tariff for OCPI sessions)

Commission Rate Card (roaming fees owed to partner)

Outbound OCPI version (CDR push)

Integration profile Select a partner-specific compatibility layer. This only affects that partner's OCPI behavior.

Enable connector public-label IDs (A4/B4) for this partner

When enabled, outbound OCPI connector IDs use your mapped public labels when available; inbound commands also accept labels.

Overrides sit between site and global defaults. Leave blank to use the chain CP → site → global.

Timezone (IANA)

Operator name

Tariff IDs (comma-separated)

Parking restrictions

Inbound token (the eMSP sends this as Authorization: Token … when calling us)

Saved tokens are registered so this eMSP can authenticate. If the eMSP gets 401 with the saved token (e.g. a handshake rotated it out), use Re-register. Use Connection info on the partner row to view everything to hand the eMSP.

Actively push Locations / Tariffs / Sessions / CDRs to this partner's receiver

Enable for eMSP/PTP partners (e.g. Nayax) who expect the CPO to push. Leave off for pull-style roaming.

Fetches the partner's /versions file and fills the module URLs below for review. Uses the URL & token on the General tab (token left blank = use the stored token). Review, then hit Save.

Locations push URL

Sessions push URL

CDRs push URL

Tariffs push URL

Periodically pull this partner's token list (self-heals missed token pushes; tokens missing from a complete pull are marked invalid)

Token pull interval (hours)

Tokens pull URL (optional)

HubClientInfo pull URL (hubs only)

Session emission cadence

How often this partner is sent an active session. A PUT carries the whole object including the charging-period breakdown; a PATCH carries only what changed (status, kWh, cost). Session start and stop are always a PUT. Turn these up if a partner asks for less traffic.

Full PUT every (seconds)

Interim PATCH every (seconds)

Blank module URLs fall back to {base url}/receiver/{version}/{module}. Set OCPI version on the General tab to 2.2.1 for Nayax.

Enable periodic liveness check for this partner

Interval (seconds, blank = global default)

Timeout (ms, blank = global default)

Authorize cut-off (ms) Hard per-check timeout on real-time token authorize calls to this partner. Partners are asked to answer in 1-2 s; a slower answer counts as no answer and the next partner is consulted. Default 2500.

Override status SUSPENDED is operator-set: probes are skipped until you flip back to PLANNED.

This partner's cached tokens (read-only; UIDs and contract IDs masked) and the per-token activity trail — pushes, pull-sync lifecycle changes, sweep invalidations and retention prunes.

UID (partial)

Valid

Recent token activity

Permit All charge points

Or allow specific sites — expand a site to include/exclude individual chargers (an unchecked site’s chargers can still be shared one-by-one):

This partner is an OCPI hub

This partner is a platform hosting several parties

A hub is one peering that relays for many eMSPs. Its requests name the real sender in OCPI-from; each eMSP behind it is registered below with its own rate cards and access, and our messages to them go through the hub addressed with OCPI-to. Unknown party behind this peering Parties the hub reports through ClientInfo are registered automatically. Under Reject they wait disabled until you enable them; new parties copy this hub's rate cards, modules and site access.

Route a credential straight to this partner instead of consulting every partner in turn. The first row is this partner's own eMAID issuer (country + party ID) and cannot be removed. Add rows for acquired issuers or RFID ranges. Patterns match the uppercased, separator-free form (write AUCFX, not AU*CFX*); glob & regex are auto-anchored. Fall-through: try this partner first, then continue to other partners only if it doesn't recognise the credential.

Type	Match	Pattern	Priority	Fall thru	On

Publishing settings

One amenity=charging_station node per publicly accessible live site. Writes are refused unless publishing is enabled and an access token has been obtained. The live map additionally needs the explicit confirmation below.

Publishing enabled

Target map

Sweep (min)

Comments (min)

Blank = default (sweep hourly, comments every 6 h), 0 = off. Sweep: otherwise 5 to 1440. Comments: 0 or 15–10080. Price changes publish within a minute unless the sweep is 0, which turns all publishing off.

Wiki page describing this editor

Linked from every changeset's description tag. Must be a page on wiki.openstreetmap.org.

OpenStreetMap account

Not connected.

Access token, if you already have one

Optional. Use this only when you already hold a bearer token. Otherwise leave it blank and use Set up connection. Write-only: never shown again once saved.

Remove the stored token

Status

Loading...

Publishable sites and every site we have ever written. Select a site to preview what would be written, change its OpenStreetMap settings, adopt an existing node, or read mappers' comments.

Site	Status	OSM object	Version	Last published	Comments	Actions

OpenADR (Demand Response)

Manage upstream VTN connections and their virtual-VENs. All OpenADR configuration lives here. During a demand-response event, power sharing continues at a reduced total capacity.

Loading…

Active curtailments

Loading…

Recent events

Loading…

Enable OpenADR (master switch)

2.0 process (A/B)

3.0 process

3.1 process (MQTT)

Dispatch mode — apply real curtailment (off = advisory only)

Report granularity (seconds)

Min curtailment floor (kW)

Event notifications

Recipient emails (comma-separated)

On event created

On event updated

On event recalled

Third Parties

For accounting: link charge points to third parties. Mark charge points as Third Party and assign.

Rate Cards

Tariff cards for pricing: flat, time-of-use, quantity tiers, composite logic, or external API. Assign to OCPI partners or use from webhook.

Admin Users

Create and manage admin users. Admin role required.

Firmware Updates

OCPP 2.0.1 UpdateFirmware. Add images with URL to firmware binary.

Trigger Update

Charge Points

Manage chargers. Set type (AC/DC), max power, and pricing.

Status

Site

Group

Show decommissioned

Availability (90 days)

Charge Point ID

Max 36 chars; letters, digits and dashes only.

OCPI EVSE UID

Group

Site

Type

Max kW

Current type

Derived from Type (DC* → DC).

Phases

AC supply phases — defaults to 3, the fleet standard. Change only for a charger not cabled 3-phase. Hidden for DC.

Rated voltage (V)

Optional grid-side line voltage (415 V 3φ / 240 V 1φ).

Vehicle-side voltage (V, DC)

DC chargers only; required before OCPI publish.

Phase rotation

Maps L1/L2/L3 to supply phases A/B/C for per-phase load balancing. Hidden for DC.

Supply meter (a capped group must stay on one meter)

The supply meter this charger draws from. Defaults to its cabinet’s meter when unset.

Power-sharing priority

-10 to 10 (default 0). Higher = more surplus and earlier minimum reservation under contention; negative deprioritises.

Vendor

Model

Serial number

Firmware

Meter type

Meter serial (NMI)

SIM ICCID

SIM IMSI

NMI manufactured on

NMI certificate ref

NMI accuracy class

NMI sealing status

Free To Charge (no auth required)

Connectors (ordered — row N is OCPP connector N)

Connector	Type	EVSE group	Max kW (opt.)	Actions

One row per physical plug (max 4); the same type can repeat (e.g. dual Type2). EVSE group maps plugs to OCPI EVSEs — an EVSE charges ONE vehicle at a time. Plugs sharing a power unit (only one usable at once) share a group; a unit charging N vehicles simultaneously uses N groups. Examples: Type2 + CHAdeMO, one vehicle → both group 1. Dual-gun simultaneous → groups 1 and 2. 4 guns / 2 vehicles → groups 1,1,2,2. Each group becomes its own EVSE at OCPI partners with stable identity; group 1 keeps this charger's existing EVSE UID.

Connector format

Advertised connectors

Connector public labels

Connector	Public Label	Actions

Map numeric connector IDs to user-facing labels (e.g. A4, B4).

Location name

OCPI Physical Reference

Max 16 chars.

Timezone

OCPI time zone

OCPI operator

OCPI tariff

Charger override. Beats the site and partner tariff.

Floor level

Accepted service providers (eMSP names, max 50 chars each)

Directions (language + text pairs — leave empty to inherit from the site; set here to override)

Images (leave empty to inherit the site's photos; set here to override)

Parking / access type

Capabilities (OCPI EVSE capabilities; remote start/stop and RFID are advertised automatically. UNLOCK_CAPABLE, RESERVABLE and CHARGING_PROFILE_CAPABLE are advertised — and the matching partner commands accepted — only when selected here. UNLOCK_CAPABLE is ignored while Connector format is Cable: a tethered cable has nothing to unlock. CHARGING_PROFILE_CAPABLE is shown only to partners whose permitted modules include Charging profiles)

Parking restrictions (leave empty to inherit site default)

Vehicle types (tip: add DISABLED to express disabled-user accessibility)

Parking detail

Restricted to type

Reservation required

Roofed

Lighting

Dangerous goods allowed

Drive-through

Direction

Max weight (kg)

Max height (m)

Max length (m)

Max width (m)

Space length (m)

Space width (m)

Time limit (min)

Standards (e.g. PAS 1899)

Charger screen — live cost display

Default is None (no cost updates). Requires system setting "Allow cost display (master)". OCPP 2.0.1 uses SetDisplayMessage; OCPP 1.6 uses DataTransfer with vendor/message below.

Cost display

Vendor ID

Message ID

Message template

Charger screen — messages & QR

Default None. Requires system "Allow display messages (master)". OCPP 2.0.1 uses SetDisplayMessage; OCPP 1.6 uses DataTransfer with vendor/message IDs below.

Display messages

Auto on plug-in

Vendor ID

Text message ID

QR message ID

Clear message ID

Plug-in text template

QR URL template

Client Frontend QR Codes

Boot Config Group

Monitoring Severity (OCPP 2.x)

SLA target (%)

Vendor Config Group

Set display modes below to Inherit to use it.

Basic Auth Required (OCPP SP1)

Bypass Charger Auth (Fail-open)

Auto-lockout on critical fault

EMAID auto-auth

EVCCID autocharge

RFID Inbound Format

Third Party charger

Third Party

Auth token

Shared power group

Diagnostics collector

Where THIS charger uploads diagnostics. Blank = the system default.

Map View

Chargers and groups. Terrain view; all chargers fit in viewport.

Sessions

Authorisation attempts across OCPP, OCPI, API, and admin flows. Click a business transaction ID for the full audit trail and linked sessions.

Filters

Start

End

Limit

Protocol

Default is All. Type/select and press Enter to add.

Charge point

Transaction ID

Failures only

Denials only

Loading authorisation audit…

Alerts

Network Alerts

Active charger errors across the fleet and recent fault history.

Active Errors

Charge Point	Connector	Site	Error Code	Details	Vendor Code	Status	Since	Actions

Recent Fault History

Severity	Charge Point	Connector	Message	Count	Time	Status	Actions

Every trigger of this alarm, newest first — repeat triggers fold onto the one alarm row but each is logged here.

Time	Error Code	Message

OpenADR Demand-Response Events

Event	Detail	Time

Error Code Knowledge Base

Vendor/model globs scope an entry to matching chargers; the error-code glob matches the charger's vendor error code first, then the generic OCPP error code. Troubleshooting shows on the Alerts and Network Alerts pages.

Availability Schedules (OOO/OOS)

Time-bound out-of-order or out-of-service for chargers. Times are in the selected timezone.

Commissions

Two independent commission streams — the same charger and session can contribute to both: third_party_commission (charger-host clip charge + monthly fees) and payment_gateway_fee (the OCPI partner's cut as payment processor, from commission rate cards).

Third-party commission (charger hosts)

Payment gateway fees (OCPI partners) Per-partner totals for the month selected above — the partner's cut per its commission rate card (gateway %, flagfall, per-kWh/idle), summed from completed OCPI sessions.

Third-party commission report

Third party

Start

End

Run the report to view commission totals.

Email Templates

Customize all outbound email templates and the PDF invoice HTML template. Select a template pack, then edit individual templates.

Template Packs

SMS Templates

Customize SMS message templates for notifications. Plain text only.

Template Types

Charge Detail Records (CDRs)

Browse CDRs for billing and audit purposes. CDRs are created for every session.

Job Queues

Monitor background job queues (email, SMS, OCPI callbacks, webhooks).

Queue Jobs

ID	Name	Status	Attempts	Created	Data

Debug Log

Live log output. Requires admin or diagnostic role.

OCPP Strict Exception Metrics

Loading...

Profile	Action	Allowed	Exception	Blocked

Compliance Snapshot Operations

Prune older than days

Loading snapshot health...

Filename	Modified	Size	Action

Compliance Audit Trail

Days

Limit

Action filter

Only failures

Loading compliance audit...

Time	Action	Status	User	Source IP	Details

OCPP Packet Logs

Days

Limit

Charge point

Direction

Contains

Loading OCPP logs...

Time	Direction	Charge Point	Message	File

OCPI Protocol Logs

Days

Limit

Phase

Direction

Contains

Loading OCPI logs...

Time	Phase	Dir	Method	Path	Status	Request ID	Source IP	Body

Live log stream

Auto-scroll

Remote Start

Remote Stop

System (DB overrides config.json)

Dashboard display

EV Screens (ESP32 Displays)

Adopt a Screen

Site Screen Configuration

All DB Settings

Charger Boot Configuration

Vendor Config Groups

Dashboard Configs (Multi-Brand)

End Users

Auto Charge

Enrolled Credentials

Sightings Log

Banned Credentials

Power Limit Hierarchy (Sites)

Add Site

Charger Groups

API Keys

OCPI Admin Suite

OCPI Partners

OCPI Token Cache (Read-Only)

Publishing settings

Status

Orphan nodes

Preview

Site settings

Adopt an existing node

Mapper comments

OpenADR (Demand Response)

Active curtailments

Recent events

Event notifications

Third Parties

Rate Cards

Admin Users

Firmware Updates

Add Firmware Image

Trigger Update

Charge Points

Map View

Sessions

Alerts

Network Alerts

Error Code Knowledge Base

Availability Schedules (OOO/OOS)

Commissions

Third-party commission (charger hosts)

Email Templates

SMS Templates

Charge Detail Records (CDRs)

Job Queues

Debug Log