Seth

I went and changed my working system from Device IDs`1,2` to use `1,3` in SetApp and it works fine for me. Here's my diagnostic file as proof: [config_entry-solaredge_modbus_multi-e3b4ad891a831bb72b37a1247705753f.json](https://github.com/user-attachments/files/16787612/config_entry-solaredge_modbus_multi-e3b4ad891a831bb72b37a1247705753f.json)

> Could you please check the code in this old PR and see if there is something that can be missing in your code. I remember I had to invest...

Merging since there are enough success reports from the first pre-release.

Support has to come from the SolarEdge side.

May need to disconnect and reconnect to the modbus device if a context timeout is triggered, or enable pymodbus built in reconnect. Reconnect in pymodbus was disabled intentionally in PR...

Testing with the following settings in `configuration.yaml`: ``` solaredge_modbus_multi: modbus: reconnect_delay: 1.0 # Minimum in seconds.milliseconds before reconnecting. reconnect_delay_max: 16.0 # Maximum in seconds.milliseconds before reconnecting. ```

Pymodbus 3.9 raises `ModbusIOException` in an asyncio timeout context. See PR #864

There should be more logs, I need to see all of them especially the parts where it it tries to read the inverter data up through the coordinator false message....

Your inverters may have had a firmware update recently. SolarEdge changed the way they handle unsupported functions in some firmware versions. The best way is to return an "unsupported" response,...

> I'll continue to monitor, but hopefully we have a temporary fix until the repo owner can implement a fix. > > I'm no coder by the way, but if...