no supporter feture fork of evcc.io
Find a file
2025-10-14 13:37:32 +02:00
.devcontainer chore: update devcontainer image to latest version 2025-09-20 08:07:38 +02:00
.github chore: proper escaping, see #24300, drop actions/ai-inference and use plain js 2025-10-14 10:09:35 +02:00
.storybook chore: Typescript: Rewrite Configs (#21763) 2025-09-28 11:10:24 +02:00
.vscode Configure Typescript (#19774) 2025-03-21 15:00:50 +01:00
api Add BMW CarData api (#23972) 2025-10-04 09:43:34 +00:00
assets Forecast chart: fix solar area glitch (#24408) 2025-10-14 11:58:35 +02:00
charger Hardy-Barth Salia: support firmware 2.3.0+ (#24327) 2025-10-12 18:21:31 +02:00
cmd chore: add missing bracket 2025-10-13 14:21:43 +02:00
core Optimizer: fix first slot of homeProfile (#24381) 2025-10-12 21:12:32 +02:00
hems SMA: remove remote control (BC) (#23906) 2025-10-03 14:51:12 +00:00
i18n Translations update from Hosted Weblate (#24076) 2025-10-12 08:10:59 +02:00
LICENSES chore: align wording with readme 2025-09-10 12:40:19 +02:00
meter Homeassistant meter: fix panic 2025-10-12 16:17:18 +02:00
packaging chore: add metrics 2025-09-15 15:41:32 +02:00
plugin Cardata: fix mqtt receive and logging 2025-10-10 15:40:56 +02:00
push chore: consistently rename vehicle Title api to GetTitle (#21955) 2025-06-21 12:33:41 +02:00
server chore: reduce logging 2025-10-09 13:23:45 +02:00
tariff EntsoE: only consider timeseries at position 1 2025-10-05 22:39:51 +02:00
templates BMW Cardata: add alternative datapoints for Plug-in Hybrids (#24391) 2025-10-13 10:27:34 +00:00
tests Config UI: add ext meter (#24044) 2025-10-10 09:47:45 +02:00
util chore: fix marking monitor waited once 2025-10-14 13:37:32 +02:00
vehicle BMW Cardata: add alternative datapoints for Plug-in Hybrids (#24391) 2025-10-13 10:27:34 +00:00
.cursorrules chore: Add AGENTS.md (#22776) 2025-08-05 11:38:05 +02:00
.dockerignore Docker: fix build, ts config (#23974) 2025-09-30 15:15:03 +02:00
.editorconfig chore: fix npm run lint; spaces > tabs for .ts (#21879) 2025-06-17 17:14:55 +02:00
.gitignore chore: ignore databases 2025-08-02 18:17:53 +02:00
.golangci.yml chore: upgrade go 1.25 (#22904) 2025-08-14 14:21:54 +00:00
.goreleaser-nightly.yml chore: exclude from changelog 2025-06-07 13:37:29 +02:00
.goreleaser.yml chore: match case insensitively 2025-08-27 11:06:24 +02:00
.prettierignore chore: fix npm run lint; spaces > tabs for .ts (#21879) 2025-06-17 17:14:55 +02:00
AGENTS.md UI: make loadpoints sortable and hideable (#23621) 2025-09-29 13:05:29 +02:00
CLAUDE.md chore: Add AGENTS.md (#22776) 2025-08-05 11:38:05 +02:00
CONTRIBUTING.md chore: English in Issues & PRs (#24300) 2025-10-14 06:10:55 +00:00
Dockerfile chore: restore prettier vscode/cursor integration (#24312) 2025-10-10 16:43:10 +00:00
env.d.ts Site: add config UI (BC) (#9812) 2024-01-27 13:38:16 +01:00
eslint.config.mts chore: Typescript: Rewrite Configs (#21763) 2025-09-28 11:10:24 +02:00
evcc.dist.yaml Loadpoint: add asleep messaging event if wakeup fails (#23116) 2025-08-24 14:50:41 +00:00
go.mod Tariffs: switch to 15m slots (#21162) 2025-10-03 16:45:56 +02:00
go.sum Tariffs: switch to 15m slots (#21162) 2025-10-03 16:45:56 +02:00
icon.png Implement basic hardware detection (#435) 2020-11-21 17:13:59 +01:00
jest.config.ts chore: Typescript: Rewrite Configs (#21763) 2025-09-28 11:10:24 +02:00
LICENSE chore: license communication (#23493) 2025-09-10 12:37:34 +02:00
lm.md Load Management and Peak Shaving (#13207) 2024-04-27 10:50:35 +02:00
main.go i18n: Replace toml with json (#20817) 2025-04-29 14:59:38 +02:00
Makefile chore: add license checker (#23494) 2025-09-10 18:29:47 +02:00
package-lock.json chore(deps-dev): bump happy-dom from 19.0.1 to 20.0.0 in the npm_and_yarn group across 1 directory (#24323) 2025-10-14 10:29:54 +02:00
package.json chore(deps-dev): bump happy-dom from 19.0.1 to 20.0.0 in the npm_and_yarn group across 1 directory (#24323) 2025-10-14 10:29:54 +02:00
playwright.config.ts chore: Typescript: Rewrite Configs (#21763) 2025-09-28 11:10:24 +02:00
prettier.config.js chore: restore prettier vscode/cursor integration (#24312) 2025-10-10 16:43:10 +00:00
README.md chore: license communication (#23493) 2025-09-10 12:37:34 +02:00
schema.json chore: allow number capacity (#18470) 2025-01-28 15:59:00 +01:00
tsconfig.json chore: Typescript: Rewrite tests (#21723) 2025-06-15 23:23:22 +02:00
vite.config.ts Fix provider authorization ui error handling (#24250) 2025-10-09 09:39:08 +02:00
vitest.config.ts chore: Typescript: Rewrite Configs (#21763) 2025-09-28 11:10:24 +02:00

evcc 🚘☀️

Build Translation Docker Pulls OSS hosting by cloudsmith Latest Version
Built with Depot

evcc is an extensible EV Charge Controller and home energy management system.

Screenshot

Our goal is to provide local energy management, without relying on cloud services. Featured in PV Magazine and c’t Magazin.

Features

  • simple and clean user interface
  • support for many EV chargers:
    • ABB, ABL, Alfen, Alphatec, Amperfied, Ampure, Audi, AUTEL, Autoaid, Bender, BMW, cFos, Charge Amps, Compleo, CUBOS, Cupra, Dadapower, DaheimLaden, Delta, E.ON Drive, E3/DC, Easee, Ebee, echarge, EcoHarmony, Edgetech, Elecq, eledio, Elli, EM2GO, EN+, enercab, Ensto, EntraTek, ESL, eSystems, Etrel, EVBox, Free2Move, Free2move eSolutions, Fronius, Garo, go-e, Hardy Barth, Heidelberg, Hesotec, Homecharge, Huawei, Innogy, INRO, Juice, Kathrein, KEBA, Kontron Solar, Kostal, KSE, LadeFoxx, LRT, Mennekes, NRGkick, OBO Bettermann, OpenEVSE, openWB, Optec, Orbis, PC Electric, Peblar, Phoenix Contact, Plugchoice, Porsche, Pracht, Pulsares, Pulsatrix, Qcells, Schneider, Schrack, SENEC, Siemens, Skoda, SMA, Smartfox, SolarEdge, Solax, Sonnen, Spelsberg, Stark in Strom, Sungrow, TechniSat, Tesla, Tigo, TinkerForge, Ubitricity, V2C Trydan, Vestel, Victron, Viridian EV, Volkswagen, Volt Time, Wallbe, wallbox, Walther Werke, Webasto, Weidmüller, Zaptec, ZJ Beny. Read more.
    • EEBus support (Elli, PMCC)
    • OCPP support
    • build-your-own: Phoenix Contact (includes ESL Walli), EVSE DIN
    • smart switches: AVM, FRITZ!, Home Assistant, Homematic IP, HomeWizard, myStrom, Shelly, Tasmota, TP-Link. Read more.
    • heat pumps and electric heaters: alpha innotec, Bosch, Buderus, Bösch, CTA All-In-One, Daikin, Elco, IDM, Junkers, Kermi, Lambda, my-PV, Nibe, Novelan, Roth, Stiebel Eltron, Tecalor, Vaillant, Viessmann, Wolf, Zewotherm. Read more.
  • support for many energy meters:
    • solar inverters and battery systems: A-Tronix, Acrel, Ads-tec, Alpha ESS, Ampere, Anker, APsystems, AVM, Axitec, BGEtech, Bosch, Bosswerk, Carlo Gavazzi, Deye, E3/DC, Eastron, Enphase, FENECON, FRITZ!, FoxESS, Fronius, Ginlong, go-e, GoodWe, Growatt, Homematic IP, HomeWizard, Hoymiles, Huawei, IAMMETER, IGEN Tech, Kostal, LG, Loxone, M-TEC, Marstek, myStrom, OpenEMS, Powerfox, Qcells, RCT, SAJ, SAX, SENEC, Senergy, Shelly, Siemens, Sigenergy, SMA, Smartfox, SofarSolar, Solaranzeige, SolarEdge, SolarMax, Solarwatt, Solax, Solinteng, Sonnen, St-ems, Steca, Sungrow, Sunsynk, Sunway, Tasmota, Tesla, TP-Link, VARTA, Victron, Wattsonic, Youless, ZCS Azzurro, Zendure. Read more.
    • general energy meters: A-Tronix, ABB, Acrel, Alpha ESS, Ampere, AVM, Axitec, Bernecker Engineering, BGEtech, Bosch, Carlo Gavazzi, cFos, Deye, DSMR, DZG, E3/DC, Eastron, Enphase, ESPHome, FENECON, FoxESS, FRITZ!, Fronius, Ginlong, go-e, GoodWe, Growatt, Homematic IP, HomeWizard, Huawei, IAMMETER, inepro, IOmeter, Janitza, KEBA, Kostal, LG, Loxone, M-TEC, mhendriks, my-PV, myStrom, OpenEMS, ORNO, P1Monitor, Powerfox, Qcells, RCT, Saia-Burgess Controls (SBC), SAJ, SAX, Schneider Electric, SENEC, Shelly, Siemens, Sigenergy, SMA, Smartfox, SofarSolar, Solaranzeige, SolarEdge, SolarMax, Solarwatt, Solax, Solinteng, Sonnen, St-ems, Sungrow, Sunsynk, Sunway, Tasmota, Tesla, Tibber, TQ, VARTA, Victron, Volkszähler, Wago, Wattsonic, Weidmüller, Youless, ZCS Azzurro, Zuidwijk. Read more.
    • integrated systems: SMA Sunny Home Manager and Energy Meter, KOSTAL Smart Energy Meter (KSEM, EMxx)
    • sunspec-compatible inverter or home battery devices
    • mbmd-compatible devices, see volkszaehler/mbmd for a complete list
  • vehicle integrations (state of charge, remote charge, battery and preconditioning status):
    • Aiways, Audi, BMW, Citroën, Dacia, DS, Fiat, Ford, Hyundai, Jeep, Kia, Mercedes-Benz, MG, Mini, Nissan, NIU, Opel, Peugeot, Polestar, Renault, Seat, Skoda, Smart, Tesla, Toyota, Volkswagen, Volvo, Zero Motorcycles. Read more.
    • services: OVMS, Tronity, evNotify, ioBroker.bmw, mg2mqtt, mz2mqtt, TeslaLogger, TeslaMate, Tessi, volvo2mqtt
  • plugins for integrating with any charger, smartswitch, heatpump, electric heater, meter, solar- / battery-inverter or vehicle:
    • Modbus, HTTP, MQTT, JavaScript, WebSocket, Go and shell scripts
  • status notifications using Telegram, PushOver and many more
  • logging using InfluxDB and Grafana
  • REST and MQTT APIs for integration with home automation systems
  • Add-ons for Home Assistant and openHAB (not maintained by the evcc core team)

Getting Started

You'll find everything you need in our documentation.

Contributing

Technical details on how to contribute, how to add translations and how to build evcc from source can be found here.

Weblate Hosted

Sponsorship

evcc 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 ours that provide additional value to otherwise closed hardware. Where this is not the case, evcc requires "sponsor token" to finance ongoing development and support of evcc.

Learn more about our sponsorship model.

License

This project is licensed under the MIT License. See the LICENSE file for details.

For additional license information regarding fonts, icons, and other assets, please see the LICENSES folder.

Note: All sponsor-required components are excluded from the MIT License. See file license header for details. If you want to use them in your own project, one evcc sponsorship token is required per evcc instance. Custom licensing agreements are available - please contact us to discuss your specific requirements.