Home › Generic / protocol › OCPP 1.6J compatible
OCPP 1.6J compatible
EV charger by Generic / protocol. Compatibility with energy supplier apps, Home Assistant and evcc.
At a glance
| Device type | EV charger [evcc template, 2026-10-19] |
|---|---|
| evcc support | Yes |
| Connection | OCPP (inferred from evcc template parameters) [evcc template, 2026-10-19] |
| Local control (no cloud) | Yes via evcc's connection type [evcc template, 2026-10-19] |
| Home Assistant | Unknown know this? tell us (brand not yet checked) |
| Known firmware notes | Unknown know this? tell us |
Energy supplier apps
Supplier lists are published per brand (sometimes with model conditions). A brand match does not guarantee your exact model works — check the linked page or the supplier's app.
| Supplier / service | Status for Generic / protocol charger | Source |
|---|---|---|
| Frank Energie | Not listed Generic / protocol is not on Frank Energie's EV-charger list | [source, 2026-10-19] |
| Tibber | Not listed Generic / protocol is not on Tibber's EV-charger list | [source, 2026-10-19] |
| Zonneplan | Not listed Zonneplan only lists its own hardware | [source, 2026-10-19] |
| Eneco | Unknown know this? tell us | — |
| ANWB Energie | Unknown know this? tell us | — |
| Vattenfall | Unknown know this? tell us | — |
Home Assistant integrations for Generic / protocol
Unknown know this? tell us — we have not yet checked Home Assistant support for Generic / protocol.
evcc details
| Template | ocpp (charger) [source, 2026-10-19] |
|---|---|
| Connection | OCPP (inferred) |
| Capabilities | mArfid1p3pdim [source, 2026-10-19] |
| Requirements | With OCPP the connection will be established from charger (client) to evcc (server).
The charger needs to be able to reach evcc via the host name (functioning DNS resolution required!) or via the IP address on port 8887.
By default, the first incoming connection with any station identifier is used.
In order to be able to clearly assign several charging points, the respective station identifier (`stationid: `) and connector number (`connector: `) must be configured.
Many wallboxes automatically add the `station id` to the backend URL, some have to do this manually `ws://<evcc-host>:8887/<stationid>`.
If the charger supports sending metering values, try to adjust the interval to a short time span (< 10s) .
Use your RFID tags (this allows e.g. vehicle identification) or set your charger to "free charging" or "autostart" to generate the transaction required for charging release.
If the charger does not offer any option to start transactions locally, the `remotestart` advanced option can be used to automatically start a transaction as soon as a vehicle is connected.
This should only be necessary in exceptional cases.
Requirements:
* If necessary, remove previously configured OCPP profiles (e.g. used for a different backend connection) in the charger configuration
* Backend URL (Central System) in the charger configuration: `ws://<evcc-host>:8887/` (possibly add `stationid`)
* Protocol: OCPP-J v1.6, ocpp16j, JSON, Websocket, ws:// or similar
* No encryption, no authentication, no password
* Local network connection
The specific configuration and the actual usable functionality depend on the charger model and its software. [source, 2026-10-19]evcc sponsor token required |
| Known caveats | None listed in the evcc template. |
“Works for me” reports
No user reports yet. Report your firmware version and setup TODO: form
Where to buy
Shop links will appear here. TODO: affiliate placeholder — no links yet See our affiliate disclosure.