Skip to main content

Keba P40

Updated

 

 

You can add your Keba P40 to our system via OCPP to enable intelligent control.
To do this, you only need to enter the OCPP link from our app into your Keba P40:

In our app, tap "Add device" -> "Wallbox" -> "Keba P40".

Ensure that the name of the wallbox does not contain any "_" or spaces " ".

Also, ensure that the latest update 1.2.2 is installed on the wallbox and perform a factory reset. You can then integrate the wallbox into our system.

shared image (2).jpg
shared image (4).jpg

Next, we enter the OCPP link from the app into the wallbox:

 

Go to settings:

shared image (5).jpg

 

Under OCPP settings:

shared image (3).jpg
shared image.jpg

 

For Central System Hostname, enter: "cleverpv-ocpp.azurewebsites.net"

For Central System Path, enter the part of the link starting after ocpp: "ocpp/xxxxxx"

The Central System Port is: 443

Troubleshooting

Question: "I have registered you as the OCPP backend and can no longer access my wallbox using the Keba app. What should I do?"

Answer: "This is normal behavior when an OCPP backend is active. However, you can continue to use the Keba app on your local Wi-Fi. To do this, open the app, tap the three dots in the top right corner, and change the connection to 'Network'. This allows you to access your wallbox locally."


KEBA P40: Setting the OCPP Security Profile to 0

When do you need this? Your wallbox runs firmware 1.4.5 or later, it is set to OCPP Security Profile 3, and it always shows "Waiting for status" or "Offline" in the app.

Background: OCPP can only raise the security profile, not lower it. KEBA designed it this way. So the change has to be made locally through the wallbox's REST API. There is currently no setting for this in the web interface or the KEBA app.

What you need

  • A computer on the same network as the wallbox
  • The IP address of the wallbox (for example from your router's device list)
  • The wallbox credentials: the same username and password you use for its web interface (see the password sheet that came with the wallbox)

1. Open the API page

  1. Open https://<wallbox-IP>:8443/docs in your browser.
  2. Your browser shows a security warning because the wallbox uses a self-signed certificate. Click "Advanced" and then "Proceed to … (unsafe)".
  3. You should now see a page titled "rest.app" with a section called "V2_AUTH".

2. Log in

  1. In the V2_AUTH section, expand POST /v2/jwt/login.
  2. Click "Try it out".
  3. The text field now contains a template. Enter your username and password there. Leave the field names and quotation marks as they are.
  4. Click "Execute".
  5. Under "Response body" you'll see a response with an access token (a long string). Copy it without the quotation marks.
  6. Scroll to the top and click "Authorize" (lock icon). Paste the token, click "Authorize", then "Close".

The token expires after a while. If you later get 401 Unauthorized, just repeat step 2.

3. Read the current OCPP configuration

  1. Scroll down below V2_AUTH and find the section for the OCPP configuration (look for "ocpp" or "config").
  2. Open the GET entry there, click "Try it out" and then "Execute".
  3. In the response, find the entry ocpp_security_profile. It should show 3.
  4. Write down the current value or take a screenshot so you can restore it later.

4. Set the security profile to 0

  1. In the same section, open the entry for changing the configuration (PUT or PATCH).
  2. Click "Try it out".
  3. Edit the text field so that the key ocpp_security_profile is set to 0. Keep the structure Swagger gives you, or the one you saw in the GET response in step 3. Change only this one value.
  4. Click "Execute".
  5. The result should be 200 or 204.

5. Check the result

  1. Run the GET from step 3 again. ocpp_security_profile should now be 0.
  2. The OCPP connection drops briefly and reconnects on its own. No reboot is needed.
  3. After one or two minutes, the wallbox should be back online in the app.

Troubleshooting

  • The value isn't saved: Factory reset the wallbox and set it up again without Security Profile 3.
  • Login fails: Check your username and password. They are on the wallbox's password sheet.
  • The page doesn't load: Check the IP address and that your computer is on the same network. Make sure you use https:// and port :8443.