SofarSolar: timeout

[hrampf]

Describe the bug

Es tritt ein Lesefehler grid auf

Steps to reproduce

Fehler tritt immer auf

Configuration details

network:
  port: 7070

log: debug

interval: 30s

meters:

  - name: sofar-battery-1
    type: template
    template: sofarsolar-g3
    usage: battery
    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.178.87 # Hostname
    port: 8899 # Port  
    delay: '0s'
    capacity: 12
    minsoc: 10
    maxsoc: 100

  - name: sofar-grid
    type: template
    template: sofarsolar-g3
    usage: grid
    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.178.87 # Hostname
    port: 8899 # Port  
    delay: '0s'

  - name: sofar-pv
    type: template
    template: sofarsolar-g3
    usage: pv
    # Modbus TCP
    modbus: tcpip
    id: 1
    host: 192.168.178.87 # Hostname
    port: 8899 # Port  
    delay: '0s'

  - name: shelly
    type: template
    template: shelly-3em # Shelly 3EM als Grid-Meter
    usage: grid
    host: 192.168.178.89

chargers:
  type: template
  template: elvi
  stationid: EVB-P22217851
  connector: 1
  connecttimeout: 5m
  timeout: 2m
  meter: false
  meterinterval: 4s
  name: wallbox1

vehicles:
  type: template
  template: tesla
  title: Tesla
  icon: car
  accessToken: 
  refreshToken: 
  capacity: 70
  phases: 3
  mode: minpv
  minCurrent: 5
  maxCurrent: 16
  priority: 1
  name: ev1
  #onIdentify:
  #  mode: pv
  #  minSoC: 1
  #  targetSoC: 90
  #cloud: false  

site:
  title: Zuhause
  meters:
    grid: sofar-grid
    pv: sofar-pv
    battery: sofar-battery-1
  #prioritySoC: 90 # give home battery priority up to this soc (0 to disable)
  #bufferSoC: 80
  residualPower: 100

loadpoints:
  - title: Carport
    charger: wallbox1
    mode: pv
    phases: 3
    #meter: sofar-grid
    meter: shelly
    vehicle: ev1


tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)
  grid:
    type: fixed
    price: 0.30 # EUR/kWh
  feedin:
    type: fixed
    price: 0.082 # EUR/kWh
  co2:
    type: grünstromindex
    zip: 83661

influx:
  #url: http://localhost:8086
  url: http://influxdb:8086
  database: evccdb
  user: 
  password:

Log details

grid power: read failed: read tcp 172.21.0.3:60524->192.168.178.87:8899: i/o timeout
vor 3 Minuten

grid power: read failed: read tcp 172.21.0.3:58400->192.168.178.87:8899: i/o timeout
vor 3 Minuten

battery 1 power: read failed: read tcp 172.21.0.3:41510->192.168.178.87:8899: i/o timeout
vor 3 Minuten

pv 1 power: add[0]: read failed: read tcp 172.21.0.3:36550->192.168.178.87:8899: i/o timeout
vor 4 Minuten

grid power: read failed: read tcp 172.21.0.3:37024->192.168.178.87:8899: i/o timeout
vor 6 Minuten

grid power: read failed: read tcp 172.21.0.3:42172->192.168.178.87:8899: i/o timeout

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

Installierte Version: 0.201.1

[Chris45671]

Es handelt sich dabei ja um ganz andere IP Adressen in einem anderen Bereich?
Läuft das in einem Docker?
Können die IP Adressen von dem Rechner angepingt werden?
Sieht nach einem reinen Netzwerkproblem aus.

[andig]

Ist der Fehler neu oder ging das noch nie mit einer alten Version?

[r1st0]

@aklickermann könntest Du mal probieren, ob ein längerer Timeout wirklich helfen würde? Dafür:

EVCC_TEMPLATE_RENDER=sofarsolar-g3 evcc

damit bekommst Du das komplette "gerenderte" Template. Dann könntest Du bei jedem Messwert einen neuen Timeout einbauen:

timeout: 3s

und das Ganze dann als "custom" einbauen.

wir genau kann ich es probieren? "timeout" wird beim template nicht unterstützt. was genau meinst du mit custom? die meter als custom eintragen? dann müsste man ja alle modbus adressen manuell nochmal eintippen oder geht es einfacher?

[andig]

Probiers doch einfach aus- alle deine Fragen werden sich von selbst beantworten.

[r1st0]

ok, das mit dem EVCC_TEMPLATE_RENDER=sofarsolar-g3 hab ich nicht gecheckt. hab also umständlich das ganze template in die config als custom kopiert + timeout: 3s
jetzt bekomme ich keine timeouts mehr aber folgendes:

[lp-1 ] INFO 2025/04/19 11:17:31 vehicle updated: unknown -> GolfStrom
[lp-1 ] INFO 2025/04/19 11:17:40 car connected
[lp-1 ] INFO 2025/04/19 11:17:40 start charging ->
[lp-1 ] ERROR 2025/04/19 11:17:40 climater: strconv.ParseBool: parsing "off": invalid syntax
[lp-1 ] INFO 2025/04/19 11:18:19 stop charging <-
[site ] ERROR 2025/04/19 11:19:16 2025-04-19 11:19:10.991406152 +0200 CEST m=+113.786173390 !! 5543ms add[2]: read failed: modbus: exception '4' (server device failure), function '3'
[site ] ERROR 2025/04/19 11:19:16 pv 1 power: add[2]: read failed: modbus: exception '4' (server device failure), function '3'
[site ] ERROR 2025/04/19 11:19:45 2025-04-19 11:19:41.023474442 +0200 CEST m=+143.818241680 !! 4196ms read failed: modbus: exception '4' (server device failure), function '3'
[site ] ERROR 2025/04/19 11:19:45 battery 1 power: read failed: modbus: exception '4' (server device failure), function '3'
[site ] ERROR 2025/04/19 11:19:47 2025-04-19 11:19:41.023566944 +0200 CEST m=+143.818334183 !! 6572ms add[0]: read failed: modbus: exception '4' (server device failure), function '3'
[site ] ERROR 2025/04/19 11:19:47 pv 1 power: add[0]: read failed: modbus: exception '4' (server device failure), function '3'
[site ] ERROR 2025/04/19 11:21:44 2025-04-19 11:21:41.013483404 +0200 CEST m=+263.808250646 !! 3760ms add[0]: read failed: modbus: exception '4' (server device failure), function '3'
[site ] ERROR 2025/04/19 11:21:44 pv 1 power: add[0]: read failed: modbus: exception '4' (server device failure), function '3'
[site ] ERROR 2025/04/19 11:21:45 2025-04-19 11:21:41.013816889 +0200 CEST m=+263.808584128 !! 4866ms read failed: modbus: exception '4' (server device failure), function '3'
[site ] ERROR 2025/04/19 11:21:45 battery 1 power: read failed: modbus: exception '4' (server device failure), function '3' 

und im PV mode startet die ladung nicht automatisch, aber das ist vielleicht ein anderes Problem
maxacpower war versehentlich in kW anstelle W

[r1st0]

auch probiert mit conn.Timeout(3 * time.Second) (siehe #20684)
keine timeouts mehr, aber die errors alle 2min bleiben

[andig]

@r1st0 danke für den Test. Das Gerät ist also etwas zickig und ein einfacher Timeout reicht nicht. Könntest Du für [email protected] Remotezugang für den Modbus Port einrichten, das dass ich das selbst mal testen könnte?

[cwseiler]

Wie man im Log-File sieht passiert das so alle zwei Minuten. Das auch erst nach Update auf 0.203.0. inzwischen auf 0.203.1 geupdated, aber weiterhin der Fehler. Hier mal ein Auszug aus dem Log: [site ] ERROR 2025/04/14 11:30:59 2025-04-14 11:30:57.946366288 +0200 CEST m=+3041.271007143 !! 2017ms add[0]: read failed: read tcp 192.168.178.39:58352->192.168.178.125:8899: i/o timeout [site ] ERROR 2025/04/14 11:30:59 pv 1 power: add[0]: read failed: read tcp 192.168.178.39:58352->192.168.178.125:8899: i/o timeout [site ] ERROR 2025/04/14 11:31:00 2025-04-14 11:30:57.946382086 +0200 CEST m=+3041.271022942 !! 3036ms read failed: read tcp 192.168.178.39:58358->192.168.178.125:8899: i/o timeout [site ] ERROR 2025/04/14 11:31:00 battery 1 power: read failed: read tcp 192.168.178.39:58358->192.168.178.125:8899: i/o timeout [site ] ERROR 2025/04/14 11:31:03 battery 1 soc: read failed: read tcp 192.168.178.39:58376->192.168.178.125:8899: i/o timeout [site ] ERROR 2025/04/14 11:31:03 grid power: read failed: read tcp 192.168.178.39:58366->192.168.178.125:8899: i/o timeout [site ] DEBUG 2025/04/14 11:31:07 ---- [lp-1 ] DEBUG 2025/04/14 11:31:07 charge power: 0W [lp-1 ] DEBUG 2025/04/14 11:31:07 charge currents: [0 0 0]A [site ] DEBUG 2025/04/14 11:31:08 grid power: -1370W [site ] DEBUG 2025/04/14 11:31:09 battery 1 power: -0W [site ] DEBUG 2025/04/14 11:31:09 battery 1 soc: 100% [site ] DEBUG 2025/04/14 11:31:10 pv 1 power: 1900W [site ] DEBUG 2025/04/14 11:31:10 grid powers: [-470 -470 -470]W [site ] DEBUG 2025/04/14 11:31:11 grid currents: [-3.56 -2.13 -2.09]A [site ] DEBUG 2025/04/14 11:31:11 site power: -1370W [lp-1 ] DEBUG 2025/04/14 11:31:11 charge total import: 6295.725kWh [lp-1 ] DEBUG 2025/04/14 11:31:11 charger status: A [site ] DEBUG 2025/04/14 11:31:11 solar forecast: accumulated 4.006kWh, produced 3.534kWh, scale 0.882 [site ] DEBUG 2025/04/14 11:31:17 ---- [lp-1 ] DEBUG 2025/04/14 11:31:17 charge power: 0W [lp-1 ] DEBUG 2025/04/14 11:31:17 charge currents: [0 0 0]A [site ] DEBUG 2025/04/14 11:31:20 battery 1 power: 10W [site ] DEBUG 2025/04/14 11:31:20 grid power: -1300W [site ] DEBUG 2025/04/14 11:31:20 battery 1 soc: 100% [site ] DEBUG 2025/04/14 11:31:21 pv 1 power: 1830W [site ] DEBUG 2025/04/14 11:31:22 grid powers: [-400 -450 -420]W [site ] DEBUG 2025/04/14 11:31:23 grid currents: [-3.92 -1.96 -1.91]A [site ] DEBUG 2025/04/14 11:31:23 site power: -1290W [lp-1 ] DEBUG 2025/04/14 11:31:23 charge total import: 6295.725kWh [lp-1 ] DEBUG 2025/04/14 11:31:23 charger status: A [site ] DEBUG 2025/04/14 11:31:23 solar forecast: accumulated 4.022kWh, produced 3.534kWh, scale 0.879 [site ] DEBUG 2025/04/14 11:31:27 ---- [lp-1 ] DEBUG 2025/04/14 11:31:27 charge power: 0W [lp-1 ] DEBUG 2025/04/14 11:31:27 charge currents: [0 0 0]A [site ] DEBUG 2025/04/14 11:31:28 grid power: -1410W [site ] DEBUG 2025/04/14 11:31:29 battery 1 power: -0W [site ] DEBUG 2025/04/14 11:31:30 battery 1 soc: 100% [site ] DEBUG 2025/04/14 11:31:31 grid powers: [-470 -460 -470]W [site ] DEBUG 2025/04/14 11:31:31 pv 1 power: 1810W [site ] DEBUG 2025/04/14 11:31:32 grid currents: [-2.33 -2.15 -2.13]A [site ] DEBUG 2025/04/14 11:31:33 site power: -1410W [lp-1 ] DEBUG 2025/04/14 11:31:33 charge total import: 6295.725kWh [lp-1 ] DEBUG 2025/04/14 11:31:33 charger status: A [site ] DEBUG 2025/04/14 11:31:33 solar forecast: accumulated 4.035kWh, produced 3.534kWh, scale 0.876 [site ] DEBUG 2025/04/14 11:31:37 ---- [lp-1 ] DEBUG 2025/04/14 11:31:37 charge power: 0W [lp-1 ] DEBUG 2025/04/14 11:31:37 charge currents: [0 0 0]A [site ] DEBUG 2025/04/14 11:31:38 grid power: -1380W [site ] DEBUG 2025/04/14 11:31:38 battery 1 power: -0W [site ] DEBUG 2025/04/14 11:31:39 battery 1 soc: 100% [site ] DEBUG 2025/04/14 11:31:40 pv 1 power: 1780W [site ] DEBUG 2025/04/14 11:31:40 grid powers: [-460 -460 -460]W [site ] DEBUG 2025/04/14 11:31:41 grid currents: [-2.34 -2.09 -2.05]A [site ] DEBUG 2025/04/14 11:31:41 site power: -1380W [lp-1 ] DEBUG 2025/04/14 11:31:41 charge total import: 6295.725kWh [lp-1 ] DEBUG 2025/04/14 11:31:41 charger status: A [site ] DEBUG 2025/04/14 11:31:41 solar forecast: accumulated 4.047kWh, produced 3.534kWh, scale 0.873 [site ] DEBUG 2025/04/14 11:31:47 ---- [lp-1 ] DEBUG 2025/04/14 11:31:47 charge power: 0W [lp-1 ] DEBUG 2025/04/14 11:31:47 charge currents: [0 0 0]A [site ] DEBUG 2025/04/14 11:31:48 grid power: -1400W [site ] DEBUG 2025/04/14 11:31:48 battery 1 power: -0W [site ] DEBUG 2025/04/14 11:31:49 battery 1 soc: 100% [site ] DEBUG 2025/04/14 11:31:50 pv 1 power: 1760W [site ] DEBUG 2025/04/14 11:31:50 grid powers: [-460 -470 -470]W [site ] DEBUG 2025/04/14 11:31:51 grid currents: [-3.41 -2.05 -2.03]A [site ] DEBUG 2025/04/14 11:31:51 site power: -1400W [lp-1 ] DEBUG 2025/04/14 11:31:51 charge total import: 6295.725kWh [lp-1 ] DEBUG 2025/04/14 11:31:51 charger status: A [site ] DEBUG 2025/04/14 11:31:51 solar forecast: accumulated 4.061kWh, produced 3.534kWh, scale 0.870 [site ] DEBUG 2025/04/14 11:31:57 ---- [lp-1 ] DEBUG 2025/04/14 11:31:57 charge power: 0W [lp-1 ] DEBUG 2025/04/14 11:31:57 charge currents: [0 0 0]A [site ] DEBUG 2025/04/14 11:31:58 grid power: -1330W [site ] DEBUG 2025/04/14 11:31:58 battery 1 power: 10W [site ] DEBUG 2025/04/14 11:31:59 battery 1 soc: 100% [site ] DEBUG 2025/04/14 11:32:00 pv 1 power: 1740W [site ] DEBUG 2025/04/14 11:32:00 grid powers: [-450 -440 -450]W [site ] DEBUG 2025/04/14 11:32:01 grid currents: [-2.34 -2.01 -2.03]A [site ] DEBUG 2025/04/14 11:32:01 site power: -1320W [lp-1 ] DEBUG 2025/04/14 11:32:01 charge total import: 6295.725kWh [lp-1 ] DEBUG 2025/04/14 11:32:01 charger status: A [site ] DEBUG 2025/04/14 11:32:01 solar forecast: accumulated 4.075kWh, produced 3.534kWh, scale 0.867 [site ] DEBUG 2025/04/14 11:32:07 ---- [lp-1 ] DEBUG 2025/04/14 11:32:07 charge power: 0W [lp-1 ] DEBUG 2025/04/14 11:32:07 charge currents: [0 0 0]A [site ] ERROR 2025/04/14 11:32:09 2025-04-14 11:32:07.943479835 +0200 CEST m=+3111.268120693 !! 2016ms add[0]: read failed: read tcp 192.168.178.39:46560->192.168.178.125:8899: i/o timeout [site ] ERROR 2025/04/14 11:32:09 pv 1 power: add[0]: read failed: read tcp 192.168.178.39:46560->192.168.178.125:8899: i/o timeout [site ] ERROR 2025/04/14 11:32:10 2025-04-14 11:32:07.943496794 +0200 CEST m=+3111.268137648 !! 3031ms read failed: read tcp 192.168.178.39:46562->192.168.178.125:8899: i/o timeout [site ] ERROR 2025/04/14 11:32:10 battery 1 power: read failed: read tcp 192.168.178.39:46562->192.168.178.125:8899: i/o timeout [site ] ERROR 2025/04/14 11:32:13 battery 1 soc: read failed: read tcp 192.168.178.39:46576->192.168.178.125:8899: i/o timeout [site ] ERROR 2025/04/14 11:32:13 grid power: read failed: read tcp 192.168.178.39:46566->192.168.178.125:8899: i/o timeout [site ] DEBUG 2025/04/14 11:32:17 ---- [lp-1 ] DEBUG 2025/04/14 11:32:17 charge power: 0W [lp-1 ] DEBUG 2025/04/14 11:32:17 charge currents: [0 0 0]A [site ] DEBUG 2025/04/14 11:32:18 grid power: -1360W [site ] DEBUG 2025/04/14 11:32:18 battery 1 power: 10W [site ] DEBUG 2025/04/14 11:32:19 battery 1 soc: 100% [site ] DEBUG 2025/04/14 11:32:20 pv 1 power: 1710W Am 14. April 2025 10:56:16 MESZ schrieb andig ***@***.***>:

…

Möglich. Gibts ein Logfile? Helfen würde Remotezugang für ***@***.*** damit ich das selbst nachvollziehen kann. -- Reply to this email directly or view it on GitHub: #20247 (reply in thread) You are receiving this because you commented. Message ID: ***@***.***>

[wardwygaerts]

I have the same errors since 0.203

[site ] ERROR 2025/04/15 17:01:57 2025-04-15 17:01:55.964913232 +0200 CEST m=+60127.262223917 !! 2013ms read failed: read tcp 192.168.128.5:54034->192.168.0.37:8899: i/o timeout
[site ] ERROR 2025/04/15 17:01:57 battery 1 power: read failed: read tcp 192.168.128.5:54034->192.168.0.37:8899: i/o timeout
[site ] ERROR 2025/04/15 17:01:58 2025-04-15 17:01:55.964874885 +0200 CEST m=+60127.262185573 !! 1001ms add[0]: read failed: read tcp 192.168.128.5:51826->192.168.0.37:8899: i/o timeout 2025-04-15 17:01:56.996833501 +0200 CEST m=+60128.294144204 !! 1994ms add[0]: read failed: read tcp 192.168.128.5:54044->192.168.0.37:8899: i/o timeout
[site ] ERROR 2025/04/15 17:01:58 pv 1 power: add[0]: read failed: read tcp 192.168.128.5:54044->192.168.0.37:8899: i/o timeout
[site ] ERROR 2025/04/15 17:02:00 battery 1 soc: read failed: read tcp 192.168.128.5:54048->192.168.0.37:8899: i/o timeout

Although only the 3rd error is new in my setup, the other ones were already present, but is related to the LSE-3 stick.

[hrampf]

Guten Morgen, obwohl wir die anfragen mit proxy minimiert haben. Ist es bei mir nach dem update leider noch schlimmer geworden. [site ] DEBUG 2025/04/20 09:09:44 pv 1 power: 3930W [site ] DEBUG 2025/04/20 09:09:44 grid currents: [5.41 4.91 4.67]A [site ] DEBUG 2025/04/20 09:09:45 site power: -2850W [lp-1 ] DEBUG 2025/04/20 09:09:46 charge voltages: [240 240 240]V [lp-1 ] DEBUG 2025/04/20 09:09:46 detected connected phases: 3p [lp-1 ] DEBUG 2025/04/20 09:09:46 charge total import: 2596.249kWh [lp-1 ] DEBUG 2025/04/20 09:09:46 charger status: B [lp-1 ] DEBUG 2025/04/20 09:09:46 pv charge current: 4.13A = 0A + 4.13A (-2850W @ 3p) [site ] DEBUG 2025/04/20 09:10:14 ---- [lp-1 ] DEBUG 2025/04/20 09:10:14 charge power: 7W [lp-1 ] DEBUG 2025/04/20 09:10:14 charge currents: [0.04 0.02 0.02]A [proxy-5021] DEBUG 2025/04/20 09:10:15 failed to write response: write tcp 127.0.0.1:5021->127.0.0.1:38356: i/o timeout [site ] ERROR 2025/04/20 09:10:16 2025-04-20 09:10:14.582005414 +0200 CEST m=+6597.037592500 !! 2012ms add[0]: read failed: read tcp 127.0.0.1:60328->127.0.0.1:5021: i/o timeout [site ] ERROR 2025/04/20 09:10:16 pv 1 power: add[0]: read failed: read tcp 127.0.0.1:60328->127.0.0.1:5021: i/o timeout [site ] ERROR 2025/04/20 09:10:17 2025-04-20 09:10:14.582217136 +0200 CEST m=+6597.037804185 !! 3025ms read failed: read tcp 127.0.0.1:60338->127.0.0.1:5021: i/o timeout [site ] ERROR 2025/04/20 09:10:17 battery 1 power: read failed: read tcp 127.0.0.1:60338->127.0.0.1:5021: i/o timeout [site ] ERROR 2025/04/20 09:10:19 battery 1 soc: read failed: read tcp 127.0.0.1:60356->127.0.0.1:5021: i/o timeout [site ] ERROR 2025/04/20 09:10:19 grid power: read failed: read tcp 127.0.0.1:60348->127.0.0.1:5021: i/o timeout [site ] DEBUG 2025/04/20 09:10:49 ---- [lp-1 ] DEBUG 2025/04/20 09:10:49 charge power: 7W [lp-1 ] DEBUG 2025/04/20 09:10:49 charge currents: [0.04 0.02 0.02]A [site ] DEBUG 2025/04/20 09:10:51 battery 1 power: -3710W [site ] ERROR 2025/04/20 09:10:52 2025-04-20 09:10:49.768877089 +0200 CEST m=+6632.224464046 !! 2992ms add[0]: read failed: read tcp 127.0.0.1:47738->127.0.0.1:5021: i/o timeout [site ] ERROR 2025/04/20 09:10:52 pv 1 power: add[0]: read failed: read tcp 127.0.0.1:47738->127.0.0.1:5021: i/o timeout [site ] DEBUG 2025/04/20 09:10:54 battery 1 soc: 51% [site ] ERROR 2025/04/20 09:10:54 grid power: read failed: read tcp 127.0.0.1:34120->127.0.0.1:5021: i/o timeout [site ] DEBUG 2025/04/20 09:11:24 ---- [lp-1 ] DEBUG 2025/04/20 09:11:24 charge power: 7W [lp-1 ] DEBUG 2025/04/20 09:11:24 charge currents: [0.04 0.02 0.02]A [site ] ERROR 2025/04/20 09:11:26 2025-04-20 09:11:24.674907938 +0200 CEST m=+6667.130494894 !! 2036ms add[0]: read failed: read tcp 127.0.0.1:41592->127.0.0.1:5021: i/o timeout [site ] ERROR 2025/04/20 09:11:26 pv 1 power: add[0]: read failed: read tcp 127.0.0.1:41592->127.0.0.1:5021: i/o timeout [site ] ERROR 2025/04/20 09:11:28 2025-04-20 09:11:24.67441716 +0200 CEST m=+6667.130004117 !! 1023ms read failed: read tcp 127.0.0.1:41576->127.0.0.1:5021: i/o timeout 2025-04-20 09:11:25.714053915 +0200 CEST m=+6668.169640853 !! 3024ms read failed: read tcp 127.0.0.1:41602->127.0.0.1:5021: i/o timeout [site ] ERROR 2025/04/20 09:11:28 battery 1 power: read failed: read tcp 127.0.0.1:41602->127.0.0.1:5021: i/o timeout [site ] ERROR 2025/04/20 09:11:29 battery 1 soc: read failed: read tcp 127.0.0.1:41612->127.0.0.1:5021: i/o timeout [site ] ERROR 2025/04/20 09:11:29 grid power: read failed: read tcp 127.0.0.1:41600->127.0.0.1:5021: i/o timeout Von: r1st0 ***@***.***> Gesendet: Samstag, 19. April 2025 12:13 An: evcc-io/evcc ***@***.***> Cc: hrampf ***@***.***>; Author ***@***.***> Betreff: Re: [evcc-io/evcc] SofarSolar: timeout (Discussion #20247) auch probiert mit conn.Timeout(3 * time.Second) (siehe #20684 <#20684> ) keine timeouts mehr, aber die errors alle 2min bleiben — Reply to this email directly, view it on GitHub <#20247 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BMQWNAACSINRTWCKZEMZHWT22IOSHAVCNFSM6AAAAAB2CI5DAWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOBYGQZDGNY> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/BMQWNAA6M7ND2I5FDKQZKDL22IOSHA5CNFSM6AAAAAB2CI5DAWWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAYSMQ2.gif> Message ID: ***@***.*** ***@***.***> >

[r1st0]

timeout immer noch bei 1s oder ist das mit 3s?

[andig]

keine timeouts mehr, aber die errors alle 2min bleiben

ich verstehe nicht was du meinst. worauf bezieht sich das Log?

[andig]

Da die 3s zu helfen scheinen können wir mal probieren, ob es mit #20730 besser wird.

[cwseiler]

Mit der neuen Version läufts besser, aber leider kommt weiterhin ein timeout Fehler:

[lp-1 ] DEBUG 2025/04/22 21:28:16 charge power: 0W
[lp-1 ] DEBUG 2025/04/22 21:28:16 charge currents: [0 0 0]A
[site ] ERROR 2025/04/22 21:28:22 2025-04-22 21:28:16.217864386 +0200 CEST m=+140.514956728 !! 6017ms add[0]: read failed: read tcp 192.168.178.39:57342->192.168.178.125:8899: i/o timeout
[site ] ERROR 2025/04/22 21:28:22 pv 1 power: add[0]: read failed: read tcp 192.168.178.39:57342->192.168.178.125:8899: i/o timeout
[site ] DEBUG 2025/04/22 21:28:24 battery 1 power: 200W
[site ] DEBUG 2025/04/22 21:28:24 grid power: 30W
[site ] DEBUG 2025/04/22 21:28:24 battery 1 soc: 93%
[site ] DEBUG 2025/04/22 21:28:25 grid powers: [10 10 10]W
[site ] DEBUG 2025/04/22 21:28:26 grid currents: [0.31 0.61 0.38]A
[site ] DEBUG 2025/04/22 21:28:26 site power: 230W
[lp-1 ] DEBUG 2025/04/22 21:28:27 charge total import: 6375.155kWh
[lp-1 ] DEBUG 2025/04/22 21:28:27 charger status: A
[site ] DEBUG 2025/04/22 21:28:27 ----
[lp-1 ] DEBUG 2025/04/22 21:28:27 charge power: 0W
[lp-1 ] DEBUG 2025/04/22 21:28:27 charge currents: [0 0 0]A
[site ] DEBUG 2025/04/22 21:28:27 grid power: 570W
[site ] DEBUG 2025/04/22 21:28:28 battery 1 power: 70W
[site ] DEBUG 2025/04/22 21:28:28 battery 1 soc: 93%
[site ] DEBUG 2025/04/22 21:28:29 grid powers: [210 190 190]W
[site ] DEBUG 2025/04/22 21:28:29 pv 1 power: 0W
[site ] DEBUG 2025/04/22 21:28:30 grid currents: [0.77 0.71 0.57]A
[site ] DEBUG 2025/04/22 21:28:30 site power: 640W
[lp-1 ] DEBUG 2025/04/22 21:28:30 charge total import: 6375.155kWh
[lp-1 ] DEBUG 2025/04/22 21:28:30 charger status: A
[site ] DEBUG 2025/04/22 21:28:36 ----
[lp-1 ] DEBUG 2025/04/22 21:28:36 charge power: 0W
[lp-1 ] DEBUG 2025/04/22 21:28:36 charge currents: [0 0 0]A
[site ] DEBUG 2025/04/22 21:28:36 grid power: 50W
[site ] DEBUG 2025/04/22 21:28:37 battery 1 power: 270W
[site ] DEBUG 2025/04/22 21:28:37 battery 1 soc: 93%
[site ] DEBUG 2025/04/22 21:28:38 grid powers: [20 10 10]W
[site ] DEBUG 2025/04/22 21:28:38 pv 1 power: 0W
[site ] DEBUG 2025/04/22 21:28:39 grid currents: [0.31 0.62 0.33]A
[site ] DEBUG 2025/04/22 21:28:40 site power: 320W
[lp-1 ] DEBUG 2025/04/22 21:28:40 charge total import: 6375.155kWh
[lp-1 ] DEBUG 2025/04/22 21:28:40 charger status: A
[site ] DEBUG 2025/04/22 21:28:46 ----
[lp-1 ] DEBUG 2025/04/22 21:28:46 charge power: 0W
[lp-1 ] DEBUG 2025/04/22 21:28:46 charge currents: [0 0 0]A
[site ] DEBUG 2025/04/22 21:28:46 battery 1 power: 310W
[site ] DEBUG 2025/04/22 21:28:46 battery 1 soc: 93%
[site ] DEBUG 2025/04/22 21:28:46 grid power: 30W
[site ] DEBUG 2025/04/22 21:28:49 pv 1 power: 0W
[site ] DEBUG 2025/04/22 21:28:49 grid powers: [10 10 10]W
[site ] DEBUG 2025/04/22 21:28:50 grid currents: [0.31 0.62 0.33]A
[site ] DEBUG 2025/04/22 21:28:50 site power: 340W
[lp-1 ] DEBUG 2025/04/22 21:28:50 charge total import: 6375.155kWh
[lp-1 ] DEBUG 2025/04/22 21:28:50 charger status: A
[site ] DEBUG 2025/04/22 21:28:56 ----
[lp-1 ] DEBUG 2025/04/22 21:28:56 charge power: 0W
[lp-1 ] DEBUG 2025/04/22 21:28:56 charge currents: [0 0 0]A
[site ] DEBUG 2025/04/22 21:28:56 grid power: 30W
[site ] DEBUG 2025/04/22 21:28:57 battery 1 power: 310W
[site ] DEBUG 2025/04/22 21:28:58 battery 1 soc: 93%
[site ] DEBUG 2025/04/22 21:28:58 grid powers: [10 10 10]W
[site ] DEBUG 2025/04/22 21:28:58 pv 1 power: 0W
[site ] DEBUG 2025/04/22 21:28:59 grid currents: [0.31 0.62 0.35]A
[site ] DEBUG 2025/04/22 21:29:00 site power: 340W
[lp-1 ] DEBUG 2025/04/22 21:29:00 charge total import: 6375.155kWh
[lp-1 ] DEBUG 2025/04/22 21:29:00 charger status: A
[site ] DEBUG 2025/04/22 21:29:06 ----
[lp-1 ] DEBUG 2025/04/22 21:29:06 charge power: 0W
[lp-1 ] DEBUG 2025/04/22 21:29:06 charge currents: [0 0 0]A
[site ] DEBUG 2025/04/22 21:29:06 grid power: 20W
[site ] DEBUG 2025/04/22 21:29:07 battery 1 power: 300W
[site ] DEBUG 2025/04/22 21:29:07 battery 1 soc: 93%
[site ] DEBUG 2025/04/22 21:29:08 grid powers: [10 -0 10]W
[site ] DEBUG 2025/04/22 21:29:08 pv 1 power: 0W
[site ] DEBUG 2025/04/22 21:29:09 grid currents: [0.34 0.65 0.36]A
[site ] DEBUG 2025/04/22 21:29:10 site power: 320W
[lp-1 ] DEBUG 2025/04/22 21:29:10 charge total import: 6375.155kWh
[lp-1 ] DEBUG 2025/04/22 21:29:10 charger status: A
[site ] DEBUG 2025/04/22 21:29:16 ----
[lp-1 ] DEBUG 2025/04/22 21:29:16 charge power: 0W
[lp-1 ] DEBUG 2025/04/22 21:29:16 charge currents: [0 0 0]A
[site ] DEBUG 2025/04/22 21:29:16 grid power: 30W
[site ] DEBUG 2025/04/22 21:29:17 battery 1 power: 300W
[site ] DEBUG 2025/04/22 21:29:18 battery 1 soc: 93%
[site ] DEBUG 2025/04/22 21:29:18 grid powers: [10 10 10]W
[site ] DEBUG 2025/04/22 21:29:18 pv 1 power: 0W
[site ] DEBUG 2025/04/22 21:29:19 grid currents: [0.31 0.64 0.35]A
[site ] DEBUG 2025/04/22 21:29:20 site power: 330W
[lp-1 ] DEBUG 2025/04/22 21:29:20 charge total import: 6375.155kWh
[lp-1 ] DEBUG 2025/04/22 21:29:20 charger status: A
[site ] DEBUG 2025/04/22 21:29:26 ----
[lp-1 ] DEBUG 2025/04/22 21:29:26 charge power: 0W
[lp-1 ] DEBUG 2025/04/22 21:29:26 charge currents: [0 0 0]A
[site ] DEBUG 2025/04/22 21:29:26 grid power: 30W
[site ] DEBUG 2025/04/22 21:29:27 battery 1 power: 310W
[site ] ERROR 2025/04/22 21:29:30 grid powers: read failed: read tcp 192.168.178.39:57354->192.168.178.125:8899: i/o timeout
[site ] ERROR 2025/04/22 21:29:33 2025-04-22 21:29:26.221693011 +0200 CEST m=+210.518785356 !! 7255ms add[1]: read failed: read tcp 192.168.178.39:59320->192.168.178.125:8899: i/o timeout
[site ] ERROR 2025/04/22 21:29:33 pv 1 power: add[1]: read failed: read tcp 192.168.178.39:59320->192.168.178.125:8899: i/o timeout
[site ] DEBUG 2025/04/22 21:29:35 battery 1 soc: 93%
[site ] DEBUG 2025/04/22 21:29:36 grid currents: [0.31 0.62 0.33]A
[site ] DEBUG 2025/04/22 21:29:36 site power: 340W
[lp-1 ] DEBUG 2025/04/22 21:29:36 charge total import: 6375.155kWh
[lp-1 ] DEBUG 2025/04/22 21:29:36 charger status: A
[site ] DEBUG 2025/04/22 21:29:36 ----

[hrampf]

Das mit dem timeout bei mir weiß ich nicht genau. Wir probieren es mit modbus proxy. Jetzt haben wir die nightly probiert- aber da fährt er nicht hoch. Jetzt wieder Version 202.1. die fähert hoch und geht so einigermaßen mit den bekannten fehlermeldungen image: evcc/evcc:nightly ***@***.***:/opt/evcc# docker logs evcc [main ] INFO 2025/04/21 11:35:08 evcc 0.124.1 (de1fb86) [main ] INFO 2025/04/21 11:35:08 using config file: /etc/evcc.yaml [main ] INFO 2025/04/21 11:35:08 starting ui and api at :7070 [db ] INFO 2025/04/21 11:35:08 using sqlite database: /root/.evcc/evcc.db [EVB-P22217851-1] DEBUG 2025/04/21 11:35:08 waiting for chargepoint: 5m0s [ocpp ] DEBUG 2025/04/21 11:35:08 charge point connected: EVB-P22217851 [main ] FATAL 2025/04/21 11:36:08 cannot create charger 'wallbox1': cannot create charger type 'template': cannot create charger type 'ocpp': ocpp message (229956721): GenericError - Request timed out [main ] FATAL 2025/04/21 11:36:08 will attempt restart in: 5m0s ***@***.***:/opt/evcc# docker logs evcc [main ] INFO 2025/04/21 11:35:08 evcc 0.124.1 (de1fb86) [main ] INFO 2025/04/21 11:35:08 using config file: /etc/evcc.yaml [main ] INFO 2025/04/21 11:35:08 starting ui and api at :7070 [db ] INFO 2025/04/21 11:35:08 using sqlite database: /root/.evcc/evcc.db [EVB-P22217851-1] DEBUG 2025/04/21 11:35:08 waiting for chargepoint: 5m0s [ocpp ] DEBUG 2025/04/21 11:35:08 charge point connected: EVB-P22217851 [main ] FATAL 2025/04/21 11:36:08 cannot create charger 'wallbox1': cannot create charger type 'template': cannot create charger type 'ocpp': ocpp message (229956721): GenericError - Request timed out [main ] FATAL 2025/04/21 11:36:08 will attempt restart in: 5m0s ***@***.***:/opt/evcc# docker logs evcc [main ] INFO 2025/04/21 11:35:08 evcc 0.124.1 (de1fb86) [main ] INFO 2025/04/21 11:35:08 using config file: /etc/evcc.yaml [main ] INFO 2025/04/21 11:35:08 starting ui and api at :7070 [db ] INFO 2025/04/21 11:35:08 using sqlite database: /root/.evcc/evcc.db [EVB-P22217851-1] DEBUG 2025/04/21 11:35:08 waiting for chargepoint: 5m0s [ocpp ] DEBUG 2025/04/21 11:35:08 charge point connected: EVB-P22217851 [main ] FATAL 2025/04/21 11:36:08 cannot create charger 'wallbox1': cannot create charger type 'template': cannot create charger type 'ocpp': ocpp message (229956721): GenericError - Request timed out [main ] FATAL 2025/04/21 11:36:08 will attempt restart in: 5m0s Von: r1st0 ***@***.***> Gesendet: Sonntag, 20. April 2025 09:19 An: evcc-io/evcc ***@***.***> Cc: hrampf ***@***.***>; Author ***@***.***> Betreff: Re: [evcc-io/evcc] SofarSolar: timeout (Discussion #20247) timeout immer noch bei 1s oder ist das mit 3s? � Reply to this email directly, view it on GitHub <#20247 (comment) 7> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BMQWNAGSC5TSSKTNRNG4SFT22 NC4TAVCNFSM6AAAAAB2CI5DAWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTE OBYHA3DSNY> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/BMQWNAAVM4AJMUMSLJP25Y322NC4TA5CNFS M6AAAAAB2CI5DAWWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3T UL5UWJTQAYSVHS.gif> Message ID: ***@***.*** ***@***.***> >

[andig]

aber da fährt er nicht hoch.

Das ja nix hiermit zu tun:

cannot create charger 'wallbox1': cannot
create charger type 'template': cannot create charger type 'ocpp': ocpp
message (229956721): GenericError - Request timed out

[hrampf]

Das wenn ich genau wüsste warum? Mit der alten Version geht es sofort Ich bin ratlos. Von: andig ***@***.***> Gesendet: Montag, 21. April 2025 12:31 An: evcc-io/evcc ***@***.***> Cc: hrampf ***@***.***>; Author ***@***.***> Betreff: Re: [evcc-io/evcc] SofarSolar: timeout (Discussion #20247) aber da fährt er nicht hoch. Das ja nix hiermit zu tun: cannot create charger 'wallbox1': cannot create charger type 'template': cannot create charger type 'ocpp': ocpp message (229956721): GenericError - Request timed out — Reply to this email directly, view it on GitHub <#20247 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BMQWNAH3OTUTT6SPBXD53Y322TCHBAVCNFSM6AAAAAB2CI5DAWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOBZG42TKOA> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/BMQWNABYOTBBFDDQGCRJ4J322TCHBA5CNFSM6AAAAAB2CI5DAWWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAYTGRM.gif> Message ID: ***@***.*** ***@***.***> >

[andig]

!! 6017ms

Keine Antwort innerhalb von 6s. Das ist schon hart. Der alte Timeout war 10s, den könnten wir auch noch wieder herstellen (aktuell 5s). Mehr fällt mir dann nicht mehr ein...

[mcsteevi]

Hallo Andig,

mein name ist Stefan, ich helfe "hrampf" bei der evcc Konfiguration. Unser erster Ansatz war die Abfrageanzahl an den LSE-3 zu vermindern,
indem wir einen modbus proxy konfiguriert hatten. Das hat eigentlich nichts gebracht und wir sind zurück zur Config, wie im ersten Thread hier angegeben. Soeben haben wir die neue evcc 0.203.3 getestet aber da haben wir viel mehr timeouts als mit evcc 0.201.1:

[main ] INFO 2025/04/25 15:35:58 evcc 0.203.3
[main ] INFO 2025/04/25 15:35:58 using config file: /etc/evcc.yaml
[db ] INFO 2025/04/25 15:35:58 using sqlite database: /root/.evcc/evcc.db
[main ] INFO 2025/04/25 15:35:58 listening at :7070
[EVB-P22217851-1] DEBUG 2025/04/25 15:35:58 waiting for chargepoint: 5m0s
[ocpp ] DEBUG 2025/04/25 15:36:01 charge point connected: EVB-P22217851
[EVB-P22217851-1] DEBUG 2025/04/25 15:36:31 failed configuring availability: timeout
[EVB-P22217851-1] WARN 2025/04/25 15:37:02 failed configuring MeterValuesSampledData: timeout
[lp-1 ] DEBUG 2025/04/25 15:37:05 charge total import: 2692.157kWh
...
...
...
[site ] ERROR 2025/04/25 15:37:12 2025-04-25 15:37:06.016694891 +0200 CEST m=+68.406213026 !! 6907ms read failed: read tcp 172.22.0.4:49232->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:37:12 battery 1 power: read failed: read tcp 172.22.0.4:49232->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:37:15 grid powers: read failed: read tcp 172.22.0.4:38994->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:37:18 grid currents: read failed: read tcp 172.22.0.4:39006->192.168.178.87:8899: i/o timeout
...
...
...
[site ] ERROR 2025/04/25 15:37:59 2025-04-25 15:37:53.912543434 +0200 CEST m=+116.302061458 !! 6037ms read failed: read tcp 172.22.0.4:45400->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:37:59 battery 1 power: read failed: read tcp 172.22.0.4:45400->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:38:05 2025-04-25 15:37:53.912529322 +0200 CEST m=+116.302047347 !! 3024ms add[0]: read failed: read tcp 172.22.0.4:45394->192.168.178.87:8899: i/o timeout 2025-04-25 15:37:56.948199707 +0200 CEST m=+119.337717898 !! 9026ms add[0]: read failed: read tcp 172.22.0.4:59694->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:38:05 pv 1 power: add[0]: read failed: read tcp 172.22.0.4:59694->192.168.178.87:8899: i/o timeout
[site ] DEBUG 2025/04/25 15:38:08 battery 1 soc: 47%
[site ] ERROR 2025/04/25 15:38:08 grid power: read failed: read tcp 172.22.0.4:45406->192.168.178.87:8899: i/o timeout
[site ] DEBUG 2025/04/25 15:38:22 ----
[lp-1 ] DEBUG 2025/04/25 15:38:23 charge power: 7W
[lp-1 ] DEBUG 2025/04/25 15:38:23 charge currents: [0.04 0.02 0.02]A
[site ] ERROR 2025/04/25 15:38:29 2025-04-25 15:38:23.793492761 +0200 CEST m=+146.183010860 !! 3001ms read failed: read tcp 172.22.0.4:59706->192.168.178.87:8899: i/o timeout 2025-04-25 15:38:26.811616367 +0200 CEST m=+149.201134522 !! 20ms read failed: dial tcp 192.168.178.87:8899: connect: connection refused 2025-04-25 15:38:26.866289138 +0200 CEST m=+149.255807347 !! 12ms read failed: dial tcp 192.168.178.87:8899: connect: connection refused 2025-04-25 15:38:26.921085945 +0200 CEST m=+149.310604062 !! 3012ms read failed: read tcp 172.22.0.4:42758->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:38:29 battery 1 power: read failed: read tcp 172.22.0.4:42758->192.168.178.87:8899: i/o timeout
[site ] DEBUG 2025/04/25 15:38:30 grid power: -0W
[site ] ERROR 2025/04/25 15:38:34 2025-04-25 15:38:23.793576391 +0200 CEST m=+146.183094508 !! 3026ms add[0]: read failed: dial tcp 192.168.178.87:8899: connect: connection refused 2025-04-25 15:38:26.841821373 +0200 CEST m=+149.231339546 !! 15ms add[0]: read failed: dial tcp 192.168.178.87:8899: connect: connection refused 2025-04-25 15:38:26.886721938 +0200 CEST m=+149.276240055 !! 24ms add[0]: read failed: dial tcp 192.168.178.87:8899: connect: connection refused 2025-04-25 15:38:26.972574992 +0200 CEST m=+149.362093109 !! 7137ms add[0]: read failed: read tcp 172.22.0.4:42762->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:38:34 pv 1 power: add[0]: read failed: read tcp 172.22.0.4:42762->192.168.178.87:8899: i/o timeout
[site ] DEBUG 2025/04/25 15:38:36 battery 1 soc: 47%
[site ] DEBUG 2025/04/25 15:38:40 grid powers: [-0 10 -0]W
[site ] ERROR 2025/04/25 15:38:43 grid currents: read failed: read tcp 172.22.0.4:35258->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:38:46 grid energy: read failed: read tcp 172.22.0.4:33256->192.168.178.87:8899: i/o timeout
[site ] DEBUG 2025/04/25 15:38:46 site power: 100W
...
...
...
[site ] ERROR 2025/04/25 15:39:29 2025-04-25 15:39:22.98464198 +0200 CEST m=+205.374160078 !! 6462ms add[1]: read failed: read tcp 172.22.0.4:44748->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:39:29 pv 1 power: add[1]: read failed: read tcp 172.22.0.4:44748->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:39:32 2025-04-25 15:39:22.984752443 +0200 CEST m=+205.374270541 !! 9476ms read failed: read tcp 172.22.0.4:44760->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:39:32 battery 1 power: read failed: read tcp 172.22.0.4:44760->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:39:38 battery 1 soc: read failed: read tcp 172.22.0.4:38340->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:39:38 grid power: read failed: read tcp 172.22.0.4:38334->192.168.178.87:8899: i/o timeout
[site ] DEBUG 2025/04/25 15:39:52 ----
[lp-1 ] DEBUG 2025/04/25 15:39:53 charge power: 7W
[lp-1 ] DEBUG 2025/04/25 15:39:53 charge currents: [0.04 0.02 0.02]A
[site ] DEBUG 2025/04/25 15:40:00 battery 1 power: -3390W
[site ] ERROR 2025/04/25 15:40:04 2025-04-25 15:39:53.943349069 +0200 CEST m=+236.332867204 !! 3024ms add[0]: read failed: dial tcp 192.168.178.87:8899: connect: connection refused 2025-04-25 15:39:56.985464212 +0200 CEST m=+239.374982366 !! 18ms add[0]: read failed: dial tcp 192.168.178.87:8899: connect: connection refused 2025-04-25 15:39:57.029921126 +0200 CEST m=+239.419439280 !! 12ms add[0]: read failed: dial tcp 192.168.178.87:8899: connect: connection refused 2025-04-25 15:39:57.091494041 +0200 CEST m=+239.481012270 !! 12ms add[0]: read failed: dial tcp 192.168.178.87:8899: connect: connection refused 2025-04-25 15:39:57.154285143 +0200 CEST m=+239.543803278 !! 12ms add[0]: read failed: dial tcp 192.168.178.87:8899: connect: connection refused 2025-04-25 15:39:57.230313912 +0200 CEST m=+239.619832048 !! 26ms add[0]: read failed: dial tcp 192.168.178.87:8899: connect: connection refused 2025-04-25 15:39:57.379945822 +0200 CEST m=+239.769464124 !! 12ms add[0]: read failed: dial tcp 192.168.178.87:8899: connect: connection refused 2025-04-25 15:39:57.657290008 +0200 CEST m=+240.046808218 !! 6978ms add[1]: read failed: read tcp 172.22.0.4:54722->192.168.178.87:8899: i/o timeout
[site ] ERROR 2025/04/25 15:40:04 pv 1 power: add[1]: read failed: read tcp 172.22.0.4:54722->192.168.178.87:8899: i/o timeout

Da sind auch "connection refused" dabei. Es scheint in dieser Version gibt es mehr output und wir haben z.B. !! 9476ms read failed, das sind ja schon an die 10 Sekunden. Die Fehler sind so häufig, dass wir wieder auf die 0.201.1 zurückgehen mussten. Dieser LSE-3 Stick macht nach Firmware Upgrade von SofarSolar massiv Probleme.

Du schreibst weiter oben an "r1st0"
"@r1st0 danke für den Test. Das Gerät ist also etwas zickig und ein einfacher Timeout reicht nicht. Könntest Du für [email protected] Remotezugang für den Modbus Port einrichten, das dass ich das selbst mal testen könnte?"

Wir würden Dir gerne Remotezugang einrichten. Hier wäre nur die Frage wie das technisch funktioniert ? Evcc läuft auf einem Raspi im Docker Container.

Vielen Dank für Deine Mühen !
Gruß
Stefan

[r1st0]

Meldet das doch direkt dem SofarSolar Support. Der soll euch die alte LSE-3 firmware geben. Ich habe die Version ME_0D_270A_1.09 und bekomme bei evcc Version 0.203.1 nur etwa alle 5min timeout errors (was nicht dramatisch ist!).

Remotezugang: Im Router müsstet ihr den Port 8899 von 192.168.178.87 weiterleiten/freigeben. Ich empfehle aber dringend in diesem Fall den Modbus Proxy, da man dort readonly: true einstellen kann. Dann ist es aber die IP von evcc, die den Modbus Port bereitstellt.

[mcsteevi]

Hallo,

vielen Dank für die schnelle Antwort !
Wir waren mit dem SofarSolar Support in Kontakt, aber wegen neuer Cloud wollen die nicht mehr auf die ME_0D_270A_1.09 zurückstellen. Man bekommt die Firmware sonst nirgendwo. Er hatte ME_0E_270A_1.11-D1 bekommen, sagte mir aber heute dass er inzwischen wohl ein neues Update für den LSE-3 von SofarSolar erhalten hat. Bei uns sind die Timeout mit 0.203.1 quasi in jedem Abfrageintervall. Mit 0.201.1 geht es so leidlich.
Da ich nicht vor Ort bin kann ich die Freigabe nicht gleich machen. Ich versuche das nächste Woche hinzubekommen. Wir hatten ja Modbus Proxy schon probiert, da ich dachte es muss dann nicht jeder "Meter" einzeln abfragen und pro Intervall wäre es dann nur eine Modbus Proxy Abfrage. Dem scheint aber nicht so zu sein.

Ich gebe Bescheid, wenn ich dass mit dem Remote Zugang freigeschalten habe.

Danke !
Stefan

[r1st0]

Das mit dem Remotezugang warte mal ab ob @andig das überhaupt braucht. Ich bezweifle es, denn es ist wohl eher ein Problem von SofarSolar.

[andig]

Im aktuellen Nightly sind jetzt wieder 10s timeout eingestellt.

[mcsteevi]

Hallo,
ich könnte morgen vermutlich den Modbus Zugang einrichten. Würde u.U. helfen, dann mache ich das gerne oder macht es keinen Sinn wenn es, wie r1st0 schreibt nur SofarSolar lösen kann ?

Gruß Stefan