Ladezustand Mokka wird nicht mehr angezeigt #16229

diver77 · 2024-09-20T06:40:38Z

diver77
Sep 20, 2024

Hallo zusammen,
habe seit ein paar Tagen das Problem, dass bei meinem Mokka der Ladezustand nicht mehr angezeigt wird.
Der Mokka wird an einer Ge-e-Charge V3 angeschlossen. habe schon gaaaaaannnnzzzzz lange keine Probleme mehr damit gehabt, aber seit ein paar Tagen sieht es so aus.

Habt Ihr eine Idee an was es liegen kann. Hat es vielleicht damit zu tun, dass ich das neueste update von evcc eingespielt habe in mein Homeassistant?
Danke für Eure Hilfe
Gruß Diver

diver77 · 2024-09-20T17:21:59Z

diver77
Sep 20, 2024
Author

Hat denn keiner eine Idee an was das liegen kann. im Logfile kommt leider auch kein Fehler.
[site ] DEBUG 2024/09/20 19:18:58 battery soc: 86%
[site ] DEBUG 2024/09/20 19:18:58 battery power: 736W
[site ] DEBUG 2024/09/20 19:18:58 grid meter: 6W
[site ] DEBUG 2024/09/20 19:18:59 grid powers: [-150 130 25]W
[site ] DEBUG 2024/09/20 19:18:59 grid currents: [-0.8 1.8 0.7]A
[site ] DEBUG 2024/09/20 19:18:59 site power: 842W
[site ] DEBUG 2024/09/20 19:19:07 ----
[lp-1 ] DEBUG 2024/09/20 19:19:08 charge power: 0W
[lp-1 ] DEBUG 2024/09/20 19:19:08 charge currents: [0 0 0]A
[lp-2 ] DEBUG 2024/09/20 19:19:09 charge power: 0W
[site ] DEBUG 2024/09/20 19:19:09 pv power: 0W
[site ] DEBUG 2024/09/20 19:19:09 battery soc: 86%
[site ] DEBUG 2024/09/20 19:19:09 battery power: 768W
[site ] DEBUG 2024/09/20 19:19:09 grid meter: 601W
[site ] DEBUG 2024/09/20 19:19:09 grid powers: [-164 751 14]W
[site ] DEBUG 2024/09/20 19:19:09 grid currents: [-0.8 1.8 0.7]A
[site ] DEBUG 2024/09/20 19:19:09 site power: 1469W
[lp-1 ] DEBUG 2024/09/20 19:19:09 charge total import: 6301.018kWh
[lp-1 ] DEBUG 2024/09/20 19:19:09 charger status: B
[lp-1 ] DEBUG 2024/09/20 19:19:09 plan: charge 5h0m2s between 2024-09-21 00:29:58 +0200 CEST until 2024-09-21 05:30:00 +0200 CEST (power: 11040W, avg cost: 0.294)
[lp-1 ] DEBUG 2024/09/20 19:19:09 pv charge current: 0A = 0A + -6.39A (1469W @ 1p)
[site ] DEBUG 2024/09/20 19:19:17 ----
[lp-1 ] ERROR 2024/09/20 19:19:27 charge power: Get "http://192.168.188.197/api/status?filter=alw,car,eto,nrg,wh,trx,cards": context deadline exceeded
[lp-1 ] DEBUG 2024/09/20 19:19:33 charge currents: [0 0 0]A
[lp-2 ] DEBUG 2024/09/20 19:19:33 charge power: 0W
[site ] DEBUG 2024/09/20 19:19:34 pv power: 0W
[site ] DEBUG 2024/09/20 19:19:34 battery soc: 86%
[site ] DEBUG 2024/09/20 19:19:34 battery power: 743W
[site ] DEBUG 2024/09/20 19:19:34 grid meter: 4W
[site ] DEBUG 2024/09/20 19:19:34 grid powers: [-154 117 17]W
[site ] DEBUG 2024/09/20 19:19:34 grid currents: [-0.9 1.8 0.7]A
[site ] DEBUG 2024/09/20 19:19:34 site power: 847W
[lp-2 ] DEBUG 2024/09/20 19:19:34 charge total import: 0.000kWh
[lp-2 ] DEBUG 2024/09/20 19:19:34 charger status: B
[lp-2 ] DEBUG 2024/09/20 19:19:34 pv charge current: 0A = 0A + -3.68A (847W @ 1p)
[site ] DEBUG 2024/09/20 19:19:34 ----
[lp-1 ] DEBUG 2024/09/20 19:19:34 charge power: 0W
[lp-1 ] DEBUG 2024/09/20 19:19:34 charge currents: [0 0 0]A
[lp-2 ] DEBUG 2024/09/20 19:19:34 charge power: 0W
[site ] DEBUG 2024/09/20 19:19:34 pv power: 0W
[site ] DEBUG 2024/09/20 19:19:34 battery soc: 86%
[site ] DEBUG 2024/09/20 19:19:34 battery power: 762W
[site ] DEBUG 2024/09/20 19:19:34 grid meter: -20W
[site ] DEBUG 2024/09/20 19:19:35 grid powers: [-160 122 18]W
[site ] DEBUG 2024/09/20 19:19:35 grid currents: [-0.9 1.8 0.7]A
[site ] DEBUG 2024/09/20 19:19:35 site power: 842W
[site ] DEBUG 2024/09/20 19:19:37 ----
[lp-1 ] DEBUG 2024/09/20 19:19:38 charge power: 0W
[lp-1 ] DEBUG 2024/09/20 19:19:38 charge currents: [0 0 0]A
[lp-2 ] DEBUG 2024/09/20 19:19:38 charge power: 0W
[site ] DEBUG 2024/09/20 19:19:39 pv power: 0W
[site ] DEBUG 2024/09/20 19:19:39 battery soc: 86%
[site ] DEBUG 2024/09/20 19:19:39 battery power: 735W
[site ] DEBUG 2024/09/20 19:19:39 grid meter: -6W
[site ] DEBUG 2024/09/20 19:19:39 grid powers: [-152 118 27]W
[site ] DEBUG 2024/09/20 19:19:39 grid currents: [-0.9 1.8 0.7]A
[site ] DEBUG 2024/09/20 19:19:39 site power: 829W
[lp-1 ] DEBUG 2024/09/20 19:19:39 charge total import: 6301.018kWh
[lp-1 ] DEBUG 2024/09/20 19:19:39 charger status: B
[lp-1 ] DEBUG 2024/09/20 19:19:39 plan: charge 5h0m2s between 2024-09-21 00:29:58 +0200 CEST until 2024-09-21 05:30:00 +0200 CEST (power: 11040W, avg cost: 0.294)

2 replies

mdkeil Sep 20, 2024

poste mal deine config bitte.

diver77 Sep 21, 2024
Author

hallo hier mal meine config. nicht wundern, da ist viel drin was man nicht mehr braucht, aber ich tue mir immer schwer etwas zu löschen, da ich doch nicht ganz so fit bin in programieren daher versehe ich alles immer mit einem #.

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

interval: 10s # 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: XXXX
# 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: 192.XXX.187: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: solaredge-hybrid
    usage: grid     
    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.XXX.187 # Hostname
    port: 1502 # Port  
  - name: my_pv
    type: template
    template: solaredge-hybrid
    usage: pv
   # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.XXX.187 # Hostname
    port: 1502 # Port
  - name: my_battery
    type: template
    template: solaredge-hybrid
    usage: battery  
    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.XXX.187 # Hostname
    port: 1502 # 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: Wallbox_mokka
    type: template
    template: go-e-v3
    host: 192.XXX.197 # IP-Adresse oder Hostname 
    
    # Shelly für Wärmepumpe
  - name: waermepumpe_warmwasser
    type: template
    template: shelly 
    host: 192.XXX.189
    channel: 0
    standbypower: -500 #was zieht denn deine Wärmepumpe
    integrateddevice: true 
    icon: waterheater
    
    # Shelly für Poolwärmepumpe
  - name: waermepumpe_pool
    type: template
    template: shelly 
    host: 192.XXX.193
    channel: 0
    standbypower: -2600 #was zieht denn deine Wärmepumpe
    integrateddevice: true 
    icon: waterheater
    

# 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: Mokka
#    type: template
#    template: opel
#    title: Mokka # Wird in der Benutzeroberfläche angezeigt # Optional
#    user: XXX@gmail.com # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
#    password: XXX # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)
#    vin: XXX # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind # Optional
#    capacity: 50 # Akkukapazität in kWh # Optional 
#    targetsoc: 100 # ausgeschalten lassen

  - name: Mokka
    type: template
    template: flobz
    title: Mokka neu # Wird in der Benutzeroberflaeche angezeigt (Optional)
    url: http://192.XXX.160:5000
    vin: XXX # Erforderlich
    capacity: 50 # Akkukapazität in kWh (Optional)
    
#  - type: template
#    template: offline
#    title: Warmwasser
#    name: Warmwasser  
#    icon: waterheater
    
#  - type: template
#    template: offline
#    title: Waermepumpe Pool
#    name: Waermepumpe Pool  
#    icon: waterheater
   

# site describes the EVU connection, PV and home battery
site:
  title: XXX # 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 # auxiliary meters for adjusting grid operating point
#  prioritySoc: 80 # give home battery priority up to this soc (empty to disable)
#  bufferSoc: 90 # ignore home battery discharge above soc (empty to disable)
  residualPower: 100

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Wallbox Mokka # display name for UI
    charger: Wallbox_mokka # charger
    # meter: charge # charge meter
    mode: pv #now = schnell, PV = PV, pvmin = pvmin, Off = aus
    vehicle: Mokka # set default vehicle (disables vehicle detection) Referenz auf Standardfahrzeug
#    resetOnDisconnect: true # set defaults when vehicle disconnects
    phases: 0 # 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: 16 # maximum charge current (default 16A)

    # remaining settings are experts-only and best left at default values
    priority: 10 # 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)
    
  - title: Wärmepumpe Warmwasser
    charger: waermepumpe_warmwasser
    mode: pv
#    vehicle: Warmwasser
    phases: 1
    minCurrent: 2 # schaltet ein wenn 2.65 x 230V = 609W
    maxCurrent: 3 # maximum charge current (default 16A)
#    resetOnDisconnect: true
    enable:
      threshold: -600		#Einschalten wenn Einspeisung über 600W steigt
      delay: 20s			##Schaltet wenn Schwellwert 20s überschritten ist
    disable:
      threshold: -400		#Ausschalten wenn Einspeisung unter 400W sinkt
      delay: 1m			#Schaltet wenn Schwellwert 10s unterschritten ist
    guardduration: 15m		#Zeitabstand zwischen zwei Schaltvorgängen
    priority: 8 # Prio bei PV-überschusss, höhere Zahl ist höhere Prio
    
  - title: Wärmepumpe Poolpumpe
    charger: waermepumpe_pool
    mode: pv
    phases: 1
    minCurrent: 11 # schaltet ein wenn 11,3 x 230V = 2600W
    maxCurrent: 12 # maximum charge current (default 16A)
#   resetOnDisconnect: true nicht mehr auskomentieren
    enable:
      threshold: -2600 #Einschalten wenn Einspeisung über 2600W steigt
      delay: 20s #Schaltet wenn Schwellwert 10s überschritten ist
    disable:
      threshold: -1000 #Ausschalten wenn Einspeisung unter 1000W sinkt
      delay: 1m #Schaltet wenn Schwellwert 10s unterschritten ist
    guardduration: 15m #Zeitabstand zwischen zwei Schaltvorgängen
    priority: 9 # Prio bei PV-überschusss, höhere Zahl ist höhere Prio


# 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 # (default EUR)
  grid:
    # static grid price
    type: fixed
    price: 0.294 # [currency]/kWh

  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.07 # [currency]/kWh
#  planner:
#    type: grünstromindex
#    zip: XXX # PLZ mit führender Null mit in "" setzen
    # planner tariff can be used for target charging if not grid tariff is specified
    # GrünStromIndex (Germany only) or ElectricityMaps provide CO2 intensity forecast

    # type: grünstromindex
    # zip: <zip>

    # type: electricitymaps
    # 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>

VolkerK62 · 2024-09-20T17:28:46Z

VolkerK62
Sep 20, 2024

Das kennst du? #16118

17 replies

docsnyder7 Sep 23, 2024

https://github.com/hurzhurz/psa-token-helper/releases/tag/v0.0.0.0.1.1

diver77 Sep 23, 2024
Author

oh super danke für Eure Hilfe ich habe es hinbekommen.
Jetzt muss nur noch das Auto heute abend angeschlossen werden, damit ich prüfen kann ob wieder alles läuft wie es soll.
Danke danke danke nochmal für Eure Geduld und Hilfe. Ihr macht echt einen Mega Job.
Sonnige Grüße aus dem Allgäu
Diver

docsnyder7 Sep 23, 2024

eigentlich dürfte der Ladezustand des opel schon angezeigt werden, zumindest wenn du die Abfrage in der yaml auf always stehen hast

diver77 Sep 23, 2024
Author

ok jetzt habe ich das Auto angeschlossen aber leider bekomme ich wieder eine fehlermeldung
05:30:00 +0200 CEST (power: 11040W, avg cost: 0.294)
[site ] DEBUG 2024/09/23 17:54:17 ----
[lp-1 ] DEBUG 2024/09/23 17:54:17 charge power: 0W
[lp-1 ] DEBUG 2024/09/23 17:54:17 charge currents: [0 0 0]A
[lp-2 ] DEBUG 2024/09/23 17:54:17 charge power: 0W
[site ] DEBUG 2024/09/23 17:54:17 pv power: 0W
[site ] DEBUG 2024/09/23 17:54:18 battery soc: 34%
[site ] DEBUG 2024/09/23 17:54:18 battery power: 2864W
[site ] DEBUG 2024/09/23 17:54:18 grid meter: -15W
[site ] DEBUG 2024/09/23 17:54:18 grid powers: [266 -606 323]W
[site ] DEBUG 2024/09/23 17:54:18 grid currents: [3 -3.1 2.2]A
[site ] DEBUG 2024/09/23 17:54:18 site power: 2949W
[lp-2 ] DEBUG 2024/09/23 17:54:18 charge total import: 0.000kWh
[lp-2 ] DEBUG 2024/09/23 17:54:18 charger status: B
[lp-2 ] DEBUG 2024/09/23 17:54:18 pv charge current: 0A = 0A + -12.8A (2949W @ 1p)
[lp-2 ] DEBUG 2024/09/23 17:54:26 charge total import: 0.000kWh
Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2024/09/23 17:54:28 evcc 0.130.11
[main ] INFO 2024/09/23 17:54:28 using config file: /config/evcc.yaml
[main ] INFO 2024/09/23 17:54:30 listening at :7070
[main ] ERROR 2024/09/23 17:54:48 creating vehicle my_car failed: cannot create vehicle type 'template': cannot create vehicle type 'opel': token expired
[main ] FATAL 2024/09/23 17:54:48 failed configuring loadpoints: failed configuring loadpoint: not found: Mokka
[main ] FATAL 2024/09/23 17:54:48 will attempt restart in: 15m0s
[main ] INFO 2024/09/23 17:54:49 new version available: 0.130.12
Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2024/09/23 17:57:31 evcc 0.130.11
[main ] INFO 2024/09/23 17:57:31 using config file: /config/evcc.yaml
[main ] INFO 2024/09/23 17:57:31 listening at :7070

die Yaml sieht jetzt so aus.

vehicles:
#  - name: Mokka
#    type: template
#    template: opel
#    title: Mokka # Wird in der Benutzeroberfläche angezeigt # Optional
#    user: XXX@gmail.com # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
#    password: XXX # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)
#    vin: VXXX9 # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind # Optional
#    capacity: 50 # Akkukapazität in kWh # Optional 
#    targetsoc: 100 # ausgeschalten lassen

  - name: my_car
    type: template
    template: opel
    title: Mokka neuer token # Wird in der Benutzeroberfläche angezeigt (optional)
    user: XXX@gmail.com # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    accessToken: 3XXXeb
    refreshToken: 4XXXb
    vin: VXXX9 # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind (optional)
    capacity: 50 # Akkukapazität in kWh (optional)

Habe ich da noch was falsch gemacht oder an was liegt es denn jetzt schon wieder?

diver77 Sep 23, 2024
Author

ah glaube ich habe den Fehler doch selber gefunden. .-)
Habe vergessen den Namen auf Mokka zu ändern.

diver77 · 2024-09-25T14:09:56Z

diver77
Sep 25, 2024
Author

ok, also der Ladezustand wurde gestern angezeigt. jetzt habe ich aber folgendes Protokoll und evcc startet nicht mehr.

[site ] DEBUG 2024/09/25 15:49:55 pv power: 1988W
[site ] DEBUG 2024/09/25 15:49:55 battery soc: 91%
[site ] DEBUG 2024/09/25 15:49:55 battery power: -496W
[site ] DEBUG 2024/09/25 15:49:55 grid meter: -3W
[site ] DEBUG 2024/09/25 15:49:56 grid powers: [669 -266 -406]W
[site ] DEBUG 2024/09/25 15:49:56 grid currents: [3.8 -1.7 -1.8]A
[site ] DEBUG 2024/09/25 15:49:56 giving loadpoint priority for additional: 500W
[site ] DEBUG 2024/09/25 15:49:56 site power: -899W
[site ] DEBUG 2024/09/25 15:49:56 ----
[lp-1 ] DEBUG 2024/09/25 15:49:56 charge power: 0W
[lp-1 ] DEBUG 2024/09/25 15:49:56 charge currents: [0 0 0]A
[lp-2 ] DEBUG 2024/09/25 15:49:57 charge power: 500W
[site ] DEBUG 2024/09/25 15:49:57 pv power: 1988W
[site ] DEBUG 2024/09/25 15:49:58 battery soc: 91%
[site ] DEBUG 2024/09/25 15:49:58 battery power: -496W
[site ] DEBUG 2024/09/25 15:49:59 grid meter: 2W
[site ] DEBUG 2024/09/25 15:50:01 grid powers: [673 -255 -404]W
[site ] DEBUG 2024/09/25 15:50:04 grid currents: [3.8 -1.4 -1.8]A
[site ] DEBUG 2024/09/25 15:50:04 giving loadpoint priority for additional: 500W
[site ] DEBUG 2024/09/25 15:50:04 site power: -894W
[lp-1 ] DEBUG 2024/09/25 15:50:05 charge total import: 6316.249kWh
[lp-1 ] DEBUG 2024/09/25 15:50:05 charger status: A
[site ] DEBUG 2024/09/25 15:50:06 ----
[lp-1 ] DEBUG 2024/09/25 15:50:06 charge power: 0W
[lp-1 ] DEBUG 2024/09/25 15:50:06 charge currents: [0 0 0]A
[lp-2 ] DEBUG 2024/09/25 15:50:09 charge power: 500W
[site ] DEBUG 2024/09/25 15:50:10 pv power: 2012W
[site ] DEBUG 2024/09/25 15:50:11 battery soc: 91%
[site ] DEBUG 2024/09/25 15:50:11 battery power: -172W
[site ] DEBUG 2024/09/25 15:50:12 grid meter: -317W
[site ] DEBUG 2024/09/25 15:50:13 grid powers: [568 -369 -512]W
[site ] DEBUG 2024/09/25 15:50:13 grid currents: [3.7 -1.3 -2.2]A
[site ] DEBUG 2024/09/25 15:50:13 site power: -389W
[lp-2 ] DEBUG 2024/09/25 15:50:14 charge total import: 0.000kWh
[lp-2 ] DEBUG 2024/09/25 15:50:14 charger status: C
[lp-2 ] DEBUG 2024/09/25 15:50:14 pv charge current: 4.69A = 3A + 1.69A (-389W @ 1p)
[site ] DEBUG 2024/09/25 15:50:16 ----
[lp-1 ] DEBUG 2024/09/25 15:50:16 charge power: 0W
[lp-1 ] DEBUG 2024/09/25 15:50:16 charge currents: [0 0 0]A
[lp-2 ] ERROR 2024/09/25 15:50:21 charge power: Get "http://192.168.188.189/relay/0": dial tcp 192.168.188.189:80: i/o timeout
[site ] DEBUG 2024/09/25 15:50:38 pv power: 1987W
[site ] DEBUG 2024/09/25 15:50:45 battery soc: 91%
[site ] DEBUG 2024/09/25 15:50:45 battery power: -119W
[site ] ERROR 2024/09/25 15:50:55 grid meter: model 203 block 0 point W: read tcp 192.168.188.160:49916->192.168.188.187:1502: i/o timeout
[site ] DEBUG 2024/09/25 15:50:55 ----
[lp-1 ] DEBUG 2024/09/25 15:51:03 charge power: 0W
[lp-1 ] DEBUG 2024/09/25 15:51:03 charge currents: [0 0 0]A
[lp-2 ] ERROR 2024/09/25 15:51:08 charge power: Get "http://192.168.188.189/relay/0": dial tcp 192.168.188.189:80: i/o timeout
[site ] ERROR 2024/09/25 15:51:19 pv 1 power: add[0]: model 103 block 0 point DCW: dial tcp 192.168.188.187:1502: i/o timeout
[site ] DEBUG 2024/09/25 15:51:19 pv power: 0W
[site ] ERROR 2024/09/25 15:51:35 battery 1 power: read failed: read tcp 192.168.188.160:49136->192.168.188.187:1502: i/o timeout
[site ] DEBUG 2024/09/25 15:51:35 ----
[lp-1 ] ERROR 2024/09/25 15:51:40 charge power: Get "http://192.168.188.197/api/status?filter=alw,car,eto,nrg,wh,trx,cards": dial tcp 192.168.188.197:80: i/o timeout
[lp-1 ] ERROR 2024/09/25 15:51:45 charge currents: Get "http://192.168.188.197/api/status?filter=alw,car,eto,nrg,wh,trx,cards": dial tcp 192.168.188.197:80: i/o timeout
[lp-2 ] ERROR 2024/09/25 15:51:50 charge power: Get "http://192.168.188.189/relay/0": dial tcp 192.168.188.189:80: i/o timeout
[site ] ERROR 2024/09/25 15:52:00 pv 1 power: add[0]: model 103 block 0 point DCW: dial tcp 192.168.188.187:1502: i/o timeout
[site ] DEBUG 2024/09/25 15:52:00 pv power: 0W
[site ] ERROR 2024/09/25 15:52:10 battery 1 power: read failed: dial tcp 192.168.188.187:1502: i/o timeout
[site ] DEBUG 2024/09/25 15:52:10 ----
[lp-1 ] ERROR 2024/09/25 15:52:15 charge power: Get "http://192.168.188.197/api/status?filter=alw,car,eto,nrg,wh,trx,cards": dial tcp 192.168.188.197:80: i/o timeout
[lp-1 ] ERROR 2024/09/25 15:52:20 charge currents: Get "http://192.168.188.197/api/status?filter=alw,car,eto,nrg,wh,trx,cards": dial tcp 192.168.188.197:80: i/o timeout
[lp-2 ] ERROR 2024/09/25 15:52:25 charge power: Get "http://192.168.188.189/relay/0": dial tcp 192.168.188.189:80: i/o timeout
[site ] DEBUG 2024/09/25 15:52:42 pv power: 1909W
[site ] DEBUG 2024/09/25 15:52:51 battery soc: 92%
[site ] DEBUG 2024/09/25 15:52:51 battery power: -388W
[site ] DEBUG 2024/09/25 15:52:56 grid meter: -6W
[site ] DEBUG 2024/09/25 15:53:14 grid powers: [698 -280 -412]W
[site ] ERROR 2024/09/25 15:53:24 grid currents: model 203 block 0 point AphA: read tcp 192.168.188.160:56456->192.168.188.187:1502: i/o timeout
[lp-2 ] ERROR 2024/09/25 15:53:31 charge total import: Get "http://192.168.188.189/status": dial tcp 192.168.188.189:80: i/o timeout
Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2024/09/25 15:53:32 evcc 0.130.11
[main ] INFO 2024/09/25 15:53:32 using config file: /config/evcc.yaml
[main ] INFO 2024/09/25 15:53:33 listening at :7070
[main ] FATAL 2024/09/25 15:54:55 cannot create meter 'my_grid': cannot create meter type 'template': cannot create meter type 'custom': power: read tcp 192.168.188.160:49912->192.168.188.187:1502: i/o timeout
[main ] FATAL 2024/09/25 15:54:55 will attempt restart in: 15m0s
[main ] INFO 2024/09/25 15:54:55 new version available: 0.130.12
Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2024/09/25 15:56:35 evcc 0.130.11
[main ] INFO 2024/09/25 15:56:35 using config file: /config/evcc.yaml
[main ] INFO 2024/09/25 15:56:35 listening at :7070
[main ] FATAL 2024/09/25 15:57:12 cannot create meter 'my_grid': cannot create meter type 'template': cannot create meter type 'custom': currents: [1] read tcp 192.168.188.160:43418->192.168.188.187:1502: i/o timeout
[main ] FATAL 2024/09/25 15:57:12 will attempt restart in: 15m0s
[main ] INFO 2024/09/25 15:57:12 new version available: 0.130.12
Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2024/09/25 15:59:37 evcc 0.130.11
[main ] INFO 2024/09/25 15:59:37 using config file: /config/evcc.yaml
[main ] INFO 2024/09/25 15:59:38 listening at :7070
[main ] FATAL 2024/09/25 15:59:58 cannot create meter 'my_grid': cannot create meter type 'template': cannot create meter type 'custom': power: dial tcp 192.168.188.187:1502: i/o timeout
[main ] FATAL 2024/09/25 15:59:58 will attempt restart in: 15m0s
[main ] INFO 2024/09/25 15:59:58 new version available: 0.130.12
Using config file: /config/evcc.yaml
starting evcc: 'EVCC_DATABASE_DSN=/data/evcc.db evcc --config /config/evcc.yaml'
[main ] INFO 2024/09/25 16:02:40 evcc 0.130.11
[main ] INFO 2024/09/25 16:02:40 using config file: /config/evcc.yaml
[main ] INFO 2024/09/25 16:02:40 listening at :7070
[main ] FATAL 2024/09/25 16:03:14 cannot create meter 'my_grid': cannot create meter type 'template': cannot create meter type 'custom': power: sunspec: subdevice 1 not found
[main ] FATAL 2024/09/25 16:03:14 will attempt restart in: 15m0s
[main ] INFO 2024/09/25 16:03:14 new version available: 0.130.12

an was kann das denn liegen? Habe nachgeschaut aber der Port 80 ist aktiv. Das einzigste was ich gemacht habe, ist das ich von Duckdns auf cloudfair gewechselt bin um von aussen auf meinen Homeassistant zu kommen.

Danke wie immer für Eure hilfe
Gruß Diver

1 reply

VolkerK62 Sep 25, 2024

wenn du das um ca. 15:50 Uhr gemacht hast, dann kennst du den Grund für die Fehler.

diver77 · 2024-09-27T13:12:41Z

diver77
Sep 27, 2024
Author

ok, nachdem ich alles wieder zurück geändert habe, geht evcc wieder, dass einzigste was aber immer noch nicht angezeigt ist der Ladezustand. Jetzt wird wir nur noch angezeigt, wieviel geladen wurde.

in der yaml habe ich den neuen Token und alten Token eingetragen.

vehicles:
  - name: Mokka
    type: template
    template: opel
    title: Mokka # Wird in der Benutzeroberfläche angezeigt (optional)
    user: mXXXe@gmail.com # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    accessToken: 3XXXb
    refreshToken: 4XXXb
    vin: VXXX9 # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind (optional)
    capacity: 50 # Akkukapazität in kWh (optional)

irgendwie habe ich das Gefühl, ich bin langsam zu dumm für das Programm. :-(
Alles hat so gut funtkioniert, bis PSA seine Api geändert hat.

Danke für Eure Hilfe und schönes Wochenende
Gruß Diver

0 replies

diver77 · 2024-10-01T10:17:54Z

diver77
Oct 1, 2024
Author

Also ich habe jetzt mal meine Yaml bereinigt und nur das drinnen gelassen, wo ich dachte das wird benötigt. Habe sogar nochmal einen neuen refresh Token erstellt. aber irgendwie wird mir immer noch kein Ladestand angezeigt. bin wirklich am verzweifeln und bitte nochmal um eure Hilfe. was ich auch nicht verstehe ist das durchgestrichene cloudzeichen neben Mokka. was bedeutet das? Jetzt habe ich auch noch das Problem, dass er nur noch mit 2,9 KW läd und nicht mehr mit 7 KW.
bitte bitte um Hilfe.
hier mal ein auszug aus dem Protokoll
[site ] DEBUG 2024/10/01 12:07:01 ----
[lp-1 ] DEBUG 2024/10/01 12:07:01 charge power: 2900W
[lp-1 ] DEBUG 2024/10/01 12:07:01 charge currents: [4 4 4.1]A
[lp-2 ] DEBUG 2024/10/01 12:07:01 charge power: 0W
[site ] DEBUG 2024/10/01 12:07:01 pv power: 1517W
[site ] DEBUG 2024/10/01 12:07:01 battery soc: 48%
[site ] DEBUG 2024/10/01 12:07:01 battery power: 4916W
[site ] DEBUG 2024/10/01 12:07:01 grid meter: 15W
[site ] DEBUG 2024/10/01 12:07:01 grid powers: [-1085 754 346]W
[site ] DEBUG 2024/10/01 12:07:02 grid currents: [-4.1 3.3 3.5]A
[site ] DEBUG 2024/10/01 12:07:02 site power: 5031W
[lp-2 ] DEBUG 2024/10/01 12:07:02 charge total import: 0.000kWh
[lp-2 ] DEBUG 2024/10/01 12:07:02 charger status: B
[lp-2 ] DEBUG 2024/10/01 12:07:02 pv charge current: 0A = 0A + -21.9A (5031W @ 1p)
[site ] DEBUG 2024/10/01 12:07:11 ----
[lp-1 ] DEBUG 2024/10/01 12:07:11 charge power: 2880W
[lp-1 ] DEBUG 2024/10/01 12:07:11 charge currents: [4 3.9 4.1]A
[lp-2 ] DEBUG 2024/10/01 12:07:11 charge power: 0W
[site ] DEBUG 2024/10/01 12:07:11 pv power: 1583W
[site ] DEBUG 2024/10/01 12:07:11 battery soc: 47%
[site ] DEBUG 2024/10/01 12:07:11 battery power: 3051W
[site ] DEBUG 2024/10/01 12:07:11 grid meter: 10W
[site ] DEBUG 2024/10/01 12:07:14 grid powers: [-501 -432 931]W
[site ] DEBUG 2024/10/01 12:07:14 grid currents: [-2.5 -3 4.7]A
[site ] DEBUG 2024/10/01 12:07:14 site power: 3161W
[site ] DEBUG 2024/10/01 12:07:21 ----
[lp-1 ] DEBUG 2024/10/01 12:07:21 charge power: 2890W
[lp-1 ] DEBUG 2024/10/01 12:07:21 charge currents: [4.1 3.9 4.1]A
[lp-2 ] DEBUG 2024/10/01 12:07:21 charge power: 0W
[site ] DEBUG 2024/10/01 12:07:21 pv power: 1564W
[site ] DEBUG 2024/10/01 12:07:21 battery soc: 47%
[site ] DEBUG 2024/10/01 12:07:21 battery power: 3076W
[site ] DEBUG 2024/10/01 12:07:21 grid meter: -10W
[site ] DEBUG 2024/10/01 12:07:21 grid powers: [-498 -436 923]W
[site ] DEBUG 2024/10/01 12:07:21 grid currents: [-2.3 -2.9 4.9]A
[site ] DEBUG 2024/10/01 12:07:21 site power: 3166W
[lp-1 ] DEBUG 2024/10/01 12:07:21 detected active phases: 3p
[lp-1 ] DEBUG 2024/10/01 12:07:21 charge total import: 6400.772kWh
[lp-1 ] DEBUG 2024/10/01 12:07:21 charger status: C
[lp-1 ] DEBUG 2024/10/01 12:07:21 plan: charge 4h31m13s between 2024-10-02 02:28:47 +0200 CEST until 2024-10-02 07:00:00 +0200 CEST (power: 11040W, avg cost: 0.294)

hier die yaml.

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

interval: 10s # control cycle interval



# sponsor token enables optional features (request at https://sponsor.evcc.io)
sponsortoken: eyJhbGxxxwZ8MOf9csNE

# 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: 192.xxx.xxx.187: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: solaredge-hybrid
    usage: grid     
    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.xxx.xxx.187 # Hostname
    port: 1502 # Port  
  - name: my_pv
    type: template
    template: solaredge-hybrid
    usage: pv
   # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.xxx.xxx.187 # Hostname
    port: 1502 # Port
  - name: my_battery
    type: template
    template: solaredge-hybrid
    usage: battery  
    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.xxx.xxx.187 # Hostname
    port: 1502 # 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: Wallbox_mokka
    type: template
    template: go-e-v3
    host: 192.xxx.xxx.197 # IP-Adresse oder Hostname 
    
    # Shelly für Wärmepumpe
  - name: waermepumpe_warmwasser
    type: template
    template: shelly 
    host: 192.xxx.xxx.189
    channel: 0
    standbypower: -500 #was zieht denn deine Wärmepumpe
    integrateddevice: true 
    icon: waterheater
    
    # Shelly für Poolwärmepumpe
  - name: waermepumpe_pool
    type: template
    template: shelly 
    host: 192.xxx.xxx.193
    channel: 0
    standbypower: -2600 #was zieht denn deine Wärmepumpe
    integrateddevice: true 
    icon: waterheater
    

# 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: Mokka
    type: template
    template: opel
    title: Mokka # Wird in der Benutzeroberfläche angezeigt (optional)
    user: xxx@gmail.com # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    accessToken: f6xxxfe
    refreshToken: e1xxx3cc
 #   vin: Vxxx79 # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind (optional)
    capacity: 50 # Akkukapazität in kWh (optional)
      

# site describes the EVU connection, PV and home battery
site:
  title: xxx # 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
 #  prioritySoc: 80 # give home battery priority up to this soc (empty to disable)
#  bufferSoc: 90 # ignore home battery discharge above soc (empty to disable)
  residualPower: 100

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Wallbox Mokka # display name for UI
    charger: Wallbox_mokka # charger
    mode: pv #now = schnell, PV = PV, pvmin = pvmin, Off = aus
    vehicle: Mokka # set default vehicle (disables vehicle detection) Referenz auf Standardfahrzeug
    phases: 0 # 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: 16 # maximum charge current (default 16A)

    # remaining settings are experts-only and best left at default values
    priority: 10 # 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)
    
  - title: Wärmepumpe Warmwasser
    charger: waermepumpe_warmwasser
    mode: pv
    phases: 1
    minCurrent: 2 # schaltet ein wenn 2.65 x 230V = 609W
    maxCurrent: 3 # maximum charge current (default 16A)

    enable:
      threshold: -600		#Einschalten wenn Einspeisung über 600W steigt
      delay: 20s			##Schaltet wenn Schwellwert 20s überschritten ist
    disable:
      threshold: -400		#Ausschalten wenn Einspeisung unter 400W sinkt
      delay: 1m			#Schaltet wenn Schwellwert 10s unterschritten ist
    guardduration: 15m		#Zeitabstand zwischen zwei Schaltvorgängen
    priority: 8 # Prio bei PV-überschusss, höhere Zahl ist höhere Prio
    
  - title: Wärmepumpe Poolpumpe
    charger: waermepumpe_pool
    mode: pv
    phases: 1
    minCurrent: 11 # schaltet ein wenn 11,3 x 230V = 2600W
    maxCurrent: 12 # maximum charge current (default 16A)

    enable:
      threshold: -2600 #Einschalten wenn Einspeisung über 2600W steigt
      delay: 20s #Schaltet wenn Schwellwert 10s überschritten ist
    disable:
      threshold: -1000 #Ausschalten wenn Einspeisung unter 1000W sinkt
      delay: 1m #Schaltet wenn Schwellwert 10s unterschritten ist
    guardduration: 15m #Zeitabstand zwischen zwei Schaltvorgängen
    priority: 9 # Prio bei PV-überschusss, höhere Zahl ist höhere Prio


# 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 # (default EUR)
  grid:
    # static grid price
    type: fixed
    price: 0.294 # [currency]/kWh

  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.07 # [currency]/kWh

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

0 replies

RTTTC · 2024-10-01T10:36:22Z

RTTTC
Oct 1, 2024

Do you use the latest version of evcc ?
Have you tried to create the vehicle in UI instead of yaml ?

2 replies

diver77 Oct 1, 2024
Author

ok i tried it to use the UI.
in the yaml l delete the vehicle and the Loadpoint for the Mokka?
but now i just see my two heatpump and the car just in the experimentel layout.

if i use the UI for my Mokka i see the Ladezustand. :-) juhuu
can i use a hybrit mode or do i have to delete my yaml completly? if i can use the hybrit how do i see my car in the overview?

RTTTC Oct 1, 2024

in the yaml l delete the vehicle and the Loadpoint for the Mokka?

Only vehicle had to be removed.
Loadpoint must remain in yaml for the time being.
(without this line: vehicle: Mokka # set default vehicle (disables vehicle detection) Referenz auf Standardfahrzeug)

diver77 · 2024-10-01T11:45:16Z

diver77
Oct 1, 2024
Author

juhuu i got it.

thanks for your help and hopfully it works for a long time now :-)

0 replies

diver77 · 2024-10-10T08:51:45Z

diver77
Oct 10, 2024
Author

Hallo zusammen,
leider hat die Freude nicht all zu lange gehalten.
Der neue Token hält immer nur 2 Tage, danach wird wieder nichts angezeigt und der Mokka wird jetzt nur noch als Gastfahrzeug erkannt.
Wenn ich dann in die Konfiguration in evcc gehe und das Fahrzeug prüfe, bekomme ich die Fehlermeldung das der Token abgelaufen ist. Erzeuge ich einen neuen Token, und speichere den in evcc, dann ist wieder alles gut für 2 Tage. An was kann das liegen?
Habe das Auto komplett aus der yaml gelöscht und nur noch über die Konfiguration der UI angelegt.
Wenn der Mokka dann nach zwei Tagen wieder angeschlossen wird sieht es so aus.

was mir noch auffällt, ist wenn ich dann auf den Mokka umstelle, wird wieder kein Ladezustand angezeigt und neben der Schrift Mokka ist eine durchgestrichene Wolke zu sehen.

Danke für Eure Hilfe

leider regnerische Grüße aus dem Allgäu

Diver

3 replies

docsnyder7 Oct 10, 2024

Hast du den Mokka Neu in der yaml als vehicle unter dem loadpoint eingertragen... da müsste dann nicht mokka neu rein, sondern db:1 oder 2 je nachdem welches es in der db ist.. dann ist zumindest der mokka automatisch dem loadpoint zugeordnet.

meine yaml schaut dann so aus

loadpoints:
- title: Garage
  charger: my_elvi
  phases: 3
  mincurrent: 6
  maxcurrent: 16
  vehicle: db:8
  soc:
    poll:
      mode: always
      interval: 60m
    estimate: true
  enable:
    delay: 2m
    threshold: -200
  disable: 
     delay: 3m
     threshold: 500 
  guardduration: 5m

und den poll mode hab ich auf always, statt auf connected oder charging

diver77 Oct 10, 2024
Author

nein habe in der yaml kein vehicle mehr unter loadpoint. da RTTTC mir sagt das da nichts rein soll.

Loadpoint must remain in yaml for the time being.
(without this line: vehicle: Mokka # set default vehicle (disables vehicle detection) Referenz auf Standardfahrzeug)

wenn da doch der Datenbankeintrag rein muss, wie finde ich raus, welcher datenbankeintrag der Mokka ist?

docsnyder7 Oct 10, 2024

kann man wol über die db herausfinden.. ich lese die Daten in iobroker via mqtt ein und dann kommt der passende Datenpunkt mit db:xx an

unser Mokka läuft damit sehr gut.. soc auch wenn nicht am Ladekabel hängt

RTTTC · 2024-10-10T09:57:47Z

RTTTC
Oct 10, 2024

Tokens usually expire instantly (for safety reasons) if another instance of evcc or some other app/program/system tries to use the same tokens.
Make sure this is not the case.

1 reply

diver77 Oct 10, 2024
Author

ok, i also habe the PSA Car Controller-addon in use. so that could be the problem that my token expire. i stop the addon and try it again.
thanks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Ladezustand Mokka wird nicht mehr angezeigt #16229

{{title}}

Replies: 9 comments 26 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Ladezustand Mokka wird nicht mehr angezeigt #16229

Replies: 9 comments · 26 replies

diver77 Sep 20, 2024 Author

diver77 Sep 21, 2024 Author

diver77 Sep 23, 2024 Author

diver77 Sep 23, 2024 Author

diver77 Sep 23, 2024 Author

diver77 Sep 25, 2024 Author

diver77 Sep 27, 2024 Author

diver77 Oct 1, 2024 Author

diver77 Oct 1, 2024 Author

diver77 Oct 1, 2024 Author

diver77 Oct 10, 2024 Author

diver77 Oct 10, 2024 Author

diver77 Oct 10, 2024 Author

Replies: 9 comments 26 replies

diver77
Sep 20, 2024
Author

diver77 Sep 21, 2024
Author

diver77 Sep 23, 2024
Author

diver77 Sep 23, 2024
Author

diver77 Sep 23, 2024
Author

diver77
Sep 25, 2024
Author

diver77
Sep 27, 2024
Author

diver77
Oct 1, 2024
Author

diver77 Oct 1, 2024
Author

diver77
Oct 1, 2024
Author

diver77
Oct 10, 2024
Author

diver77 Oct 10, 2024
Author

diver77 Oct 10, 2024
Author