Plötzlich lässt sich das wallbox template nicht mehr erstellen

[trombose009]

Hallo,

seit heute habe ich folgendes Phänomen:

[main  ] INFO 2025/01/07 12:49:46 evcc 0.132.0
[main  ] INFO 2025/01/07 12:49:46 using config file: /etc/evcc.yaml
[db    ] INFO 2025/01/07 12:49:46 using sqlite database: /root/.evcc/evcc.db
[mqtt  ] INFO 2025/01/07 12:49:46 connecting evcc-663076226 at tcp://192.168.178.44:1883
[main  ] INFO 2025/01/07 12:49:46 listening at :7070
[main  ] FATAL 2025/01/07 12:49:56 cannot create charger 'wallbox2': cannot create charger type 'template': cannot create charger type 'easee': Post "https://api.easee.com/api/accounts/login": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
[main  ] FATAL 2025/01/07 12:49:56 will attempt restart in: 15m0s
[main  ] INFO 2025/01/07 12:54:55 evcc 0.132.0
[main  ] INFO 2025/01/07 12:54:55 using config file: /etc/evcc.yaml
[db    ] INFO 2025/01/07 12:54:55 using sqlite database: /root/.evcc/evcc.db
[mqtt  ] INFO 2025/01/07 12:54:55 connecting evcc-1392915104 at tcp://192.168.178.44:1883
[main  ] INFO 2025/01/07 12:54:55 listening at :7070
[main  ] FATAL 2025/01/07 12:55:17 cannot create charger 'wallbox3': cannot create charger type 'template': cannot create charger type 'easee': i/o timeout
[main  ] FATAL 2025/01/07 12:55:17 will attempt restart in: 15m0s
[main  ] INFO 2025/01/07 12:57:45 evcc 0.132.0
[main  ] INFO 2025/01/07 12:57:45 using config file: /etc/evcc.yaml
[db    ] INFO 2025/01/07 12:57:45 using sqlite database: /root/.evcc/evcc.db
[mqtt  ] INFO 2025/01/07 12:57:46 connecting evcc-553582933 at tcp://192.168.178.44:1883
[main  ] INFO 2025/01/07 12:57:46 listening at :7070
[main  ] FATAL 2025/01/07 12:57:56 cannot create charger 'wallbox3': cannot create charger type 'template': cannot create charger type 'easee': Post "https://api.easee.com/api/accounts/login": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
[main  ] FATAL 2025/01/07 12:57:56 will attempt restart in: 15m0s
[main  ] INFO 2025/01/07 13:10:12 evcc 0.132.0
[main  ] INFO 2025/01/07 13:10:12 using config file: /etc/evcc.yaml
[db    ] INFO 2025/01/07 13:10:12 using sqlite database: /root/.evcc/evcc.db
[mqtt  ] INFO 2025/01/07 13:10:12 connecting evcc-155026721 at tcp://192.168.178.44:1883
[main  ] INFO 2025/01/07 13:10:12 listening at :7070
[main  ] FATAL 2025/01/07 13:10:22 cannot create charger 'wallbox2': cannot create charger type 'template': cannot create charger type 'easee': Post "https://api.easee.com/api/accounts/login": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
[main  ] FATAL 2025/01/07 13:10:22 will attempt restart in: 15m0s

Keine Ahnung warum.

mein config sieht so aus:

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

log: info
levels:
  cache: error

interval: 20s # control cycle interval

sponsortoken: eyJhbGciOiJIUzI1NiIsInsdfgNTA3NzQ2OTUsImlhdCI6MTY1NjE2NjY5NSwiaXNzIjoiZXZjYy5pbyIsInN1YiI6InRyb21ib3NlMDA5In0.9zuGWbHm7VlATz_p-c1kdLyIcxQhxZr-SH_A4nXOfbY

meters:
- type: template
  template: fronius-solarapi-v1 
  usage: grid  
  host: 192.168.178.121  
  name: grid1
- type: template
  template: fronius-solarapi-v1 
  usage: pv  
  host: 192.168.178.121  
  name: pv1
- type: template
  template: fronius-solarapi-v1 
  usage: pv  
  host: 192.168.178.121  
  name: pv3
- name: SML
  type: custom
  power:
    source: mqtt
    topic: strom/smartmeter/sensor/1/obis/1-0:16.7.0/255/value


chargers:
- type: template
  template: easee 
  user: [email protected]  
  password: sdfg
  charger: sdfg
  name: wallbox3
- type: template
  template: easee 
  user:[email protected]  
  password: sdfg
  charger: sdgf  
  name: wallbox2
#- type: template
#  template: easee 
#  user: [email protected]  
#  password: sdgf
#  charger: sdgf
#  name: wallbox1
  
vehicles:
- type: template
  template: kia 
  title: Kia EV6  
  user: [email protected]  
  password: hgkjh!
  vin: sdfgdsfg
  capacity: 77  
  phases: 3  
  language: de  
  mode: pv   
  minCurrent: 6  
  maxCurrent: 16  
  cloud: false  
  name: EV6
- type: template
  template: nissan 
  title: unser Leaf  
  user: [email protected]  
  password: hgkjgh!  
  vin: dfgsdfg
  capacity: 40  
  mode: pv 
  name: nissan1
#- type: template
#  template: nissan 
#  title: Leaf Abbas
#  user: [email protected]  
#  password: fhfgdh*  
#  vin: sdgf
#  capacity: 62  
#  mode: pv
#  name: nissan2

loadpoints:
#- title: Abbas
#  charger: wallbox1
#  vehicle: nissan2
#  mode: pv
#  phases: 1
#  mincurrent: 7
#  maxcurrent: 32
- title: Garage rechts
  charger: wallbox2
  vehicle: nissan1
  mode: pv
  phases: 1
  mincurrent: 6
  maxcurrent: 32
- title: Garage links
  charger: wallbox3
  vehicle: EV6
  mode: pv
  phases: 3
  mincurrent: 6
  maxcurrent: 16

site:
  title: Zuhause
  meters:
  #  grid: SML
    grid: grid1
    pv:
    - pv1
    #- pv2
# mqtt message broker
mqtt:
   broker: 192.168.178.44:1883
   topic: evcc # root topic for publishing, set empty to disable
influx:
  url: http://192.168.178.44:8086
  database: evcc
#  interval: 30s # alle 15 Sekunden wird an influxdb gesendet

Hat jemand eine idee?

[OlliLu]

Jede Zeile, in der ein # vorne steht, ist unwirksam, nennt sich auskommentiert. Ist das Absicht?

[trombose009]

Ja. Derzeit ist eine wallbox außer Betrieb und es sind auch nur zwei und nicht drei e-autos vorhanden

[VolkerK62]

Da antwortet der Easee Server nicht.

[trombose009]

Dumme Frage: wenn dieser genannte Fehler Auftritt, funktioniert dann die fronius Abfrage und das mqtt publishing via evcc auch nicht? Weil das wäre mir ganz unabhängig von der wallboxgeschichte wichtig

[VolkerK62]

Wenn der Fehler auftritt, während evcc läuft, ist das kein Problem.
Sind die aber beim Start nicht verfügbar, startet evcc nicht.

[trombose009]

Wenn ich kurzfristig die wallboxen aus kommentiere, startet evcc dann normal? Also ganz ohne wallboxes

[VolkerK62]

ne, ohne Wallbox geht das nciht.
Du kannst aber den Demo-Charger konfigurieren und einem bestehende loadpoint zuordnen.
Dann startet evcc wieder
https://docs.evcc.io/docs/devices/chargers#demowallbox