Where the setting lives
In the WiFi module's web interface (http://openevse.local or its IP): Settings → OCPP.
Step by step
- Update the WiFi module firmware from Settings → Firmware update; old versions do not have the OCPP page.
- Settings → OCPP: in Server your brand's base URL (below); in Charge box ID the identifier you register (you choose it here: there is no fixed serial number).
- Authorization key: the password the panel gave you when you added the charger (required).
- If you want it to charge without a card, set a Default ID tag and enable automatic authorisation. Save; it connects in seconds and sessions appear under History.
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 OpenEVSE, 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
- The identifier is case-sensitive and must be unique within your brand: with several OpenEVSE units, do not leave the default on all of them.
- When a CSMS is connected its commands take priority over local schedules and RFID, but not over the unit's own safety limits.
- With Suspend EVSE enabled the charger gives no current until the platform authorises; untick it if that is not what you want.
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)