# Cupra Charger Connect

Source: https://docs.evcc.io/en/chargers/cupra-charger-connect

The device has to have a fix IP address (manuall or via DHCP).

The identification of a vehicle using the RFID card is not possible.

Important: A mostly flawless functionality can only be provided with an external energy meter and no usage of CT coils, due to sosftware bugs of the Wallbox. Using a LAN connection is highly recommended.

Note: If you've added an energy meter to your charger please use the Pro or Connected+ integration.

Supported features: dim

## Known limitations

- Many known EEBUS firmware bugs that the manufacturer will not fix: charging measurements are often missing or stale and the connection drops frequently. An external meter is required.
 (https://github.com/evcc-io/evcc/discussions/15367)

## Parameters

| Name | Description | Default / example | |
| --- | --- | --- | --- |
| ski | Subject Key Identifier (SKI) Usually found on the web interface of the wallbox |  |  |
| ip | IP address | 192.0.2.2 |  |

## Configuration example for evcc.yaml

```yaml
chargers:
    - name: my_charger
      type: template
      template: elliconnect
      ski: # Subject Key Identifier (SKI), Usually found on the web interface of the wallbox
      ip: 192.0.2.2 # IP address, optional
```