Modbus RTU AlphaEss

[chatter80]

Description

Es kommt in dieser Version immer ein time out Fehler von meinen T10

Steps to Reproduce

Habe mal Verzögerungen gesetzt aber keine Abhilfe

⚠️ RETURN TO EVCC TAB → COPY STEP 2 → PASTE HERE

Version

v0.313.0

System

linux/amd64, CEST +02:00

[chatter80]

Configuration (YAML)

no yaml configuration

Configuration (UI)

{
  "charger": [
    {"id":1,"name":"db:1","type":"template","config":{"id":1,"template":"abl","baudrate":38400,"comset":"8E1","host":"192.168.178.160","modbus":"rs485tcpip","port":502},"deviceProduct":"ABL eMH1"}
  ],
  "experimental": true,
  "influx": {"database":"","insecure":false,"org":"","password":"","token":"","url":"","user":""},
  "interval": 30,
  "loadpoints": [
    {"id":2,"name":"db:2","batteryBoostLimit":80,"charger":"db:1","defaultMode":"","limitEnergy":0,"limitSoc":100,"maxCurrent":32,"minCurrent":6,"minSoc":0,"phasesConfigured":3,"planEnergy":0,"planPrecondition":0,"planStrategy":{"continuous":false,"precondition":0},"planTime":"0001-01-01T00:00:00Z","priority":0,"smartCostLimit":null,"smartFeedInPriorityLimit":null,"soc":{"estimate":true,"poll":{"interval":3600000000000,"mode":"charging"}},"thresholds":{"disable":{"delay":180000000000,"threshold":0},"enable":{"delay":60000000000,"threshold":0}},"title":"Garage","ui":{"maxTemp":100,"minTemp":0}}
  ],
  "messenger": [
    {"id":11,"name":"db:11","type":"template","config":{"template":"homeassistant","critical":"false","insecure":false,"uri":"***"},"deviceProduct":"Home Assistant"}
  ],
  "meter": [
    {"id":6,"name":"db:6","type":"template","config":{"id":85,"template":"alpha-ess-smile","baudrate":9600,"comset":"8N1","delay":300000000,"host":"192.168.178.159","maxacpower":"0","modbus":"rs485tcpip","port":502,"timeout":300000000,"usage":"grid"},"deviceProduct":"Alpha ESS Storion SMILE"},
    {"id":12,"name":"db:12","type":"template","config":{"id":85,"template":"alpha-ess-smile","baudrate":9600,"comset":"8N1","delay":300000000,"host":"192.168.178.159","maxacpower":10000,"modbus":"rs485tcpip","port":502,"timeout":300000000,"usage":"pv"},"deviceProduct":"Alpha ESS Storion SMILE","deviceTitle":"AlphaESS T10"},
    {"id":4,"name":"db:4","type":"template","config":{"id":85,"template":"alpha-ess-smile","baudrate":9600,"capacity":17.5,"comset":"8N1","delay":300000000,"host":"192.168.178.159","maxacpower":"0","maxsoc":100,"minsoc":12,"modbus":"rs485tcpip","port":502,"timeout":300000000,"usage":"battery"},"deviceProduct":"Alpha ESS Storion SMILE","deviceTitle":"AlphaEss T10 Batterie"}
  ],
  "mqtt": {"broker":"","caCert":"","clientCert":"","clientID":"","clientKey":"","insecure":false,"password":"","topic":"evcc","user":""},
  "residualPower": 0,
  "shm": {"deviceId":"","deviceSerial":"","vendorId":""},
  "site": {"aux":null,"battery":["db:4"],"consumer":null,"ext":null,"grid":"db:6","pv":["db:12"],"title":"MeinHeim"},
  "tariff": [
    {"id":8,"name":"db:8","type":"template","config":{"template":"fixed","price":0.0758},"deviceProduct":"Fester Preis"},
    {"id":7,"name":"db:7","type":"template","config":{"template":"fixed","price":0.315},"deviceProduct":"Fester Preis"},
    {"id":10,"name":"db:10","type":"template","config":{"template":"solcast","interval":"3h","site":"ac2a-78a8-8588-3a1e","token":"***"},"deviceProduct":"Solcast","deviceTitle":"Solcast"},
    {"id":9,"name":"db:9","type":"template","config":{"template":"electricitymaps-free","token":"***","zone":"DE"},"deviceProduct":"Electricity Maps Free API"}
  ],
  "tariffRefs": {"co2":"db:9","feedIn":"db:8","grid":"db:7","planner":"","solar":["db:10"],"temperature":""},
  "vehicle": [
    {"id":5,"name":"db:5","type":"template","config":{"template":"mercedes","accessToken":"***","autodetectdisabled":false,"cache":"15m","capacity":85,"climaterdisabled":false,"icon":"car","maxPower":11000,"mode":"pv","priority":0,"refreshToken":"***","region":"EMEA","title":"CLA350 EQ","user":"***","wakeupdisabled":false},"deviceProduct":"Mercedes-Benz"}
  ]
}

Logs

[site  ] DEBUG 2026/07/31 21:16:40 solar forecast: produced 65643.700kWh, forecasted 58.429kWh, scale 1123.478
[lp-1  ] DEBUG 2026/07/31 21:16:40 set battery boost limit: 80
[lp-1  ] DEBUG 2026/07/31 21:16:40 phase timer inactive
[lp-1  ] DEBUG 2026/07/31 21:16:40 pv timer inactive
[site  ] DEBUG 2026/07/31 21:16:40 ----
[lp-1  ] DEBUG 2026/07/31 21:16:40 charge power: 0W
[lp-1  ] DEBUG 2026/07/31 21:16:40 charge currents: [0 0 0]A
[site  ] DEBUG 2026/07/31 21:16:41 grid power: 0W
[site  ] ERROR 2026/07/31 21:16:41 grid currents: read failed: read tcp 192.168.178.133:54284->192.168.178.159:502: i/o timeout
[site  ] DEBUG 2026/07/31 21:16:42 battery 1 power: 1540W
[site  ] DEBUG 2026/07/31 21:16:47 battery 1 soc: 58%
[site  ] DEBUG 2026/07/31 21:16:50 pv 1 power: 67W
[site  ] DEBUG 2026/07/31 21:16:51 site power: 1640W
[site  ] DEBUG 2026/07/31 21:16:51 optimizer: optimizing 192 slots until 2026-08-02 21:15:00 +0200 CEST: grid=587, feedIn=587, solar=379, first slot: 13m8s
[site  ] DEBUG 2026/07/31 21:16:51 optimizer: home slots updated with measured 629Wh: [249 280 284 171] -> [629 542 456 286]
[site  ] DEBUG 2026/07/31 21:16:51 solar forecast: produced 65643.700kWh, forecasted 58.429kWh, scale 1123.478
[site  ] DEBUG 2026/07/31 21:16:51 optimizer: pv slots updated with scale 0.00: [8210 3414 1423 0] -> [29 863 714 0]
[lp-1  ] DEBUG 2026/07/31 21:16:51 charger status: B
[lp-1  ] INFO 2026/07/31 21:16:51 car connected
[lp-1  ] DEBUG 2026/07/31 21:16:51 vehicle api cache reset
[lp-1  ] DEBUG 2026/07/31 21:16:51 pv timer elapse
[lp-1  ] DEBUG 2026/07/31 21:16:51 pv timer inactive
[homeassistant] DEBUG 2026/07/31 21:16:51 loading token for http://192.168.178.133:7070-d1f71b85 from database
[lp-1  ] DEBUG 2026/07/31 21:16:51 !! plan: plan time zero
[site  ] DEBUG 2026/07/31 21:16:51 solar forecast: produced 65643.700kWh, forecasted 58.429kWh, scale 1123.478

[andig]

…und gleiches Log von Vorversion geht? Mal Timeout erhöht?

[github-actions]

Thanks for the report. Looking at the log, the actual error is a network-level Modbus TCP timeout, not an application error:

[site  ] ERROR ... grid currents: read failed: read tcp 192.168.178.133:54284->192.168.178.159:502: i/o timeout

This means evcc sent a Modbus request to the AlphaESS Smile RS485↔TCP gateway (192.168.178.159:502, alpha-ess-smile template) and got no response within the configured timeout of 300 ms. Your config has "delay":300000000 and "timeout":300000000 (both 300 ms) on all three alpha-ess-smile meters (grid/pv/battery), which is quite tight for a serial RS485-over-TCP gateway that has to service many register reads per poll cycle (grid alone reads 6 registers, pv up to 8, battery up to 5). You mention trying to change the delay — did you also try raising the timeout value (e.g. to 1000 ms) in the meter's advanced Modbus settings? That's the setting that directly governs this error.

To confirm whether this is a regression rather than a gateway/network hiccup, could you provide:

• Which evcc version you were running before upgrading to v0.313.0 (worked fine there)?
• Whether the timeout happens on every poll cycle or only occasionally — the snippet shown only has a single occurrence and the site recovers immediately afterwards. A longer log excerpt (several minutes / poll cycles) would help clarify the frequency/pattern.

Note: v0.313.0 includes a recent change to how Modbus delay/timeout settings are applied (#31996, "Modbus: unify delay and timeout settings"), so if this only started after upgrading, that's the most likely area to investigate further — but we need the above to confirm.

🤖 Generated with Claude Code

[chatter80]

Danke für den Bericht. Wenn man sich das Protokoll ansieht, ist der eigentliche Fehler ein Netzwerk-Modbus-TCP-Timeout und kein Anwendungsfehler:

[site  ] ERROR ... grid currents: read failed: read tcp 192.168.178.133:54284->192.168.178.159:502: i/o timeout

Das bedeutet, dass evcc eine Modbus-Anfrage an das AlphaESS Smile RS485↔TCP-Gateway (Vorlage) gesendet hat und innerhalb der konfigurierten 300 ms keine Antwort erhalten hat. Deine Konfiguration hat und (beide 300 ms) an allen drei Messern (Netz/PV/Batterie), was ziemlich enges ist für ein serielles RS485-über-TCP-Gateway, das pro Abfragezyklus viele Registerlesearten bedienen muss (Grid allein liest 6 Register, PV bis 8, Batterie bis 5). Du erwähnst, dass du versucht hast, die Verzögerung zu ändern – hast du auch versucht, den Timeout-Wert (z. B. auf 1000 ms) in den erweiterten Modbus-Einstellungen des Messgeräts zu erhöhen? Das ist die Einstellung, die diesen Fehler direkt steuert.192.168.178.159:502``alpha-ess-smile``timeout``"delay":300000000``"timeout":300000000``alpha-ess-smile

Um zu bestätigen, ob es sich um eine Regression und kein Gateway-/Netzwerkproblem handelt, könnten Sie folgendes angeben:

• Welche EVCC-Version hast du vor dem Upgrade verwendet (hat dort gut funktioniert)?v0.313.0
• Egal, ob die Auszeit in jedem Umfragezyklus oder nur gelegentlich auftritt – der gezeigte Ausschnitt hat nur einen einzigen Vorfall und die Seite erholt sich sofort danach. Ein längerer Protokollauszug (mehrere Minuten / Umfragezyklen) würde helfen, die Häufigkeit und das Muster zu klären.

Hinweis: Beinhaltet eine kürzliche Änderung bei der Anwendung von Modbus / Einstellungen (#31996, "Modbus: Vereinheitlichen von Verzögerungs- und Timeout-Einstellungen"), also wenn das erst nach dem Upgrade begann, ist das der wahrscheinlichste Bereich, um weiter zu untersuchen – aber wir brauchen das oben Genannte zur Bestätigung.v0.313.0``delay``timeout

🤖 Erstellt mit Claude Code

sind das sekunden oder millisekunden ?? 300ms sind dann 0,3sek ???
habe bei verzögerung 1 sek also 1000ms drin
Habe das Problem schon seit 2 wochen auch mit der 313er version schon gehabt und mit der davor ... im Juni lief alles noch bestens !

Habe den switch, und die modbus tcp rtu erneuert zum testen problem besteht weiterhin !

Netzwerkkabel ist alles Cat 6 bzw. Cat7

[chatter80]

[site ] ERROR 2026/08/01 15:24:55 grid return energy: read failed: read tcp 192.168.178.133:47142->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 15:25:05 grid currents: read failed: read tcp 192.168.178.133:48096->192.168.178.159:502: i/o timeout

[chatter80]

habe mal so eingestellt und seither keinerlei timeout mehr beobachte mal weiter

frage ist es sind sek keine ms

delay 1sek / 1000ms
wait time 0,03sek 30ms

[chatter80]

Leider vergebens

[site ] ERROR 2026/08/01 19:14:32 pv 1 energy: read failed: read tcp 192.168.178.133:47064->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:18:29 battery 1 energy: read failed: read tcp 192.168.178.133:50146->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:18:30 grid currents: read failed: modbus: response data size '4' does not match request quantity '1'
[site ] ERROR 2026/08/01 19:18:32 battery 1 return energy: read failed: read tcp 192.168.178.133:50180->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:18:34 grid energy: read failed: read tcp 192.168.178.133:50184->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:18:35 battery 1 soc: read failed: modbus: response data size '4' does not match request quantity '1'
[site ] ERROR 2026/08/01 19:18:37 pv 1 power: add[1]: read failed: read tcp 192.168.178.133:50210->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:18:38 pv 1 energy: read failed: read tcp 192.168.178.133:36446->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:18:54 grid currents: read failed: modbus: response data size '4' does not match request quantity '1'
[site ] ERROR 2026/08/01 19:22:25 grid currents: read failed: modbus: response data size '4' does not match request quantity '1'
[site ] ERROR 2026/08/01 19:24:00 grid energy: read failed: read tcp 192.168.178.133:53688->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:27:29 battery 1 return energy: read failed: read tcp 192.168.178.133:55224->192.168.178.159:502: i/o timeout
2026/08/01 19:33:23 [ERR] yamux: Failed to read header: failed to get reader: failed to read frame header: EOF
[site ] ERROR 2026/08/01 19:34:59 grid currents: read failed: read tcp 192.168.178.133:60270->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:37:59 grid currents: read failed: read tcp 192.168.178.133:39616->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:39:26 grid currents: read failed: read tcp 192.168.178.133:39750->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:44:28 battery 1 energy: read failed: read tcp 192.168.178.133:58950->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:46:31 battery 1 soc: read failed: read tcp 192.168.178.133:37020->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:47:31 battery 1 soc: read failed: read tcp 192.168.178.133:44674->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:48:02 grid return energy: read failed: read tcp 192.168.178.133:56116->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:56:26 grid currents: read failed: read tcp 192.168.178.133:48866->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:57:34 pv 1 energy: read failed: read tcp 192.168.178.133:39212->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 19:58:02 grid return energy: read failed: read tcp 192.168.178.133:45500->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 20:06:57 grid currents: read failed: read tcp 192.168.178.133:60220->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 20:09:55 grid currents: read failed: modbus: response data size '4' does not match request quantity '1'
[site ] ERROR 2026/08/01 20:12:32 grid return energy: read failed: read tcp 192.168.178.133:32892->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 20:20:04 pv 1 energy: read failed: read tcp 192.168.178.133:40986->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/01 20:22:29 grid currents: read failed: read tcp 192.168.178.133:57138->192.168.178.159:502: i/o timeout

[chatter80]

Die komplette vorhersage versäumt es auch...

[chatter80]

[site ] ERROR 2026/08/02 13:06:51 pv 1 power: add[3]: read failed: read tcp 192.168.178.133:59746->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/02 13:17:44 grid currents: read failed: read tcp 192.168.178.133:51176->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/02 13:26:46 grid currents: read failed: read tcp 192.168.178.133:50252->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/02 13:30:48 pv 1 power: add[3]: read failed: read tcp 192.168.178.133:36510->192.168.178.159:502: i/o timeout
[site ] ERROR 2026/08/02 13:32:49 battery 1 soc: read failed: read tcp 192.168.178.133:38260->192.168.178.159:502: i/o timeout
[site ] WARN 2026/08/02 13:32:49 battery soc: read failed, keeping last 100%

[naltatis]

frage ist es sind sek keine ms
delay 1sek / 1000ms
wait time 0,03sek 30ms

Ja korrekt. Im UI werden hier Sekunden eingetragen (siehe sichtbare Einheit). Kommazahlen werden automatisch umgerechnet. #32458 behebt einen Eingabe-Bug bei dem, abhängig vom Locale und System, die erste 0 nach dem Komma abgelehnt wurde. Aber in deinem Screenshot sieht man, dass die Eingabe korrekt ist.

[chatter80]

frage ist es sind sek keine ms delay 1sek / 1000ms Wartezeit 0,03sek 30ms

Ja korrekt. Im UI werden hier Sekunden eingetragen (siehe sichtbare Einheit). Kommazahlen werden automatisch umgerechnet. #32458 behebt einen Eingabe-Bug bei dem, abhängig vom Locale und System, die erste 0 nach dem Komma abgelehnt wurde. Aber in deinem Screenshot sieht man, dass die Eingabe korrekt ist.

habe leider immer noch timeouts

der rtu tcp adapter ist so eingestellt:

die Max Wait time war immer 224ms und habe ich nun erhöht ...
trotzdem kommen immer wieder timeouts

Beim Netzzähler / PV& Batterie
sind die erweiterten Einstellungen so :

zeitüberschreitung "2 sek"
verzögerung aktuell "keine"

egal was ich da eintrage es kommen immer sporatische timeouts

[site ] ERROR 2026/08/03 09:58:38 pv 1 energy: read failed: read tcp 192.168.178.133:38154->192.168.178.159:502: i/o timeout