no supporter feture fork of evcc.io
Find a file
2023-05-23 09:34:04 +02:00
.github chore: don't mark bugs as stale 2023-05-20 09:39:46 +02:00
api chore: handle invalid and error charger states (#8073) 2023-05-19 10:55:42 +02:00
assets Check new version only for releases (#8107) 2023-05-20 17:14:59 +02:00
charger chore: add license 2023-05-23 09:34:04 +02:00
cmd chore: remove hidden parameters (#8112) 2023-05-21 11:29:44 +02:00
core Reduce amount of sync messages (#8126) 2023-05-22 08:50:15 +02:00
detect chore: replace unmaintained go-ping 2023-01-22 12:24:48 +01:00
docker/bin Update entrypoint.sh (#6306) 2023-02-18 21:30:26 +01:00
docs chore: add some docs 2022-11-05 17:35:25 +01:00
hems Add smartCostLimit to site (#6732) 2023-03-19 17:45:34 +01:00
i18n Translations update from Hosted Weblate (#7873) 2023-05-21 13:40:29 +02:00
meter Hardybarth Salia: ignore hearbeat errors up to one minute (#8074) 2023-05-19 16:30:46 +02:00
mock Add ui for price/co2 limit (#6935) 2023-04-05 13:14:56 +02:00
packaging Service: correctly extract home dir (#6487) 2023-02-27 12:55:31 +01:00
patch Add support for Elli chargers (#4207) 2022-09-30 10:52:17 +02:00
provider Plugins: make javascript return values more permissive (#8106) 2023-05-20 17:17:20 +02:00
push Simplify template handling and trim trailing spaces (#7144) 2023-04-01 10:32:49 +02:00
server chore: add missing cors options 2023-05-21 15:49:39 +02:00
tariff Tariffs: configure charges and taxes (#8088) 2023-05-21 10:06:12 +02:00
templates Add Deye hybrid inverters (#7961) 2023-05-22 09:23:59 +02:00
util chore: remove hidden parameters (#8112) 2023-05-21 11:29:44 +02:00
vehicle Add MG mqtt gateway template (#8069) 2023-05-20 23:16:38 +02:00
.dockerignore chore: ignore zipped images 2022-10-17 20:11:28 +02:00
.editorconfig Revert undesired markdown changes 2021-02-24 11:53:00 +01:00
.eslintrc.js Replace storybook with histoire (#5154) 2022-11-14 17:24:32 +01:00
.gitignore Remove dist folder from repo (#5862) 2023-01-21 12:42:36 +01:00
.golangci.yml chore: upgrade to Go 1.20 (#5993) 2023-02-12 13:18:53 +01:00
.goreleaser-nightly.yml chore: revert armv6 package name change 2023-04-09 11:30:15 +02:00
.goreleaser.yml chore: revert armv6 package name change 2023-04-09 11:30:15 +02:00
.prettierrc.js Refactor UI into single file components (#491) 2020-12-02 08:29:54 +01:00
Dockerfile chore: re-add patch 2023-05-09 16:47:33 +02:00
evcc.dist.yaml chore: improve description 2023-05-21 10:12:45 +02:00
go.mod Plugins: make javascript return values more permissive (#8106) 2023-05-20 17:17:20 +02:00
go.sum Hardybarth Salia: ignore hearbeat errors up to one minute (#8074) 2023-05-19 16:30:46 +02:00
histoire.config.js Add option to show current price and co2 info (#6048) 2023-02-06 21:57:00 +01:00
icon.png Implement basic hardware detection (#435) 2020-11-21 17:13:59 +01:00
jest.config.js Visualisation of Site Energy Flow (#1148) 2021-08-04 14:53:51 +02:00
LICENSE Update license 2021-01-25 17:27:08 +01:00
main.go chore: upgrade to Go 1.20 (#5993) 2023-02-12 13:18:53 +01:00
Makefile Ocpp: reduce timeouts during testing (#7342) 2023-04-10 17:05:20 +02:00
package-lock.json Restore ios 12 support, using vite-legacy (#7413) 2023-04-13 21:03:58 +02:00
package.json Restore ios 12 support, using vite-legacy (#7413) 2023-04-13 21:03:58 +02:00
README.md Add Siemens Versicharge Gen3 (#6613) 2023-03-10 10:42:59 +01:00
schema.json Add battery settings UI (#7802) 2023-05-08 18:11:31 +02:00
tools.go chore: upgrade unmaintained alvaroles/enumer (#4092) 2022-08-10 17:30:36 +02:00
vite.config.js Restore ios 12 support, using vite-legacy (#7413) 2023-04-13 21:03:58 +02:00
vitest.config.js Add Target Charge Plan Visualisation (#5860) 2023-01-29 21:53:37 +01:00

evcc 🚘☀️

Build Status Code Quality Translation Open in Visual Studio Code OSS hosting by cloudsmith Latest Version

evcc is an extensible EV Charge Controller with PV integration implemented in Go. Featured in PV magazine.

Screenshot

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, Menneckes (Amedio, Amtron Premium/Xtra, Amtron ChargeConrol), NRGkick, 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
    • experimental 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, 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 HomeAssistant and OpenHAB (not maintained by the evcc core team)

Getting Started

You'll find everything you need in our documentation (German).

Contribute

To build evcc from source, Go 1.20 and Node 18 are required.

Build and run go backend. The UI becomes available at http://127.0.0.1:7070/

make ui
make install
make
./evcc

For frontend development start the Vue toolchain in dev-mode. Open http://127.0.0.1:7071/ to get to the livelreloading development server. It pulls its data from port 7070 (see above).

npm install
npm run start

Code formatting

We use linters (golangci-lint, Prettier) to keep a coherent source code formatting. It's recommended to use the format-on-save feature of your editor. For VSCode use the Go, Prettier and Veture extension. You can manually reformat your code by running:

make lint
make lint-ui

Changing templates

evcc supports a massive amount of different devices. To keep our documentation and website in sync with the latest software the core project (this repo) generates meta-data that's pushed to the docs and evcc.io repository. Make sure to update this meta-data every time you make changes to a templates.

make docs

If you miss one of the above steps Gitub Actions will likely trigger a Porcelain error.

Adding or modifying translations

evcc already includes many translations for the UI. Weblate Hosted is used to maintain all languages. Feel free to add more languages or verify and edit existing translations. Weblate will automatically push all modifications on a regular base to the evcc repository.

Weblate Hosted Languages

https://hosted.weblate.org/projects/evcc/evcc/

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.