Innogy ebox: connection to wallbox after update to 0.126.2 not possible anymore

[ThomasPloski]

Describe the bug

After update from 0.125 to 0.126.2, the connection to the already defined wallbox (eon Professional) refused.

The defined ip address and port to wallbox has not been changed after update to 0.126.2 - furthtermore, I am able to logon to the wallbox backend using the mentioned IP address.

Restarting of the wallbox does not help.

Would you please assist me?

Steps to reproduce

1. Update evcc from 0.125 to 0.126.2
2. restart evcc
3. see entries in logs ...

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: 5s # control cycle interval

# database configuration for persisting charge sessions and settings
# database:
#   type: sqlite
#   dsn: <path-to-db-file>

# sponsor token enables optional features (request at https://sponsor.evcc.io)
sponsortoken: [exists]

# 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

# log settings
log: info
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

# 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: my_grid
    type: template
    template: solaredge-inverter
    usage: grid      

    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.178.25 # Hostname
    port: 1502 # Port 

  - name: my_pv
    type: template
    template: solaredge-inverter
    usage: pv      

    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.178.25 # Hostname
    port: 1502 # Port 

# 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: wallbox
    type: template 
    template: innogy-ebox

     # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.178.100 # Hostname
    port: 502 # Port 

# 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: bmw_ix3
    type: template
    template: bmw
    title: BMW iX3  # Wird in der Benutzeroberfl he angezeigt # Optional
    user: [exists] # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    password: [exists]
    vin: [exists] # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind # Optional
    capacity: 80 # Akkukapazit  in kWh # Optional 
#    phases: 1

#  - name: bmw_ix3_3p
#    type: template
#    template: bmw
#    title: BMW iX3 (3phasig)  # Wird in der Benutzeroberfl he angezeigt # Optional
#    user: thomas@ploski.de # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
#    password: 2kdLG0ioclIb8IjL4owYMuzlGBE0UWOjWDkvAHq+ # Passwort des Benutzerkontos (bei f renden Nullen bitte in einfache Hochkommata setzen)
#    vin: WBY41DU030S500821 # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind # Optional
#    capacity: 80 # Akkukapazit  in kWh # Optional 
#    phases: 3

# site describes the EVU connection, PV and home battery
site:
  title: Zuhause # display name for UI
  meters:
    grid: my_grid # grid meter
    pv:
      - my_pv # list of pv inverters/ meters
  prioritySoc: # give home battery priority up to this soc (empty to disable)
  bufferSoc: # ignore home battery discharge above soc (empty to disable)

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Garage # display name for UI
    charger: wallbox # charger
    vehicle: bmw_ix3         
    mode: "pv" # set default charge mode, use "off" to disable by default if charger is publicly available
    # vehicle: car1 # set default vehicle (disables vehicle detection)
    # resetOnDisconnect: true # set defaults when vehicle disconnects
    # phases: 3 # electrical connection (normal charger: default 3 for 3 phase, 1p3p charger: 0 for "auto" or 1/3 for fixed phases)
    # minCurrent: 6 # minimum charge current (default 6A)
    # maxCurrent: 16 # maximum charge current (default 16A)

    # 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: 5m
      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)
    guardDuration: 5m # switch charger contactor not more often than this (default 5m)

# tariffs are the fixed or variable tariffs
tariffs:
  currency: EUR # (default EUR)
  grid:
    type: fixed
    price: 0.3544 # [currency]/kWh

  feedin:
    type: fixed
    price: 0.09163 # [currency]/kWh

# mqtt message broker
mqtt:
  # broker: localhost:1883
  # topic: evcc # root topic for publishing, set empty to disable
  # user:
  # 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://<user>:<password>@<host>:<port>/?fromAddress=<from>&toAddresses=<to>
  # - type: ntfy
  #   uri: https://<host>/<topics>
  #   priority: <priority>
  #   tags: <tags>

Log details

[main ] INFO 2024/05/06 05:30:39 evcc 0.126.2
[main ] INFO 2024/05/06 05:30:39 using config file: /etc/evcc.yaml
[main ] INFO 2024/05/06 05:30:39 starting ui and api at :7070
[db ] INFO 2024/05/06 05:30:39 using sqlite database: /root/.evcc/evcc.db
[lp-1 ] ERROR 2024/05/06 05:31:44 charge total import: EOF
[site ] INFO 2024/05/06 05:31:45 site config:
[site ] INFO 2024/05/06 05:31:45 meters: grid ✓ pv ✓ battery ✗
[site ] INFO 2024/05/06 05:31:45 grid: power ✓ energy ✗ currents ✗
[site ] INFO 2024/05/06 05:31:45 pv 1: power ✓ energy ✗ currents ✗
[site ] INFO 2024/05/06 05:31:45 vehicles:
[site ] INFO 2024/05/06 05:31:45 vehicle 1: range ✓ finish ✗ status ✓ climate ✗ wakeup ✓
[lp-1 ] INFO 2024/05/06 05:31:45 loadpoint 1:
[lp-1 ] INFO 2024/05/06 05:31:45 mode: pv
[lp-1 ] INFO 2024/05/06 05:31:45 charger: power ✓ energy ✓ currents ✓ phases ✗ wakeup ✗
[lp-1 ] INFO 2024/05/06 05:31:45 meters: charge ✓
[lp-1 ] INFO 2024/05/06 05:31:45 charge: power ✓ energy ✓ currents ✓
[lp-1 ] DEBUG 2024/05/06 05:31:45 phase timer inactive
[lp-1 ] DEBUG 2024/05/06 05:31:45 pv timer inactive
[lp-1 ] INFO 2024/05/06 05:31:45 vehicle updated: unknown -> BMW iX3
[lp-1 ] ERROR 2024/05/06 05:31:45 charger enabled: dial tcp 192.168.178.100:502: connect: connection refused
[site ] WARN 2024/05/06 05:31:45 interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval
[site ] DEBUG 2024/05/06 05:31:45 ----
[lp-1 ] ERROR 2024/05/06 05:31:46 charge power: dial tcp 192.168.178.100:502: connect: connection refused
[lp-1 ] ERROR 2024/05/06 05:31:47 charge currents: dial tcp 192.168.178.100:502: connect: connection refused
[site ] DEBUG 2024/05/06 05:31:47 pv power: 0W
[site ] DEBUG 2024/05/06 05:31:47 grid meter: 721W
[site ] DEBUG 2024/05/06 05:31:47 site power: 721W
[lp-1 ] DEBUG 2024/05/06 05:31:47 vehicle odometer: 40811km
[lp-1 ] ERROR 2024/05/06 05:31:47 charge total import: dial tcp 192.168.178.100:502: connect: connection refused
[lp-1 ] ERROR 2024/05/06 05:31:47 charger status: dial tcp 192.168.178.100:502: connect: connection refused
[site ] DEBUG 2024/05/06 05:31:50 ----
[lp-1 ] DEBUG 2024/05/06 05:31:50 charge power: 0W
[lp-1 ] DEBUG 2024/05/06 05:31:50 charge currents: [0.03 0.03 0.07]A
[site ] DEBUG 2024/05/06 05:31:50 pv power: 0W
[site ] DEBUG 2024/05/06 05:31:50 grid meter: 703W
[site ] DEBUG 2024/05/06 05:31:50 site power: 703W
[lp-1 ] ERROR 2024/05/06 05:32:51 charge total import: EOF

What type of operating system are you running?

Docker container

Version

0.126.2

[StefanSchoof]

Did you try to downgrade to make sure evcc still works with the old version?

[ThomasPloski]

Not yet, but this will be my fallback, in case there is not quick solution for my issue.

[StefanSchoof]

Please try. In many cases where user think a evcc update broke something, something else has changed and only the restart of evcc for the update made it visible.

[ThomasPloski]

With v0.125.0 evcc works fine. Connection to wallbox has been established successfully.

[premultiply]

Running multiple instances at the same time?

[ThomasPloski]

No, just one at the same time.

[andig]

[lp-1 ] ERROR 2024/05/06 05:31:44 charge total import: EOF

Sieht aus wie https://github.com/evcc-io/evcc/issues/13631.

@samuelbrucksch fällt Dir dazu etwas ein? Sonst müssten wir https://github.com/evcc-io/evcc/commit/da4af01d736503b77901648d8a03f45516a99591 zurück rollen. /cc @lukaslo

[SamuelBrucksch]

Habe es bei mir auch nicht zum laufen bekommen. Am besten zurückrollen, ich richte mir dann mal eine manuelle Morbus Verbindung ein zum testen...Am 06.05.2024 13:11 schrieb andig @.***>: [lp-1 ] ERROR 2024/05/06 05:31:44 charge total import: EOF

Sieht aus wie #13631. @SamuelBrucksch fällt Dir dazu etwas ein? Sonst müssten wir da4af01 zurück rollen.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[andig]

Closed in 7d67b502a7600a8231aabb98cc6c144990d62445

[Logocad]

Hallo andig

Ist dieses Problem mit der innogy eBox Professional nun gelöst? Oder kommt die Lösung mit der nächsten Version. Hab das Problem ebenfalls mit der 0.126.2 wenn ich die 0.125.0 installiere ist wieder alles top,

[StefanSchoof]

Der Fix ist bisher nur in dem nightly.

[Logocad]

Danke für die schnelle Antwort. Werde ich dann mal installieren und testen.