Where the setting lives
In the charger's web interface (by its IP on the local network), Integrations tab → OCPP 1.6 → Link.
Step by step
- Open the charger's IP in a browser (it is in the manual or assigned by your router). Log in with the web interface credentials.
- Go to Integrations, enable the OCPP 1.6 integration and click Link to open the OCPP setup.
- Charge Box tab: in OCPP Identifier enter the identifier you register on askacharge.com (unique within your brand).
- Central System tab: in Host URL your brand's base URL (below). Leave Use OCPP time synchronization on Yes.
- Recommended: Energy for Start/Stop transaction and Energy for MeterValues set to PARTIAL, and User confirmation required on remote start set to NO, so remote starts and QR payment work without touching the charger.
- Save and reboot. Check at
http://<IP>/services/cpi/log?app=ocpp1.6that CB boot notification: success appears.
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 Circontrol, the serial number is the easiest choice. |
| Password | Blank by default. If you enable the charger's OCPP credential in the panel (recommended for units exposed to the internet), the username is the identity and the password is the one the panel generates: OCPP Security Profile 2. |
| 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. |
Where it usually fails
- The identifier must be unique: with several eNext units, do not leave the default value on all of them.
- If User confirmation required on remote start stays on Yes, the driver will have to press the charger after paying by QR and it will look as if the payment did not start the charge.
- The log at
/services/cpi/logis the fastest way to see why it will not connect (certificate, DNS, identity rejected).
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
- 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
- askacharge.com technical documentation (OCPP, API)