EVCC unter Home Assistant - wie die evcc.yaml richtig schreiben?

[lkün]

Hallo,

ich verscuhe gerade meine Warp 2 Box in EVCC unter Home Assistant einzubinden. Das Ad-On ist installiert und es muss eigentlich "nur" die evcc.yaml richtig erstellt werden.

Dabei bekomme ich jedoch immer wieder die Fehlermeldung, dass der charger nicht erstellt werden kann.

Meine Fehlermeldung lautet im Protokoll:

Using config file:  /config/evcc.yaml
starting evcc: 'evcc --config  /config/evcc.yaml'
[main  ] INFO 2022/10/10 17:36:56 evcc 0.104.2
[main  ] INFO 2022/10/10 17:36:56 using config file: /config/evcc.yaml
[main  ] INFO 2022/10/10 17:36:56 listening at :7070
[warp  ] INFO 2022/10/10 17:36:56 connecting evcc-1901320301 at tcp://192.168.x.xxx:1883
[main  ] FATAL 2022/10/10 17:36:56 cannot create charger 'WARP2': cannot create charger 'template': cannot create charger 'warp': error connecting: not Authorized
[main  ] FATAL 2022/10/10 17:36:56 will attempt restart in: 5m0s

 

Die yaml lautet:

 

Network:

  schema: http
  host: 192.168.X.XXX # IP vom Home Assistant 
  # port is the listening port for UI and api
  # evcc will listen on all available interfaces
  port: 7070

interval: 10s # control cycle interval


# log settings
log: info
levels:
  site: debug
  lp-1: debug
  lp-2: debug

# 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: gridmeter
  type: custom
  power:
    source: script
    cmd: /bin/sh -c 'echo -1000'
- name: pvmeter
  type: custom
  power:
    source: script
    cmd: /bin/sh -c 'echo 9000'

# 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: WARP2
    type: template
    template: tinkerforge-warp
    fw2: # Firmware v2 installiert
    host: 192.168.x.xxx # IP Adresse oder der Hostname des MQTT Brokers
    #port: 1883 # MQTT Broker Port # Optional
    topic: warp2/Xb6 # Topic (ohne / am Anfang) # Optional 

# 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: my_car
    type: custom
    title: Mein Auto # display name for UI
    capacity: 50 # byttery capacity (kWh)

# site describes the EVU connection, PV and home battery
site:
  title: Home # display name for UI
  meters:
    grid: gridmeter # grid meter
    #pvs:
    #  - pv # list of pv inverters/ meters
    #battery: battery # battery meter
  #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: WARP2 # charger
    meter: gridmeter # charge meter
    mode: "off" # 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
    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)
    phases: 3 # electrical connection (normal charger: default 3 for 3 phase, 1p3p charger: 0 for "auto" or 1/3 for fixed phases)
    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)
    minCurrent: 6 # minimum charge current (default 6A)
    maxCurrent: 16 # 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
    type: fixed
    price: 0.321 # EUR/kWh

  

Ich verstehe nicht ganz wo der Fehler liegen soll. Unter Network habe ich die IP Adresse vom Home Assistant angegeben. Unter charger haben ich die IP Adresse vom MQTT Broker (ebenfalls Home Assistent) eingetragen. Warum kann sich EVCC nicht mit der Warp2 verbinden? Mit MQTT Explorer kann ich auf die Warp2 zugreifen und konnte sie auch im Homeassistent einbinden.

Hat jemand eine Idee? 

[rtrbt]

Not Authorized als Fehler ist interessant. Hast du bei deinem MQTT-Broker Benutzername und Passwort konfiguriert? Dann musst du das in der EVCC-Konfiguration eintragen.

Frag ansonsten am besten auch mal im EVCC-Forum: https://github.com/evcc-io/evcc/discussions

[PV-Michel]

Am 10.10.2022 um 18:03 schrieb lkün:

Hallo,

ich verscuhe gerade meine Warp 2 Box in EVCC unter Home Assistant einzubinden. Das Ad-On ist installiert und es muss eigentlich "nur" die evcc.yaml richtig erstellt werden.

Dabei bekomme ich jedoch immer wieder die Fehlermeldung, dass der charger nicht erstellt werden kann.

Meine Fehlermeldung lautet im Protokoll:

Using config file:  /config/evcc.yaml
starting evcc: 'evcc --config  /config/evcc.yaml'
[main  ] INFO 2022/10/10 17:36:56 evcc 0.104.2
[main  ] INFO 2022/10/10 17:36:56 using config file: /config/evcc.yaml
[main  ] INFO 2022/10/10 17:36:56 listening at :7070
[warp  ] INFO 2022/10/10 17:36:56 connecting evcc-1901320301 at tcp://192.168.x.xxx:1883
[main  ] FATAL 2022/10/10 17:36:56 cannot create charger 'WARP2': cannot create charger 'template': cannot create charger 'warp': error connecting: not Authorized
[main  ] FATAL 2022/10/10 17:36:56 will attempt restart in: 5m0s

 

Die yaml lautet:

 

Network:

  schema: http
  host: 192.168.X.XXX # IP vom Home Assistant 
  # port is the listening port for UI and api
  # evcc will listen on all available interfaces
  port: 7070

interval: 10s # control cycle interval


# log settings
log: info
levels:
  site: debug
  lp-1: debug
  lp-2: debug

# 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: gridmeter
  type: custom
  power:
    source: script
    cmd: /bin/sh -c 'echo -1000'
- name: pvmeter
  type: custom
  power:
    source: script
    cmd: /bin/sh -c 'echo 9000'

# 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: WARP2
    type: template
    template: tinkerforge-warp
    fw2: # Firmware v2 installiert
    host: 192.168.x.xxx # IP Adresse oder der Hostname des MQTT Brokers
    #port: 1883 # MQTT Broker Port # Optional
    topic: warp2/Xb6 # Topic (ohne / am Anfang) # Optional 

# 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: my_car
    type: custom
    title: Mein Auto # display name for UI
    capacity: 50 # byttery capacity (kWh)

# site describes the EVU connection, PV and home battery
site:
  title: Home # display name for UI
  meters:
    grid: gridmeter # grid meter
    #pvs:
    #  - pv # list of pv inverters/ meters
    #battery: battery # battery meter
  #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: WARP2 # charger
    meter: gridmeter # charge meter
    mode: "off" # 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
    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)
    phases: 3 # electrical connection (normal charger: default 3 for 3 phase, 1p3p charger: 0 for "auto" or 1/3 for fixed phases)
    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)
    minCurrent: 6 # minimum charge current (default 6A)
    maxCurrent: 16 # 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
    type: fixed
    price: 0.321 # EUR/kWh

  

Ich verstehe nicht ganz wo der Fehler liegen soll. Unter Network habe ich die IP Adresse vom Home Assistant angegeben. Unter charger haben ich die IP Adresse vom MQTT Broker (ebenfalls Home Assistent) eingetragen. Warum kann sich EVCC nicht mit der Warp2 verbinden? Mit MQTT Explorer kann ich auf die Warp2 zugreifen und konnte sie auch im Homeassistent einbinden.

Hat jemand eine Idee? 

Bist Du da weitergekommen..? Ich hab grad ein ähnliches Problem...

 

LG

Michael

[Hansiputz]

Hi
Habe eben mit genau dem gleichen Problem gekämpft.
Scheint zu laufen wie folgt:

mqtt:

broker: 192.168.93.203:1883

user: mqtt

password: xxxx

 

chargers:

- type: template

template: tinkerforge-warp

fw2: true

host: 192.168.93.203

port: 1883

topic: warp2/22rE

timeout: 30s

name: warp2

user: mqtt

password: xxxx

Alos Benutzer / Pwd unter der MQTT Broker Definition UND im Charger erintragen

[Hansiputz]

Sorry für die vielen Leerzeilen. Die waren beim Editieren noch nicht da :-(

 

[inuites]

Dear all,

I have installed my warp2-pro with mqtt. Everything is working.

I'm trying to setup EVCC (HA-addon) but I have an error "missing loadpoints" whereas my configuration (mqtt ip and topic are the good one) as I see evcc and my wallbox into mqtt explorer. 

Any idee ? 

Thank you !

 

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

mqtt:
  broker: 192.168.1.10:1883
  topic: evcc

log: info
levels:
  cache: error

interval: 10s # control cycle interval

chargers:
- name: warp2
  type: template
  template: tinkerforge-warp
  fw2: true
  host: 192.168.1.10
  port: 1883
  topic: warp2/pro

loadpoints:
- title: Garage
  charger: warp2
  mode: off
  phases: 3
  mincurrent: 6
  maxcurrent: 16
  resetOnDisconnect: false

meters:
- nom : pv_meter
  type : custom 
  power : 
    source : mqtt
    cmd : homeassistant/meter/prod_instant

- nom : grid_meter
  type : custom 
  power : 
    source : mqtt
    cmd : homeassistant/meter/puissance_globale

site:
  title: Home
  meters:
    grid: grid_meter
    pv: pv_meter

 

[inuites]

vor 2 Stunden schrieb inuites:

Dear all,

I have installed my warp2-pro with mqtt. Everything is working.

I'm trying to setup EVCC (HA-addon) but I have an error "missing loadpoints" whereas my configuration (mqtt ip and topic are the good one) as I see evcc and my wallbox into mqtt explorer. 

Any idee ? 

Thank you !

 

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

mqtt:
  broker: 192.168.1.10:1883
  topic: evcc

log: info
levels:
  cache: error

interval: 10s # control cycle interval

chargers:
- name: warp2
  type: template
  template: tinkerforge-warp
  fw2: true
  host: 192.168.1.10
  port: 1883
  topic: warp2/pro

loadpoints:
- title: Garage
  charger: warp2
  mode: off
  phases: 3
  mincurrent: 6
  maxcurrent: 16
  resetOnDisconnect: false

meters:
- nom : pv_meter
  type : custom 
  power : 
    source : mqtt
    cmd : homeassistant/meter/prod_instant

- nom : grid_meter
  type : custom 
  power : 
    source : mqtt
    cmd : homeassistant/meter/puissance_globale

site:
  title: Home
  meters:
    grid: grid_meter
    pv: pv_meter

 

Resolved. It was a problem in vscode that was not saving correctly the file.. sorry 

bearbeitet February 2, 2023 at 18:37 von inuites

[Eugenius]

Jetzt man eine generelle Frage:
Warum nutzt man MQTT für die WARP Integration? Warum nicht HTTP oder gar ModbusTCP?

[MatzeTF]

HTTP hat viel Overhead, da für jedes Kommando eine neue HTTP-Verbindung aufgebaut werden muss.

Die Wallbox bekommt mit dem nächsten Firmware-Update Unterstützung für Phasenumschaltung per Modbus TCP, IIRC. Ob/Wann das von EVCC unterstützt wird, weiß ich nicht.