Skip to main content

Chargers

To control charging, evcc needs to be able to communicate with at least one Charger.

The configuration is formatted as follows:

charger:
- name: wallbox
type: ...

All of the Chargers listed on this page are supported by evcc. Once you have adapted the code samples to suit your Charger(s) in evcc.yaml, you can test the connection using the evcc charger command, which returns the current status of all connected Chargers. If you just want to test one Charger at a time, use evcc charger --name my_charger.

$ ./evcc charger

Power: 0W
Current L1..L3: 0A 0A 0A
Charge status: A
Enabled: false

ABB Terra AC πŸ’šβ€‹

Requires firmware >= 1.6.5

chargers:
- name: my_charger
type: template
template: abb

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 1
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 9600 # PrΓΌfe die GerΓ€teeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8N1" # Kommunikationsparameter fΓΌr den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port

# Modbus TCP
modbus: tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

ABL​

eM4 (SBCx) πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: abl-em4

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

eMH1, eMH2 πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: abl

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 1
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 38400 # PrΓΌfe die GerΓ€teeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8E1" # Kommunikationsparameter fΓΌr den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Alfen Eve πŸ’šβ€‹

The "Active load balancing" license is required for external Modbus control of the charger. Enable "Active Load Balancing" and select "Energy Management System" as Data Source in the configuration. When using "Double" charger both loadpoints need to be added. The the first port (or single) is accessable on ID 1, second port on ID 2.

chargers:
- name: my_charger
type: template
template: alfen

# Modbus TCP
modbus: tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
note

Automatic 1p/3p switching is supported.

Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Alphatec Wallbox Mini/ AW1eM πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: alphatec

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 1
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 9600 # PrΓΌfe die GerΓ€teeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8N1" # Kommunikationsparameter fΓΌr den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Amperfied​

Wallbox connect.business πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: amperfied

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Wallbox connect.home πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: amperfied

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Wallbox Energy Control πŸ’šβ€‹

Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2).

chargers:
- name: my_charger
type: template
template: heidelberg

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 1
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 19200 # PrΓΌfe die GerΓ€teeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8E1" # Kommunikationsparameter fΓΌr den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Audi​

Audi Wallbox pro (Beta)​

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.

chargers:
- name: my_charger
type: template
template: ellipro
ski: # The SKI of the wallbox, usually found on the web interface of the wallbox
ip: 192.0.2.2 # IP address

Wallbox plus (Beta)​

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.

chargers:
- name: my_charger
type: template
template: elliconnect
ski: # The SKI of the wallbox, usually found on the web interface of the wallbox
ip: 192.0.2.2 # IP address

Bender CC612/613 πŸ’šβ€‹

The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On.

chargers:
- name: my_charger
type: template
template: bender
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

BMW​

i Wallbox πŸ’šβ€‹

Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required.

chargers:
- name: my_charger
type: template
template: keba-modbus

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
note

Automatic 1p/3p switching is supported.

Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

i Wallbox (legacy UDP protocol)​

This requires the UDP function to be enabled with DIP 1.3 = ON, see the installation manual.

chargers:
- name: my_charger
type: template
template: keba
host: 192.0.2.2 # IP address or hostname

cFos Power Brain, Power Brain Solar πŸ’šβ€‹

The meter- if present- must be configured separately as charge meter. Phase switching is only available with the Solar variant and must be enabled by the user.

chargers:
- name: my_charger
type: template
template: cfos
host: 192.0.2.2 # IP address or hostname
note

Automatic 1p/3p switching is supported.

Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Compleo eBox πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: innogy-ebox

# Modbus TCP
modbus: tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Cupra​

Charger Connect (Beta)​

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.

chargers:
- name: my_charger
type: template
template: elliconnect
ski: # The SKI of the wallbox, usually found on the web interface of the wallbox
ip: 192.0.2.2 # IP address

Charger Pro (Beta)​

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.

chargers:
- name: my_charger
type: template
template: ellipro
ski: # The SKI of the wallbox, usually found on the web interface of the wallbox
ip: 192.0.2.2 # IP address

Dadapower Premium Wallbox​

chargers:
- name: my_charger
type: template
template: dadapower

# Modbus TCP
modbus: tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
note

Automatic 1p/3p switching is supported.

DaheimLaden​

Wallbox​

For use with evcc, the wallbox must be operated in RFID mode.

chargers:
- name: my_charger
type: template
template: daheimladen
token: # Request your access token from Daheimladen support: info@daheimladen.de. (optional)
stationid: # Serial number as displayed on the wallbox display. (optional)

Wallbox (via ModbusTCP)​

Wallbox must be operated with a recent firmware including Modbus support. Furthermore, β€œNachladen” (Smart) or β€œRSDA” (Touch) must be activated in settings.

chargers:
- name: my_charger
type: template
template: daheimladen-mb
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)

E.ON Drive​

eBox πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: innogy-ebox

# Modbus TCP
modbus: tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

vBox πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: vestel

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

E3/DC Easy Connect πŸ’šβ€‹

DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended.

chargers:
- name: my_charger
type: template
template: phoenix-ev-eth

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Easee Home πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: easee
user: # Email address
password: # same as Easee app or the web portal (https://easee.cloud)
charger: EH______
authorize: # Controls wether evcc shall perform authentication against charger. Benefit is a contolled start of charging. Not compatible with RFID identification of vehicles. (optional)
note

Automatic 1p/3p switching is supported.

Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Ebee Wallbox πŸ’šβ€‹

The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On.

chargers:
- name: my_charger
type: template
template: bender
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

echarge​

cPH1 πŸ’šβ€‹

Charge mode must be configured as manual

chargers:
- name: my_charger
type: template
template: hardybarth-ecb1
host: 192.0.2.2 # IP address or hostname
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

cPH2, cPΞΌ2 πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: hardybarth-salia
host: 192.0.2.2 # IP address or hostname
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Elli​

Charger Connect (Beta)​

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.

chargers:
- name: my_charger
type: template
template: elliconnect
ski: # The SKI of the wallbox, usually found on the web interface of the wallbox
ip: 192.0.2.2 # IP address

Charger Pro (Beta)​

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.

chargers:
- name: my_charger
type: template
template: ellipro
ski: # The SKI of the wallbox, usually found on the web interface of the wallbox
ip: 192.0.2.2 # IP address

EM2GO Pro Power/OCPP/ONC​

Recent firmware with Modbus support required (Pro Power: 1.01 and OCPP/ONC: 3.15)

chargers:
- name: my_charger
type: template
template: em2go

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port

Ensto Chago Wallbox πŸ’šβ€‹

The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On.

chargers:
- name: my_charger
type: template
template: bender
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

ESL Walli LIGHT πŸ’šβ€‹

DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended.

chargers:
- name: my_charger
type: template
template: phoenix-ev-eth

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Etrel​

INCH πŸ’šβ€‹

The charger must be switched to "Power" charging mode.

chargers:
- name: my_charger
type: template
template: etrel
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

INCH Duo πŸ’šβ€‹

The charger must be switched to "Power" charging mode.

chargers:
- name: my_charger
type: template
template: etrel-duo
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

EVBox Elvi​

chargers:
- name: my_charger
type: template
template: elvi
meter: true # Deactivate if the charger has no integrated metering device installed (optional)

EVSE DIN​

chargers:
- name: my_charger
type: template
template: evse-din

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 1
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 9600 # PrΓΌfe die GerΓ€teeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8N1" # Kommunikationsparameter fΓΌr den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port

EVSE-WiFi​

chargers:
- name: my_charger
type: template
template: evsewifi
host: 192.0.2.2 # IP address or hostname

Fronius Wattpilot​

Requires firmware 36.3 or later.

chargers:
- name: my_charger
type: template
template: fronius-wattpilot
host: 192.0.2.2 # IP address or hostname
password: # Password of the user account (use single quotes in case of leading zeros) (optional)
note

Automatic 1p/3p switching is supported.

Garo GLB, GLB+, LS4, LS4 compact πŸ’šβ€‹

The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On.

chargers:
- name: my_charger
type: template
template: bender
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

go-eCharger​

Gemini, HOME+, HOMEfix (V3) πŸ’šβ€‹

Requires firmware 052.1 or later.

For 1P/3P-Phase switching the HTTP API v2 in the charger setup needs to be activated.

chargers:
- name: my_charger
type: template
template: go-e-v3
host: 192.0.2.2 # IP address or hostname
note

Automatic 1p/3p switching is supported.

Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

HOME+, HOMEfix, Pro πŸ’šβ€‹

Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated.

chargers:
- name: my_charger
type: template
template: go-e
host: 192.0.2.2 # IP address or hostname
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

HardyBarth​

cPH1 πŸ’šβ€‹

Charge mode must be configured as manual

chargers:
- name: my_charger
type: template
template: hardybarth-ecb1
host: 192.0.2.2 # IP address or hostname
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

cPH2, cPΞΌ2 πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: hardybarth-salia
host: 192.0.2.2 # IP address or hostname
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Heidelberg Energy Control πŸ’šβ€‹

Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2).

chargers:
- name: my_charger
type: template
template: heidelberg

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 1
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 19200 # PrΓΌfe die GerΓ€teeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8E1" # Kommunikationsparameter fΓΌr den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Hesotec eSat, eBox πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: hesotec

# Modbus TCP
modbus: tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Innogy eBox πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: innogy-ebox

# Modbus TCP
modbus: tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

INRO Pantabox​

chargers:
- name: my_charger
type: template
template: pantabox
host: 192.0.2.2 # IP address or hostname

Juice Charger Me πŸ’šβ€‹

The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On.

chargers:
- name: my_charger
type: template
template: bender
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

KEBA​

KeContact P20, P30, C/X Series πŸ’šβ€‹

Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required.

chargers:
- name: my_charger
type: template
template: keba-modbus

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
note

Automatic 1p/3p switching is supported.

Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

KeContact P20, P30, C/X Series (legacy UDP protocol)​

This requires the UDP function to be enabled with DIP 1.3 = ON, see the installation manual.

chargers:
- name: my_charger
type: template
template: keba
host: 192.0.2.2 # IP address or hostname

KSE wBX16 πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: kse

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 100
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 9600 # PrΓΌfe die GerΓ€teeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8E1" # Kommunikationsparameter fΓΌr den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 100
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

LadeFoxx EvLoad/ Mikro 2.0​

chargers:
- name: my_charger
type: template
template: phoenix-charx

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port

Mennekes​

Amedio, Amtron ChargeControl, Professional πŸ’šβ€‹

The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On.

chargers:
- name: my_charger
type: template
template: bender
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

AMTRON XTRA, AMTRON PREMIUM πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: amtron

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

NRGKick​

Bluetooth​

chargers:
- name: my_charger
type: template
template: nrgkick-bluetooth
mac:
pin:

Connect​

chargers:
- name: my_charger
type: template
template: nrgkick-connect
host: 192.0.2.2 # IP address or hostname
mac:
password: # Password of the user account (use single quotes in case of leading zeros)

OBO Bettermann Ion​

chargers:
- name: my_charger
type: template
template: obo

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 101
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 19200 # PrΓΌfe die GerΓ€teeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8E1" # Kommunikationsparameter fΓΌr den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 101
host: 192.0.2.2 # Hostname
port: 502 # Port

# Modbus TCP
modbus: tcpip
id: 101
host: 192.0.2.2 # Hostname
port: 502 # Port

OpenEVSE​

Requires firmware 7.0 or later.

chargers:
- name: my_charger
type: template
template: openevse
host: 192.0.2.2 # IP address or hostname
user: # User account (e.g. email address, user id, etc.) (optional)
password: # Password of the user account (use single quotes in case of leading zeros) (optional)

openWB​

Pro​

chargers:
- name: my_charger
type: template
template: openwb-pro
host: 192.0.2.2 # IP address or hostname
note

Automatic 1p/3p switching is supported.

series2​

The wallbox has to be configured as loadpoint.

chargers:
- name: my_charger
type: template
template: openwb
host: 192.0.2.2 # IP address or hostname

Optec Mobility One πŸ’šβ€‹

The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On.

chargers:
- name: my_charger
type: template
template: bender
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Orbis Viaris Uni​

chargers:
- name: my_charger
type: template
template: orbis-viaris

PC Electric Garo πŸ’šβ€‹

Only devices configured as master can be used right now!

chargers:
- name: my_charger
type: template
template: pcelectric-garo
host: 192.0.2.2 # IP address or hostname
port: 8080 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Phoenix Contact​

CHARX​

chargers:
- name: my_charger
type: template
template: phoenix-charx

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port

EM-CP-PP-ETH (Modbus TCP)​

chargers:
- name: my_charger
type: template
template: phoenix-em-eth

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port

EV-CC-AC1-M3-CBC-RCM-ETH, EV-CC-AC1-M3-CBC-RCM-ETH-3G, EV-CC-AC1-M3-RCM-ETH-XP, EV-CC-AC1-M3-RCM-ETH-3G-XP πŸ’šβ€‹

DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended.

chargers:
- name: my_charger
type: template
template: phoenix-ev-eth

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

EV-SER (Modbus RTU)​

chargers:
- name: my_charger
type: template
template: phoenix-ev-ser

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 1
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 9600 # PrΓΌfe die GerΓ€teeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8N1" # Kommunikationsparameter fΓΌr den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port

Porsche​

Mobile Charger Connect​

chargers:
- name: my_charger
type: template
template: pmcc
ski: # The SKI of the wallbox, usually found on the web interface of the wallbox
ip: 192.0.2.2 # IP address (optional)

Mobile Charger Plus​

chargers:
- name: my_charger
type: template
template: pmcp
ski: # The SKI of the wallbox, usually found on the web interface of the wallbox
ip: 192.0.2.2 # IP address (optional)

Pracht Alpha XT, XT+, Mono XT, Mono XT+, PNI πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: pracht-alpha

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 1
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 9600 # PrΓΌfe die GerΓ€teeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8N1" # Kommunikationsparameter fΓΌr den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port

# Modbus TCP
modbus: tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

chargers:
- name: my_charger
type: template
template: schneider-evlink

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Schrack i-CHARGE CION​

chargers:
- name: my_charger
type: template
template: ichargecion

# Modbus TCP
modbus: tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port

SENEC​

Wallbox pro πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: abl

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 1
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 38400 # PrΓΌfe die GerΓ€teeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8E1" # Kommunikationsparameter fΓΌr den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Wallbox pro s πŸ’šβ€‹

Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2).

chargers:
- name: my_charger
type: template
template: heidelberg

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 1
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 19200 # PrΓΌfe die GerΓ€teeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8E1" # Kommunikationsparameter fΓΌr den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Siemens Versicharge GEN3 πŸ’šβ€‹

Requires firmware >= 2.121.5

chargers:
- name: my_charger
type: template
template: versicharge

# Modbus TCP
modbus: tcpip
id: 2
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Skoda​

iV Charger Connect (Beta)​

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.

chargers:
- name: my_charger
type: template
template: elliconnect
ski: # The SKI of the wallbox, usually found on the web interface of the wallbox
ip: 192.0.2.2 # IP address

iV Charger Connect+ (Beta)​

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.

chargers:
- name: my_charger
type: template
template: ellipro
ski: # The SKI of the wallbox, usually found on the web interface of the wallbox
ip: 192.0.2.2 # IP address

SMA EV Charger πŸ’šβ€‹

The charger must be switched to "Fast" charging mode and the user must have "Administrator" rights.

chargers:
- name: my_charger
type: template
template: smaevcharger
host: 192.0.2.2 # IP address or hostname
user: # User account (e.g. email address, user id, etc.)
password: # Password of the user account (use single quotes in case of leading zeros)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

smartWB​

chargers:
- name: my_charger
type: template
template: smartwb
host: 192.0.2.2 # IP address or hostname

SolarEdge Home EV Charger πŸ’šβ€‹

Requires firmware version 3.10.42 (C-series) bzw. 1.11 (X-series). For phase switching the Keba phase switch (KeContact S10) is also required.

chargers:
- name: my_charger
type: template
template: keba-modbus

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
note

Automatic 1p/3p switching is supported.

Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Sonnen sonnenCharger πŸ’šβ€‹

The charger must be switched to "Power" charging mode.

chargers:
- name: my_charger
type: template
template: etrel
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Stark in Strom Easy​

chargers:
- name: my_charger
type: template
template: evse-din

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 1
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 9600 # PrΓΌfe die GerΓ€teeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8N1" # Kommunikationsparameter fΓΌr den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port

TechniSat Technivolt πŸ’šβ€‹

The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On.

chargers:
- name: my_charger
type: template
template: bender
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Tesla TWC3​

The TWC wallbox cannot be controlled directly. Control is via the vehicle. The vehicle must be associated with the TWC3 loadpoint. At this time only Tesla vehicles are supported.

chargers:
- name: my_charger
type: template
template: twc3
host: 192.0.2.2 # IP address or hostname

TinkerForge​

WARP Charger Pro​

Firmware v2 required. Automatic phase switching requires the additional WARP Energy Manager.

chargers:
- name: my_charger
type: template
template: tinkerforge-warp
host: 192.0.2.2 # IP address or hostname of the MQTT broker
port: 1883 # MQTT broker port (optional)
topic: warp # Topic (omit leading /) (optional)
energymanager: # EnergyManager MQTT topic if installed (optional)
note

Automatic 1p/3p switching is supported.

WARP Charger Smart​

Firmware v2 required. Automatic phase switching requires the additional WARP Energy Manager.

chargers:
- name: my_charger
type: template
template: tinkerforge-warp
host: 192.0.2.2 # IP address or hostname of the MQTT broker
port: 1883 # MQTT broker port (optional)
topic: warp # Topic (omit leading /) (optional)
energymanager: # EnergyManager MQTT topic if installed (optional)
note

Automatic 1p/3p switching is supported.

Ubitricity Heinz πŸ’šβ€‹

The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On.

chargers:
- name: my_charger
type: template
template: bender
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Vestel EVC04 Home Smart/Connect Plus πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: vestel

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Volkswagen​

ID. Charger Connect (Beta)​

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.

chargers:
- name: my_charger
type: template
template: elliconnect
ski: # The SKI of the wallbox, usually found on the web interface of the wallbox
ip: 192.0.2.2 # IP address

ID. Charger Pro (Beta)​

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.

chargers:
- name: my_charger
type: template
template: ellipro
ski: # The SKI of the wallbox, usually found on the web interface of the wallbox
ip: 192.0.2.2 # IP address

Wallbe​

Eco, Eco 2.0(s), Pro πŸ’šβ€‹

DIP switch 10 at the controller needs to be set to 'ON'. A recent controller firmware is recommended.

chargers:
- name: my_charger
type: template
template: phoenix-ev-eth

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Eco, Pro​

The Wallbe must be connected using Ethernet and the DIP switch 10 must be set to 'ON'.

chargers:
- name: my_charger
type: template
template: wallbe
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)

Eco, Pro (pre ~2019)​

DIP switch 10 must be set to 'ON'.

chargers:
- name: my_charger
type: template
template: wallbe-pre2019
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)

Eco, Pro (pre ~2019, with meter)​

DIP switch 10 must be set to 'ON'.

chargers:
- name: my_charger
type: template
template: wallbe-pre2019-meter
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)

Eco, Pro (with meter)​

DIP switch 10 must be set to 'ON'.

chargers:
- name: my_charger
type: template
template: wallbe-meter
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)

wallbox Pulsar Plus / Commander 2 / Copper SB​

Setup Guide: https://support.wallbox.com/en/knowledge-base/ocpp-activation-and-setup-guide/

  • Switch on β€œEnable OCPP” (myWallbox app) or enable the β€œOCPP WebSocket connection” switch (myWallbox Portal)
  • URL: ws://[evcc-adresse]:8887/ (local network connection)
  • Charge Point Identity: Custom value (e.g. serial number of charger) which is reused in configuration as stationid
  • Password: leave empty
chargers:
- name: my_charger
type: template
template: pulsarplus

Walther Werke Basic Evo Pro πŸ’šβ€‹

Please read the wiring and configuration manual carefully. All boxes must be configured for external control in follower mode (DIP S5/4 OFF). Each box needs an individual Modbus ID (DIP S4). Ensure correct RS485 cabling including bus termination (DIP S6/2).

chargers:
- name: my_charger
type: template
template: heidelberg

# RS485 via adapter (Modbus RTU)
modbus: rs485serial
id: 1
device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
baudrate: 19200 # PrΓΌfe die GerΓ€teeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
comset: "8E1" # Kommunikationsparameter fΓΌr den Adapter

# RS485 via TCP/IP (Modbus RTU)
modbus: rs485tcpip
id: 1
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Webasto​

Live πŸ’šβ€‹

The 'Modbus TCP Server' must be enabled. The setting 'Register Address Set' must NOT be set to 'Phoenix' or 'TQ-DM100'. Use the third selection labeled 'Ebee', 'Bender', 'MENNEKES' etc. Set 'Allow UID Disclose' to On.

chargers:
- name: my_charger
type: template
template: bender
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

NEXT πŸ’šβ€‹

Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc.

chargers:
- name: my_charger
type: template
template: webasto-next
host: 192.0.2.2 # IP address or hostname
port: 502 # Port (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Unite πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: vestel

# Modbus TCP
modbus: tcpip
id: 255
host: 192.0.2.2 # Hostname
port: 502 # Port
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Zaptec Go/Pro πŸ’šβ€‹

chargers:
- name: my_charger
type: template
template: zaptec
id: # Charger ID (optional)
user: # User account (e.g. email address, user id, etc.) (optional)
password: # Password of the user account (use single quotes in case of leading zeros) (optional)
Sponsor Token Required

More information on πŸ’š evcc Sponsorship can be found here.

Generic support​

Custom​

chargers:
- name: my_charger
type: custom
status: # charger status A..F
source: ...
# ...
enabled: # charger enabled state (true/false or 0/1)
source: ...
# ...
enable: # set charger enabled state (true/false or 0/1)
source: ...
# ...
maxcurrent: # set charger max current (A)
source: ...
# ...

EEBUS compatible Wallbox​

chargers:
- name: my_charger
type: template
template: eebus
ski: # The SKI of the wallbox, usually found on the web interface of the wallbox
ip: 192.0.2.2 # IP address (optional)

OCPP 1.6J compatible charger with Smart Charging Profile​

With OCPP the connection will be established from charger (client) to evcc (server). The charger needs to be able to reach evcc via the host name (functioning DNS resolution required!) or via the IP address on port 8887. By default, the first incoming connection with any station identifier is used. In order to be able to clearly assign several charging points, the respective station identifier (stationid: ) and connector number (connector: ) must be configured. Many wallboxes automatically add the station id to the backend URL, some have to do this manually ws://<evcc>:8887/<stationid>. The charger may need a pre-configured (virtual) token ID/RFID identifier (idtag: ) with which the charging sessions can be started without authorization. If the charger supports sending metering values try to adjust the interval to a short time span.

Requirements:

  • If necessary, remove previously configured OCPP profiles (e.g. used for a different backend connection) in the charger configuration
  • Backend URL (Central System) in the charger configuration: ws://[evcc-adresse]:8887/ (possibly add stationid)
  • Protocol: OCPP-J v1.6, ocpp16j, JSON, Websocket, ws:// or similar
  • No encryption, no authentication, no password
  • Local network connection
chargers:
- name: my_charger
type: template
template: ocpp

Switchable sockets​

Switchable Sockets (including smart-home switches) supported by evcc can be operated in one of two modes:

  • Charger Mode (default)
  • Static-Switch Mode

Charger Mode allows use of the Switchable Socket to control the charging of battery-operated devices such as e-Motorcycles, e-Bikes, etc). Charging current is measured and displayed by evcc, and the device is considered "charged" when power draw drops to a trickle (i.e power < standbypower)

In contrast, Static-Switch Mode can be used to easily control consumers such as heat pumps, air conditioning systems, and more. The status of the device is determined by whether the Socket is on or off (on = "charging", off = "charged").

note

When using Static-Switch Mode, it is recommended to define a separate custom Meter in order to display meaningful performance information.

For all Switchable Sockets, the mode depends on how standbypower is configured.

If the value of standbypower is greater than or equal to 0 (standbypower >= 0), then the Socket uses Charger Mode, and the set value is treated as the threshold value (in Watts). So long as the measured socket power is above this threshold value, the device is treated as "charging". If the power falls below this value (usually when the device is trickle-charging when its battery is full), it is treated as "charged" / complete.

If standbypower is set to a negative value, then the Socket uses Static-Switch Mode.

info

The Charging Point parameter phases must be set to 1 when using a switchable socket to ensure proper control.

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
- title: Shelly # display name for UI
charger: my_charger # charger
vehicle: audi
mode: pv
---
mincurrent: 9 # 9A*220V=1980W minimum charge current (default 6A)
maxcurrent: 10 # 10A*220V=2200W maximum charge current (default 16A)
phases: 1 # ev phases (default 3)

AVM FritzDECT​

chargers:
- name: my_charger
type: template
template: fritzdect
uri: https://fritz.box # HTTP(S) address (optional)
user: # User account (e.g. email address, user id, etc.)
password: # Password of the user account (use single quotes in case of leading zeros)
ain: 307788992233 # The AIN is printed on the type label on the back of the device. Embed it in double quotes in case of leading zeroes.
standbypower: 15 # Power values above this value will be considered as charging pow (optional)

Homematic / Homematic IP​

chargers:
- name: my_charger
type: template
template: homematic
host: 192.0.2.2 # IP address or hostname
port: 2010 # Port (optional)
device: '0001EE89AAD848' # Homematic device id like shown in the CCU web user interface.
user: # User account (e.g. email address, user id, etc.) (optional)
password: # Password of the user account (use single quotes in case of leading zeros) (optional)
standbypower: 15 # Power values above this value will be considered as charging pow (optional)

HomeWizard​

chargers:
- name: my_charger
type: template
template: homewizard
host: 192.0.2.2 # IP address or hostname
standbypower: 15 # Power values above this value will be considered as charging pow (optional)

myStrom Switch​

chargers:
- name: my_charger
type: template
template: mystrom
host: 192.0.2.2 # IP address or hostname
standbypower: 15 # Power values above this value will be considered as charging pow (optional)

Shelly​

chargers:
- name: my_charger
type: template
template: shelly
host: 192.0.2.2 # IP address or hostname
user: # User account (e.g. email address, user id, etc.) (optional)
password: # Password of the user account (use single quotes in case of leading zeros) (optional)
channel: 0 # optional
standbypower: 15 # Power values above this value will be considered as charging pow (optional)

Tasmota​

chargers:
- name: my_charger
type: template
template: tasmota
host: 192.0.2.2 # IP address or hostname
user: # admin is default (optional)
password: # Password of the user account (use single quotes in case of leading zeros) (optional)
channel: 1 # Device relay channel number (allowed range 1-8)
standbypower: 15 # Power values above this value will be considered as charging pow (optional)

H-Series Smart Plug​

chargers:
- name: my_charger
type: template
template: tplink
host: 192.0.2.2 # IP address or hostname
standbypower: 15 # Power values above this value will be considered as charging pow (optional)

Tapo P-Series Smart Plug​

chargers:
- name: my_charger
type: template
template: tapo
host: 192.0.2.2 # IP address or hostname
user: # User account (e.g. email address, user id, etc.)
password: # Password of the user account (use single quotes in case of leading zeros)
standbypower: 15 # Power values above this value will be considered as charging pow (optional)