Standards and compliance status
Which standards EdgeTech hardware and software implement, at what revision, with one of five literal status words: Shipped, Implemented on order, Tested, Planned, Not. IEC 61851, IEC 62752, Modbus RTU (open), DSMR 5 P1, GridShield, SG-Ready and evcc shipped; Matter over Thread and OCPP 1.6J implemented on order; S2, EEBus, ISO 15118 module and NTA 8043 planned or on request; MID on request; no V2G yet.
Status words on this page have fixed meanings, because agents pass them through. Shipped: in products customers buy today. Implemented, on order: a working implementation, finished into a product when a customer orders it. Tested: working in our lab or a pilot, not yet in a product. Planned: on the roadmap, no code yet. Not: not supported and not planned.
Summary
| Standard | Revision | Status | Where |
|---|---|---|---|
| IEC 61851-1 (Mode 3 AC charging) | 2017 | Shipped | EVSE-C-3x32A, all chargers |
| IEC 61851-23 Ed. 2 (EV wake-up by CP disconnect) | 2023 | Shipped | EVSE-C-3x32A firmware 2.10.17, April 2025 |
| IEC 62752 (residual DC detection, 6 mA) | 2016 + A1 | Shipped | DC-leakage sensor in every charger |
| Modbus RTU over RS485, open and documented | — | Shipped | Charge controller (slave); site controllers and GridShield receiver (master) |
| DSMR 5 / ESMR 5 P1 | 5.0.2 | Shipped | EVSE-SC-02; only DSMR 5 meters work with load balancing |
| MQTT over TLS (device to platform) | — | Shipped | Site controllers, EdgeTech platform |
| SG-Ready (heat pump 2-contact interface) | BWP 2013 | Shipped | GridShield receiver relays; Matter SG-Ready module |
| GridShield (ElaadNL), LoRa point-to-point | — | Shipped | Controller and receiver, tested against ElaadNL both ways |
| evcc device template | smartevse | Shipped | Official template, EdgeTech-maintained |
| LoRa 868 MHz (EN 300 220) | — | Shipped | GridShield |
| Matter 1.4 Energy EVSE device type (0x050C) over Thread | 1.4 | Implemented, on order | Matter over Thread set; not CSA-certified, certification on request |
| Matter Electrical Power Measurement (0x0090) | 1.4 | Implemented, on order | Charger module and P1 meter reader |
| OCPP 1.6J | 1.6 | Implemented, on order | Working implementation, not yet deployed |
| ISO 15118-2 / -20 (digital communication, SoC on AC, vehicle ID) | -2:2014, -20 | Implemented, on order | ISO 15118 module, add-on, expensive |
| S2 (EN 50491-12-2) | 2024 | Planned | Site controller and GridShield as S2 resource managers |
| EEBus SPINE/SHIP (heat-pump use cases) | — | Planned | Supported interface for heat pumps, on order |
| NTA 8043 / NCS 8043:2026 (NL smart charging, self-declaration) | 2026 | Planned | Self-declaration package on request; not filed yet |
| MID (legal metering) | — | Implemented, on order | MID certification of the on-board measurement as a paid option; no external meter, only a display |
| V2G / bidirectional | — | Not | Under investigation; nothing claimed |
| OCPP 2.0.1 / 2.1 | — | Not | Not until 1.6J is in production |
IEC 61851 — shipped
The EVSE-C-3x32A implements IEC 61851-1 Mode 3: control pilot PWM with states A, B, C and D exposed in the Modbus State register, proximity pilot reading for cable rating, contactor control, and the 6 A minimum. The declaration of conformity references IEC 61851-22.
Firmware 2.10.17 (April 2025) added the wake-up procedure of IEC 61851-23 Edition 2: a controlled control-pilot disconnect that brings vehicles back from deep sleep after a long pause, needed for several 2022+ vehicles that otherwise never resume. It is configurable per socket (AUTO_CP_DISCONNECT, EV40_CP_DISCONNECT) because a few vehicles react badly to it.
Phase switching: 1-phase to 3-phase during a session is supported with a mandatory 10 s pause; the same behaviour EdgeTech contributed to evcc.
IEC 62752 — shipped
The DC-leakage sensor, part of every charger, detects DC residual current above 6 mA and the charge controller opens the contactor within about 300 ms. This is what allows a Type A RCD upstream. See the sensor page.
Modbus RTU — shipped
Every charge controller is a Modbus RTU slave. The full register map, with the semantics of every field, is on the Modbus registers page and in the open-source repository. Third-party controllers can drive the board with two registers: State (0x0103) and RemoteMaxCurrent (0x0201).
DSMR / ESMR 5 P1 — shipped
The EVSE-SC-02 parses the P1 telegram of DSMR 5.0 and ESMR 5.0 meters at 1 s intervals, including per-phase delivered and returned power. Belgian Fluvius meters work. DSMR 4 (10 s interval, unpowered port) and Austrian encrypted P1 do not. Fields used: P1 telemetry.
Matter — implemented, on order
A retrofit module (ESP32-C6, Thread) attaches to the charge controller over Modbus and exposes it as a Matter 1.4 Energy EVSE device (device type 0x050C):
| Cluster | ID | Implemented |
|---|---|---|
| Energy EVSE | 0x0099 | State, SupplyState, FaultState, session ID/duration/energy, per-phase readings; commands Disable, EnableCharging(min, max), SetTargets, GetTargets, ClearTargets; UserMaximumChargeCurrent as the load-balancing knob; feature flag PREF |
| Energy EVSE Mode | 0x009D | Manual and scheduled modes |
| Electrical Power Measurement | 0x0090 | Voltage, ActiveCurrent, ActivePower per phase on three Electrical Sensor endpoints |
| Device Energy Management | 0x0098 | Stub: cluster present, no forecasting or power adjustment |
| Descriptor | 0x001D | Yes |
V2G attributes are reported as 0. The set is sold as the wireless smart variant, with our own controller in the box; it is not CSA-certified, and certification is done on the customer’s request and cost. The same firmware base gives a Matter power meter from a P1 port.
An SG-Ready heat-pump module as two Matter On/Off Plug-in Units is part of the set.
OCPP 1.6J — implemented, on order
A working OCPP 1.6J implementation exists and is not yet deployed. It is finished into a product when a customer’s project needs it, for example to represent a site as a charge point towards a third-party back-office or to accept a Dutch charge card through the NFC reader. Ask sales for the time-to-product for your case.
OCPP 2.0.1 and 2.1 are not planned until 1.6J is in production.
S2 — planned
S2 (EN 50491-12-2) is the protocol a Dutch home energy management system uses to tell a device how much power it may use. The site controller already does that job for chargers, over Modbus. The S2 work exposes the site controller and the GridShield receiver as S2 resource managers, PEBC first, OMBC for SG-Ready outputs. Available as an engineering engagement now; a product when ordered.
EEBus — planned
EEBus SPINE over SHIP is what German heat pumps and some energy managers expect. It is a supported interface for heat pumps on order: a gateway on the site controller or the Matter hub, using the same internal control model as SG-Ready and S2.
ISO 15118 — implemented, on order
The ISO 15118 module: HomePlug GreenPHY on the control pilot, a digital-communication mode on the charge controller, analog fallback per 15118-3. With 15118-20 vehicles it gives state of charge on AC and vehicle identification. Expensive, on request. V2G is a separate investigation.
NTA 8043 / NCS 8043:2026 — planned
The Dutch smart charging standard, with self-declaration by the manufacturer. EdgeTech has not filed a self-declaration. The functional requirements that map onto what ships today: dynamic current limiting per second, a minimum of 6 A, a safe fallback on loss of communication, and remote control by an external party. What is missing is the formal test evidence and the declared interface. If you need a charger that can be self-declared, this is an engineering engagement; ask for the current test status.
What is deliberately not there
- MID: the on-board meter is not certified as shipped. On request the on-board power measurement is MID-certified as a paid option: no external kWh meter, only a display.
- V2G: no bidirectional charging today. Under investigation, technical and regulatory; nothing is claimed until it is done.
- OCPP 2.x: see above.
- LoRaWAN: GridShield uses LoRa point-to-point, not LoRaWAN.