cannot create charger type 'ocpp':

[hf81-ble]

Describe the bug

Not Possible to use the Atronix Wallbox OCPP (WEEYU manufacturer, same as em2go) .

failed configuration availbility.

I assume something wrong in the initial handshake. If i use the SteVe OCPP Server the box is working.

I would also contribute the solution, if anybody could give me a hint to the sources and a short brief overview to the sources.

Best reagrds Holger

Steps to reproduce

1. Wallbox is configured for OCPP 1.6j
2. Working with SteVe (see log)
3. Migrating to EVCC with attached config
4. Error during Connection and status request

Configuration details

chargers:
  
  - name: Wallbox11k
    type: template
    template: ocpp
    stationid: "184702771966111" # Station ID, Station ID des Ladepunktes. Nur erforderlich wenn mehrere OCPP-Ladestationen eingerichtet sind um diese korrekt zuzuweisen. Eine einzelne OCPP-Ladestation kann auch automatisch zugeordnet werden. Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form `ws://<evcc-adresse>:8887/<stationid>` anzuhängen. Die meisten Ladestationen fügen die ID intern automatisch hinzu. (optional)
    remotestart: true

Log details

[184702771966111-1] DEBUG 2025/08/04 10:26:42 waiting for chargepoint: 5m0s
[ocpp  ] DEBUG 2025/08/04 10:26:57 charge point connected: 184702771966111
[ocpp  ] DEBUG 2025/08/04 10:26:59 charge point disconnected: 184702771966111
[184702771966111-1] DEBUG 2025/08/04 10:26:59 failed configuring availability: timeout
[mercedes] DEBUG 2025/08/04 10:26:59 identity.NewIdentity - database token found
[mercedes] DEBUG 2025/08/04 10:26:59 identity.NewIdentity - refreshToken started
[main  ] ERROR 2025/08/04 10:27:00 creating tariff co2 failed: invalid tariff type: grã¼nstromindex
[main  ] FATAL 2025/08/04 10:27:00 charger [Wallbox11k] cannot create charger 'Wallbox11k': cannot create charger type 'template': cannot create charger type 'ocpp': cannot send request 295242667, no client 184702771966111 exists
loadpoint [lp-1] charger: not found: Wallbox11k
[main  ] FATAL 2025/08/04 10:27:00 will attempt restart in: 15m0s:05:12 will attempt restart in: 15m0s

What type of operating system or environment does evcc run on?

HomeAssistant Add-on

External automation

• I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.

Nightly build

• I have verified that the issue is reproducible with the latest nightly build

Version

207.1

[andig]

[ocpp ] DEBUG 2025/08/04 10:26:59 charge point disconnected: 184702771966111

Your charger disconnected, reason unknown.

[hf81-ble]

But if even if it reconnects.. nothing happens... other implementations like the Steve OCPP Server are working... so guess, its a timing issue. but how can i debug this?

See here the other logs

`[mqtt ] DEBUG 2025/08/01 18:08:10 tcp://192.168.200.68:1883 connected
[main ] INFO 2025/08/01 18:08:10 UI listening at :7070
[184702771966111-1] DEBUG 2025/08/01 18:08:10 waiting for chargepoint: 5m0s
[ocpp ] DEBUG 2025/08/01 18:10:28 charge point connected: 184702771966111
[ocpp ] DEBUG 2025/08/01 18:10:30 charge point disconnected: 184702771966111
[184702771966111-1] DEBUG 2025/08/01 18:10:30 failed configuring availability: timeout
[main ] FATAL 2025/08/01 18:10:30 charger [Wallbox11k] cannot create charger 'Wallbox11k': cannot create charger type 'template': cannot create charger type 'ocpp': cannot send request 963144119, no client 184702771966111 exists
[main ] FATAL 2025/08/01 18:10:30 will attempt restart in: 15m0s
[ocpp ] DEBUG 2025/08/01 18:11:20 charge point connected: 184702771966111
[ocpp ] DEBUG 2025/08/01 18:12:53 charge point disconnected: 184702771966111
[ocpp ] DEBUG 2025/08/01 18:13:44 charge point connected: 184702771966111

Restart:
Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2025/08/01 19:03:43 evcc 0.206.1
[main ] INFO 2025/08/01 19:03:43 using config file: /config/evcc.yaml
[db ] INFO 2025/08/01 19:03:43 using sqlite database: /data/evcc.db
[mqtt ] INFO 2025/08/01 19:03:43 connecting evcc-1013534546 at tcp://192.168.200.68:1883
[mqtt ] DEBUG 2025/08/01 19:03:43 tcp://192.168.200.68:1883 connected
[main ] INFO 2025/08/01 19:03:43 UI listening at :7070
[184702771966111-1] DEBUG 2025/08/01 19:03:43 waiting for chargepoint: 5m0s
[ocpp ] DEBUG 2025/08/01 19:04:08 charge point connected: 184702771966111
[ocpp ] DEBUG 2025/08/01 19:04:10 charge point disconnected: 184702771966111
[184702771966111-1] DEBUG 2025/08/01 19:04:10 failed configuring availability: timeout
[main ] FATAL 2025/08/01 19:04:10 charger [Wallbox11k] cannot create charger 'Wallbox11k': cannot create charger type 'template': cannot create charger type 'ocpp': cannot send request 4204585898, no client 184702771966111 exists
[main ] FATAL 2025/08/01 19:04:10 will attempt restart in: 15m0s
[ocpp ] DEBUG 2025/08/01 19:05:00 charge point connected: 184702771966111

Restart:
Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2025/08/03 10:16:57 evcc 0.206.1
[main ] INFO 2025/08/03 10:16:57 using config file: /config/evcc.yaml
[db ] INFO 2025/08/03 10:16:57 using sqlite database: /data/evcc.db
[mqtt ] INFO 2025/08/03 10:16:57 connecting evcc-562849984 at tcp://192.168.200.68:1883
[mqtt ] DEBUG 2025/08/03 10:16:57 tcp://192.168.200.68:1883 connected
[main ] INFO 2025/08/03 10:16:57 UI listening at :7070
[184702771966111-1] DEBUG 2025/08/03 10:16:57 waiting for chargepoint: 5m0s
[ocpp ] DEBUG 2025/08/03 10:17:45 charge point connected: 184702771966111
[ocpp ] DEBUG 2025/08/03 10:17:47 charge point disconnected: 184702771966111
[184702771966111-1] DEBUG 2025/08/03 10:17:47 failed configuring availability: timeout
[main ] FATAL 2025/08/03 10:17:47 charger [Wallbox11k] cannot create charger 'Wallbox11k': cannot create charger type 'template': cannot create charger type 'ocpp': cannot send request 2371072261, no client 184702771966111 exists
[main ] FATAL 2025/08/03 10:17:47 will attempt restart in: 15m0s
[main ] INFO 2025/08/03 10:17:47 new version available: 0.207.0
[ocpp ] DEBUG 2025/08/03 10:18:37 charge point connected: 184702771966111

Restart:
Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2025/08/04 10:26:42 evcc 0.207.1
[main ] INFO 2025/08/04 10:26:42 using config file: /config/evcc.yaml
[db ] INFO 2025/08/04 10:26:42 using sqlite database: /data/evcc.db
[mqtt ] INFO 2025/08/04 10:26:42 connecting evcc-14966283 at tcp://192.168.200.68:1883
[mqtt ] DEBUG 2025/08/04 10:26:42 tcp://192.168.200.68:1883 connected
[main ] INFO 2025/08/04 10:26:42 UI listening at :7070
[184702771966111-1] DEBUG 2025/08/04 10:26:42 waiting for chargepoint: 5m0s
[ocpp ] DEBUG 2025/08/04 10:26:57 charge point connected: 184702771966111
[ocpp ] DEBUG 2025/08/04 10:26:59 charge point disconnected: 184702771966111
[184702771966111-1] DEBUG 2025/08/04 10:26:59 failed configuring availability: timeout
[mercedes] DEBUG 2025/08/04 10:26:59 identity.NewIdentity - database token found
[mercedes] DEBUG 2025/08/04 10:26:59 identity.NewIdentity - refreshToken started
[main ] ERROR 2025/08/04 10:27:00 creating tariff co2 failed: invalid tariff type: grã¼nstromindex
[main ] FATAL 2025/08/04 10:27:00 charger [Wallbox11k] cannot create charger 'Wallbox11k': cannot create charger type 'template': cannot create charger type 'ocpp': cannot send request 295242667, no client 184702771966111 exists
loadpoint [lp-1] charger: not found: Wallbox11k
[main ] FATAL 2025/08/04 10:27:00 will attempt restart in: 15m0s
[ocpp ] DEBUG 2025/08/04 10:27:49 charge point connected: 184702771966111`

[aspengler]

Ist evtl das hier nötig?

Hinweis: In Ausnahmefällen kann es erforderlich sein, diese ID manuell an die OCPP-URL der Ladestation in der Form ws://<evcc-adresse>:8887/<stationid> anzuhängen.

[hf81-ble]

ich glaube die warten länger. An der ID:0 liegt es auf jedenfall nicht.

Hier der ChangeAvailabilityRequest

Und die Antwort kommt auch

[hf81-ble]

Doofe Frage, wartet ihr die die BootNotification ab? Ich habe einen wireshark dump gemacht, und mit dem Aufbau des websockets, versucht ihr direkt die Availability zu senden. Auf was basiert euer Connected Event?

[premultiply]

StatusNotification

Einfach im Code schauen 😉

[hf81-ble]

Ich habe jetzt erstmal Blackbox Testing gemacht ;)

Und mit Wireshark den Websocket Traffic angeschaut.

OCPP mit EVCC

OCPP mit SteVe

OCPP mit EVCC nochmal ein längerer Trace bei dem die Reihefolge nochmal klar wird.

Ohne BootNotification mit Accept weißt doch der Chargepoint gar nicht, ob er von dem CS überhaupt gesteuert werden darf. Somit könnte das Verhalten durchaus gewollt sein. So nach dem Motto: "Da könnte ja jeder kommen"

[premultiply]

Die BootNotification ist eigentlich für die Funktion mit evcc nicht relevant.
Wir versuchen sie nur anzutriggern und werten sie aus um den Hersteller und Typ/Firmware des CP anzuzeigen.

Ein CP signalisiert ansonsten damit dem CS nur dass er (neu)gestartet wurde. Für evcc eigentlich nicht relevant.