[WIP] myenergi zappi: Tutorial for OCPP integration

[koeberlue]

IMPORTANT

This currently does not work as myenergi seems to reset the commercial mode when the OCPP config changes (if you read the tutorial, this might make sense to you). Workaround can be found here: #21270 (reply in thread).

How to integrate myenergi's zappi using OCPP

Note: I am definitely not an expert at this. Use at your own risk.

Preface

The myenergi zappi is a multiphase ev charger.

It can be integrated to evcc using the OCPP 1.6 protocol. But while other chargers are capable of communicating through OCPP in your local network, the zappi has implemented OCPP as a cloud solution.

evcc has a builtin OCPP server. To control the zappi with evcc you will have to make this server accessible from the public internet so that the myenergi server can reach your evcc installation.

Note: To use the OCPP integration in evcc, you will need a sponsor token. You can use the trial token provided by evcc to test this setup, but this will change every once in a while. So, if you haven't already, consider sponsoring this great software, which saves you actual money!

Preparation

To make the integration work, you will first have to prepare zappi and your evcc installation by:

1. Make sure the zappi is not connected to your vehicle
2. Enabling commercial mode on the zappi
3. Make evcc's builtin OCPP server reachable from the internet

Enabling commercial mode on the zappi

Commercial mode is a special mode for the zappi which basically allows a third-party platform to gain control over the wallbox. This has to be enabled, otherwise Smart Charging profiles will not work.

Update: The following procedure does not work. See #21270 (reply in thread) for details. The tutorial will be updated at some point in time

1. Go to https://monta.com/en/charge-point-ocpp-integrations/ and click Start testing
2. Copy the URL that is shown to you (currently wss://ocpp-toolkit-api.monta.app )
3. Think of a random name for your zappi and enter it into the Identity field
4. You should aim for a unique name here, be creative :)
5. Click on Connect. You should see a warning, that the wallbox is not connected yet
6. Go to https://myaccount.myenergi.com/location#products and click on OCPP settings for your zappi
   1. Make sure the toggle button is enabled
   2. As EV Management Platform select Other / Manually Enter
   3. As Backend URI enter the URL you just copied from monta.com (currently wss://ocpp-toolkit-api.monta.app/).
      Important: Make sure the URL ends with a trailing /~~
   4. As Chargebox ID enter the Identity you have chosen on monta.com
   5. As Username enter the Identity you have chosen on monta.com
   6. Leave Authorization Key empty
   7. Click on Save
7. Go back to the monta.com site. It should now show information about your wallbox and some log messages.
8. Go to the Configuration tab
9. Find the entry CommercialMode in the list
10. Click on the edit button (the pencil)
11. Change the Value to True and click on Save

* Important: The popup will seem to be hanging for a minute or so and the configuration will also show a value of False for some time. You may have to wait for up to five(?) minutes until the commercial mode is actually activated. You can go to the Log tab and wait for a message like Receiving <= [ 3, "<some-id>", {"status":"Accepted"}]

Congratulations. Your zappi is now in Commercial Mode. If you check the screen on your wallbox it should display something like:

No Charger Name
ID: N/A
£0.00/kWh

Plug in to start

Note: If you ever need to disable commercial mode again, just follow the same steps as before, but set the CommercialMode to False in the last step.

Untested (optional): Set MeterValuesSampledData to Current.Import,Current.Offered,Energy.Active.Import.Register,Frequency,Power.Active.Import,Power.Factor,Voltage to show more information about the current charging session in evcc.

Untested (optional): You might want to change some other configuration parameters to change the display of the wallbox. Use with caution!

Note: If you want to take a break at this point, you should disable OCPP in the myenergi account settings again. Otherwise, everyone who guesses the Identity you set at mona.com could potentially control your wallbox.

Make evcc's builtin OCPP server reachable from the internet

When you install evcc and configure the OCPP integration (we will do this later in this tutorial), it will start an OCPP server on port 8887 which is usually reachable from within your local network.

As mentioned before, we will have to make this server reachable from the public internet. There are multiple ways to solve this (e.g. port forwarding on your router while having a public IP / DynDNS).

For the sake of simplicity we will use https://ngrok.com for this, as this software is designed for this exact use case, and they offer a free tier. There are also some alternatives out there you might want to check out, e.g. https://tnnl.de (tested), localtunnel.me (untested), pinggy.io (untested), cloudflare (untested).

Note: For this tutorial I am assuming you have evcc installed on a bare metal linux installation. If that is not the case, let me know and maybe we can expand this section together.

Generate an auth token and a domain for using ngrok

1. Create an account at ngrok.com
2. You will receive a verification mail, click the verification link
3. Configure Multi-factor Authentication (or skip this step, if you want)
4. In the dashboard navigate to Authtokens
5. Click on Add Tunnel Authtoken
6. (optional) Fill the Description with something meaningful
7. Click on Save. You will be presented a new token. Save it somewhere. You will need it in a minute.
8. In the dashboard navigate to Domains
9. Click on New domain (Note: Only the first domain is free!)
10. You will see a domain like adjusted-amazed-cat.ngrok-free.app. Save it somewhere. You will need it in a minute.

Install ngrok

Follow the official installation guide from the ngrok documentation.

As of today, on a Debian Linux, you can enter this command in a terminal on the machine where evcc is installed:

curl -sSL https://ngrok-agent.s3.amazonaws.com/ngrok.asc \
  | sudo tee /etc/apt/trusted.gpg.d/ngrok.asc >/dev/null \
  && echo "deb https://ngrok-agent.s3.amazonaws.com buster main" \
  | sudo tee /etc/apt/sources.list.d/ngrok.list \
  && sudo apt update \
  && sudo apt install ngrok

Note: The snap installation did not work for me. Use the apt installation from above.

Setup ngrok

On the machine where evcc is installed, create a new file ~/.config/ngrok/ngrok.yml with the following content:

version: "3"
agent:
  authtoken: <your auth token here>
endpoints:
  - name: evcc
    url: https://<your domain here>
    upstream:
      url: 8887

Then execute the following commands to enable the ngrok service:

sudo ngrok service install --config ~/.config/ngrok/ngrok.yml
sudo ngrok service start

That's it. You should now be able to access your evcc OCPP server from the internet.

Note: In the ngrok dashboard you can find a Traffic Inspector. You might want to keep it open during the next steps to verify if myenergi actually tries to connect to your server.

Configuration

Now that we have everything prepared, we can start the actual configuration. Don't worry, we are almost done at this
point.

Configure OCPP in the myenergy account

We now want to tell myenergi to talk to your evcc OCPP server. We already have done somethin similar before to enable commercial mode, but with a different URL.

1. Go to https://myaccount.myenergi.com/location#products and click on OCPP settings for your zappi
   1. Make sure the toggle button is enabled
   2. As EV Management Platform select Other / Manually Enter
   3. As Backend URI enter your ngrok URL, but prefix it with wss:// (e.g.
      wss://adjusted-amazed-cat.ngrok-free.app/). Important: Make sure the URL ends with a trailing /
   4. As Chargebox ID enter a name of your liking
   5. As Username enter the same name you used for the Chargebox ID
   6. Leave Authorization Key empty
   7. Click on Save

Configure evcc to control the wallbox

Personally I could not get the OCPP configuration running using the UI configuration. So I had to configure the integration using evcc.yaml.

Add the following content to /etc/evcc.yaml:

chargers:
  - name: myenergi # you can change this
    type: template
    template: ocpp
    stationid: <chargebox id> # use the same name you used for the Chargebox ID in the myenergy OCPP settings
    meterinterval: 30s
loadpoints:
  - title: Garage # you can change this
    charger: myenergi # has to match chargers[0].name from above
sponsortoken: <your sponsor token>

# the following code block is optional, but it can help tremendously when debugging or testing new configurations
levels:
  ocpp: trace
  lp-1: debug

Restart evcc.

Note: Restarting might take some time. See the Known issues section for details

Reduce control behavior

To reduce wear on the memory chip, myenergi limits the amount of charge profile writes to 26 per hour. So we need to artificially slow down evcc to not run into this limit.

1. Visit your evcc installation
2. Open the burger menu in the top right corner
3. Select User Interface
4. Enable Experimental
5. Open the burger menu in the top right corner again
6. Select Configuration
7. Under General edit the Control behavior
8. Set the Update interval to 180s

Done

You are done. Connect your vehicle to the wallbox. Open evcc. Enjoy!

Note: Due to the update interval of three minutes the evcc UI is actually kind of boring to watch :)

Known issues

Phase switching does not work

Although the zappi is capable of switching between 1- and 3-phases, I could not get it running over OCPP yet.

evcc takes a long time to boot

This is a bug in the OCPP implementation of myenergi. When evcc starts, it will try to configure the wallbox over OCPP. At one point it will set the meterinterval. Although this command always succeeds, myenergi never sends a confirmation. So evcc will wait up to 30(?) seconds for this confirmation before it continues booting. Just be patient.

[paheinen]

Hi,
mega Anleitung!
Erstmal Herzlichen Danke dafür.

Ich hatte es alles am laufen... Dann verlor die Zappi plötzlich den commercialMode.

Habe den CommercialMode nochmals über monta.app auf True gesetzt, ich bekomme auch "accepted" zurück und das Display schaltet auch auf CommerialMode.

Sobald ich dann aber die zappi wieder an mein evcc hänge verliert diese die Einstallung CommercialMode.

Als wenn evcc hier die Daten überschreibt ?

Den Fehler schon gehabt oder bekannt ?

Vielen Dank
Peter

[koeberlue]

Hi @paheinen ,

ja, das ist leider bekannt. Ich habe versucht im ersten Satz der Anleitung darauf hinzuweisen, aber scheinbar habe ich es nicht so gut formuliert :D

Ich habe es bei mir über einen anderen Weg ans Laufen bekommen. Ich bin nur leider noch nicht dazu gekommen, die Anleitung anzupassen. Ich hoffe, ich finde am Wochenende mal die nötige Zeit.

Falls du dich in der Zwischenzeit schonmal damit beschäftigen willst, hier die (viel zu knappe) Kurzanleitung:

TL;DR: Wir ersetzen monta.app durch die Anwendung "Steve", die wir auf dem gleichen Gerät laufen lassen können wir evcc. Dann können wir die URL in der myenergi Webapp für das Setzen des Commercial Mode und für evcc einfach gleich lassen.

Das hier ersetzt also den kompletten Schritt Enabling commercial mode on the zappi aus der Anleitung.

Steve aufsetzen

Steve clonen

In einem beliebigen Ordner:

git clone https://github.com/steve-community/steve

Steve konfigurieren

In steve/src/main/resources/config/docker/main.properties folgenden Einstellung umändern:

auto.register.unknown.stations = true

Reverse Proxy für Steve einrichten

Neue Datei anlegen: steve/nginx/nginx.conf mit folgendem Inhalt:

events {
  worker_connections 1024;
}

http {
    map $http_upgrade $connection_upgrade {
        default upgrade;
        '' close;
    }
  
    server {
        listen 9000;
        location / {
            proxy_pass http://app:8180/steve/websocket/CentralSystemService/;
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection $connection_upgrade;
            proxy_set_header Host $host;
        }
    }
}

Außerdem die Datei steve/docker-compose.yml erweitern:

version: "3.0"

volumes:
  db-data:
    external: false

services:

  db:
    # Pinning MariaDB to point release 10.4.30 works around the issues with the
    # database migrations seen with 10.4.31 in issue #1212.
    #
    # TODO: Get database migrations to work with the latest point releases of
    # MariaDB 10.4.
    image: mariadb:10.4.30
    restart: unless-stopped
    ports:
      - 3306:3306
    environment:
      MYSQL_RANDOM_ROOT_PASSWORD: "yes"
      MYSQL_DATABASE: stevedb
      MYSQL_USER: steve
      MYSQL_PASSWORD: changeme
  app:
    restart: unless-stopped
    build: .
    links:
      - "db:mariadb"
    volumes:
      - .:/code
    ports:
      - "8180:8180"
      - "8443:8443"
    depends_on:
      - db
      
######### vvvvvvvvvvvvvvvvv   Das hier kommt dazu vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##########      
      
  nginx:
    restart: unless-stopped
    image: nginx:latest
    ports: ["9000:9000"]
    volumes:
      - ./nginx:/etc/nginx
    depends_on:
      - app

Steve starten

Im Ordner steve folgendes Kommando ausführen:

docker compose up -d

Jetzt solltest du unter http://evcc.local:8180/steve/manager/signin auf Steve zugreifen können. (URL möglicherweise zu deinem Setup anpassen)

Es kann aber gute fünf bis zehn Minuten dauern, bis Steve gestartet ist. Das kannst du verfolgen mit:

docker container logs steve-app-1 -f

(Um die Logs zu beenden, Strg + C drücken)

Sobald du auf die Weboberfläche kommst, kann du dich mit dem Benutzernamen admin anmelden. Das Passwort lautet 1234.

Ngrok auf Steve umbiegen

Jetzt müssen wir ngrok noch sagen, dass es alle Anfragen temporär zu Steve umleiten soll.

Dafür in der Datei ~/.config/ngrok/ngrok.yml folgenden Eintrag ändern:

    upstream:
      url: 9000

Dann ngrok einmal neustarten:

sudo ngrok service restart

myenergi konfigurieren

Jetzt einmalig aus obiger Anleitung den Schritt Configure OCPP in the myenergy account ausführen.

Wenn alles funktioniert hat, taucht die zappi jetzt in der Steve Adminoberfläche auf.

Commercial Mode setzen

In der Steve Weboberfläche einloggen und so durchklicken: Operations > OCPP v1.6 > ChangeConfiguration.

Unter Charge Points sollte die zappi auftauchen. Die muss ausgewählten werden.

Unter Parameters müssen diese Einstellungen gesetzt werden:

1. Key Type > Custom
2. Custom Configuration Key > CommercialMode
3. Value > True

Dann auf Perform klicken.

Jetzt dauert es ein paar Minuten, dann sollte die zappi wieder wie in der anderen Anleitung in den Commercial Mode springen.

ngrok wieder auf evcc zeigen lassen

Jetzt müssen wir ngrok noch sagen, dass es wieder auf evcc umleiten soll.

Dafür in der Datei ~/.config/ngrok/ngrok.yml den Eintrag wieder zurückändern auf:

    upstream:
      url: 8887

Dann ngrok einmal neustarten:

sudo ngrok service restart

Steve beenden

Auf Nummer sicher sollte Steve jetzt beendet werden. Dafür im Ordner steve folgendes Kommando ausführen:

docker compose down

evcc neustarten und warten

Jetzt muss evcc nur noch einmal neugestartet werden und wir sind im Grunde fertig.

Höchstwahrscheinlich wird evcc ein paar Anläufe brauchen um hochzufahren.

Das liegt daran, dass evcc nur dann erfolgreich startet, wenn die OCPP Verbindung von myenergi innerhalb von wenigen Sekunden (30?) erfolgreich aufgebaut wird. myenergi versucht aber nur sehr unregelmäßig, die Verbindung aufzubauen, sodass es einfach auf beiden Seiten ein paar Anläufe braucht, bis man sich findet.

Ich musste hier ca. zwei Stunden warten. Evtl. finden wir aber mittelfristig noch andere Möglichkeiten, das zu beschleunigen.

---

Du siehst, alles etwas komplizierter als über die monta.app, aber man sollte sich nicht abschrecken lassen. Es ist alles nicht so kompliziert wie es vielleicht auf den ersten Moment scheint :)

Falls du Fragen hast oder über Probleme stolperst, lass hier ruhig fleißig Kommentare da. Und lass mich auf jeden Fall wissen, ob das Setup bei dir funktioniert hat!

[sebnolte]

Hi!

Mir hat die Anleitung sehr geholfen, auch meine Zappi an EVCC anzubinden.

Ich habe als alternative den Dienst von Cloudflare ausprobiert und kann auch hier sagen, das funktioniert.
Voraussetzung ist allerdings, dass man über eine eigene Domain verfügen, die man vorab dort anbindet.

So ein paar kleinere Errormeldungen tauchen in den Logs noch auf. Zum Beispiel:

Sep 09 17:49:59 evcc evcc[3394]: [lp-1 ] ERROR 2025/09/09 17:49:59 charge voltages: timeout
Sep 09 17:49:59 evcc evcc[3394]: [lp-1 ] ERROR 2025/09/09 17:49:59 charge total import: timeout

Wobei charge voltages: timeout scheinbar verschwindet, sobald das Auto an der Wallbox angeschlossen ist. Dann sieht es so aus:

Sep 09 20:07:44 evcc evcc[6145]: [lp-1 ] DEBUG 2025/09/09 20:07:44 charge voltages: [235 233 235]V

Eine Meldung die auch immer wieder auftaucht ist die folgende:

Sep 09 17:52:55 evcc evcc[3394]: [ocpp ] ERROR 2025/09/09 17:52:55 ocpp message (1617561895): PropertyConstraintViolation - Field CallResult.Payload.ChargingSchedule.ChargingSchedulePeriod must be minimum 1, but was 0 for feature GetCompositeSchedule ([3,"1617561895",{"status":"Accepted","connectorId":1,"scheduleStart":"2025-09-09T15:52:54.947Z","chargingSchedule":{"duration":60,"startSchedule":"2025-09-09T15:52:54.947Z","chargingRateUnit":"W","chargingSchedulePeriod":[]}}])

Ist aber auch verschwunden, sobald ein Auto an der Wallbox angeschlossen ist.

Interessant ist auch das Verhalten, dass die Wallbox erstmal anfängt zu laden, auch wenn die Parameter für Überschuss und Batterie unterschritten sind. Der Ladevorgang wird dann aber nach ca. 1 Minute wieder abgebrochen. Wäre natürlich schöner, wenn der Ladevorgang erst gar nicht beginnen würde.

Ich bin mal gespannt, ob in die Zappi vielleicht nochmal ein bisschen investiert wird.

[FransTwisk]

First of all thank you very much for figuring this all out! I have been trying to set this all up in the last few days and hit a lot of bumps but slowly getting there. I have a working publicly accessible (Caddy server) domain name which I can either point to SteVe or EVCC OCCP port, both confirmed working. The only issue I have now is that I am unable to put the Zappi in Commercial Mode (using SteVe).

Myenergi settings confirms my local OCCP server is connected. I see the wallbox connected in SteVe (and EVCC if I switch local server in Caddy). I can query all settings or just CommercialMode which returns False. If I however try to change the configuration using key CommercialMode with value True the request doesn't get any response and keeps retrying until eventually (maybe up to 20 minutes) the server replies with Rejected.

Am I missing something here? Or did myenergi make changes recently we are yet unaware of?

[koeberlue]

I really hope they did not change anything concerning the commercial mode.

I vaguely remember having the same problem once while writing the tutorial. But I am not quite sure what helped.

Things I remember trying:

• Disabling OCPP in the myenergy account. Wait a few minutes. Enable it again.
• Disconnect the zappi from the internet (I used my router settings for this)
• Power cycle the zappi
• Just do nothing for an hour and then try again

I would be happy if you let us know if you solved this issue. I will add it to the tutorial then.

[FransTwisk]

I figured it out: My home network is quite strict with firewall and DNS rules, but I assumed everything should have worked since the Zappi itself was connected to the myenergi servers. It was, but since I have never rebooted the Zappi, new connections where blocked due to my (since updated) DNS blocklist...

I also blocked any other IP addresses from directly accessing my Caddy server besides my own IP and Cloudflare. I disabled Cloudflare's proxy when trying to get this to work and my firewall basically blocked the request from myenergi. Obviously this is all a good thing, means my rules work, but sometimes makes it hard to debug (especially since getting initial OCPP connection or updating config can be very slow) 😄

What I learned:

• API calls from Zappi to myenergi servers use the domain (*.)myenergi.online. Make sure this DNS request is not blocked
• It seems myenergi uses a machine on IP address 3.248.7.108 to communicate OCPP requests to your local OCPP server. There might be others as well. This IP address is not mentioned in their docs

I can continue tinkering with this for now!

[FransTwisk]

I just started my first charging session after also enabling FreeCharging and FreeVendScreen options on the now through EVCC controlled Zappi, but I am very confused...

It doesn't seem to matter which option I set in EVCC, it seems to always charge in Fast mode. What is even weirder is that according to my Home Assistant and EVCC config I have set the Zappi to use Phase 1 yet the current charge rate is over 10kWh...

Any thoughts? Do I need any additional configuration of the Zappi? Whatever I do the Zappi always charges in Phase 3 in Fast mode with boosting enabled.

[koeberlue]

It doesn't seem to matter which option I set in EVCC, it seems to always charge in Fast mode

So this is a little bit confusing but the short version: This is expected.

So the Fast mode you are seeing in Home Assistant probably comes from the ha-myenergi plugin. So this is the mode of the Zappi, not the evcc mode.

So we do want to set the zappi Fast mode with our configuration. This means we tell the zappi to always charge the car, but using OCPP we then limit the actual output of the zappi.

[...] yet the current charge rate is over 10kWh

Please note that we configured evcc to only send commands to the zappi every three minutes. So after every click in the evcc Frontend (that changes charging behavior) you should wait for at least three minutes.

If you enabled debug logging for ocpp as described in the tutorial you might want to check the logs. There you should be able to follow what evcc is currently trying to do.

Did you configure a charging plan? If so, what did you configure?

What is even weirder is that according to my Home Assistant and EVCC config I have set the Zappi to use Phase 1 [...]

Yeah, I could not get phase switching to work with OCPP. For now I also always load with three phases. It should be possible but I probably missed the correct setting in evcc. I did not find the time to tinker around this issue yet. Until then maybe someone else finds the correct setting to do this.

I discontinued working on this, often the Zappi didn‘t start to charge an the scheduled time in the Zappi was very wired. Sometimes the time was in the past or it was planned for in two days. Nothing I can work with.

That's too bad, but I get it. This can be a tiresome experience. Although it sounds like something was messed up in your plan configuration.

As for me I am running this setup in Min + Solar mode with a Min. charge % of 50% on Arrival and a daily Charging goal of 80% at 5 a.m.. I have this running since April and so far it has not failed me.

[FransTwisk]

I am aware of the delay and let it charge for quite some time. It always stayed in "Fast" mode with 10+ KWh. I did however not do any extensive debugging yet. I was also aware that automatic phase switching does not work (at least with current setup) but assumed manual switching would work? Can you confirm of deny this?

If I cannot even switch to phase 1 it wouldn't be very useful for me, since my main goal is to by default only use surplus energy and only do fast charging on cheap energy prices when I need the car the next day or so. I am currently figuring out how to do this straight through Home Assistant because of the experiences with EVCC so far.

[romkeller]

Hello everyone, are there any new experience reports from you by now? Is the setup running smoothly? Are there already solutions for the phase switching?

[romkeller]

Since the latest EVCC update, there is now the option to add ‘Home Assistant wallboxes’. I think this brings us a step closer to mapping the Zappi in EVCC. Unfortunately, the Myenergi Home Assistant integration is still missing an entity to control the maximum charging speed. Maybe something will happen there in the future.

[Jaques-Ludwig]

Has anyone got the Zappi to work with the EVCC option Wallbox: "Home Assistant Charger"?

Which entities do I have to enter?

[riemers]

https://github.com/riemers/evcc, i wanted to see how far i could bring it. I can only turn it on and off, and i can say in a config that off = eco+ and fast is for example "eco" while still keeping off/fast an option. 1 or 3 phases switch is possible but api keys don't allow managing amps. So with this it would just turn it into a dummy on/off. Was just some vibe coding so i don't dare to PR it but might be usefull for inspiration/other ideas. I saw an oauth option is there too with amps but then it needs to be fully managed too and i already have an occp profile in use and i believe you can only set one in myenergy.

I think https://api-docs.s18.myenergi.net/authentication might be the best in this case, but that requires more work as you don't get a id/secret out of the box.

[romkeller]

ome time has passed since then, has anyone gathered new experience here? In the meantime, there have also been updates to the Zappi and the myenergi backend.