Open
Description
Describe the bug
Mein Kostal Plenticore wird falsch ausgelesen.
Was in Out Verbrauch und Batterie laden wäre, wird als Summe unter Einspeisung ausgewiesen.
(siehe Screenshots)
Steps to reproduce
...
Configuration details
# 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: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
interval: 30s # control cycle interval
sponsortoken: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
# sponsors can set telemetry: true to enable anonymous data aggregation
# see https://github.com/evcc-io/evcc/discussions/4554
telemetry: false
meters:
- type: template
template: kostal-plenticore
id: 71
host: 192.168.50.83
port: 1502
usage: pv
modbus: tcpip
name: pv1
- type: template
template: kostal-plenticore
id: 71
host: 192.168.50.83
port: 1502
usage: battery
modbus: tcpip
name: battery2
chargers:
- type: template
template: sungrow
id: 248
host: 192.168.50.32
port: 502
modbus: rs485tcpip
name: wallbox4
vehicles:
- type: template
template: opel
title: Corsa
capacity: 50
user: r.weber@regino-gym.de
accessToken: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
refreshToken: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
vin: xxxxxxxxxxxxxxxxxxxxxxx
name: ev3
loadpoints:
- title: Carport
charger: wallbox4
vehicle: ev3
mode: pv
site:
title: Mein Zuhause
meters:
pv:
- pv1
battery:
- battery2Log details
weber@IoT-Server:~ $ sudo journalctl -fau evcc
Jun 20 14:37:55 IoT-Server evcc[10813]: [lp-1 ] ERROR 2025/06/20 14:37:55 charge currents: read tcp 192.168.50.37:45234->192.168.50.32:502: i/o timeout
Jun 20 14:37:56 IoT-Server evcc[10813]: [site ] DEBUG 2025/06/20 14:37:56 battery 1 power: 0W
Jun 20 14:37:56 IoT-Server evcc[10813]: [site ] DEBUG 2025/06/20 14:37:56 battery 1 soc: 98%
Jun 20 14:37:56 IoT-Server evcc[10813]: [site ] DEBUG 2025/06/20 14:37:56 pv 1 power: 7161W
Jun 20 14:37:56 IoT-Server evcc[10813]: [site ] DEBUG 2025/06/20 14:37:56 site power: -7161W
Jun 20 14:37:59 IoT-Server evcc[10813]: [lp-1 ] ERROR 2025/06/20 14:37:59 charge voltages: read tcp 192.168.50.37:45248->192.168.50.32:502: i/o timeout
Jun 20 14:38:02 IoT-Server evcc[10813]: [lp-1 ] ERROR 2025/06/20 14:38:02 charge total import: read tcp 192.168.50.37:45258->192.168.50.32:502: i/o timeout
Jun 20 14:38:05 IoT-Server evcc[10813]: [lp-1 ] ERROR 2025/06/20 14:38:05 charger status: read tcp 192.168.50.37:38452->192.168.50.32:502: i/o timeout
Jun 20 14:38:05 IoT-Server evcc[10813]: [site ] DEBUG 2025/06/20 14:38:05 ----
Jun 20 14:38:18 IoT-Server evcc[10813]: [lp-1 ] ERROR 2025/06/20 14:38:18 charge power: read tcp 192.168.50.37:58976->192.168.50.32:502: i/o timeout
Jun 20 14:38:30 IoT-Server evcc[10813]: [lp-1 ] ERROR 2025/06/20 14:38:30 charge currents: read tcp 192.168.50.37:47702->192.168.50.32:502: i/o timeout
Jun 20 14:38:30 IoT-Server evcc[10813]: [site ] DEBUG 2025/06/20 14:38:30 battery 1 power: 0W
Jun 20 14:38:30 IoT-Server evcc[10813]: [site ] DEBUG 2025/06/20 14:38:30 battery 1 soc: 98%
Jun 20 14:38:31 IoT-Server evcc[10813]: [site ] DEBUG 2025/06/20 14:38:31 pv 1 power: 7200W
Jun 20 14:38:31 IoT-Server evcc[10813]: [site ] DEBUG 2025/06/20 14:38:31 site power: -7200W
Jun 20 14:38:34 IoT-Server evcc[10813]: [lp-1 ] ERROR 2025/06/20 14:38:34 charge voltages: read tcp 192.168.50.37:57218->192.168.50.32:502: i/o timeout
Jun 20 14:38:37 IoT-Server evcc[10813]: [lp-1 ] ERROR 2025/06/20 14:38:37 charge total import: read tcp 192.168.50.37:57234->192.168.50.32:502: i/o timeout
Jun 20 14:38:40 IoT-Server evcc[10813]: [lp-1 ] ERROR 2025/06/20 14:38:40 charger status: read tcp 192.168.50.37:57248->192.168.50.32:502: i/o timeout
Jun 20 14:38:40 IoT-Server evcc[10813]: [site ] DEBUG 2025/06/20 14:38:40 ----
^C
What type of operating system or environment does evcc run on?
Linux
External automation
- I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.
Nightly build
- I have verified that the issue is reproducible with the latest nightly build
Version
0.204.3