Modbus Error Messages Solaredge

[The-Paran0id-Andr0id]

Description

Hi evcc team,

I regularly get the following error messages in EVCC. On the loading screen, I see a question mark at the top and no readings from PV, battery or meter. The PV system is from Solaredge.

Log Entries:

[site ] ERROR 2026/08/04 17:24:49 pv 1 power: add[0]: model 103 block 0 point DCW: modbus: response transaction id '11081' does not match request '11083'
[site ] ERROR 2026/08/04 17:24:49 battery 1 power: read failed: modbus: response transaction id '11082' does not match request '11084'
[site ] ERROR 2026/08/04 17:24:49 battery 1 energy: read failed: modbus: response transaction id '11083' does not match request '11085'
[site ] ERROR 2026/08/04 17:24:49 battery 1 return energy: read failed: modbus: response transaction id '11084' does not match request '11086'
[site ] ERROR 2026/08/04 17:24:49 battery 1 soc: read failed: modbus: response transaction id '11085' does not match request '11087'
[site ] WARN 2026/08/04 17:24:49 battery soc: read failed, keeping last 38%
[site ] ERROR 2026/08/04 17:24:49 grid power: read failed: modbus: response transaction id '11080' does not match request '11082'

After restarting evcc:

[main ] FATAL 2026/08/04 17:37:44 meter [db:19] cannot create template 'db:19': cannot create meter type 'template:solaredge-hybrid': cannot create meter type 'custom': power: add[0]: not a SunSpec device
[main ] FATAL 2026/08/04 17:37:44 will attempt restart in: 15m0s

Steps to Reproduce

n/a

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

Version

v0.312.1

System

linux/amd64, CEST +02:00

[LeonSol]

It looks like an access from another system to your solaredge inverter at the same time.

[LeonSol]

Not exactly to say. Somehing caught your requst-id´s in between your call. App, HA, or something else - I don´t know what you are running.

[The-Paran0id-Andr0id]

Running evcc as an HA App. Not using the HA integration of evcc. It was working fine for the last days. Today I already had the error 3 times. Strange...

[The-Paran0id-Andr0id]

I’ve now added the EVCC Modbus proxy to the chain, even though I don’t have any other clients accessing the inverter. But never mind, the request ID errors have gone.

It worked fine for a while, although the setup was very tedious due to timeouts when saving. Now I’m getting these errors and it’s not working with the proxy either.

read failed: modbus: exception “4” (server device failure), function “3”

Does anyone else have any advice for me?

[LeonSol]

This means the device got the call but isn´t able to answer. Therefore a restart of the target device will be the first choice. Probably also an update of the firmware.

[The-Paran0id-Andr0id]

I have try set up the HA Modbus proxy add-on. It is now running smoothly and without errors. The setup in EVCC also worked straight away, without any errors or timeouts. I’ll leave it like this for now. Thanks for your help!