Evcc startet nicht nach Update auf 0.130.8

Allwaysfly commented 2 months ago

Describe the bug

Nach Update von 0.130.7 auf 0.130.8 startet evcc nicht mehr und endet mit einem Fatal error:

main ] INFO 2024/09/10 10:48:13 evcc 0.130.8 [main ] INFO 2024/09/10 10:48:13 using config file: /etc/evcc.yaml [db ] INFO 2024/09/10 10:48:13 using sqlite database: /var/lib/evcc/evcc.db [main ] INFO 2024/09/10 10:48:13 listening at :7070 [main ] FATAL 2024/09/10 10:48:22 cannot create meter 'battery3': cannot create meter type 'template': cannot create meter type 'custom': power: connection already registered with different protocol: 192.168.178.121:1502 [main ] FATAL 2024/09/10 10:48:22 will attempt restart in: 15m0s

Die Konfiguration wurde nicht geändert. Nach Downgrade auf 0.130.7 läuft evcc wieder

Es existiert bereits eine Diskussion mit Stefan Schoof zu dem Fehler, der mir geraten hat, einen bug zu eröffnen #16013

Ich habe folgende Geräte im Einsatz Evcc: raspberry PI 4 / Ubuntu 24.04 LTS Wechselrichter: SolarEdge SE7K Batterie: SolarEdge Home Batterie Charger: 2x Easee Home, wobei nur einer in evcc definiert und benutzt wird Vehicle: Peugeot e2008

Ich habe den nightly build NICHT getestet (muss es aber markieren), da ich nicht weiss, wie ich das in einer existierenden Installation rein bekomme (in der Dokumentation wird nur die Erstinstallation beschrieben). Und ich möchte meine Installation auch möglichst nicht ändern, da es wegen der PSA Schnittstelle tricky genug war, es einzurichten.

Steps to reproduce

sudo systemctl stop evcc
sudo apt update
sudo apt —only-upgrade install -y evcc
sudo systemctl start evcc

Hier der Trace log: evcc-20240911-183411-trace.log

Configuration details

[main ] INFO 2024/09/10 20:02:37 evcc 0.130.7
[main ] INFO 2024/09/10 20:02:37 using config file: /etc/evcc.yaml
[db ] INFO 2024/09/10 20:02:37 using sqlite database: /home/raspberry-solar/.evcc/evcc.db
[main ] ERROR 2024/09/10 20:02:49 creating vehicle ev4 failed: cannot create vehicle type 'template': cannot create vehicle type 'peugeot': token expired
[lp-1 ] DEBUG 2024/09/10 20:02:49 charge total import: 1326.890kWh

Konfiguration (/etc/evcc.yaml):

open evcc at http://evcc.local:7070

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

log: debug
levels:
cache: error

unique installation id

plant: *****

interval: 15s # control cycle interval

sponsortoken: *****

sponsors can set telemetry: true to enable anonymous data aggregation

see #4554

telemetry: false

meters:

type: template
template: solaredge-hybrid
id: 1
host: 192.168.178.121
port: 1502
usage: grid
modbus: rs485tcpip
name: grid1
type: template
template: solaredge-hybrid
id: 1
host: 192.168.178.121
port: 1502
usage: pv
modbus: rs485tcpip
name: pv2
type: template
template: solaredge-hybrid
id: 1
host: 192.168.178.121
port: 1502
usage: battery
modbus: rs485tcpip
name: battery3
chargers:

type: template
template: easee
user: *****
password: *****
charger: EHNZYGLD
timeout: 20s
authorize: true
name: wallbox5
vehicles:

type: template
template: peugeot
title: e2008
user: *****
accessToken: *****
refreshToken: *****
capacity: 50
name: ev4
loadpoints:

title: Garage
charger: wallbox5
mode: pv
site:
title: Mein Zuhause
meters:
grid: grid1
pv:
- pv2
battery:
- battery3
residualpower: 150

Version: 0.130.7

Log details

Siehe Datei in „Steps to procedure“

What type of operating system are you running?

Linux

Nightly build

[X] I have verified that the issue is reproducible with the latest nightly build

Version

Momentan 0.130.7, Fehler in 0.130.8

Allwaysfly commented 2 months ago

Ich habe gerade gesehen, dass es 0.130.9 gibt. Aber auch da tritt der Fehler noch auf: evcc-20240912-092619-trace.log

andig commented 2 months ago

Please give remote access to info@evcc.io for testing

Allwaysfly commented 2 months ago

It would be nice, if you can give me some advice how to do this as I'm not an IT expert and didn't open my PCs for remote access yet.

andig commented 2 months ago

You can try something like FritzBox VPN. Unfortunately I don't have the capacity for supporting this :(

brmien commented 2 months ago

Similar issues here with Easee. Had to downgrade to 0.130.7 as well to get it running again.

removed offer to support

andig commented 2 months ago

Hier gehts um Modbus, nicht um Easee.

Allwaysfly commented 2 months ago

Could it be, that the problem is with Modbus and Easee, as there are already three with the same situation? Anyway, I have as well not the time to get fit in setting up any remote connection. 0.130.7 works fine for me.

andig commented 2 months ago

Neues Nightly in 30min- Retest wäre Klasse. Vielen Dank!

evcc-io / evcc