Exception Response(131, 3, None)

[glyn12]

Hi,

I previously had my system (SE6000h + SE3000 + G100 Meter) working fine, however, after a power cut, I now hit this exception (131,3, none).

I believe I have fully removed and then re-installed in HA, but no change
The IP address of the SE6000h (the master & where G100 meter is connected is unchanged - fixed IP)
The settings in SetApp all match (id's of 1 & 126, port 502, IP address)
I have tried re-booting the SE6000h (turning it off and on again)
I have tried re-booting the G100 Meter (turning it off and on again)

I also have a Victron Multiplus, which is showing data listening to the same port. I do recall that it states that only one connection is supported according the SolarEdge doc, but I have tried removing the modbus connection from the Victron inverter to no avail (and it previously worked with both HA and victron listening). I can see the SE6000h modbus values via my Victron HA integration and on the Victron VRM monitoring, so I am pretty confident that the SolarEdge is still broadcasting.

Using a basic TCP Modbus listening app, I can connect to the solaredge.

Any suggestion of the meaning of the exception, and what other steps I can take to try to resolve would be gratefully received!
Thanks Glyn.

[WillCodeForCats]

Try turning off all of the configure options except leave on "Auto-Detect Meters".

[glyn12]

Thanks for the reply, I have figured it out after trying that and then looking at the logs - my inverters have lost connection with each other, so I can only connect to id=126 (the SC6000h), and trying to connect to the one with id=1 causes the exception.

So I'm now all up an running - but only one inverter - so I'll go and debug why they've lost their RS485 connection!

[WillCodeForCats]

I will make a note to see if I can make the integration give a better error message or something when an inverter connection is lost.

[nicola-spreafico]

Hello,
I also started receiving Response(131, 3, None).

From HA history, last data is 3 days ago, February 3th 10.40 AM.

From my understanding on this topic it means the the inverter lost connection?
I haven't changed recently network configuration and it was working fine

Inverter is connected to local network, ping is responding, also nmap is showing the port as open.

This is the second inverter, configured as "follower" and the modbus ID 2, but it has its own network connectivity (in fact I'm using the direct IP to the 2nd inverter, it does not receive connection from the leader)

Any suggestions? I already tried rebooting the inverter

[WillCodeForCats]

It means the ID is incorrect or additional features like battery or additional entities are no longer available over modbus possibly due to firmware update on the inverter.

[nicola-spreafico]

Thank you for your suggestions. I connected to the inverter and in fact I found a wrong configuration, I don't know when and how it got changed, I haven't touched anything... Basically the connectivity configuration was set to "RS485 leader" instead of directly WiFi, also the ID wasn't 2 anymore but it was 3. I now reverted connection to WiFi and restored ID to 2.

At first I didn't have the Response 131 error anymore, but instead I was getting a connection error:

Waiting few minutes and configuring from scratch the integration made the change:
Data are now available: