search

evcc-io / evcc

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

Fahrzeug Lädt direkt mit voller Leistung Porsche Taycan + Porsche Charger Connect #12895

Closed hegi2k closed 5 months ago

hegi2k commented 5 months ago

Describe the bug

Laden startet direkt mit voller leistung beim Einstecken obwohl Anzeige auf Solar steht. Selbst auf Off zu stellen stoppt den Ladevorgang nicht. Muss das Fahrzeug wieder ausstecken Einen tag vorher hat alles normal funktioniert. Soc vom Fahrzeug 40 Prozent

Steps to reproduce

1. 2. 3. ... Fahrzeug anstecken

Configuration details

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

log: debug
levels:
  cache: error

# unique installation id
plant: 4087cd7ef3b1a821efefe3b57dc14909bba3021dd7f11f669f96e9524633d54e

interval: 30s # control cycle interval

meters:
- type: template
  template: sma-home-manager
  usage: grid
  host: 192.168.188.43
  name: grid1
- type: template
  template: sma-inverter-speedwire
  usage: pv
  host: 192.168.188.44
  password: 
  name: pv2

chargers:
- type: template
  template: pmcc
  ski: 4a4c-0fa0-288c-fe99-e7c6-1b4a-0e92-47b5-e304-d34d
  ip: 192.168.188.92
  name: wallbox3

loadpoints:
- title: Garage9
  charger: wallbox3
  mode: pv

site:
  title: Home
  meters:
    grid: grid1
    pv:
    - pv2

eebus:
  certificate:
      private: |
          -----BEGIN EC PRIVATE KEY-----
          MHcCAQEEIFxO4LBig6/rjCNwj6arKRGUsu3a1a8pY4PcgWuv6eHIoAoGCCqGSM49
          AwEHoUQDQgAE5IbTuB4ZGjN6GxI5CMbpiU5yVXH1lzcbZbxGk1j3KPu17NmuG/E7
          t7KV0r91QATfUt2DxoSn5L1/KfFk5NzYLQ==
          -----END EC PRIVATE KEY-----
      public: |
          -----BEGIN CERTIFICATE-----
          MIIBvDCCAWOgAwIBAgIRAmmOOIkOf/JH175WryaTbLcwCgYIKoZIzj0EAwIwPjEL
          MAkGA1UEBhMCREUxDTALBgNVBAoTBEVWQ0MxCTAHBgNVBAsTADEVMBMGA1UEAwwM

Log details

pi@raspberrypi:~ $ evcc --log debug
[main  ] INFO 2024/03/13 08:02:13 evcc 0.124.7
[main  ] INFO 2024/03/13 08:02:13 using config file: /etc/evcc.yaml
[main  ] INFO 2024/03/13 08:02:13 starting ui and api at :7070
[db    ] INFO 2024/03/13 08:02:14 using sqlite database: /home/pi/.evcc/evcc.db
[eebus ] INFO 2024/03/13 08:02:14 Local SKI:  e6732d47ed63b59be77cc8f7b1764a5c52                                                                                   8d4dff
[eebus ] DEBUG 2024/03/13 08:02:14 mdns: announce
[eebus ] DEBUG 2024/03/13 08:02:14 mdns: using avahi
[eebus ] DEBUG 2024/03/13 08:02:14 starting websocket server on :4712
[eebus ] DEBUG 2024/03/13 08:02:15 incoming connection request from 4a4c0fa0288c                                                                                   fe99e7c61b4a0e9247b5e304d34d
[eebus ] DEBUG 2024/03/13 08:02:15 ski 4a4c0fa0288cfe99e7c61b4a0e9247b5e304d34d                                                                                    is not paired, closing the connection
[eebus ] DEBUG 2024/03/13 08:02:16 mdns: start search
[eebus ] DEBUG 2024/03/13 08:02:16 ski: 4a4c0fa0288cfe99e7c61b4a0e9247b5e304d34d name: Porsche-EVSE-00126095 brand: Porsche model: EVSE typ: EVSE identifier: Porsche-EVSE-00126095 register: false host: ICCPD-0126095.local port: 4711 addresses: [192.168.188.92]
[eebus ] DEBUG 2024/03/13 08:02:16 delaying connection to 4a4c0fa0288cfe99e7c61b4a0e9247b5e304d34d by 284ms to minimize double connection probability
[eebus ] DEBUG 2024/03/13 08:02:16 trying to connect to 4a4c0fa0288cfe99e7c61b4a0e9247b5e304d34d at 192.168.188.92
[eebus ] DEBUG 2024/03/13 08:02:16 initiating connection to 4a4c0fa0288cfe99e7c61b4a0e9247b5e304d34d at 192.168.188.92:4711
[site  ] INFO 2024/03/13 08:02:17 site config:
[site  ] INFO 2024/03/13 08:02:17   meters:      grid ✓ pv ✓ battery ✗
[site  ] INFO 2024/03/13 08:02:17     grid:      power ✓ energy ✓ currents ✓
[site  ] INFO 2024/03/13 08:02:17     pv 1:      power ✓ energy ✓ currents ✓
[lp-1  ] INFO 2024/03/13 08:02:17 loadpoint 1:
[lp-1  ] INFO 2024/03/13 08:02:17   mode:        pv
[lp-1  ] INFO 2024/03/13 08:02:17   charger:     power ✓ energy ✗ currents ✓ phases ✗ wakeup ✗
[lp-1  ] INFO 2024/03/13 08:02:17   meters:      charge ✓
[lp-1  ] INFO 2024/03/13 08:02:17     charge:    power ✓ energy ✗ currents ✓
[lp-1  ] DEBUG 2024/03/13 08:02:17 phase timer inactive
[lp-1  ] DEBUG 2024/03/13 08:02:17 pv timer inactive
[site  ] DEBUG 2024/03/13 08:02:17 ----
[lp-1  ] DEBUG 2024/03/13 08:02:17 charge power: 0W
[site  ] DEBUG 2024/03/13 08:02:17 pv power: 384W
[site  ] DEBUG 2024/03/13 08:02:17 grid meter: -58W
[site  ] DEBUG 2024/03/13 08:02:17 grid powers: [-81 25 -2]W
[site  ] DEBUG 2024/03/13 08:02:17 grid currents: [-0.697 1.14 -0.469]A
[site  ] DEBUG 2024/03/13 08:02:17 site power: -58W
[lp-1  ] DEBUG 2024/03/13 08:02:17 charge currents: [0 0 0]A
[lp-1  ] DEBUG 2024/03/13 08:02:17 charger status: A
[lp-1  ] INFO 2024/03/13 08:02:17 car disconnected
[lp-1  ] DEBUG 2024/03/13 08:02:17 set session soc limit: 0
[lp-1  ] DEBUG 2024/03/13 08:02:17 set session energy limit: 0
[eebus ] DEBUG 2024/03/13 08:02:17 Send:  read 1 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to NodeManagement read 1614020 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 reply 2 1614020 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to NodeManagement reply 1614025 1 NodeManagementDetailedDiscoveryData
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 read 4 DeviceClassificationManufacturerData
[eebus ] DEBUG 2024/03/13 08:02:17 Send:  call 3 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 read 5 DeviceDiagnosisStateData
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 read 6 NodeManagementUseCaseData
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to NodeManagement read 1614030 NodeManagementDestinationListData
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 reply 7 1614030 NodeManagementDestinationListData
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 result 8 1614030 ResultData 0
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to NodeManagement read 1614032 NodeManagementUseCaseData
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 reply 9 1614032 NodeManagementUseCaseData
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 result 10 1614032 ResultData 0
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to DeviceClassification reply 1614039 4 DeviceClassificationManufacturerData
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to NodeManagement call 1614034 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 result 11 1614034 ResultData 0
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to NodeManagement result 1614044 3 ResultData 0
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to DeviceDiagnosis reply 1614051 5 DeviceDiagnosisStateData
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to DeviceClassification read 1614049 DeviceClassificationManufacturerData
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 reply 12 1614049 DeviceClassificationManufacturerData
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 result 13 1614049 ResultData 0
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to NodeManagement reply 1614056 6 NodeManagementUseCaseData
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to DeviceClassification read 1614061 DeviceClassificationManufacturerData
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 result 14 1614061 ResultData 7
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to DeviceDiagnosis read 1614066 DeviceDiagnosisStateData
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 reply 15 1614066 DeviceDiagnosisStateData
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 result 16 1614066 ResultData 0
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to NodeManagement call 1614071 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 result 17 1614071 ResultData 0
[main  ] INFO 2024/03/13 08:02:17 new version available: 0.124.9
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to DeviceDiagnosis read 1614080 DeviceDiagnosisStateData
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 result 18 1614080 ResultData 7
[eebus ] DEBUG 2024/03/13 08:02:17 Recv: d:_i:19667_PorscheEVSE-00126095: to NodeManagement call 1614086 NodeManagementSubscriptionRequestCall
[eebus ] DEBUG 2024/03/13 08:02:17 Send: d:_i:19667_PorscheEVSE-00126095 result 19 1614086 ResultData 1
[eebus ] DEBUG 2024/03/13 08:02:18 Send: d:_i:19667_PorscheEVSE-00126095 notify 20 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:19 Send: d:_i:19667_PorscheEVSE-00126095 notify 21 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:19 Send: d:_i:19667_PorscheEVSE-00126095 notify 22 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:20 Send: d:_i:19667_PorscheEVSE-00126095 notify 23 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:21 Send: d:_i:19667_PorscheEVSE-00126095 notify 24 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:22 Send: d:_i:19667_PorscheEVSE-00126095 notify 25 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:23 Send: d:_i:19667_PorscheEVSE-00126095 notify 26 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:23 avahi - error resolving service: Timeout reached
[eebus ] DEBUG 2024/03/13 08:02:23 Send: d:_i:19667_PorscheEVSE-00126095 notify 27 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:24 Send: d:_i:19667_PorscheEVSE-00126095 notify 28 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:25 Send: d:_i:19667_PorscheEVSE-00126095 notify 29 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:26 Send: d:_i:19667_PorscheEVSE-00126095 notify 30 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:27 Send: d:_i:19667_PorscheEVSE-00126095 notify 31 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:27 Send: d:_i:19667_PorscheEVSE-00126095 notify 32 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:28 avahi - error resolving service: Timeout reached
[eebus ] DEBUG 2024/03/13 08:02:28 Send: d:_i:19667_PorscheEVSE-00126095 notify 33 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:29 Send: d:_i:19667_PorscheEVSE-00126095 notify 34 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:30 Send: d:_i:19667_PorscheEVSE-00126095 notify 35 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:31 Send: d:_i:19667_PorscheEVSE-00126095 notify 36 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:31 Send: d:_i:19667_PorscheEVSE-00126095 notify 37 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:32 Send: d:_i:19667_PorscheEVSE-00126095 notify 38 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:33 Send: d:_i:19667_PorscheEVSE-00126095 notify 39 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:34 Send: d:_i:19667_PorscheEVSE-00126095 notify 40 DeviceDiagnosisHeartbeatData
[eebus ] DEBUG 2024/03/13 08:02:35 Send: d:_i:19667_PorscheEVSE-00126095 notify 41 DeviceDiagnosisHeartbeatData
^C[eebus ] DEBUG 2024/03/13 08:02:35 mdns: stop announcement
[eebus ] DEBUG 2024/03/13 08:02:35 mdns: stop announcement
[eebus ] DEBUG 2024/03/13 08:02:35 restarting mdns search

What type of operating system are you running?

Linux

Version

evcc version 0.124.7

DerAndereAndi commented 5 months ago

Das Auto ladet IMMER mit voller Leistung bis evcc im Intervall die Daten bekommt und einschreiten kann. Dein Interval ist auf 30s, wenn du es 1s nach dem Intervall einsteckst, dauert es 29s bis geregelt wird. Stell das Interval auf z.b. 10s wenn deine Meter das unterstützen. Dann hast du den Effekt nur für max 10s.

Das ist normales Verhalten so wie evcc arbeitet. Bei EEBUS kann evcc ohne angestecktes Auto die Ladung nicht unterbrechen und damit nur im Intervall einschreiten.

Ergänzung: Das ist normales Verhalten beim Taycan wenn einer der folgenden Fälle zutrifft:

hegi2k commented 5 months ago

Danke für die Antwort. Also am Intervall liegt es nicht, da er eine Stunde geladen hat. Komischerweise hat es ja mehrere Tage korrekt funktioniert. Habe jetzt Direktladen ausgemacht, dann scheint es korrekt zu funktionieren. Muss ich das, wenn ich an einem HPC Charger lade, wieder einschalten?

Würde es nicht Sinn machen diese Informationen in der Doku zu ergänzen?