Firmware 4.25.15 bug or solaredge is closing modbus?

[LightBridge16]

Describe the bug

Hi,

I have the latest firmware but now I can’t get data from older inverters with display anymore 😥.

Inverter model SE3680H-RW000BEN4 without a display is Master connectivity internet over WiFi.

Wattnode meter on RS485-1
Inverter with display and storage/ SESTI Tesla Powerwall gen 1 —> 2 batteries.

Your beautiful script can’t get data from the older inverters over modbus anymore. Is this a bug at SolarEdge side or just a step closer to facing out older hardware?

Expected behavior

?

Screenshots

No response

Diagnostic File

Is privé ask for it

Debug logs

Home Assistant Version

Latest

solaredge-modbus-multi Version

3.3.6

Installation Type

HAOS

Read the Instructions

• My configuration follows https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Configuration
• I have read the Known Issues https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Known-Issues
• This issue is not about a template error (do not report template errors, read https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Template-Design-Notes)

Additional Context

No response

[WillCodeForCats]

You may have to turn modbus/tcp off then back on if stops responding.

https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Known-Issues#inverter-stops-responding-after-firmware-update

[LightBridge16]

Sorry but after turning Modbus off and on it’s the same.

[rogervdh]

Just installed a Solaredge SE3500H second hand inverter, the firmware was updated to 4.25.15 during provisioning and it seems that I have the same issue. The integration discovers the inverter automatically:

But adding fails. I have tried manual adding, port 502, etc., but without success. Maybe the same issue as LightBridge16?

[WillCodeForCats]

You might have to turn on debug logging and see what it does when it tries to scan.

[LightBridge16]

I got response from solaredge in Dutch

“ Geachte klant,

Bedankt voor uw contact met de technische ondersteuning van SolarEdge!

Het probleem met de Powerwall is geen bekend probleem. Recent is er een API-upgrade uitgevoerd en het lijkt erop dat er momenteel problemen zijn met systemen van derden en de rapportage van gegevens. Ons team is op de hoogte van het probleem en werkt aan een oplossing.

We raden u aan het systeem te monitoren terwijl de nodige oplossingen worden geïmplementeerd. Laat het ons weten als u verdere hulp nodig heeft. Als uw probleem hiermee is opgelost, kunnen we deze case sluiten. Bedankt.”

[jqmons]

SE3680H-RW000BNN4 on CPU 4.25.15, DSP1 1.0.2208 and DSP2 2.0.1308, linked over ethernet to SolarEdge Commercial Gateway SE1000-CCG-G-S1 on 3.2537, linked over RS-485 to MTR-240-3PC1-D-A-MW (configured as SE-RGMTR-1D-240C-A import+export meter). More reliable then Solaredge Home Network with no option for a direct RS-485-connection I thought my antique setup would give problems, but all is working fine with SolarEdge Modbus Multi version 3.3.9.

[LightBridge16]

Home net is needed for the latest ev charger unfortunately 😉

[LightBridge16]

SE3680H-RW000BNN4 on CPU 4.25.15, DSP1 1.0.2208 and DSP2 2.0.1308, linked over ethernet to SolarEdge Commercial Gateway SE1000-CCG-G-S1 on 3.2537, linked over RS-485 to MTR-240-3PC1-D-A-MW (configured as SE-RGMTR-1D-240C-A import+export meter). More reliable then Solaredge Home Network with no option for a direct RS-485-connection I thought my antique setup would give problems, but all is working fine with SolarEdge Modbus Multi version 3.3.9.

I have a cable only for rs485 not networking