network: # schema is the HTTP schema # setting to `https` does not enable https, it only changes the way URLs are generated schema: http # host is the hostname or IP address # if the host name contains a `.local` suffix, the name will be announced on MDNS # docker: MDNS announcements don't work. host must be set to the docker host's name. host: 192.168.0.202 # port is the listening port for UI and api # evcc will listen on all available interfaces port: 7070 interval: 30s # control cycle interval. Interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval # sponsor token enables optional features (request at https://sponsor.evcc.io) sponsortoken: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx telemetry: false # log settings # log: info log: debug levels: site: debug lp-1: debug lp-2: debug cache: error db: error # modbus proxy for allowing external programs to reuse the evcc modbus connection # each entry will start a proxy instance at the given port speaking Modbus TCP and # relaying to the given modbus downstream device (either TCP or RTU, RS485 or TCP) modbusproxy: # - port: 5200 # uri: solar-edge:502 # # rtu: true # # readonly: true # use `deny` to raise modbus errors # meter definitions # name can be freely chosen and is used as reference when assigning meters to site and loadpoints # for documentation see https://docs.evcc.io/docs/devices/meters meters: - name: grid type: template template: e3dc-rscp usage: grid host: 192.168.0.204 port: 5033 user: xxx@yyy.zz password: xxxxxx key: 0000 - name: pv type: template template: e3dc-rscp usage: pv host: 192.168.0.204 port: 5033 user: xxx@yyy.zz password: xxxxxx key: 0000 - name: battery type: template template: e3dc-rscp usage: battery host: 192.168.0.204 port: 5033 user: xxx@yyy.zz password: xxxxxx key: 0000 capacity: 12 # charger definitions # name can be freely chosen and is used as reference when assigning charger to vehicle # for documentation see https://docs.evcc.io/docs/devices/chargers chargers: - name: wb type: template template: tinkerforge-warp3 host: 192.168.0.202 # mqtt host port: 1883 # mqtt port topic: warp3/2bB4 timeout: 30s user: xxx password: '########' # vehicle definitions # name can be freely chosen and is used as reference when assigning vehicle to loadpoint # for documentation see https://docs.evcc.io/docs/devices/vehicles vehicles: - name: Corsa type: template template: opel title: Corsa user: xxx@yyy.zz password: '######' accesstoken: 986e9d10-d705-4d11-bf75-aaaaaaaaaa refreshtoken: 7ccddc6f-77fb-4245-a023-rrrrrrrrrr capacity: 46 # kWh vin: VXKUHZKXZM0000000 phases: 3 mode: PV minCurrent: 6 maxCurrent: 16 # site describes the EVU connection, PV and home battery site: title: Zuhause meters: grid: grid pv: pv battery: battery # aux: residualPower: 200 # additional household usage margin maxGridSupplyWhileBatteryCharging: 0 # ignore battery charging if AC consumption is above this value # loadpoint describes the charger, charge meter and connected vehicle loadpoints: - title: Garage charger: wb mode: "PV" phases: 0 # remaining settings are experts-only and best left at default values priority: 0 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority) soc: # polling defines usage of the vehicle APIs # Modifying the default settings it NOT recommended. It MAY deplete your vehicle's battery # or lead to vehicle manufacturer banning you from API use. USE AT YOUR OWN RISK. poll: # poll mode defines under which condition the vehicle API is called: # charging: update vehicle ONLY when charging (this is the recommended default) # connected: update vehicle when connected (not only charging), interval defines how often # always: always update vehicle regardless of connection state, interval defines how often (only supported for single vehicle) mode: charging # poll interval defines how often the vehicle API may be polled if NOT charging interval: 60m estimate: true # set false to disable interpolating between api updates (not recommended) enable: # pv mode enable behavior delay: 1m # threshold must be exceeded for this long threshold: 0 # grid power threshold (in Watts, negative=export). If zero, export must exceed minimum charge power to enable disable: # pv mode disable behavior delay: 3m # threshold must be exceeded for this long threshold: 0 # maximum import power (W) # tariffs are the fixed or variable tariffs tariffs: currency: EUR grid: type: fixed price: 0.365 # EUR/kWh feedin: # rate for feeding excess (pv) energy to the grid type: fixed price: 0.077 # EUR/kWh co2: # mqtt message broker mqtt: broker: 192.168.0.202:1883 topic: evcc # root topic for publishing, set empty to disable user: uuuuuu password: '######' # influx database influx: # url: http://localhost:8086 # database: evcc # user: # password: # eebus credentials eebus: # uri: # :4712 # interfaces: # limit eebus to specific network interfaces # - en0 # certificate: # local signed certificate, required, can be generated via `evcc eebus-cert` # public: # public key # private: # private key # push messages messaging: events: start: # charge start event title: Charge started msg: Started charging in "${mode}" mode stop: # charge stop event title: Charge finished msg: Finished charging ${chargedEnergy:%.1fk}kWh in ${chargeDuration}. connect: # vehicle connect event title: Car connected msg: "Car connected at ${pvPower:%.1fk}kW PV" disconnect: # vehicle connected event title: Car disconnected msg: Car disconnected after ${connectedDuration} soc: # vehicle soc update event title: Soc updated msg: Battery charged to ${vehicleSoc:%.0f}% guest: # vehicle could not be identified title: Unknown vehicle msg: Unknown vehicle, guest connected? services: # - type: pushover # app: # app id # recipients: # - # list of recipient ids # - type: telegram # token: # bot id # chats: # - # list of chat ids # - type: email # uri: smtp://:@:/?fromAddress=&toAddresses= # - type: ntfy # uri: https:/// # priority: # tags: #