Where the setting lives
With the ACE Service Installer program (Windows) connected to the charger over the local network, Connectivity tab. Newer models also allow first commissioning over temporary Wi-Fi with the MyEve app.
Step by step
- Get the charger's owner password: it ships with the unit or the installer / previous software provider has it. Without it the back-office settings cannot be changed.
- Install ACE Service Installer on a Windows PC on the same network as the charger and log in with the installer account Alfen provides.
- Select the charger in the list and open Connectivity. Set the connection method (Wired for Ethernet, GPRS if it has a SIM).
- Choose Manually enter backoffice settings. Protocol OCPP 1.6 (JSON), Security Profile 2:
wss://with username (the identity) and the password the panel gave you when you added the charger. - In Back office URL enter your brand's base URL (below, without the identifier): the Alfen appends its own identity.
- In the General tab, the Customer Ident. number / ChargeBoxIdentity field is the identity you must register on askacharge.com.
- Save, click the power icon at the bottom left and confirm the restart. It shows as connected within a few minutes.
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 Alfen, 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
- Without the owner password there is nothing to do: ask the installer or the previous provider for it in writing before cancelling anything.
- Old firmware versions only accept
ws://with security profile 0; askacharge.com does not offer that path (onlywss://with a password), so if profile 2 is not offered, update the firmware first. - Keep the firmware current from the same ACE Service Installer (General → Upload Firmware); older NG models need a firmware without a preset back office.
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)