evcc and Home Assistant

Driving an Edge charge controller from evcc with the official smartevse template, and what that gives you in Home Assistant, Homey and Google Home. Wiring, template parameters, phase switching.

evcc

The Edge charge controller is an official evcc device, template smartevse, listed as “Edgetech Smart EVSE”. EdgeTech sponsored evcc and maintains the template.

Minimal configuration, one charge controller on a USB RS485 adapter:

chargers:
  - name: garage
    type: template
    template: smartevse
    modbus: rs485serial
    device: /dev/ttyUSB0
    baudrate: 9600
    comset: 8N1
    id: 2           # first move the charger from factory address 1 to 2 (register 0x0200)

Over a TCP gateway (works in principle, but the response is slower than on a wired RS485 bus; never put an EdgeTech site controller behind a gateway):

    modbus: rs485tcpip
    host: 192.168.1.50
    port: 502
    id: 2

The template reads state and error from 0x0103, currents from 0x0105–0x0107, session energy from 0x0108, and writes RemoteMaxCurrent 0x0201. evcc’s own load management then does what the Edge site controller would do, using the meter evcc knows about.

Phase switching

The template supports 1P/3P switching per session with the mandatory 10 s pause. evcc pull request 22348 (October 2025, by EdgeTech) added that behaviour. Enable it with phases1p3p: true on a charger wired for 3-phase.

Home Assistant, Homey, Google Home

evcc exposes everything to Home Assistant over MQTT or its REST API; the Home Assistant evcc integration gives sensors and controls per loadpoint. Homey and Google Home work through Home Assistant.

For a direct Matter integration without evcc, see the standards page: the Matter Energy EVSE module works with Home Assistant’s Matter server today.

Do not mix controllers

A charge controller must have exactly one Modbus master. Either the Edge site controller drives it, or evcc does. Running both on one bus gives the board two masters writing 0x0201 and the bus errors that come with it.