evcc-io / evcc

Sonne tanken ☀️🚘
https://evcc.io
MIT License
2.85k stars 543 forks source link

Tinkerforge WARP3 Loadpoint Panic Error #13608

Closed Logirius closed 2 months ago

Logirius commented 2 months ago

Describe the bug

The Tinkerforge Warp3 Charger is successfully connected to the MQTT Broker. After it is configured in evcc.yaml as charger and with the Tinkerforge-warp Template all is still ok. But after there is configured a loadpoint „Carport“ with reference to the configured charger a fatal error appears after starting the addon and the homeassistant addon is restarting in a loop.

Steps to reproduce

  1. Configure the charger in evcc.yaml
  2. configure the loadpoint with these charger in evcc.yaml
  3. start the homeassistant addon ...

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

interval: 10s # control cycle interval. Interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/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:

# 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: debug
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 # use `deny` to raise modbus errors

# 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: custom
    power:
      source: modbus
      id: 1
      uri: 192.168.XXX.XXX:502
      register:
        address: 0x0488 # Total PCC active power. Selling electricity is positive, buying electricity is negative
        type: holding
        decode: int16
      scale: -10
    energy:
      source: modbus
      id: 1
      uri: 192.168.XXX.XXX:502
      register:
        address: 0x068E # Energy_Purchase_Total
        type: holding
        decode: uint32
      scale: 0.1
    currents:
      - source: modbus
        id: 1
        uri: 192.168.XXX.XXX:502
        register:
          address: 0x0492 # R phase PCC current
          type: holding
          decode: uint16
        scale: 0.01
      - source: modbus
        id: 1
        uri: 192.168.XXX.XXX:502
        register:
          address: 0x049D # S phase PCC current
          type: holding
          decode: uint16
        scale: 0.01
      - source: modbus
        id: 1
        uri: 192.168.XXX.XXX:502
        register:
          address: 0x04A8 # T phase PCC current
          type: holding
          decode: uint16
        scale: 0.01
    powers:
      - source: modbus
        id: 1
        uri: 192.168.XXX.XXX:502
        register:
          address: 0x0493 # ActivePower_PCC_R
          type: holding
          decode: int16
        scale: -10
      - source: modbus
        id: 1
        uri: 192.168.XXX.XXX:502
        register:
          address: 0x049E # ActivePower_PCC_S
          type: holding
          decode: int16
        scale: -10
      - source: modbus
        id: 1
        uri: 192.168.XXX.XXX:502
        register:
          address: 0x04A9 # ActivePower_PCC_T
          type: holding
          decode: int16
        scale: -10

  - name: my_pv
    type: custom
    power:
      source: modbus
      id: 1
      uri: 192.168.XXX.XXX:502
      register:
        address: 0x05C4 # Total PV power
        type: holding
        decode: uint16
      scale: 100
    energy:
      source: modbus
      id: 1
      uri: 192.168.XXX.XXX:502
      register:
        address: 0x0686 # PV_Generation_Total
        type: holding
        decode: uint32
      scale: 0.1

  - name: my_battery
    type: custom
    power:
      source: modbus
      id: 1
      uri: 192.168.XXX.XXX:502
      register:
        address: 0x0606 # The charging and discharging power of the first battery pack. Charge is positive, discharge is negative
        type: holding
        decode: int16
      scale: -10
    energy:
      source: modbus
      id: 1
      uri: 192.168.XXX.XXX:502
      register:
        address: 0x069A # Bat_Discharge_Total
        type: holding
        decode: uint32
      scale: 0.1
    soc:
      source: modbus
      id: 1
      uri: 192.168.XXX.XXX:502
      register:
        address: 0x0608 # No. 1 battery pack SOC
        type: holding
        decode: uint16
    capacity: 36

#****************
#meters:
#  - name: my_grid
#    type: template
#    template: sofarsolar-g3
#    usage: grid

    # RS485 via adapter (Modbus RTU)
    #modbus: rs485serial
    #id: 1
    #device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
    #baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
    #comset: "8N1" # Kommunikationsparameter für den Adapter

    # RS485 via TCP/IP (Modbus RTU)
    #modbus: rs485tcpip
    #id: 1
    #host: 192.0.2.2 # Hostname
    #port: 8899 # Port

    # Modbus TCP
#    modbus: tcpip
#    id: 1
#    host: 192.168.XXX.XXX # Hostname
#    port: 8899 # Port 

#  - name: my_pv
#    type: template
#    template: sofarsolar-g3
#    usage: pv

    # RS485 via adapter (Modbus RTU)
#    modbus: rs485serial
#    id: 1
#    device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
#    baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
#    comset: "8N1" # Kommunikationsparameter für den Adapter

    # RS485 via TCP/IP (Modbus RTU)
#    modbus: rs485tcpip
#    id: 1
#    host: 192.168.XXX.XXX # Hostname
#    port: 4196 # Port

    # Modbus TCP
#    modbus: tcpip
#    id: 1
#    host: 192.168.XXX.XXX # Hostname
#    port: 8899 # Port 

#  - name: my_battery
#    type: template
#    template: sofarsolar
#    usage: battery

#    # RS485 via adapter (Modbus RTU)
#    modbus: rs485serial
#    id: 1
#    device: /dev/ttyUSB0 # USB-RS485 Adapter Adresse
#    baudrate: 9600 # Prüfe die Geräteeinstellungen, typische Werte sind 9600, 19200, 38400, 57600, 115200
#    comset: "8N1" # Kommunikationsparameter für den Adapter

    # RS485 via TCP/IP (Modbus RTU)
#    modbus: rs485tcpip
#    id: 1
#    host: 192.0.2.2 # Hostname
#    port: 502 # Port

    # Modbus TCP
#    modbus: tcpip
#    id: 1
#    host: 192.168.XXX.XXX # Hostname
#    port: 8899 # 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

#DummyCharger
chargers:
  - name: my_charger
    type: template
    template: homematic
    host: 192.168.XXX.XXX # IP-Adresse oder Hostname
    port: 2010 # Port (optional)
    device: 'XXXA3621E' # Homematic Geräte Id, wie im CCU Webfrontend angezeigt.
    user: # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.) (optional)
    password: # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen) (optional)
    standbypower: 15 # Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (optional) 
  - name: my_charger2
    type: template
    template: tinkerforge-warp
    host: 192.168.XXX.XXX # IP Adresse oder der Hostname des MQTT Brokers
    port: 1883 # MQTT Broker Port (optional)
    user: XXX
    password: XXX
    topic: warp3/CP # Topic (ohne / am Anfang) (optional)
    timeout: 30s # Akzeptiere keine Daten die älter sind als dieser Wert (optional)
    energymanager: warp3/CP # WEM Firmware v2 erforderlich. EnergyManager MQTT Topic (falls installiert) (optional) 
#  - name: my_dummycharger
#    type: custom
#    status: # charger status A..F
#      source: script
#      cmd: /bin/sh -c 'echo b'
#    enabled: # charger enabled state (true/false or 0/1)
#      source: script
#      cmd: /bin/sh -c 'echo false'
#    enable: # set charger enabled state (true/false or 0/1)
#      source: script
#      cmd: /bin/sh -c 'echo false'
#    maxcurrent: # set charger max current (A)
#      source: script
#      cmd: /bin/sh -c 'echo 10'

#chargers:
#  - name: wallbe
#    type: wallbe # Wallbe charger
#    uri: 192.168.0.8:502 # ModBus address
#  - name: keba
#    type: ...

# 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_tesla
    type: template
    template: tesla-command # change `tesla` to `tesla-command`
    title: Tesla Model 3
    accessToken: XXX # generetad by tesla.evcc.io
    refreshToken: XXX
tesla.evcc.io
    capacity: 60 # Akkukapazität in kWh (optional)
  - name: my_id3
    type: template
    template: vw
    title: ID.3
    user: XXX
    password: XXX
    vin: #WVWZZZ... # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind (optional)
    capacity: 58 # Akkukapazität in kWh (optional)
    timeout: 10s # optional 

# site describes the EVU connection, PV and home battery
site:
  title: Home # display name for UI
  meters:
    grid: my_grid # grid meter
    pv:
      - my_pv # list of pv inverters/ meters
    battery:
      - my_battery # list of battery meters
#    aux:
 #     - aux # list of auxiliary meters for adjusting grid operating point
  residualPower: 100 # additional household usage margin
  maxGridSupplyWhileBatteryCharging: 0 # ignore battery charging if AC consumption is above this value

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Garage # display name for UI
    charger: my_charger # charger
#    meter: charge # charge meter
    mode: "off" # default charge mode to apply when vehicle is disconnected; use "off" to disable by default if charger is publicly available
    # 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: 60m
      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: 30m # threshold must be exceeded for this long
      threshold: 0 # maximum import power (W)##
  - title: Carport # display name for UI
    charger: my_charger2 # charger
#    meter: charge # charge meter
    mode: "off" # default charge mode to apply when vehicle is disconnected; use "off" to disable by default if charger is publicly available

    # 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: 60m
      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: 30m # threshold must be exceeded for this long
      threshold: 0 # maximum import power (W)

# tariffs are the fixed or variable tariffs
tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)
  grid:
    # either static grid price (or price zones)
    type: fixed
    price: 0.399 # EUR/kWh
#    zones:
#      - days: Mon-Fri
#        hours: 2-5
#        price: 0.2 # EUR/kWh
#      - days: Sat,Sun
#        price: 0.15 # EUR/kWh

    # or variable tariffs
    # type: tibber
    # token: "476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4" # access token
    # homeid: "cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c" # optional if multiple homes associated to account

    # type: awattar
    # region: de # optional, choose at for Austria
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: octopusenergy
    # tariff: AGILE-FLEX-22-11-25 # Tariff code
    # region: A # optional

    # type: elering # Nordpool
    # region: ee # or lt, lv, fi
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: energinet # Energinet using the price in DKK
    # region: dk1 # or dk2
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: entsoe # Entso-E european market data
    # domain: BZN|DE-LU # https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas
    # securitytoken: # api token
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: pun # PUN - Prezzo unico nazionale - Hourly Italian wholesale prices
    # charges: 0 # optional, additional charges per kWh
    # tax: 0 # optional, additional tax (0.1 for 10%)

    # type: amber
    # token: # api token from https://app.amber.com.au/developers/
    # siteid: # site ID returned by the API
    # channel: general

    # type: custom # price from a plugin source; see https://docs.evcc.io/docs/reference/plugins
    # price:
    #   source: http
    #   uri: https://example.org/price.json
    #   jq: .price.current

  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.08 # EUR/kWh

    # type: octopusenergy
    # tariff: AGILE-FLEX-22-11-25 # Tariff code
    # region: A # optional

    # type: amber
    # token: # api token from https://app.amber.com.au/developers/
    # siteid: # site ID returned by the API
    # channel: feedIn
  co2:
    # co2 tariff provides co2 intensity forecast and is for co2-optimized target charging if no variable grid tariff is specified
    # type: grünstromindex # GrünStromIndex (Germany only)
    # zip: <zip>

    # type: electricitymaps # https://app.electricitymaps.com/map
    # uri: <uri>
    # token: <token> # needs to be a token with forecast (not in the free tier)
    # zone: DE

    # type: ngeso # National Grid Electricity System Operator data (Great Britain only) https://carbonintensity.org.uk/
    # provides national data if both region and postcode are omitted - Choose ONE only!
    # region: 1 # optional, coarser than using a postcode - The region details are at https://carbon-intensity.github.io/api-definitions/#region-list
    # postcode: SW1 # optional - Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only

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

# 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

Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2024/04/27 16:43:28 evcc 0.125.0
[main  ] INFO 2024/04/27 16:43:28 using config file: /config/evcc.yaml
[main  ] INFO 2024/04/27 16:43:28 starting ui and api at :7070
[mqtt  ] INFO 2024/04/27 16:43:28 connecting evcc-1618428735 at tcp://localhost:1883
[mqtt  ] DEBUG 2024/04/27 16:43:28 tcp://localhost:1883 connected
[warp  ] INFO 2024/04/27 16:43:28 connecting evcc-793896146 at tcp://192.168.XXX.XXX:1883
[warp  ] DEBUG 2024/04/27 16:43:28 tcp://192.168.XXX.XXX:1883 connected
[warp  ] DEBUG 2024/04/27 16:43:28 tcp://192.168.XXX.XXX:1883 subscribe warp3/CP/evse/low_level_state
[lp-1  ] DEBUG 2024/04/27 16:43:30 charge total import: 220.977kWh
[lp-2  ] DEBUG 2024/04/27 16:43:30 charge total import: 0.000kWh
[site  ] INFO 2024/04/27 16:43:31 site config:
[site  ] INFO 2024/04/27 16:43:31   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2024/04/27 16:43:31     grid:      power ✓ energy ✓ currents ✓
[site  ] INFO 2024/04/27 16:43:31     pv 1:      power ✓ energy ✓ currents ✗
[site  ] INFO 2024/04/27 16:43:31     battery 1: power ✓ energy ✓ currents ✗ soc ✓ capacity ✓
[site  ] INFO 2024/04/27 16:43:31   vehicles:
[site  ] INFO 2024/04/27 16:43:31     vehicle 1: range ✓ finish ✓ status ✓ climate ✓ wakeup ✓
[site  ] INFO 2024/04/27 16:43:31     vehicle 2: range ✓ finish ✓ status ✓ climate ✗ wakeup ✓
[lp-1  ] INFO 2024/04/27 16:43:31 loadpoint 1:
[lp-1  ] INFO 2024/04/27 16:43:31   mode:        off
[lp-1  ] INFO 2024/04/27 16:43:31   charger:     power ✓ energy ✓ currents ✗ phases ✗ wakeup ✗
[lp-1  ] INFO 2024/04/27 16:43:31   meters:      charge ✓
[lp-1  ] INFO 2024/04/27 16:43:31     charge:    power ✓ energy ✓ currents ✗
[lp-2  ] INFO 2024/04/27 16:43:31 loadpoint 2:
[lp-2  ] INFO 2024/04/27 16:43:31   mode:        off
[lp-2  ] INFO 2024/04/27 16:43:31   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
[lp-2  ] INFO 2024/04/27 16:43:31   meters:      charge ✓
[lp-2  ] INFO 2024/04/27 16:43:31     charge:    power ✓ energy ✓ currents ✓
[site  ] DEBUG 2024/04/27 16:43:31 set priority soc: 60
[lp-1  ] DEBUG 2024/04/27 16:43:31 phase timer inactive
[lp-1  ] DEBUG 2024/04/27 16:43:31 pv timer inactive
[lp-1  ] DEBUG 2024/04/27 16:43:31 max charge current: 6A
[lp-2  ] DEBUG 2024/04/27 16:43:31 phase timer inactive
[lp-2  ] DEBUG 2024/04/27 16:43:31 pv timer inactive
[site  ] WARN 2024/04/27 16:43:31 interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval
[site  ] DEBUG 2024/04/27 16:43:31 ----
[lp-1  ] DEBUG 2024/04/27 16:43:31 charge power: 2846W
[lp-2  ] DEBUG 2024/04/27 16:43:31 charge power: 0W
[site  ] DEBUG 2024/04/27 16:43:32 pv power: 7100W
[site  ] DEBUG 2024/04/27 16:43:34 battery soc: 92%
[site  ] DEBUG 2024/04/27 16:43:34 battery power: 1560W
[site  ] DEBUG 2024/04/27 16:43:34 grid meter: -0W
[site  ] DEBUG 2024/04/27 16:43:36 grid powers: [-0 -0 -0]W
[site  ] DEBUG 2024/04/27 16:43:40 grid currents: [0 0 0]A
[site  ] DEBUG 2024/04/27 16:43:40 site power: 1660W
[lp-1  ] DEBUG 2024/04/27 16:43:40 charge total import: 221.002kWh
[lp-1  ] DEBUG 2024/04/27 16:43:40 charger status: C
[lp-1  ] DEBUG 2024/04/27 16:43:40 charge start energy: 221kWh
[lp-1  ] INFO 2024/04/27 16:43:40 car connected
[lp-1  ] DEBUG 2024/04/27 16:43:40 vehicle api refresh
[lp-1  ] DEBUG 2024/04/27 16:43:40 pv timer elapse
[lp-1  ] DEBUG 2024/04/27 16:43:40 pv timer inactive
[lp-1  ] DEBUG 2024/04/27 16:43:40 charge total import: 221.002kWh
[lp-1  ] DEBUG 2024/04/27 16:43:40 charge start energy: 221kWh
[lp-1  ] INFO 2024/04/27 16:43:40 start charging ->
[lp-1  ] DEBUG 2024/04/27 16:43:40 wake-up timer: stop
[main  ] DEBUG 2024/04/27 16:43:43 vehicle status: C (ID.3)
[main  ] DEBUG 2024/04/27 16:43:43 vehicle status: C (Tesla Model 3)
[main  ] WARN 2024/04/27 16:43:43 vehicle status: >1 matches, giving up
[lp-1  ] DEBUG 2024/04/27 16:43:43 max charge current: 16A
[site  ] DEBUG 2024/04/27 16:43:43 ----
[lp-1  ] DEBUG 2024/04/27 16:43:43 charge power: 2865W
[lp-2  ] DEBUG 2024/04/27 16:43:43 charge power: 4077W
[site  ] DEBUG 2024/04/27 16:43:44 pv power: 7100W
[site  ] DEBUG 2024/04/27 16:43:45 battery soc: 92%
[site  ] DEBUG 2024/04/27 16:43:45 battery power: 1540W
[site  ] DEBUG 2024/04/27 16:43:46 grid meter: -0W
[site  ] DEBUG 2024/04/27 16:43:48 grid powers: [-0 -0 -0]W
[site  ] DEBUG 2024/04/27 16:43:52 grid currents: [0 0 0]A
[site  ] DEBUG 2024/04/27 16:43:52 site power: 1640W
panic: runtime error: index out of range [3] with length 0

goroutine 261 [running]:
github.com/evcc-io/evcc/charger.(*Warp2).currents(0x2717ee0?)
    github.com/evcc-io/evcc/charger/warp2.go:274 +0x88
github.com/evcc-io/evcc/charger.(*decorateWarp2PhaseCurrentsImpl).Currents(0xc00117bb68?)
    github.com/evcc-io/evcc/charger/warp2_decorators.go:2728 +0x12
github.com/evcc-io/evcc/core.(*Loadpoint).updateChargeCurrents(0xc000cc8c08)
    github.com/evcc-io/evcc/core/loadpoint.go:1319 +0x92
github.com/evcc-io/evcc/core.(*Loadpoint).Update(0xc000cc8c08, 0x4099a00000000000, 0x0, 0x0, 0x0, 0x3ff0000000000000, 0xc001cf1df0, 0x0)
    github.com/evcc-io/evcc/core/loadpoint.go:1545 +0xff
github.com/evcc-io/evcc/core.(*Site).update(0xc0017deb60, {0x3808dd8, 0xc000cc8c08})
    github.com/evcc-io/evcc/core/site.go:790 +0x4e7
github.com/evcc-io/evcc/core.(*Site).Run(0xc0017deb60, 0xc0018c8900, 0x2540be400)
    github.com/evcc-io/evcc/core/site.go:910 +0x2f5
github.com/evcc-io/evcc/cmd.runRoot.func4()
    github.com/evcc-io/evcc/cmd/root.go:284 +0x25
created by github.com/evcc-io/evcc/cmd.runRoot in goroutine 1
    github.com/evcc-io/evcc/cmd/root.go:283 +0x1adf

What type of operating system are you running?

HomeAssistant Add-on

Version

0.125.0

andig commented 2 months ago

Closed in https://github.com/evcc-io/evcc/commit/07e7dedc009802f04e8f0faa37ec1f9f66046634

Logirius commented 2 months ago

Hallo vielen herzlichen Dank für die schnelle Korrektur.

Inzwischen wurde das neue Release in Homeassistant veröffentlicht und ich konnte es installieren.

Leider kommt jetzt dieser Fehler

[lp-1 ] ERROR 2024/05/04 09:16:27 charge currents: json: cannot unmarshal object into Go value of type []float64

Handelt es sich um einen Folgefehler oder ein neues Problem? In zweiterem Fall reporte ich einen neuen Issue.

Viele Grüße

Jürgen

andig commented 2 months ago

Meine Glaskugel ist zur Reparatur. Gibts ein Logfile?