Where the setting lives
In the Zaptec Portal (portal.zaptec.com): Installations → your installation → Settings → Authentication → Type. It is a setting for the whole installation, not per charger.
Step by step
- Update the firmware from the portal. Minimums for native OCPP: Go EU 2.4.2.4, Go UK 2.5.1.0, Go 2 3.2.1.0, Pro 7.5.4.0.
- Permissions: under User Groups in the portal, Allow OCPP 1.6J must be enabled for your organisation. If another company administers the installation, the owner has to grant you access (four-character partner key).
- Make sure every charger is online and no charging session is running; otherwise the mode change is not applied.
- Installations → your installation → Settings → Authentication → Type: switch to OCPP 1.6J authentication.
- In OCPP Central System URL enter your brand's base URL (below), without the serial number: Zaptec appends it by itself, in upper case. Leave Initial device password blank unless you use the panel credential.
- Save. Each charger's identity is its serial number (ZCS…, ZAP…) in upper case: register it like that in the panel. They show as connected within a couple of 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 Zaptec, 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
- With native OCPP you lose Zaptec's own phase and load balancing; what remains is the standard OCPP smart charging the platform sends. The other mode, OCPP Cloud, keeps the balancing but goes through Zaptec's cloud and needs an agreement with them.
- If Authorization required is off, the charger sends an empty idTag and sessions are attributed to nobody: turn it on or set a Default ID tag.
- Do not put the serial number in the URL: it would appear twice and the server rejects the connection.
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)