Where the setting lives
In the charger's own Web Manager, OCPP → Plant tab. Reached over the charger's Wi-Fi (name = serial number, password = first 8 digits on the label) at http://192.168.2.1:8080, or over Ethernet at http://serialNumber.local:8080.
Step by step
- Connect to the charger (Wi-Fi or cable) and open the address above with port 8080. Log in as operator with its password (unit documentation).
- If it has a SIM: ChargingPlants → serial number → Network, edit WAN, set the APN and untick Discover APN.
- OCPP → Plant: version 1.6; in the monitoring server URL, your brand's base URL (below). Save & Apply.
- OCPP → serial number: chargebox ID = the identifier you register (the serial number is the easy choice). Save & Apply.
- Charging Points → terminal Status: OCPP connected: Yes. If it takes long, the same Status page has Clear messages to flush the queue.
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 Ingeteam, 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://). If your model only supports unencrypted ws://, it can be allowed charger by charger on its page in the panel, and the password is still required. |
| 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. |
Want to check it before signing up for anything?
Point your charger at our OCPP test server: free, no account, over wss:// or ws://. You will see what it sends live and we will tell you what would fail when you connect it for real.
Where it usually fails
- No trailing spaces in any field: it is the first cause of "it will not connect" on these units.
- The Web Manager manual (2024) only documents
ws://URLs. Current firmware acceptswss://; if yours will not connect encrypted, ask Ingeteam for the update before anything else. - In sites with several terminals the master speaks OCPP for all of them; each has its own chargebox ID in its subtab.
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
- OCPP errors: why your charger won't connect or charge, and how to fix it
- 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
- Your EV chargers in Home Assistant, without giving up billing
- askacharge.com technical documentation (OCPP, API)