Where the setting lives
In the charger's web page over Ethernet: fixed IP 192.168.1.250 (set the PC to 192.168.1.x), username root@etrel.com, password toor. Menu → Connectivity.
Step by step
- Connect the PC by cable to the INCH, give the PC a 192.168.1.x IP and open
192.168.1.250. Log in with root@etrel.com / toor and change it. - Connectivity → Ethernet connectivity: enable DHCP and DNS under IPv4 (or a static IP) so the charger reaches the internet through your network. Save.
- Connectivity → OCPP: Protocol type = OCPP 1.6 JSON; Central system endpoint URL = your brand's base URL (below); note the Charge point identity (serial number) to register it in the panel.
- User → Charging authorization: Central System Only, so cards and starts are validated by the platform.
- Save and restart (from the web page or with the reset button). It connects within a minute.
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 Etrel, 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
- Change the root/toor password: it is public and the charger is otherwise open to anyone on your network.
- If authorisation stays local, cards registered on the platform will not work and it will look like an OCPP fault.
- The identity is the serial number; do not change it after connecting.
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)