Where the setting lives
In the charger's web interface, Connectivity → OCPP tab. On eMH2/eMH3: http://<charger-IP>:8300 from the same network. On eM4: abl<serial-number>.local (for example abl10325981.local), over the Controller's internal Wi-Fi (password set in the ABL Configuration App) or over the router's network. Only the Controller (or a standalone unit) carries OCPP: the Extenders hang off it. The eMH1 has no OCPP.
Step by step
- Bring the firmware up to date from ablmobility.de (Service → Downloads). On eMH3, from 2.4.p1 no certificates need uploading for
wss://. - Get the internet connection working first (Connectivity → LAN, WLAN or Mobile network; with a SIM, APN and PIN).
- Connectivity → OCPP: OCPP version = 1.6. Central system address (URL) = your brand's base URL (below), without the identity.
- Chargebox ID: the identity you register in the panel (on eM4 it ships as
ABL_<serial>; fine as it is). Local port: 7890 on eMH3; on eM4 it only matters if the URL started with https (SOAP), which it does not. Local path: empty. - Basic authentication password: the password the panel gave you when you added the charger. Save. If the interface warns about TLS certificates for
wss://, under Connectivity → TLS choose TLS 1.3 and, if asked, upload the ISRG Root X1 root certificate (Let's Encrypt). - Before rebooting: clock in UTC, operating mode Online and Free charging off if you want the platform to authorise. Maintenance → System → Hard Reset. It connects on its own at boot.
What to enter to connect it to askacharge.com
| OCPP server URL | wss://askacharge.com/askacharge/ocpp/your-brand — your-brand is your brand's identifier on askacharge.com (shown under Chargers → Add, with the full URL ready to copy). The charger appends its own identity; if your unit only has a URL field and no identity field, enter the full URL: …/ocpp/your-brand/identity. |
| Charge point identity | The same one you register in the panel when adding the charger. Case-sensitive. With ABL, the serial number is the easiest choice. |
| Username and password | Required. The username is the charger identity and the password is the one the panel shows when you add the charger (shown once; if lost, generate a new one from the charger's page). Without it the server rejects the connection. This is OCPP Security Profile 2 (Basic Auth over wss://); there is no unencrypted or password-less path. |
| Protocol | OCPP 1.6J (JSON) or OCPP 2.0.1. Subprotocol ocpp1.6 / ocpp2.0.1. |
| Before connecting | The charger must be registered in the brand with that identity; otherwise the server rejects the connection. Register under Chargers → Add. |
Where it usually fails
- A Controller + Extenders group is one OCPP connection with several connectors: in the panel it is one charger with N connectors.
- The eMH2/eMH3 web interface is on port 8300; without the port in the browser URL nothing loads.
- On eM4, if the Controller is joined to an external Wi-Fi, its internal Wi-Fi switches off: go in through the router's network.
- ABL ships preset "backend profiles" (Connectivity → Backend); do not pick one, the manual configuration above takes precedence.
If your brand isn't here
The procedure is always the same; what changes is where the setting lives: look in the manufacturer's app, in the charger's web interface (by its IP) or in the installer software for a section called OCPP, Back office, Central System or Server. You need to be able to enter the URL and, nearly always, the identity. If the field is locked or missing, the manufacturer has tied the charger to its own platform: read what to do when the manufacturer locks or switches off its server.
Other brands
Related reading
- Your charger manufacturer shut down: how to get back in control
- Charge point management software: what it is, what it costs and how to choose
- askacharge.com technical documentation (OCPP, API)