Where the setting lives
In the EVBox Connect app, over Bluetooth and in installer mode (with the security code from the box): Charging Management Platform → Different Backend URL.
Step by step
- Firmware 425 or later: on earlier versions the charger's TLS certificate has expired and it will not negotiate
wss://. Update from the app first. - Open EVBox Connect, pair over Bluetooth and write down the charger's modem number (
EVB-P…): it is its OCPP identity. Enter the security code (shipped with the unit) and authorise. - Enter Installer Mode (it asks for the code again) → Charging Management Platform → Different Backend URL.
- Enter your brand's base URL (below) → Save → Select. Save the configuration and restart the charger.
- Register the
EVB-P…in the panel as it is. If you are going to charge money, enable Activate using charge fob/key and disable Auto-start, or anyone will charge unauthorised.
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 EVBox, 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
- Engie wound down EVBox and its Everon platform stopped serving on 1 December 2025. Nothing is broken in the chargers: they speak standard OCPP and work with any platform. This guide is the way out.
- Without the security code from the box there is no installer mode. If you lost it, the original installer usually has it; otherwise ask the service Engie keeps for existing units.
- If the charger was linked to Everon, unlink it in the app first or the URL reverts to the old one after a restart.
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)