Where the setting lives
In the x-series web interface: Configuration → OCPP tab. Reached through the charger's Wi-Fi access point (name = serial number) at 192.168.2.1, or by its IP on the local network.
Step by step
- With the charger off, set DIP switch 2.5 to ON to enable the web interface (described in the configuration manual). Power on.
- Join the charger's Wi-Fi (password on the configuration label, in the bag with the installation material) and open
192.168.2.1. Username and password from the same label; change it on first login. - Configuration → Network connection: LAN, Wi-Fi or SIM (APN) so the charger has internet.
- Configuration → OCPP: Chargepoint Identity = serial number (or whatever you register); OCPP Communication Type = OCPP 1.6 JSON; Central System Hostname =
askacharge.com; Port = 443; Path =/askacharge/ocpp/your-brand; Secure Central System Connection = ON; Authentication Method = None (or Basic with the panel credential). - Apply. The charger reboots (up to 8 minutes). Status → Backend must read Connected.
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 KEBA, the serial number is the easiest choice. |
| Password | Blank by default. If you enable the charger's OCPP credential in the panel (recommended for units exposed to the internet), the username is the identity and the password is the one the panel generates: OCPP Security Profile 2. |
| 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
- c-series units (P20/P30 c-series) do not speak OCPP on their own: they connect as clients of an x-series master, which talks to the platform on behalf of all of them.
- Firmware older than 1.16.1 has known connection issues; update from the same web page (System → Update).
- If the charger was linked to the KEBA eMobility app, the web settings overwrite the app ones. No trailing spaces in any field.
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)