Where the setting lives
It depends on the family. GLB+, GTB+, Twin+ and LS4: in the controller's web interface, with a laptop plugged by micro-USB cable into the controller's config port and the browser on 192.168.123.123 (user operator, password cherry_zone or yellow_zone), Backend menu. Entity Pro: in the GARO Connect app as installer, Third-party CPO/OCPP settings. GARO asks for a certified electrician to do it.
Step by step
- Add the charger on askacharge.com with the identity you will use (the serial number, no spaces or special characters) and keep the panel's password.
- GLB+, GTB+, Twin+, LS4: with the charger de-energised, open the cover and connect the laptop to the controller's micro-USB port with a cable that carries data (not a charge-only one). Twin+ and LS4 have two controllers: the right-hand one is the master.
- Open
192.168.123.123(new interface, white background). On older firmware:192.168.123.123/operator/operator, or on Twin+/LS4 ports:81and:82for each outlet. Log in asoperator. - Backend → Connection menu: Connection Type = Ethernet or GSM depending on how it reaches the internet. In OCPP ChargeBoxIdentity (ChargePointID), the identity registered in the panel. OCPP Mode = OCPP-J 1.6.
- WebSockets JSON OCPP URL of the Backend:
wss://askacharge.com/askacharge/ocpp/your-brand/, ending in a slash; the controller appends the ChargeBoxIdentity. In the same menu's Basic Auth password field (on these controllers, HTTP Basic Authentication password), the panel's password. - Save, then Restart. When the LED is green again, log back in and under Diagnostics check Connection State (Backend) reads Connected.
- Entity Pro: in GARO Connect, as installer, pick the location and the master charger → Third-party CPO/OCPP settings. In GaroDeviceId, the identity registered in the panel; in GaroRemoteCsmsUrl,
wss://askacharge.com/askacharge/ocpp/your-brand(if the field is a drop-down, choose manual entry). Save, restart and repeat on each master in the installation.
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 GARO, 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 trailing slash in the URL, the GLB+/LS4 controllers do not connect. Other brands use the same controller and it is the number-one failure.
- A "charge-only" micro-USB cable does not open the interface: it looks as if the controller is not responding.
- Every change under Backend needs a Restart. If it "does nothing", the restart is missing.
- Published guides for the GARO Connect app show no password field for the Entity Pro. askacharge.com requires one: if your app does not have it, write to us before going further and we will sort it out with you.
- On Twin+ and LS4, with the legacy interface changes are made on the master controller only.
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)