search

evcc-io / evcc

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

Fehler gefunden, Pulsar Plus über OCPP seit letzten Update von Pulsar verurschacht ständige Abstürtze von EVCC, EVCCfriertein und nichts funktioniert mehr. #10395

Closed killerwahl closed 1 year ago

killerwahl commented 1 year ago

Describe the bug

Hallo, seit update von HA auf 2023.10 läuft EVCC nicht mehr richtig. EVCC startet ständig neu. Instaliert sind zwei Wallboxen KEBA und Pulsar Plus, Pulsar Plus per OCPP. Bei Pulsar Plus werden keine Fahrzeige mehr erkannt, Ladung auch nicht gestartet, schalte ich OCPP aus, kann ich Ladung manuell Starten. Bei Keba werden Fahrzeigen zwar Erkannt aber z.B. bei 5kw überschuß ladet es nur mit 1.4kw und geht auch nicht hoch. Bis zu Update vom HA hat alles wunderbar funktioniert. Update auf 0.121.1 hat leider auch keine abhilfe geschafft.

Steps to reproduce

1. 2. 3. ...

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

interval: 30s # 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: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

# 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: huawei-dongle-powersensor
    usage: grid

    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.178.xxx # Hostname
    port: 502 # Port 

  - name: my_pv
    type: template
    template: huawei-dongle-powersensor
    usage: pv

    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.178.xxx # Hostname
    port: 502 # Port 

  - name: my_battery
    type: template
    template: huawei-dongle-powersensor
    usage: battery

     # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.178.xxx # Hostname
    port: 502 # 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: my_charger_1
    type: template
    template: keba-modbus

    # Modbus TCP
    modbus: tcpip
    id: 255
    host: 192.168.178.xx # Hostname
    port: 502 # Port 

  - name: my_charger_2
    type: template
    template: pulsarplus
# 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: car
    type: renault
    title: Zoe
    capacity: 52 # kWh
    user: xxxxxxxxxxxxxxxxxxxxxxxxx # user
    password: xxxxxxxxxxxxxxx # password
    vin: xxxxxxxxxxxxxxxxxxxxx
    onIdentify: # set defaults when vehicle is identified
      mode: pv # enable PV-charging when vehicle is identified
      minSoc: 20 # immediately charge to 0% regardless of mode unless "off" (disabled)
      targetSoc: 95 # limit charge to 90%

  - name: my_car
    type: template
    template: hyundai
    title: Tucson # Wird in der Benutzeroberfläche angezeigt (Optional)
    user: xxxxxxxxxxxxxxxxxxxxxxxxx # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    password: xxxxxxxxxxxxxxxxxx  # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)
    vin: TMxxxxxxxxxxxxxxxxx # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind (Optional)
    capacity: 14 # Akkukapazität in kWh (Optional)
    language: de # 'de' für Deutsch und 'en' für Englisch (Optional)

# 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
    battery: my_battery # list of battery meters
# list of auxiliary meters for adjusting grid operating point
  residualPower: 0 # additional household usage margin
  prioritySoc: 0 # give home battery priority up to this soc (empty to disable)
  bufferSoc: 0 # continue charging on battery above soc (0 to disable)
  bufferStartSoc: 0 # start charging on battery above soc (0 to disable)
  maxGridSupplyWhileBatteryCharging: 0 # ignore battery charging if AC consumption is above this value
  smartCostLimit: 0 # set cost limit for automatic charging in PV mode

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Wallbox Parkplatz # display name for UI
    charger: my_charger_1 # Wallbox Referenz
    vehicle: car # Referenz auf Standardfahrzeug
    mode: pv # charge mode (off, now, minpv, pv)
    # 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: 32 # maximum charge current (default 16A)

  - title: Wallbox Garage # display name for UI
    charger: my_charger_2 # Wallbox Referenz
    vehicle: my_car # Referenz auf Standardfahrzeug
    mode: pv # charge mode (off, now, minpv, pv)
    # vehicle: car1 # set default vehicle (disables vehicle detection)
    resetOnDisconnect: true # set defaults when vehicle disconnects
    phases: 1 # 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: 32 # 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: 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: 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 # three letter ISO-4217 currency code (default EUR)
  grid:
    # either static grid price (or price zones)
    type: fixed
    price: 0.294 # EUR/kWh
    zones:
      - days: Mo-Fr
        hours: 2-5
        price: 0.2 # EUR/kWh
      - days: Sa,So
        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%)
  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.082 # EUR/kWh

    # type: octopusenergy
    # tariff: AGILE-FLEX-22-11-25 # Tariff code
    # region: A # optional
  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>
    # zone: DE

# 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

Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2023/10/19 11:16:39 evcc 0.121.1
[main  ] INFO 2023/10/19 11:16:39 using config file: /config/evcc.yaml
[main  ] INFO 2023/10/19 11:16:39 starting ui and api at :7070

What type of operating system are you running?

HomeAssistant Add-on

Version

0.121.1

killerwahl commented 1 year ago

Jetzt wurde Fahrzeig an KEBA erkannt, an Pulsar nicht, OCPP Verbindung steht. Using config file: /config/evcc.yaml starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml' [main ] INFO 2023/10/19 11:38:52 evcc 0.121.1 [main ] INFO 2023/10/19 11:38:52 using config file: /config/evcc.yaml [main ] INFO 2023/10/19 11:38:52 starting ui and api at :7070 [ocpp ] INFO 2023/10/19 11:39:46 charge point connected, registering: 264611 [site ] WARN 2023/10/19 11:39:53 battery configured but residualPower is missing or <= 0 (add residualPower: 100 to site), see https://docs.evcc.io/en/docs/reference/configuration/site#residualpower [site ] INFO 2023/10/19 11:39:53 site config: [site ] INFO 2023/10/19 11:39:53 meters: grid ✓ pv ✓ battery ✓ [site ] INFO 2023/10/19 11:39:53 grid: power ✓ energy ✓ currents ✓ [site ] INFO 2023/10/19 11:39:53 pv 1: power ✓ energy ✓ currents ✗ [site ] INFO 2023/10/19 11:39:53 battery 1: power ✓ energy ✓ currents ✗ soc ✓ capacity ✗ [site ] INFO 2023/10/19 11:39:53 vehicles: [site ] INFO 2023/10/19 11:39:53 vehicle 1: range ✓ finish ✓ status ✓ climate ✓ wakeup ✓ [site ] INFO 2023/10/19 11:39:53 vehicle 2: range ✓ finish ✓ status ✓ climate ✗ wakeup ✓ [lp-1 ] INFO 2023/10/19 11:39:53 loadpoint 1: [lp-1 ] INFO 2023/10/19 11:39:53 mode: pv [lp-1 ] INFO 2023/10/19 11:39:53 charger: power ✓ energy ✓ currents ✓ phases ✗ wakeup ✗ [lp-1 ] INFO 2023/10/19 11:39:53 meters: charge ✓ [lp-1 ] INFO 2023/10/19 11:39:53 charge: power ✓ energy ✓ currents ✓ [lp-2 ] INFO 2023/10/19 11:39:53 loadpoint 2: [lp-2 ] INFO 2023/10/19 11:39:53 mode: pv [lp-2 ] INFO 2023/10/19 11:39:53 charger: power ✗ energy ✓ currents ✗ phases ✗ wakeup ✗ [lp-2 ] INFO 2023/10/19 11:39:53 meters: charge ✗ [lp-1 ] DEBUG 2023/10/19 11:39:53 phase timer inactive [lp-1 ] DEBUG 2023/10/19 11:39:53 pv timer inactive [lp-1 ] DEBUG 2023/10/19 11:39:53 guard timer inactive [lp-1 ] INFO 2023/10/19 11:39:53 vehicle updated: unknown -> Zoe [lp-1 ] DEBUG 2023/10/19 11:39:53 set charge mode: pv [lp-1 ] DEBUG 2023/10/19 11:39:53 set target soc: 95 [lp-2 ] DEBUG 2023/10/19 11:39:54 phase timer inactive [lp-2 ] DEBUG 2023/10/19 11:39:54 pv timer inactive [lp-2 ] DEBUG 2023/10/19 11:39:54 guard timer inactive [lp-2 ] INFO 2023/10/19 11:39:54 vehicle updated: unknown -> Tucson [site ] DEBUG 2023/10/19 11:39:54 ---- [lp-1 ] DEBUG 2023/10/19 11:39:57 charge power: 0W [lp-2 ] DEBUG 2023/10/19 11:39:57 charge power: 0W [site ] DEBUG 2023/10/19 11:39:59 pv power: 195W [site ] DEBUG 2023/10/19 11:40:04 battery soc: 11% [site ] DEBUG 2023/10/19 11:40:04 battery power: 217W [site ] DEBUG 2023/10/19 11:40:06 grid power: 23W [site ] DEBUG 2023/10/19 11:40:12 grid currents: [-0.53 0.64 0.74]A [site ] DEBUG 2023/10/19 11:40:13 site power: 240W [lp-1 ] DEBUG 2023/10/19 11:40:21 vehicle odometer: 14165km [lp-1 ] DEBUG 2023/10/19 11:40:24 charge currents: [0 0 0]A [lp-1 ] DEBUG 2023/10/19 11:40:29 charge total import: 2365.183kWh [lp-1 ] DEBUG 2023/10/19 11:40:29 charger status: B [lp-1 ] DEBUG 2023/10/19 11:40:29 charge start energy: 2.37e+03kWh [lp-1 ] INFO 2023/10/19 11:40:29 car connected [lp-1 ] DEBUG 2023/10/19 11:40:29 pv timer elapse [lp-1 ] DEBUG 2023/10/19 11:40:29 pv timer inactive [lp-1 ] DEBUG 2023/10/19 11:40:29 charger: guard elapse [lp-1 ] DEBUG 2023/10/19 11:40:29 guard timer inactive [lp-1 ] DEBUG 2023/10/19 11:40:29 charge total import: 2365.183kWh [lp-1 ] DEBUG 2023/10/19 11:40:34 vehicle status: B [lp-1 ] DEBUG 2023/10/19 11:40:34 vehicle soc: 88% [lp-1 ] DEBUG 2023/10/19 11:40:34 vehicle range: 271km [lp-1 ] DEBUG 2023/10/19 11:40:34 pv charge current: 0A = 0A + -0.348A (240W @ 3p) [lp-1 ] DEBUG 2023/10/19 11:40:34 pv enable timer reset [lp-1 ] DEBUG 2023/10/19 11:40:34 pv timer inactive [site ] DEBUG 2023/10/19 11:40:34 ---- [lp-1 ] DEBUG 2023/10/19 11:40:34 charge power: 0W [lp-2 ] DEBUG 2023/10/19 11:40:34 charge power: 0W [site ] DEBUG 2023/10/19 11:40:36 pv power: 212W [site ] DEBUG 2023/10/19 11:40:38 battery soc: 10% [site ] DEBUG 2023/10/19 11:40:38 battery power: 356W [site ] DEBUG 2023/10/19 11:40:39 grid power: 49W [site ] DEBUG 2023/10/19 11:40:41 grid currents: [-0.75 -0.69 0.87]A [site ] DEBUG 2023/10/19 11:40:42 site power: 405W [lp-2 ] DEBUG 2023/10/19 11:40:43 vehicle odometer: 25081km

tobiasbayer commented 1 year ago

Ständige Neustarts bei Nutzung des HA-Addons hatten wir schon mal. Evtl. wieder die gleiche Ursache?

killerwahl commented 1 year ago

Ich probiere Watchdog auszuschalten, im moment ist wieder abgesturzt. Using config file: /config/evcc.yaml starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml' [main ] INFO 2023/10/19 11:44:55 evcc 0.121.1 [main ] INFO 2023/10/19 11:44:55 using config file: /config/evcc.yaml [main ] INFO 2023/10/19 11:44:55 starting ui and api at :7070 [ocpp ] INFO 2023/10/19 11:46:35 charge point connected, registering: 264611 [main ] FATAL 2023/10/19 11:47:35 cannot create charger 'my_charger_2': cannot create charger 'template': cannot create charger 'ocpp': ocpp message (2824873902): GenericError - Request timed out [main ] FATAL 2023/10/19 11:47:35 will attempt restart in: 5m0s

killerwahl commented 1 year ago

So, jetzt stürzt zwar EVCC nicht mehr ab, aber Regelt trotzdem nichts. KEBA Fahrzeug erkannt, Laden auf Netzladen umgestelt, Ladung startet trotzdem nicht. Pulsar Plus Fahrzeug wird immer nocht nicht erkannt.

[lp-2 ] DEBUG 2023/10/19 12:05:03 set charge mode: now [lp-1 ] DEBUG 2023/10/19 12:05:52 set charge mode: now

guhlandreas commented 1 year ago

Hallo, ich habe heute auch ein ähnliches Problem bei mir bemerkt. Ich weiß allerdings nicht genau, seit wann oder nach welchem Update oder Änderung das Problem bei mir aufgetreten ist. EVCC läuft bei mir im Home Assistant. Ich verwende die aktuelle HA (2023.10.3) und EVCC (0.121.1) version.

EVCC startet nicht mehr. Und dem log file kann ich entnehmen:

Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main  ] INFO 2023/10/19 20:49:59 evcc 0.121.1
[main  ] INFO 2023/10/19 20:49:59 using config file: /config/evcc.yaml
[main  ] INFO 2023/10/19 20:49:59 starting ui and api at :7070
[db    ] INFO 2023/10/19 20:49:59 using sqlite database: /data/evcc.db
[db    ] TRACE 2023/10/19 20:49:59 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="settings" -1 <nil>
[db    ] TRACE 2023/10/19 20:49:59 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "settings" AND sql IS NOT NULL order by type = "table" desc 1 <nil>
[db    ] TRACE 2023/10/19 20:49:59 SELECT * FROM `settings` LIMIT 1 -1 <nil>
[db    ] TRACE 2023/10/19 20:49:59 SELECT * FROM `settings` 0 <nil>
[mqtt  ] INFO 2023/10/19 20:49:59 connecting evcc-605935984 at tcp://localhost:1883
[db    ] TRACE 2023/10/19 20:49:59 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="devices" -1 <nil>
[db    ] TRACE 2023/10/19 20:49:59 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="device_details" -1 <nil>
[db    ] TRACE 2023/10/19 20:49:59 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="configs" -1 <nil>
[db    ] TRACE 2023/10/19 20:49:59 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "configs" AND sql IS NOT NULL order by type = "table" desc 1 <nil>
[db    ] TRACE 2023/10/19 20:49:59 SELECT * FROM `configs` LIMIT 1 -1 <nil>
[db    ] TRACE 2023/10/19 20:49:59 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="config_details" -1 <nil>
[db    ] TRACE 2023/10/19 20:49:59 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "config_details" AND sql IS NOT NULL order by type = "table" desc 2 <nil>
[db    ] TRACE 2023/10/19 20:49:59 SELECT * FROM `config_details` LIMIT 1 -1 <nil>
[db    ] TRACE 2023/10/19 20:49:59 SELECT count(*) FROM sqlite_master WHERE type = "table" AND tbl_name = "config_details" AND (sql LIKE "%CONSTRAINT \"fk_configs_details\" %" OR sql LIKE "%CONSTRAINT fk_configs_details %" OR sql LIKE "%CONSTRAINT `fk_configs_details`%" OR sql LIKE "%CONSTRAINT [fk_configs_details]%" OR sql LIKE "%CONSTRAINT     fk_configs_details  %") -1 <nil>
[db    ] TRACE 2023/10/19 20:49:59 SELECT count(*) FROM sqlite_master WHERE type = "index" AND tbl_name = "config_details" AND name = "idx_unique" -1 <nil>
[db    ] TRACE 2023/10/19 20:49:59 SELECT count(*) FROM sqlite_master WHERE type = "table" AND tbl_name = "config_details" AND (sql LIKE "%CONSTRAINT \"fk_devices_details\" %" OR sql LIKE "%CONSTRAINT fk_devices_details %" OR sql LIKE "%CONSTRAINT `fk_devices_details`%" OR sql LIKE "%CONSTRAINT [fk_devices_details]%" OR sql LIKE "%CONSTRAINT     fk_devices_details  %") -1 <nil>
[db    ] TRACE 2023/10/19 20:49:59 SELECT count(*) FROM sqlite_master WHERE type = "table" AND tbl_name = "config_details" AND (sql LIKE "%\"device_id\" %" OR sql LIKE "%device_id %" OR sql LIKE "%`device_id`%" OR sql LIKE "%[device_id]%" OR sql LIKE "%   device_id   %") -1 <nil>

Hat jemand eine Idee?

Ich bin ratlos und würde mich über Hilfe freuen!

Beste Grüße

Andreas

killerwahl commented 1 year ago

Andreas, schalte Watchdog aus dann startet EVCC nicht mehr ständig neu. Bei mir läuft zwar EVCC seit gestern ohne neustart aber funktionieren tut es immer noch nicht. An Pulsat über OCPP wird kein Fahrzeug erkannt und geladen. An Keba werden zwar Fahrzeugen erkannt aber wenn ich z.B.volle Netzladung auswähle fängt Auto mit nur 1,2 kw anstatt 7,4kw zu Laden, in EVCC wird Ladung aber nicht angezeigt nur in Keba APP. Letzte 3 Monaten hat alles wunderbar funktiomiert, jetzt haben wir zwar keine Sonne aber das nichts richtig funktioniert ist ärgerlich.

guhlandreas commented 1 year ago

hallo @killerwahl, danke für Deine Nachricht. Immerhin scheine ich nicht alleine mit meinem Problem zu sein ;-) Ja, Watchdog ist aus, mit dem Effekt, dass EVCC nun nach dem start hängen bleibt und nicht läuft. Mir ist der Fehler rätselhaft und ich weiss garnicht in welche Richtung ich suchen soll. Datenbank? Viele Grüße Andreas

killerwahl commented 1 year ago

@guhlandreas, habe leider auch keine Ahnung. EVCC zeigt mir auch vollig falsche Werten an, die verändern sich seit gestern nicht. Laut EVCC ist meine Batterie zu 9% voll und vom Dach nur 200W leistung kommen, obwohl Batterie leer ist und vom Dach jetzt 500w kommen.

killerwahl commented 1 year ago

Update: habe Pulsar Plus aus EVCC gelöscht und EVCC neu gestartet. Jetzt funktioniert mindestens Energie Anzeige richtig. Vor kurzem hat Pulsar Plus auch ein Update bekommen, vielleicht haben die am OCPP Protokol was geändert. Habe beim Pulsar jetzt OCPP ausgeschaltet. Werde am KEBA gleich testen ob Netzladen geht. Update: Fehler lag bei Pulsar Plus und OCPP KEBA in verbindung mit EVCC funktioniert wieder wie es soll, Pulsar kann ich im Moment leider nur über App bedienen. Werde Support von EVCC anschreiben das die ein Auge auf OCPP Protokol bei Pulsar werfen.

andig commented 1 year ago

im moment ist wieder abgesturzt.

Es ist völlig unklar, was das heissen soll. Bitte mal Logfile des konkreten Fehlers, sonst würde ich hier schließen. Wir bearbeiten keine Issues ohne Logfile!

@guhlandreas bitte neues Issue. Ob/was das hiermit zu tun hat ist völlig unklar. Bei Dir hätte ich eine Idee ;)

guhlandreas commented 1 year ago

@andig: Danke für das feedback in meine Richtung. Unter https://github.com/evcc-io/evcc/issues/10407 habe ich ein neues Issue aufgemacht. Nun bin ich neugierig auf Deine Idee ;-)

andig commented 1 year ago

Update: Fehler lag bei Pulsar Plus und OCPP... Werde Support von EVCC anschreiben

Das hier ist der Support von evcc ;) Ich mach mal zu bis es ein aussagekräftiges Logfile gibt.

killerwahl commented 1 year ago

@andig wenn du mir sagen kannst wo Logfile bei HA versteckt sind kann ich die hier selbstvertändlich posten. Im Moment komme ich nur an Protokol ran. Was mir aufgefallen ist, ist diese Fehlermeldung im Protokol: [ocpp ] INFO 2023/10/21 09:05:36 charge point connected, registering: 264611 [site ] WARN 2023/10/21 09:05:56 battery configured but residualPower is missing or <= 0 (add residualPower: 100 to site), see https://docs.evcc.io/en/docs/reference/configuration/site#residualpower Wenn ich Pulsar aus EVCC lösche habe ich die Batterie Warnmeldung nicht.

andig commented 1 year ago

Ich hab leider kein HA. Im Zweifel musst du das ohne testen.

killerwahl commented 1 year ago

Im Moment läuft 120.03 stabil. Wenn ich mehr Zeit habe installiere ich EVCC auf PC und Teste. Schönes und Arbeitsfreies Wochenende.

killerwahl commented 1 year ago

Nach Update von HA auf 2023.10.4 läuft EVCC auch als 0.121.1 wieder Einwandfrei. Morgen beobachte ich noch, wenn genug Sonne da ist.