config.ini.example

# dbus-evcc-multi - auto-discovery EVCC bridge for Victron Venus OS.
#
# Polls EVCC's /api/state and exposes ALL loadpoints automatically, each as its
# own com.victronenergy.evcharger service. No per-loadpoint setup needed.

[DEFAULT]
# Poll interval in seconds (match it to EVCC's interval).
PollSeconds = 15

# Where the chargers sit electrically, as reported in /Position:
#   0 = AC-Out (behind the inverter/charger, "essential loads")  [default]
#   1 = AC-In  (grid side, "AC loads")
# The Venus GUI uses this only to decide which loads widget the charger shows
# up in; dbus-systemcalc-py ignores /Position for evcharger services, so the
# system consumption figures do not change either way.
AcPosition = 0

# Range of DeviceInstances to hand out dynamically (40-59 recommended).
# The stable title -> DeviceInstance mapping is kept in state.json.
DeviceInstanceRangeStart = 40
DeviceInstanceRangeEnd = 59

[ONPREMISE]
# IP/hostname + port of the EVCC instance on the other host.
# Example: Host = 192.168.1.50:7070
# While empty/wrong the service still runs; the bridge waits and logs a
# "EVCC unreachable" WARNING once per poll (it does not crash).
Host =

[VRM_TUNNEL]
# Make the EVCC web UI reachable via the VRM "Control panel" button (no VPN).
# Default OFF -> the bridge behaves exactly as without the tunnel
# ("EVCC REST API"). When Enabled = true, every loadpoint is advertised with
# /Mgmt/Connection = "Modbus TCP <AdvertiseIp>", and the separate dbus-vrm-tunnel
# service must run as well.
Enabled = false

# Non-loopback IP that VRM tunnels to on :80. NOT a 127.x address.
#   On the GX device: the GX device's own LAN IP (e.g. 192.168.1.10)
#   Remote:           the LAN IP of the EVCC host (e.g. 192.168.1.50)
AdvertiseIp =

# Where the rewrite proxy forwards (the real EVCC UI).
#   On the GX device: 127.0.0.1:7070
#   Remote:           <evcc-host>:7070
EvccTarget = 127.0.0.1:7070

# Local port of the rewrite proxy (DNAT target of <AdvertiseIp>:80).
ProxyPort = 8099