Evcc is an extensible EV Charge Controller with PV integration implemented in Go. Featured in PV magazine.
- simple and clean user interface
- multiple chargers:
- Open source: openWB, EVSEWifi (includes smartWB)
- Other commercial: ABL eMH1, Alfen Eve, cFos PowerBrain, Daheimladen, go-eCharger, Heidelberg Energy Control, Innogy eBox, KEBA/BMW, Menneckes Amtron (Xtra/Premium), NRGkick, PC Electric (includes Garo), Wallbe, Mobile Charger Connect, EEBUS (experimental)
- Build-your-own: Phoenix (includes ESL Walli), EVSE DIN
- Smart-Home outlets: FritzDECT, Shelly, Tasmota, TP-Link
- multiple meters: ModBus (Eastron SDM, MPM3PM, SBC ALE3 and many more), Discovergy (using HTTP plugin), SMA Sunny Home Manager and Energy Meter, KOSTAL Smart Energy Meter (KSEM, EMxx), any Sunspec-compatible inverter or home battery devices (Fronius, SMA, SolarEdge, KOSTAL, STECA, E3DC, ...), Tesla PowerWall, LG ESS HOME
- wide support of vendor-specific vehicles interfaces (remote charge, battery and preconditioning status): Audi, BMW, Fiat, Ford, Hyundai, Kia, Mini, Nissan, Niu, Porsche, Renault, Seat, Smart, Skoda, Tesla, Volkswagen, Volvo, Tronity
- plugins for integrating with any charger/ meter/ vehicle: Modbus (meters and grid inverters), HTTP, MQTT, Javascript, WebSockets and shell scripts
- status notifications using Telegram, PushOver and many more
- logging using InfluxDB and Grafana
- granular charge power control down to mA steps with supported chargers (labeled by e.g. smartWB als OLC)
- REST and MQTT APIs for integration with home automation systems (e.g. HomeAssistant)
You'll find everything you need in our documentation (German).
To build EVCC from source, Go 1.16 and Node 16 are required:
makeEvcc believes in open source software. We're committed to provide best in class EV charging experience. Maintaining evcc consumes time and effort. With the vast amount of different devices to support, we depend on community and vendor support to keep EVCC alive.
While evcc is open source, we would also like to encourage vendors to provide open source hardware devices, public documentation and support open source projects like hours that provide additional value to otherwised closed hardware. Where this is not the case, EVCC requires "sponsor token" to finance ongoing development and support of evcc.
The personal sponsor token requires a Github Sponsorship and can be requested at cloud.evcc.io. A sponsor token is valid for one year and can be renewed any time with active sponsorship.
Evcc is heavily inspired by OpenWB. However, in 2019, I found OpenWB's architecture slightly intimidating with everything basically global state and heavily relying on shell scripting. On the other side, especially the scripting aspect is one that contributes to OpenWB's flexibility.
Hence, for a simplified and stricter implementation of an EV charge controller, the design goals for evcc were:
- typed language with ability for systematic testing - achieved by using Go
- structured configuration - supports YAML-based config file
- avoidance of feature bloat, simple and clean UI - utilizes Vue.js and Bootstrap
- containerized operation beyond Raspberry Pi - provide multi-arch Docker Image