Where the setting lives
In the TerraConfig app (installer account granted by ABB), paired with the charger over Bluetooth: OCPP server → Enable external server. The backend URL is registered beforehand in the TerraConfig portal; the app only picks it from the list.
Step by step
- Ask ABB or your distributor for a TerraConfig account ("Connected Services AC Terra" form). Without it the setting cannot be touched; the end-user ChargerSync app does not allow it.
- In the TerraConfig portal register the askacharge.com URL as a custom URL (below). For
wss://upload the server root certificate: ISRG Root X1 (Let's Encrypt). - TerraConfig app → log in → Configure a charger → your Terra AC (PIN and product code from the card in the box). Check it has internet (Wi-Fi, LAN or 4G) and current firmware.
- OCPP server → Enable external server → pick the preconfigured URL (or Add custom URL) → Configure → OK.
- The identity is the product code / serial number (TACW…): register it exactly like that in the panel. Device info shows the active URL and status; it can take up to 10 minutes to show as connected.
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 ABB, 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
- Several integrator guides say TerraConfig only accepts
ws://. That was true on old firmware; ABB's OCPP 1.6 document (v1.8, firmware 1.6.6) supportswss://with the root certificate loaded in the portal. Update the firmware. - Turn off Free Vending mode under Device Mode if you want authorisation by the platform; and if RFID cards do not work, enable external cards.
- From firmware 1.6.5 ABB no longer shows the UID of the bundled cards; read it with the platform (tap the card and look at the rejected attempt).
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)