evcc: Blocked Web UI start

Describe the bug

After upgrading from 0.111.1 to 0.112.1 the boot process stopped somewhere before initializing web interface and checking which cars are connected toward the charger. In 0.112.2 the problem persisted. Removing

planner:
    # planner tariff can be used for target charging if not grid tariff is specified
    # GrünStromIndex (Germany only) or ElectricityMaps provide CO2 intensity forecast

    type: grünstromindex
    zip: 28779

from my config.yaml solved the issue and evcc is operating back normal.

Steps to reproduce

1. Install evcc newer than 0.111.1
2. Configure tariffs.planner using gruenstromindex
3. Start evcc …

Configuration details

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: evcc.local
  # port is the listening port for UI and api
  # evcc will listen on all available interfaces
  port: 7070

interval: 10s # control cycle interval

# sponsor token: *****
sponsortoken: *****

# telemetry enables aggregated statistics
#
# Telemetry allows collecting usage data (grid and green energy, charge power).
# Data is aggregated, no individual charging sessions are tracked. The collected,
# anonymous data can be retrieved using https://api.evcc.io.
#
# See https://github.com/evcc-io/evcc/pull/4343 or details.
#
# For time being, this is only available to sponsors, hence data is associated with
# the sponsor token's identity.
#
telemetry: true

plant: *****

# log settings
log: debug
levels:
  site: debug
  core: debug
  lp-1: debug
  lp-2: debug
  cache: error
  db: error
  vw: debug
  id: debug
  tesla: debug

# 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

# meter definitions
# name can be freely chosen and is used as reference when assigning meters to site and loadpoints
# for examples see https://github.com/andig/evcc-config#meters
meters:
  - name: e3dc-pv
    type: template
    template: e3dc
    usage: pv
    host: 192.168.4.77
    port: 502
  - name: e3dc-grid
    type: template
    template: e3dc
    usage: grid
    host: 192.168.4.77
    port: 502
  - name: e3dc-battery
    type: template
    template: e3dc
    usage: battery
    host: 192.168.4.77
    port: 502

# charger definitions
# name can be freely chosen and is used as reference when assigning charger to vehicle
# for examples see https://github.com/andig/evcc-config#chargers
chargers:
  - name: wallbe
    type: template
    template: wallbe-meter
    host: 192.168.4.98 # IP-Adresse oder Hostname
    port: 502 # Port # Optional

# vehicle definitions
# name can be freely chosen and is used as reference when assigning vehicle to loadpoint
# for examples see https://github.com/andig/evcc-config#vehicles
vehicles:
  - name: e_up
    type: template
    template: vw
    title: VW e-Up
    user: *****
    password: *****
    vin: *****
    capacity: 32.3 # kWh
    mode: pv
    minSoC: 33
    targetSoC: 80

  - name: modely
    type: template
    template: tesla
    title: Tesla Model Y
    accessToken: *****
    refreshToken: *****
    #    vin: *****
    capacity: 75 # Akku-Kapazität in kWh # Optional
    mode: pv
    minSoC: 30
    targetSoC: 80

# site describes the EVU connection, PV and home battery
site:
  title: Home # display name for UI
  meters:
    grid: e3dc-grid # grid meter
    pvs:
      - e3dc-pv # list of pv inverters/ meters
    battery: e3dc-battery # battery meter
  prioritySoC: 80 # give home battery priority up to this soc (empty to disable) Winter 80, Sommer 66
  bufferSoC: 90 # ignore home battery discharge above soc (empty to disable) Winter 90, Sommer 80

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Ladepunkt # ui display name
    charger: wallbe # charger
    mode: off # set default charge mode, use "off" to disable by default if charger is publicly available
    resetOnDisconnect: true # set defaults when vehicle disconnects
    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
        mode: charging
        # poll interval defines how often the vehicle API may be polled if NOT charging
        interval: 30m
    phases: 1 # ev phases (default 3)
    enable: # pv mode enable behavior
      delay: 1m # threshold must be exceeded for this long
      threshold: -1380 # minimum export power (W). If zero, export must exceed minimum chage power to enable
    disable: # pv mode disable behavior
      delay: 3m # threshold must be exceeded for this long
      threshold: 880 # maximum import power (W)
    guardduration: 5m # switch charger contactor not more often than this (default 10m)
    mincurrent: 6 # minimum charge current (default 6A)
    maxcurrent: 20 # maximum charge current (default 16A)

# tariffs are the fixed or variable tariffs
# cheap (tibber/awattar) can be used to define a tariff rate considered cheap enough for charging
tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)
  grid:
    # either static grid price (or price zones)
    type: fixed
    price: 0.40 # EUR/kWh
    #zones:
    #  - days: Mo-Fr
    #    hours: 2-5
    #    price: 0.2 # EUR/kWh
    #  - days: Sa,So
    #    price: 0.15 # EUR/kWh

    # # or variable via tibber
    # type: tibber
    # cheap: 0.2 # EUR/kWh
    # token: *****
    # homeid: "cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c" # optional if multiple homes associated to account

    # # or variable via awattar
    # type: awattar
    # cheap: 0.2 # EUR/kWh
    # region: de # optional, choose at for Austria
  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.0987 # EUR/kWh
#  planner:
    # planner tariff can be used for target charging if not grid tariff is specified
    # GrünStromIndex (Germany only) or ElectricityMaps provide CO2 intensity forecast

#    type: grünstromindex
#    zip: 28779

    # type: electricitymaps
    # uri: <uri>
    # token: *****
    # zone: DE

# mqtt message broker
mqtt:
  broker: 192.168.4.5:1883
  topic: evcc # root topic for publishing, set empty to disable
  user: *****
  password: *****

# influx database (v1)
influx:
  url: http://familiereimann.com:8086
  database: evcc
  org: goebelmeier
  token: *****
  user: *****

# 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 of {{.vehicleTitle}} started from {{.vehicleSoc}}% to {{.targetSoc}}% SoC"
      msg: |
        Started charging ${vehicleTitle} from ${vehicleSoc:%.0f}% to ${targetSoc}% SoC
        --------------------------
        evcc Status {{printf `(%d-%02d-%02d %02d:%02d:%02d)` now.Year now.Month now.Day now.Hour now.Minute now.Second}}
        Netz-Leistung: {{round (divf .gridPower 1000) 3 }} kW
        Solar-Leistung: {{round (divf .pvPower 1000) 3 }} kW
        Eigenverbrauch: {{round (divf .homePower 1000) 3 }} kW
        {{if .batteryConfigured}}Batteriespeicher-Status: {{round (divf .batteryPower 1000) 3 }} kW ({{.batterySoc }} %){{end}}
    stop: # charge stop event
      title: "Charge of {{.vehicleTitle}} with {{.vehicleSoc}}% SoC ({{.vehicleRange}}km Range)"
      msg: |
        Finished charging ${vehicleTitle} with ${chargedEnergy:%.1fk}kWh in ${chargeDuration}. ${vehicleSoc:%.0f}% SoC (${vehicleRange}km Range)
        --------------------------
        evcc Status {{printf `(%d-%02d-%02d %02d:%02d:%02d)` now.Year now.Month now.Day now.Hour now.Minute now.Second}}
        Netz-Leistung: {{round (divf .gridPower 1000) 3 }} kW
        Solar-Leistung: {{round (divf .pvPower 1000) 3 }} kW
        Eigenverbrauch: {{round (divf .homePower 1000) 3 }} kW
        {{if .batteryConfigured}}Batteriespeicher-Status: {{round (divf .batteryPower 1000) 3 }} kW ({{.batterySoc }} %){{end}}
    connect: # vehicle connect event
      title: "A vehicle has been connected"
      msg: "A vehicle has been connected"
    disconnect: # vehicle connected event
      title: "A vehicle was disconnected with {{.vehicleSoc}}% SoC ({{.vehicleRange}}km Range)"
      msg: |
        A vehicle was disconnected after ${connectedDuration}.
        --------------------------
        evcc Status {{printf `(%d-%02d-%02d %02d:%02d:%02d)` now.Year now.Month now.Day now.Hour now.Minute now.Second}}
        Netz-Leistung: {{round (divf .gridPower 1000) 3 }} kW
        Solar-Leistung: {{round (divf .pvPower 1000) 3 }} kW
        Eigenverbrauch: {{round (divf .homePower 1000) 3 }} kW
        {{if .batteryConfigured}}Batteriespeicher-Status: {{round (divf .batteryPower 1000) 3 }} kW ({{.batterySoc }} %){{end}}
    soc: # vehicle soc update event
      title: ${vehicleTitle} is currently charged to ${vehicleSoc:%.0f}% SoC (${vehicleRange}km Range)
      msg: ${vehicleTitle} is currently charged to ${vehicleSoc:%.0f}% SoC (${vehicleRange}km Range)
  services:
    - type: pushover
      app: ****
      recipients:
        - ****
    - type: telegram
      token: *****
      chats:
        - ****

Log details

Using config file: /config/evcc.yaml
starting evcc: 'evcc --config /config/evcc.yaml --sqlite /data/evcc.db'
[main  ] INFO 2023/02/04 09:56:29 evcc 0.112.2
[main  ] INFO 2023/02/04 09:56:29 using config file: /config/evcc.yaml
[main  ] INFO 2023/02/04 09:56:29 starting ui and api at :7070
[mqtt  ] INFO 2023/02/04 09:56:29 connecting evcc-959502595 at tcp://192.168.4.5:1883
[mqtt  ] DEBUG 2023/02/04 09:56:30 tcp://192.168.4.5:1883 connected
[lp-1  ] WARN 2023/02/04 09:56:32 poll interval '30m0s' is lower than 1h0m0s and may deplete your battery or lead to API misuse. USE AT YOUR OWN RISK.
[site  ] INFO 2023/02/04 09:56:32 site config:
[site  ] INFO 2023/02/04 09:56:32   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2023/02/04 09:56:32     grid:      power ✓ energy ✗ currents ✗
[site  ] INFO 2023/02/04 09:56:32     pv 1:      power ✓ energy ✗ currents ✗
[site  ] INFO 2023/02/04 09:56:32     battery 1: power ✓ energy ✗ currents ✗ soc ✓ capacity ✗
[site  ] INFO 2023/02/04 09:56:32   vehicles:
[site  ] INFO 2023/02/04 09:56:32     vehicle 1: range ✓ finish ✓ status ✓ climate ✓ wakeup ✗
[site  ] INFO 2023/02/04 09:56:32     vehicle 2: range ✓ finish ✓ status ✓ climate ✗ wakeup ✗
[lp-1  ] INFO 2023/02/04 09:56:32 loadpoint 1:
[lp-1  ] INFO 2023/02/04 09:56:32   mode:        off
[lp-1  ] INFO 2023/02/04 09:56:32   charger:     power ✓ energy ✓ currents ✓ phases ✗ wakeup ✗
[lp-1  ] INFO 2023/02/04 09:56:32   meters:      charge ✓
[lp-1  ] INFO 2023/02/04 09:56:32     charge:    power ✓ energy ✓ currents ✓
[lp-1  ] DEBUG 2023/02/04 09:56:32 phase timer inactive
[lp-1  ] DEBUG 2023/02/04 09:56:32 pv timer inactive

What type of operating system are you running?

Linux

Version

0.112.2