search

evcc-io / evcc

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

evcc beroichtet von einem Eintrag "resetondisconnect", den ich jedoch gelöscht habe. #11531

Closed christian-moeller closed 8 months ago

christian-moeller commented 8 months ago

Describe the bug

failed configuring loadpoints failed configuring loadpoint 1 error(s) decoding: * '' has invalid keys: resetondisconnect Bitte überprüfe deine Konfigurationsdatei. Sollte dir die Fehlermeldung nicht weiterhelfen, suche in unseren GitHub Diskussionen nach einer Lösung.

Hinweis: Ein weiterer Grund könnte ein fehlerhaftes Gerät (Wechselrichter, Zähler, …) sein. Überprüfe deine Netzwerkverbindungen.

Konfiguration Verwendete Konfigurationsdatei: /etc/evcc.yaml Behebe das Problem und starte den Server neu.

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

sponsortoken: *****

tariffs:
currency: EUR
grid:
type: fixed
price: #####

feedin:
type: fixed
price: #####

co2:
type: grünstromindex
zip: #####

meters:

chargers:

loadpoints:

vehicles:

site:
title: Möller-Loccum
meters:
grid: grid1
pv: Kostal_Piko

Wenn ich nun "cat /etc/evcc.yaml" eingebe, erhalte ich folgenden Output:

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

sponsortoken: ##### tariffs: currency: EUR grid: type: fixed price: #####

feedin: type: fixed price: #####

co2: type: grünstromindex zip: #####

meters:

chargers:

loadpoints:

vehicles:

site: title: Möller-Loccum meters: grid: grid1 pv: Kostal_Piko

Wo also nimmt evcc die .yaml-Datei tatsächlich her, damit ich dem Service dieses Gehabe abgewöhnen kann?

Steps to reproduce

1. 2. 3. ...

Configuration details

s.o.

Log details

[main  ] INFO 2024/01/06 20:29:33 evcc 0.123.5
[main  ] INFO 2024/01/06 20:29:33 using config file: /home/pi/evcc.yaml
[main  ] INFO 2024/01/06 20:29:33 starting ui and api at :7070
[db    ] INFO 2024/01/06 20:29:33 using sqlite database: /home/pi/.evcc/evcc.db
[lp-1  ] DEBUG 2024/01/06 20:29:36 charge total import: 4598.761kWh
[site  ] INFO 2024/01/06 20:29:36 site config:
[site  ] INFO 2024/01/06 20:29:36   meters:      grid ✓ pv ✓ battery ✗
[site  ] INFO 2024/01/06 20:29:36     grid:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/01/06 20:29:36     pv 1:      power ✓ energy ✗ currents ✗
[site  ] INFO 2024/01/06 20:29:36   vehicles:
[site  ] INFO 2024/01/06 20:29:36     vehicle 1: range ✓ finish ✓ status ✓ climate ✓ wakeup ✗
[lp-1  ] INFO 2024/01/06 20:29:36 loadpoint 1:
[lp-1  ] INFO 2024/01/06 20:29:36   mode:        pv
[lp-1  ] INFO 2024/01/06 20:29:36   charger:     power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
[lp-1  ] INFO 2024/01/06 20:29:36   meters:      charge ✓
[lp-1  ] INFO 2024/01/06 20:29:36     charge:    power ✓ energy ✓ currents ✓
[lp-1  ] DEBUG 2024/01/06 20:29:36 phase timer inactive
[lp-1  ] DEBUG 2024/01/06 20:29:36 pv timer inactive
[lp-1  ] DEBUG 2024/01/06 20:29:36 guard timer inactive
[lp-1  ] INFO 2024/01/06 20:29:36 vehicle updated: unknown -> MokkaE
[site  ] WARN 2024/01/06 20:29:36 interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval
[site  ] DEBUG 2024/01/06 20:29:36 ----
[lp-1  ] DEBUG 2024/01/06 20:29:36 charge power: 0W
[site  ] DEBUG 2024/01/06 20:29:36 pv power: 0W
[site  ] DEBUG 2024/01/06 20:29:36 grid power: 5887W
[site  ] DEBUG 2024/01/06 20:29:36 site power: 5887W
[lp-1  ] DEBUG 2024/01/06 20:29:36 vehicle odometer: 22627km
[lp-1  ] DEBUG 2024/01/06 20:29:36 charge currents: [0 0 0]A
[lp-1  ] DEBUG 2024/01/06 20:29:36 charge total import: 4598.761kWh
[lp-1  ] DEBUG 2024/01/06 20:29:36 charger status: B
[lp-1  ] INFO 2024/01/06 20:29:36 car connected
[lp-1  ] DEBUG 2024/01/06 20:29:36 pv timer elapse
[lp-1  ] DEBUG 2024/01/06 20:29:36 pv timer inactive
[lp-1  ] DEBUG 2024/01/06 20:29:36 charger: guard elapse
[lp-1  ] DEBUG 2024/01/06 20:29:36 guard timer inactive
[lp-1  ] DEBUG 2024/01/06 20:29:36 charge total import: 4598.761kWh
[lp-1  ] DEBUG 2024/01/06 20:29:36 vehicle status: B
[lp-1  ] DEBUG 2024/01/06 20:29:36 vehicle soc: 45%
[lp-1  ] DEBUG 2024/01/06 20:29:36 vehicle range: 86km
[lp-1  ] DEBUG 2024/01/06 20:29:36 set mokkae plan soc: 0 @ 0001-01-01 00:53:28 +0053 LMT
[lp-1  ] DEBUG 2024/01/06 20:29:36 available power -5887W < 4140W min 3p threshold
[lp-1  ] DEBUG 2024/01/06 20:29:36 phase scale1p in 0s
[lp-1  ] DEBUG 2024/01/06 20:29:36 switched phases: 1p
[lp-1  ] DEBUG 2024/01/06 20:29:36 phase timer inactive
[lp-1  ] DEBUG 2024/01/06 20:29:36 pv charge current: 0A = 0A + -25.6A (5887W @ 1p)
[lp-1  ] DEBUG 2024/01/06 20:29:36 pv enable timer reset
[lp-1  ] DEBUG 2024/01/06 20:29:36 pv timer inactive

What type of operating system are you running?

Linux

Version

evcc version 0.123.5

mdkeil commented 8 months ago

Wenn ich nun "cat /etc/evcc.yaml" eingebe, erhalte ich folgenden Output:

[main  ] INFO 2024/01/06 20:29:33 evcc 0.123.5
[main  ] INFO 2024/01/06 20:29:33 using config file: /home/pi/evcc.yaml

außerdem müssen minSOC und targetSoc ebenfalls raus.

0x3d13f commented 8 months ago

In Log steht, dass er nicht die evcc.yaml in /etc, sondern in /home/pi benutzt. Dann musst Du diese auch ändern und die Änderungen in /etc bewirken nichts.