What problem it solves

Home energy systems often need to coordinate electric vehicles, chargers, meters, solar generation, batteries, and other household devices. evcc addresses this by providing local energy management without relying on cloud services.

Key features

• Local energy management — Coordinate charging and household energy locally, without depending on cloud services.

  Source: README, core

• Broad device integration — Connect EV chargers, energy meters, solar inverters, battery systems, vehicles, heat pumps, and electric heaters through supported integrations.

  Source: README, charger, meter

• Extensible plugin system — Extend support for devices and services with plugins using Modbus, HTTP, MQTT, JavaScript, WebSocket, Go, or shell scripts.

  Source: README, plugin

• Home automation APIs — Integrate the system with home automation environments through REST and MQTT APIs.

  Source: api

• Multiple charging protocols — Support EEBus and OCPP, including devices assembled through the build-your-own approach.

  Source: README

Who it may suit

This may suit users who want to coordinate EV charging and household energy locally across supported hardware and home automation systems.

Topics to discuss

• Which local device integrations would improve energy management workflows most?

• How can the plugin system make unsupported hardware easier to integrate?

• What should contributors focus on when adding or maintaining device support?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/evcc-io/evcc#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.