no supporter feture fork of evcc.io
ee398fe6ad
Return max value from two sources of production information. This allows using metering provided by either CTs or inverters, while before this commit only CT values were used. |
||
|---|---|---|
| .github | ||
| api | ||
| assets | ||
| charger | ||
| cmd | ||
| core | ||
| docs | ||
| hems | ||
| i18n | ||
| meter | ||
| packaging | ||
| provider | ||
| push | ||
| server | ||
| tariff | ||
| templates | ||
| tests | ||
| util | ||
| vehicle | ||
| .dockerignore | ||
| .editorconfig | ||
| .eslintrc.cjs | ||
| .gitignore | ||
| .golangci.yml | ||
| .goreleaser-nightly.yml | ||
| .goreleaser.yml | ||
| .prettierrc.js | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| env.d.ts | ||
| evcc.dist.yaml | ||
| go.mod | ||
| go.sum | ||
| histoire.config.js | ||
| icon.png | ||
| jest.config.js | ||
| LICENSE | ||
| lm.md | ||
| main.go | ||
| Makefile | ||
| package-lock.json | ||
| package.json | ||
| playwright.config.js | ||
| README.md | ||
| schema.json | ||
| tools.go | ||
| tsconfig.json | ||
| vite.config.js | ||
| vitest.config.js | ||
evcc 🚘☀️
evcc is an extensible EV Charge Controller and home energy management system. Featured in PV magazine.
Features
- simple and clean user interface
- wide range of supported chargers:
- ABL eMH1, Alfen (Eve), Bender (CC612/613), cFos (PowerBrain), Daheimladen, Ebee (Wallbox), Ensto (Chago Wallbox), EVSEWifi/ smartWB, Garo (GLB, GLB+, LS4), go-eCharger, HardyBarth (eCB1, cPH1, cPH2), Heidelberg (Energy Control), Innogy (eBox), Juice (Charger Me), KEBA/BMW, Mennekes (Amedio, Amtron Premium/Xtra, Amtron ChargeConrol), older NRGkicks (before 2022/2023), NRGKick Gen2,openWB (includes Pro), Optec (Mobility One), PC Electric (includes Garo), Siemens, TechniSat (Technivolt), Tinkerforge Warp Charger, Ubitricity (Heinz), Vestel, Wallbe, Webasto (Live), Mobile Charger Connect and many more
- EEBus support (Elli, PMCC)
- experimental OCPP support
- Build-your-own: Phoenix Contact (includes ESL Walli), EVSE DIN
- Smart-Home outlets: FritzDECT, Shelly, Tasmota, TP-Link
- wide range of supported meters for grid, pv, battery and charger:
- ModBus: Eastron SDM, MPM3PM, ORNO WE, SBC ALE3 and many more, see https://github.com/volkszaehler/mbmd#supported-devices for a complete list
- Integrated systems: SMA Sunny Home Manager and Energy Meter, KOSTAL Smart Energy Meter (KSEM, EMxx)
- Sunspec-compatible inverter or home battery devices: Fronius, SMA, SolarEdge, KOSTAL, STECA, E3DC, ...
- and various others: Discovergy, Tesla PowerWall, LG ESS HOME, OpenEMS (FENECON)
- vehicle integration (state of charge, remote charge, battery and preconditioning status):
- Audi, BMW, Citroën, Dacia, Fiat, Ford, Hyundai, Jaguar, Kia, Landrover, Mercedes-Benz, Mini, Nissan, Opel, Peugeot, Porsche, Renault, Seat, Smart, Skoda, Tesla, Volkswagen, Volvo, ...
- Services: OVMS, Tronity
- Scooters: Niu,
Silence
- plugins for integrating with any charger/ meter/ vehicle:
- Modbus, 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 as OLC)
- 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.
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.
The personal sponsor token requires a Github Sponsorship and can be requested at sponsor.evcc.io.