Where the setting lives
In the my.wallbox.com portal (Chargers → Settings → Connectivity → OCPP → Edit) or in the myWallbox app (charger settings cog → OCPP).
Step by step
- Update the charger firmware to the latest version from the app; older versions either hide the OCPP menu or fail to connect.
- Make sure the charger has internet over Wi-Fi or Ethernet (Wallbox asks for at least −70 dBm of signal). Bluetooth is for configuring only, not for reaching the server.
- Open my.wallbox.com → Chargers → your charger → Settings → Connectivity → OCPP → Edit.
- In OCPP server URL enter your brand's URL on askacharge.com (below). In Charge point identity the identifier you registered; Wallbox suggests the serial number, which is a good choice.
- Password: the one the panel showed when you added the charger (username = the identity). It is required: without it askacharge.com rejects the connection.
- Accept the terms, save and switch OCPP on. The charger reboots by itself (1–3 minutes) and shows as connected in the panel.
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 Wallbox, 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
- With OCPP on, some myWallbox app features (statistics, control from the app) stop being available: they move to the platform. That is normal behaviour, not a fault.
- On recent firmware, if it will not connect, try the URL without the
wss://prefix: some versions add it themselves and end up with it twice. - The charge point identity is case-sensitive and must match the registered one letter for letter.
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)