search

evcc-io / evcc

Solar Charging ☀️🚘
https://evcc.io
MIT License
3.67k stars 688 forks source link

Ladung wird doppelt gezählt Tesla TWC3 #12654

Closed themex85 closed 9 months ago

themex85 commented 9 months ago

Describe the bug

Ich habe voll Freude am Wochenende mit der v0.124.6 Sonne und ein bisschen "günstigen" Tibber-Strom geladen. Das Fahrzeug war von Samstagmittag bis Sonntagabend durchgängig angesteckt.

Aus irgendeinem Grund wurde aber die Ladung doppelt gezählt 3.3., 16:16 mit 45 kwh 3.3., 10:19 mit 33,8 kwh

Bildschirmfoto 2024-03-04 um 12 33 09

Teslamate logt die Ladevorgänge auch komplett anders mit:

Bildschirmfoto 2024-03-04 um 12 35 16

Tesla-App sagt auch, dass irgendwas um 38 kwh am 3.3. geladen wurden.

Bei mir gibt es auch weiterhin ständig rote Ausrufezeichen mit Server 500 Fehler, wenn das Fahrzeug / der Ladevorgang gesteuert werden soll.

Steps to reproduce

  1. TWC3
  2. Tesla
  3. Strom laden ...

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

# trial token, valid until 2024-02-22
sponsortoken: eyJXXXXXX

plant: cb040dd468XXXXXXXXX

# 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: trace
levels:
  site: error
  lp-1: error
  lp-2: error
  cache: error
  db: error
  tesla: trace

# 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: grid
    type: template
    template: tibber-pulse
    usage: grid
    token: mein TOken
#    homeid: meine HomeID # optional 

#  - name: grid
#    type: template
#    template: powerfox-poweropti
#    usage: grid
#    user: Mailadresse # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
#    password: Passwort # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)

#  - name: pv
#    type: template
#    template: powerfox-poweropti
#    usage: pv
#    user: XXXXXXXom # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
#    password: YXXXX # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)

  - name: pv
    type: template
    template: solaredge-inverter
    usage: pv
        # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.180.12 # 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: TWC3
    type: template
    template: twc3
    host: 192.168.180.91 # IP-Adresse oder Hostname 
#  - name: fritzdect
#    type: template
#    template: fritzdect
#    uri: https://fritz.box # HTTP(S) Adresse (Optional)
#    user: ---- # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
#    password: ----- # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)
#    ain: "XXXxX" # Die AIN ist auf dem Typenschild auf der Geräterückseite aufgedruckt. Bei führenden Nullen bitte in doppelte Hochkommata setzen.
#    standbypower: 15 # Leistung oberhalb des angegebenen Wertes wird als Ladeleistung gewertet (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: Tesla_Model_Y_SR
    type: template
    template: tesla
    control: true
    title: Tesla Model Y SR # Wird in der Benutzeroberfläche angezeigt (Optional)
    accessToken: eyJhXXXXXXXXX # Siehe https://docs.evcc.io/docs/devices/vehicles#tesla
    refreshToken: EU_d07CCCCCC# Siehe https://docs.evcc.io/docs/devices/vehicles#tesla
    vin: LRWYCCCCCCCCCC # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind (Optional)
    capacity: 62 # Akkukapazität in kWh (Optional) 
    minCurrent: 1 # minimum charge current (default 6A)
    maxCurrent: 16 # maximum charge current (default 16A)

# site describes the EVU connection, PV and home battery
site:
  title: Home # display name for UI
  meters:
    grid: grid # grid meter
    pv:
      - pv # list of pv inverters/ meters
    battery:
#      - battery # list of battery meters
    aux:
#      - aux # 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.20 # 20 ct # set cost limit for automatic charging in PV mode

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Stellplatz # display name for UI
    charger: TWC3 # Wallbox Referenz
    vehicle: Tesla_Model_Y_SR # Referenz auf Standardfahrzeug
    mode: pv # charge mode (off, now, minpv, pv)
#  - title: Garage # display name for UI
#    charger: fritzdect # Wallbox Referenz
#    vehicle: Tesla Model Y SR # Referenz auf Standardfahrzeug
#    mode: minpv # charge mode (off, now, minpv, pv)

    # 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: -500 # 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: 500 # 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.32 # EUR/kWh
    #zones:
    #  - days: Mo-Fr
    #    hours: 2-5
    #    price: 0.32 # EUR/kWh
    #  - days: Sa,So
    #    price: 0.32 # EUR/kWh
    type: tibber
    token: "9K5qSsXXXXXXXXX" # access token
    #homeid: "cc8XXXXXXXXXX" # optional if multiple homes associated to account

  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.082 # EUR/kWh
  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: evcc
  password: passwort

# 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

Ich nutze EVCC eigentlich innerhalb von HomeAssistant. Kann man das irgendwie trotzdem in den Logs nachvollziehen? Vielleicht hat jemand einen Tipp, wie ich in dem Setup trotzdem die Terminalbefehle ausführen kann und an die Log-Dateien ran komme. Ich hatte zwischenzeitlich schon mal auf einem PI die Nightly installiert wegen der Probleme mit dem TWC3 und dem Aufwecken des Fahrzeugs

What type of operating system are you running?

HomeAssistant Add-on

Version

0.124.5

andig commented 9 months ago

Logfile fehlt