Where the setting lives
There is no field in the app. Easee's native OCPP is enabled through its API (api.easee.com/local-ocpp) with your own user account: three HTTP calls. We say it as it is; you do not need to be a programmer, but you do need to copy and paste carefully.
Step by step
- Update the charger to firmware 344 or later from the Easee app. The site must have Easee as operator (if another platform is set as operator, unlink it first).
- Get a token:
POST https://api.easee.com/api/accounts/loginwith{"userName": "your-email", "password": "your-password"}. The response carriesaccessToken(valid 1 hour). Every following call sends the headerAuthorization: Bearer <accessToken>. - Store the configuration:
POST https://api.easee.com/local-ocpp/v1/connection-details/<serial-number>with body{"connectivityMode": "DualProtocol", "websocketConnectionArgs": {"url": "wss://askacharge.com/askacharge/ocpp/your-brand", "caCertificate": "<ISRG Root X1 PEM>", "caCertificateDomain": "askacharge.com"}}. The Let's Encrypt root certificate (ISRG Root X1) is downloaded from letsencrypt.org/certificates. - Apply it:
POST https://api.easee.com/local-ocpp/v1/connections/chargers/<serial-number>with{}. - Check with
GET https://api.easee.com/local-ocpp/v1/connection-details/<serial-number>. The identity the charger uses is its serial number (EH…, EC…): register it like that in the panel. It connects within a few 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 Easee, 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
- DualProtocol means the charger keeps talking to the Easee cloud at the same time: the Easee app keeps working. To switch OCPP off, the same call with
"connectivityMode": "OcppOff". - The free tool
evcc easee-ocppdoes the same in one command, but only over unencryptedws://, and askacharge.com only acceptswss://: that is why the API with certificate is shown here. - If you use Easee Cloud as operator (emulated mode), the platform must be registered as an operator with Easee; askacharge.com is not, so the route is the native one above.
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)