evcc-io/hassio-addon

cannot create charger 'keba': listen udp :7090: bind: address already in use)

fuchsbau123 opened this issue · 5 comments

Hi,
I installed the version 0.114.0 of the evcc adon on Home Assistant 2022.11.5.

When I use evcc as addon in Home Assistant I get the following error:

Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2023/03/05 23:51:06 evcc 0.114.0
[main ] INFO 2023/03/05 23:51:06 using config file: /config/evcc.yaml
[main ] INFO 2023/03/05 23:51:06 starting ui and api at :7070
[db ] INFO 2023/03/05 23:51:06 using sqlite database: /data/evcc.db
[mqtt ] INFO 2023/03/05 23:51:06 connecting evcc-289635650 at tcp://172.16.1.63:1883
[main ] FATAL 2023/03/05 23:51:06 could not open port- check that evcc is not already running (cannot create charger 'wallbox5': cannot create charger 'template': cannot create charger 'keba': listen udp :7090: bind: address already in use)
[main ] FATAL 2023/03/05 23:51:06 will attempt restart in: 5m0s

I used the evcc.yaml below. This file seems working, if I use the it on a standalone evcc on Ubuntu.

network:
schema: http
host: XXXXXX # .local suffix announces the hostname on MDNS
port: 7070

log: info
levels:
cache: error

plant: XXXXX

interval: 10s # control cycle interval

meters:

  • name: pv2
    type: custom
    power: # Leistung (W)
    source: mqtt
    topic: XXXX
  • name: grid1
    type: custom
    power: # Leistung (W)
    source: mqtt
    topic: XXXX
  • name: battery3
    type: custom
    soc: # in %
    source: mqtt
    topic: XXXX
    power: # Leistung (W)
    source: mqtt
    topic: XXXX

chargers:

  • type: template
    template: keba
    host: XXX.XXX.XXX.XXX
    name: wallbox5

vehicles:

  • type: template
    template: audi
    title: XXXX
    user: XXX@XXX.XX
    password: XXXXXXXXXX
    capacity: 14
    phases: 3
    icon: car
    cache: 15m
    mode: now
    minSoc: 0
    targetSoc: 100
    minCurrent: 6
    maxCurrent: 32
    name: ev4

loadpoints:

  • title: Wallbox
    charger: wallbox5
    vehicle: ev4
    mode: off
    phases: 3
    mincurrent: 6
    maxcurrent: 32
    resetOnDisconnect: true

site:
title: My home
meters:
grid: grid1
pv:
- pv2
battery:
- battery3

tariffs:
currency: EUR # (default EUR)
grid:
type: fixed
price: 0.XXXX # [currency]/kWh

feedin:
type: fixed
price: 0.XXXX # [currency]/kWh

mqtt:
broker: XXX.XXX.XXX.XXX:1883
user: XXXX
password: XXXXXXX

Are you already running the Home Assistant Keba Integration? This integration already binds the port 7090/udp which causes evcc to fail binding the port too.

We should add a hint to the ha-addon docu, that not both application could run in parallel.

Thanks, I am aware of this. How do I stop this connection? Does deactivating the binding in HA already givs evcc the chance to connect? I was able to establish a connection (removed the bidning and restartett HA and the wallbox) from evcc within HA and the Keba wallbox. In the webinterfarce of the Keba wallbox I could see that it was charging with minimum speed although in the evcc setting maximum was defined (so somehow evcc must had a connection to the wallbox and something with the settings was not correct). Before playing with evcc the wallbox always did load with 11 kW/h. I will start a new charging process later the day again and post the code and the screens. Unfortunately in the evcc webinterface there was nearly nothing displayed last time - although I did set up the car and the wallbox...

How do I stop this connection?

Commenting out the keba section and restarting HA should do the trick

# keba:
#   host: KEBA_HOST

From my point of view, your config should force the wallbox to instantly start at maximum power as soon as you plug in the plug into your car. But this question belongs to the main project and is not a question about this addon.

Start the charging process and create a new discussion in the main project - https://github.com/evcc-io/evcc/discussions/new/choose

thecem commented

not addon related, open it in : https://github.com/evcc-io/evcc or discuss it in https://github.com/evcc-io/evcc/discussions