Deviations from the Standard

Enua implements OCPP 2.0.1 and 1.6, but — like every real-world implementation — it does not implement every optional feature, and it adds a few of its own. This page collects every deviation in one place so you can plan your integration. Each item links to where it is discussed in detail.

Note

Charger-side behavior below was verified against current Enua charger firmware. Some details (in particular the exact TriggerMessage set and supported measurands) may vary by charger model — confirm with Enua for your specific hardware if it is critical to your integration.

Topology

Area	Deviation	More
EVSE / Connector count	Every Enua charger is a Charging Station with exactly one EVSE and one Connector. evseId and connectorId are always 1 on transmit and ignored on receive.	Architecture & Topology
Charging Station identity	The serialNumber identifying the Charging Station is the serial number of the Enua Wallmount, not the charger unit, so chargers can be swapped without reconfiguration (e.g. if replacing a charger during service).	Architecture & Topology

Connection & security

Area	Deviation	More
Security profiles	Only HTTP Basic authentication over TLS (Security Profile 1/2) is supported. Security Profile 3 (mutual TLS with client certificates) is not supported.	Connecting as a CPO
Certificate management	OCPP certificate management (InstallCertificate, CertificateSigned, SignCertificate) and ISO 15118 certificate signing are not supported.	—

Messages not supported

Message / feature	Behavior	More
DataTransfer	Inbound DataTransfer is always rejected (Status: Rejected). Note that the current docs of some CSMSs assume it is available; on Enua it is not.	—
Reservation (ReserveNow, CancelReservation)	Not supported.	—
Firmware Management over OCPP (UpdateFirmware, FirmwareStatusNotification)	Not supported over OCPP — Enua chargers are updated by Enua directly.	—
Standalone MeterValues trigger	MeterValues cannot be triggered on demand (see TriggerMessage below). Meter values are delivered as part of transactions.	Transactions

Limited support

Area	Deviation	More
TriggerMessage	Only BootNotification, Heartbeat, StatusNotification, and (2.0.1) TransactionEvent can be triggered. Any other requested message returns NotImplemented.	Remote Control
Measurands	Meter sampling reports Energy.Active.Import.Register.	Supported Configuration Keys

OCPP 1.6 ⇄ 2.0.1 translation caveats

Enua chargers are natively OCPP 2.0.1. When your CSMS uses OCPP 1.6, Enua translates transparently, with a few consequences to be aware of:

Area	Caveat	More
Transaction id	The native 2.0.1 string transactionId is mapped to a 1.6 integer. The mapping is stable for the life of a transaction.	Transactions
Transaction messages	The single 2.0.1 TransactionEvent stream is split into 1.6 StartTransaction / MeterValues / StopTransaction.	Transactions
Untranslatable values	Some 2.0.1 enum values (certain measurands, units, and trigger reasons) have no 1.6 equivalent. Where no mapping exists, the value is not forwarded.	—

Enua-specific extensions

These are additions beyond the OCPP standard. They use the Enua origin in Supported Configuration Keys, and where a message body is involved, an Enua vendor id in the customData field.

Extension	Description	More
Free Charging	Charge without authenticating each session, via a configured virtual RFID tag.	Custom Extensions → Free Charging
AutoCharge	Authorize automatically from the vehicle's identity, without a card or app.	Custom Extensions → AutoCharge
Permalock	Keep the charging cable permanently locked to the EVSE.	Custom Extensions → Permalock