Where the setting lives
In the go-e Charger app: Internet → OCPP tab (in older app versions, Settings → Connection → OCPP).
Step by step
- Update the firmware from the app. V3 units (HOMEfix/HOME+) only have OCPP on recent firmware.
- Connect the charger to your Wi-Fi (Internet → Wi-Fi). To get in the first time, the charger's hotspot and key are on the reset card in the box.
- Internet → OCPP: enable OCPP 1.6; in Server URL enter the URL complete with the identity:
wss://askacharge.com/askacharge/ocpp/your-brand/goe123456, where 123456 is the serial number (the six digits in the hotspot name). If you prefer the base URL, enable Append serial number to URL. - Internet → Reboot. Register in the panel exactly the identifier you put at the end of the URL.
What to enter to connect it to askacharge.com
| OCPP server URL | wss://askacharge.com/askacharge/ocpp/your-brand/identity — the full URL, with the charger identity at the end: on go-e there is no separate field for it. your-brand is your brand's identifier on askacharge.com (shown under Chargers → Add, with the full URL ready to copy). |
| Charge point identity | The same one you register in the panel when adding the charger. Case-sensitive. With go-e, 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 identity at the end of the URL (or the append-serial option) the charger shows up nameless and the server rejects it.
- To charge without a card while OCPP is on, set the dummy card id (default idTag) in the OCPP settings.
- All of this can also be done through the charger's local HTTP API (
/api/set?ocppe=true&ocppu=…), handy for several units.
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)