solaredge-modbus-multi icon indicating copy to clipboard operation
solaredge-modbus-multi copied to clipboard

Published 20 hours ago • verified publisher icon WillCodeForCats

Integration will not connect

Open Menz01 opened this issue 5 months ago • 53 comments

Describe the bug

integration will no longer connect and i see this:

Failed setup, will retry: Modbus error: Modbus Error: [Input/Output] Request cancelled outside pymodbus

Expected behavior

after a restart of the system i am expecting the integration to connect as it always had been

Screenshots

Image Image

Diagnostic File

i don't see a "download diagnostics"

Image

Debug logs

everytime i try and upload i am told its too long. not sure what to trim out that you may need to see

Home Assistant Version

2025.7.1

solaredge-modbus-multi Version

3.1.4

Installation Type

HAOS

Read the Instructions

  • [x] My configuration follows https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Configuration
  • [x] I have read the Known Issues https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Known-Issues
  • [x] 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

Menz01 avatar Jul 10 '25 14:07 Menz01

trimmed this part out of the debug logs...

ValueError: 299 is not a valid HTTPStatus 2025-07-10 10:14:46.974 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] solaredge_modbus_multi configuration: inverter_list=[1, 2], detect_meters=True, detect_batteries=False, detect_extras=True, keep_modbus_open=False, adv_storage_control=False, adv_site_limit_control=False, allow_battery_energy_reset=False, sleep_after_write=0, battery_rating_adjust=0, 2025-07-10 10:14:46.974 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] pymodbus version 3.9.2 2025-07-10 10:14:46.974 DEBUG (MainThread) [custom_components.solaredge_modbus_multi] Retry limit=5 time=800 ratio=3 2025-07-10 10:14:46.975 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] New AsyncModbusTcpClient: reconnect_delay=0 reconnect_delay_max=3 timeout=3 retries=3 2025-07-10 10:14:46.975 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Connecting to 192.168.0.129:1502 ... 2025-07-10 10:14:47.077 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] coordinator timeout is 67.2 2025-07-10 10:14:47.077 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for inverter at 192.168.0.129 ID 1 2025-07-10 10:14:47.110 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: Registers received=69 requested=69 address=40000 result=ReadHoldingRegistersResponse(dev_id=1, transaction_id=1, address=0, count=0, bits=[], registers=[21365, 28243, 1, 65, 21359, 27745, 29253, 25703, 25888, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 21317, 14134, 12336, 18477, 21843, 12336, 12354, 17737, 13312, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 12336, 12340, 11824, 12338, 12846, 12336, 13364, 0, 14132, 12356, 17217, 13892, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1], status=1) 2025-07-10 10:14:47.110 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_SunSpec_ID 0x53756e53<class 'int'> 2025-07-10 10:14:47.110 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_SunSpec_DID 0x1<class 'int'> 2025-07-10 10:14:47.110 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_SunSpec_Length 0x41<class 'int'> 2025-07-10 10:14:47.110 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_Device_address 0x1<class 'int'> 2025-07-10 10:14:47.110 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_Manufacturer SolarEdge<class 'str'> 2025-07-10 10:14:47.110 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_Model SE7600H-US000BEI4<class 'str'> 2025-07-10 10:14:47.110 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_Option <class 'str'> 2025-07-10 10:14:47.110 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_Version 0004.0022.0044<class 'str'> 2025-07-10 10:14:47.110 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_SerialNumber 740DCA6D<class 'str'> 2025-07-10 10:14:47.132 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: Registers received=9 requested=9 address=40121 result=ReadHoldingRegistersResponse(dev_id=1, transaction_id=2, address=0, count=0, bits=[], registers=[1, 65, 21359, 27745, 29253, 25703, 25856, 0, 0], status=1) 2025-07-10 10:14:47.132 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1 MMPPT: mmppt_DID 0x1 <class 'int'> 2025-07-10 10:14:47.132 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1 MMPPT: mmppt_Length 0x41 <class 'int'> 2025-07-10 10:14:47.132 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1 MMPPT: mmppt_Units 0x0 <class 'int'> 2025-07-10 10:14:47.132 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1 is NOT Multiple MPPT 2025-07-10 10:14:47.132 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for meter I1M1 2025-07-10 10:14:47.172 ERROR (MainThread) [homeassistant] Error doing job: Unclosed client session (None) 2025-07-10 10:14:47.173 ERROR (MainThread) [homeassistant] Error doing job: Unclosed connector (None) 2025-07-10 10:14:47.177 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: Registers received=67 requested=67 address=40121 result=ReadHoldingRegistersResponse(dev_id=1, transaction_id=3, address=0, count=0, bits=[], registers=[1, 65, 21359, 27745, 29253, 25703, 25856, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 21317, 11602, 18253, 21586, 11569, 17453, 12852, 12355, 11586, 0, 0, 0, 0, 0, 0, 0, 20594, 28516, 30051, 29801, 28526, 0, 0, 0, 14137, 0, 0, 0, 0, 0, 0, 0, 13873, 13111, 12598, 13881, 13824, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1], status=1) 2025-07-10 10:14:47.177 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_SunSpec_DID 0x1 <class 'int'> 2025-07-10 10:14:47.177 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_SunSpec_Length 0x41 <class 'int'> 2025-07-10 10:14:47.177 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_Device_address 0x1 <class 'int'> 2025-07-10 10:14:47.177 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_Manufacturer SolarEdge <class 'str'> 2025-07-10 10:14:47.177 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_Model SE-RGMTR-1D-240C-B <class 'str'> 2025-07-10 10:14:47.177 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_Option Production <class 'str'> 2025-07-10 10:14:47.177 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_Version 79 <class 'str'> 2025-07-10 10:14:47.177 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_SerialNumber 613716696 <class 'str'> 2025-07-10 10:14:47.177 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Found I1M1 2025-07-10 10:14:47.177 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for meter I1M2 2025-07-10 10:14:47.248 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: Registers received=67 requested=67 address=40295 result=ReadHoldingRegistersResponse(dev_id=1, transaction_id=4, address=0, count=0, bits=[], registers=[1, 65, 21359, 27745, 29253, 25703, 25856, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 21317, 11602, 18253, 21586, 11569, 17453, 12852, 12355, 11586, 0, 0, 0, 0, 0, 0, 0, 17784, 28783, 29300, 11081, 28016, 28530, 29696, 0, 14137, 0, 0, 0, 0, 0, 0, 0, 13873, 13111, 12598, 13881, 13824, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1], status=1) 2025-07-10 10:14:47.248 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_SunSpec_DID 0x1 <class 'int'> 2025-07-10 10:14:47.248 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_SunSpec_Length 0x41 <class 'int'> 2025-07-10 10:14:47.248 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_Device_address 0x1 <class 'int'> 2025-07-10 10:14:47.248 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_Manufacturer SolarEdge <class 'str'> 2025-07-10 10:14:47.248 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_Model SE-RGMTR-1D-240C-B <class 'str'> 2025-07-10 10:14:47.248 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_Option Export+Import <class 'str'> 2025-07-10 10:14:47.248 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_Version 79 <class 'str'> 2025-07-10 10:14:47.248 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_SerialNumber 613716696 <class 'str'> 2025-07-10 10:14:47.248 WARNING (MainThread) [custom_components.solaredge_modbus_multi.hub] Duplicate serial 613716696 on I1M2 2025-07-10 10:14:47.248 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Found I1M2 2025-07-10 10:14:47.248 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for meter I1M3 2025-07-10 10:14:47.287 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: Registers received=67 requested=67 address=40469 result=ReadHoldingRegistersResponse(dev_id=1, transaction_id=5, address=0, count=0, bits=[], registers=[701, 153, 1, 1, 65535, 1, 0, 0, 65535, 65535, 193, 193, 11, 100, 32768, 2461, 1230, 0, 60009, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 32768, 32768, 32768, 32768, 32768, 32768, 32768, 32768, 32768, 65535, 65535, 65535, 2461, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 32768, 32768, 32768], status=1) 2025-07-10 10:14:47.288 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_SunSpec_DID 0x2bd <class 'int'> 2025-07-10 10:14:47.288 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_SunSpec_Length 0x99 <class 'int'> 2025-07-10 10:14:47.288 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_Device_address 0x8000 <class 'int'> 2025-07-10 10:14:47.288 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_Manufacturer d <class 'str'> 2025-07-10 10:14:47.288 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_Model i <class 'str'> 2025-07-10 10:14:47.288 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_Option <class 'str'> 2025-07-10 10:14:47.288 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_Version <class 'str'> 2025-07-10 10:14:47.288 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_SerialNumber <class 'str'> 2025-07-10 10:14:47.288 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: Meter 3 ident incorrect or not installed. 2025-07-10 10:14:47.288 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for inverter at 192.168.0.129 ID 2 2025-07-10 10:14:47.454 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2: Registers received=69 requested=69 address=40000 result=ReadHoldingRegistersResponse(dev_id=2, transaction_id=6, address=0, count=0, bits=[], registers=[21365, 28243, 1, 65, 21359, 27745, 29253, 25703, 25888, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 21317, 13872, 12336, 18477, 21843, 12336, 12354, 17737, 13312, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 12336, 12340, 11824, 12338, 13102, 12336, 12855, 0, 14132, 12356, 16697, 16709, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2], status=1) 2025-07-10 10:14:47.454 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2: C_SunSpec_ID 0x53756e53<class 'int'> 2025-07-10 10:14:47.454 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2: C_SunSpec_DID 0x1<class 'int'> 2025-07-10 10:14:47.454 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2: C_SunSpec_Length 0x41<class 'int'> 2025-07-10 10:14:47.454 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2: C_Device_address 0x2<class 'int'> 2025-07-10 10:14:47.454 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2: C_Manufacturer SolarEdge<class 'str'> 2025-07-10 10:14:47.454 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2: C_Model SE6000H-US000BEI4<class 'str'> 2025-07-10 10:14:47.454 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2: C_Option <class 'str'> 2025-07-10 10:14:47.454 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2: C_Version 0004.0023.0027<class 'str'> 2025-07-10 10:14:47.454 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2: C_SerialNumber 740DA9AE<class 'str'> 2025-07-10 10:14:47.602 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2: Registers received=9 requested=9 address=40121 result=ReadHoldingRegistersResponse(dev_id=2, transaction_id=7, address=0, count=0, bits=[], registers=[1, 65, 21359, 27745, 29253, 25703, 25856, 0, 0], status=1) 2025-07-10 10:14:47.603 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2 MMPPT: mmppt_DID 0x1 <class 'int'> 2025-07-10 10:14:47.603 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2 MMPPT: mmppt_Length 0x41 <class 'int'> 2025-07-10 10:14:47.603 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2 MMPPT: mmppt_Units 0x0 <class 'int'> 2025-07-10 10:14:47.603 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2 is NOT Multiple MPPT 2025-07-10 10:14:47.603 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for meter I2M1 2025-07-10 10:14:47.736 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2: Registers received=67 requested=67 address=40121 result=ReadHoldingRegistersResponse(dev_id=2, transaction_id=8, address=0, count=0, bits=[], registers=[1, 65, 21359, 27745, 29253, 25703, 25856, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 21317, 11602, 18253, 21586, 11569, 17453, 12852, 12355, 11586, 0, 0, 0, 0, 0, 0, 0, 20594, 28516, 30051, 29801, 28526, 0, 0, 0, 14137, 0, 0, 0, 0, 0, 0, 0, 13873, 13111, 12596, 12593, 13568, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1], status=1) 2025-07-10 10:14:47.736 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M1: C_SunSpec_DID 0x1 <class 'int'> 2025-07-10 10:14:47.736 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M1: C_SunSpec_Length 0x41 <class 'int'> 2025-07-10 10:14:47.736 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M1: C_Device_address 0x1 <class 'int'> 2025-07-10 10:14:47.736 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M1: C_Manufacturer SolarEdge <class 'str'> 2025-07-10 10:14:47.736 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M1: C_Model SE-RGMTR-1D-240C-B <class 'str'> 2025-07-10 10:14:47.736 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M1: C_Option Production <class 'str'> 2025-07-10 10:14:47.736 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M1: C_Version 79 <class 'str'> 2025-07-10 10:14:47.736 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M1: C_SerialNumber 613714115 <class 'str'> 2025-07-10 10:14:47.736 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Found I2M1 2025-07-10 10:14:47.736 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for meter I2M2 2025-07-10 10:14:47.883 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2: Registers received=67 requested=67 address=40295 result=ReadHoldingRegistersResponse(dev_id=2, transaction_id=9, address=0, count=0, bits=[], registers=[701, 153, 1, 1, 65535, 1, 0, 0, 65535, 65535, 226, 226, 12, 100, 32768, 2458, 1229, 0, 60013, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 32768, 32768, 32768, 32768, 32768, 32768, 32768, 32768, 32768, 65535, 65535, 65535, 2458, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 32768, 32768, 32768], status=1) 2025-07-10 10:14:47.884 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M2: C_SunSpec_DID 0x2bd <class 'int'> 2025-07-10 10:14:47.884 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M2: C_SunSpec_Length 0x99 <class 'int'> 2025-07-10 10:14:47.884 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M2: C_Device_address 0x8000 <class 'int'> 2025-07-10 10:14:47.884 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M2: C_Manufacturer d <class 'str'> 2025-07-10 10:14:47.884 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M2: C_Model m <class 'str'> 2025-07-10 10:14:47.884 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M2: C_Option <class 'str'> 2025-07-10 10:14:47.884 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M2: C_Version <class 'str'> 2025-07-10 10:14:47.884 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M2: C_SerialNumber <class 'str'> 2025-07-10 10:14:47.885 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M2: Meter 2 ident incorrect or not installed. 2025-07-10 10:14:47.885 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for meter I2M3 2025-07-10 10:14:47.995 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2: Registers received=67 requested=67 address=40469 result=ReadHoldingRegistersResponse(dev_id=2, transaction_id=10, address=0, count=0, bits=[], registers=[65535, 0, 1, 2, 65535, 63487, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 0, 65534, 0, 0, 65535, 0, 0, 703, 17, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65534, 65533, 704, 65, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535], status=1) 2025-07-10 10:14:47.996 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M3: C_SunSpec_DID 0xffff <class 'int'> 2025-07-10 10:14:47.996 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M3: C_SunSpec_Length 0x0 <class 'int'> 2025-07-10 10:14:47.996 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M3: C_Device_address 0xffff <class 'int'> 2025-07-10 10:14:47.996 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M3: C_Manufacturer <class 'str'> 2025-07-10 10:14:47.996 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M3: C_Model <class 'str'> 2025-07-10 10:14:47.996 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M3: C_Option <class 'str'> 2025-07-10 10:14:47.996 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M3: C_Version <class 'str'> 2025-07-10 10:14:47.996 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M3: C_SerialNumber A <class 'str'> 2025-07-10 10:14:47.996 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I2M3: Meter 3 ident incorrect or not installed. 2025-07-10 10:14:48.042 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: Registers received=8 requested=8 address=40044 result=ReadHoldingRegistersResponse(dev_id=1, transaction_id=11, address=0, count=0, bits=[], registers=[12336, 12340, 11824, 12338, 12846, 12336, 13364, 0], status=1) 2025-07-10 10:14:48.073 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: Registers received=40 requested=40 address=40069 result=ReadHoldingRegistersResponse(dev_id=1, transaction_id=12, address=0, count=0, bits=[], registers=[102, 50, 784, 784, 65535, 65535, 65534, 2456, 65535, 65535, 1228, 1228, 65535, 65535, 19242, 65535, 60012, 65533, 19274, 65535, 11112, 65534, 9983, 65534, 255, 24533, 0, 5289, 65533, 3693, 65535, 19535, 65535, 32768, 4056, 32768, 32768, 65534, 4, 0], status=1)

Menz01 avatar Jul 10 '25 14:07 Menz01

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.

You can also try turning off the "Auto-Detect Additional Entities" option.

WillCodeForCats avatar Jul 10 '25 14:07 WillCodeForCats

hmmmm just disabling "auto detect additional entities" seems to have fixed the issue. i wonder why that is?

Menz01 avatar Jul 10 '25 16:07 Menz01

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, which is what older firmware does like the version my inverters are at (0004.0014.0229). Either some or all newer versions change that behavior can changed to stop responding and time out or fail connection instead of returning the "unsupported" response.

I've tried several ways to work around this but based on what happened with your inverters it's still not good enough for the best user experience.

Many releases ago the default for "Auto-Detect Additional Entities" was enabled. I changed the default to disabled because of this issue for new users. But if you were using the integration before the default changed the old default would continue, so you might not know why it suddenly is having a problem when it doesn't look like anything changed.

WillCodeForCats avatar Jul 10 '25 16:07 WillCodeForCats

thank you

Menz01 avatar Jul 10 '25 17:07 Menz01

Seems like there's been firmware pushed out that causes issues with Modbus TCP - my inverter went offline overnight.

I was on 4.22.44. I am now on 4.23.36, which isn't even listed on the SE Website

At 06:43 the connection failed and no amount of Integration or Home Assistant restarts would bring it back.

The integrations failed to connect:

2025-07-13 06:43:54.893 WARNING (MainThread) [pymodbus.logging] Failed to connect [Errno 111] Connect call failed ('10.0.111.75', 1502)                                                                                                    
2025-07-13 06:44:10.380 WARNING (MainThread) [pymodbus.logging] Failed to connect [Errno 111] Connect call failed ('10.0.111.75', 1502)                                                                                                    
2025-07-13 06:44:11.482 WARNING (MainThread) [pymodbus.logging] Failed to connect [Errno 111] Connect call failed ('10.0.111.75', 1502)                                                                                                    
2025-07-13 06:44:13.586 WARNING (MainThread) [pymodbus.logging] Failed to connect [Errno 111] Connect call failed ('10.0.111.75', 1502)                                                                                                    
2025-07-13 06:44:17.688 WARNING (MainThread) [pymodbus.logging] Failed to connect [Errno 111] Connect call failed ('10.0.111.75', 1502)                                                                                                    
2025-07-13 06:44:25.800 WARNING (MainThread) [pymodbus.logging] Failed to connect [Errno 111] Connect call failed ('10.0.111.75', 1502)                                                                                                    
2025-07-13 06:44:41.903 WARNING (MainThread) [pymodbus.logging] Failed to connect [Errno 111] Connect call failed ('10.0.111.75', 1502)                                                                                                    
2025-07-13 06:44:57.377 WARNING (MainThread) [pymodbus.logging] Failed to connect [Errno 111] Connect call failed ('10.0.111.75', 1502)

Probes showed no response at all from the inverter on Port 1502, I had to physically connect to the inverter from my phone and go into the SE App to diagnose.

It showed that Modbus TCP was still enabled.

However, once I had set Modbus TCP to disabled, than then back to Enabled it immediately started accepting connections again - hopefully this will help someone else!

cyberkryten avatar Jul 13 '25 11:07 cyberkryten

Seems like there's been firmware pushed out that causes issues with Modbus TCP - my inverter went offline overnight.

I was on 4.22.44. I am now on 4.23.36, which isn't even listed on the SE Website

At 06:43 the connection failed and no amount of Integration or Home Assistant restarts would bring it back.

The integrations failed to connect:

2025-07-13 06:43:54.893 WARNING (MainThread) [pymodbus.logging] Failed to connect [Errno 111] Connect call failed ('10.0.111.75', 1502)

Probes showed no response at all from the inverter on Port 1502, I had to physically connect to the inverter from my phone and go into the SE App to diagnose.

It showed that Modbus TCP was still enabled.

However, once I had set Modbus TCP to disabled, than then back to Enabled it immediately started accepting connections again - hopefully this will help someone else!

I have the same problem and the same firmware. But I do not have access to the SE App (only monitoring is possible).

Turning off/on the inverter did not work.

I raised a ticket to the SolarEdge support, maybe other can to the same, if they face the same issue!

Spacerat76 avatar Jul 13 '25 12:07 Spacerat76

You can access the inverter settings by moving the momentary switch to the P side and then connecting to the Wifi access point that appears.

Then look at the Wifi settings to see the 'Default Gateway' given. Usually this seems to be 172.16.0.1 so put that address into a web browser on the device that is connected and you'll be able to access the settings from there.

You want Site Communication then Modbus TCP. Change it to Disabled, wait a minute and change it back to Enabled.

Don't touch anything else! All risks your own, etc etc

cyberkryten avatar Jul 13 '25 12:07 cyberkryten

Mine stopped working today too i'm going to have to work out a way to automatically disable and enable ethernet on this solar edge inverter. Annoying that solar edge broke it

joelegg avatar Jul 24 '25 08:07 joelegg

got some connection failed too, since the 24/07 (after an upgrade of the inverter) 2025-07-31 00:28:30.874 WARNING (MainThread) [pymodbus.logging] Failed to connect 2025-07-31 00:38:30.522 WARNING (MainThread) [pymodbus.logging] ERROR: expected transaction 443 but got 442, IGNORING.

jluc2808 avatar Jul 30 '25 22:07 jluc2808

I just wanted to drop in and report that disabling and re-enabling the Modbus TCP setting in the inverter settings > Site Communications (SetApp) worked for me.

I've been using this custom integration for about 3 years now.

I updated my inverter firmware to 4.2.36 in early July. Home Assistant had been reporting quite frequent modbus disconnnections, but they always cleared and reconnected.

Until last night.

I updated Home Assistant Core to 2025.7.4 yesterday morning and at 2133 last night the modbus connection dropped and wouldn't reconnect. I found this issue and tried unchecking the "Auto-Detect Additional Entities" box but that made no difference. I left it for the night knowing that today was going to be a good solar day and the SE app would suffice for now.

This morning I went into the inverter settings in SetApp > Site Communication, for anyone looking, disabled Modbus TCP, waited 30 seconds and enabled it again. Home Assistant picked up the connection again almost instantly.

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 there's anything I can do to help, let me know. Our home energy use is heavily reliant on having the level of control this custom integration gives us so I wouldn't want to see it fall over completely.

Daverover66 avatar Aug 02 '25 08:08 Daverover66

That's the second time in 48 hours my modbus connection has been unable to connect with Home Assistant. Toggling the Modbus TCP setting off and on again worked, again. I've got my polling frequency set to 30s and a Home Assistant automation that reloads the config every 3 hours. Not sure if any of that is helping, or indeed making things worse.

Daverover66 avatar Aug 03 '25 21:08 Daverover66

@Daverover66, i tried to stop and reload (remove all parameter for modbus TCP) the TCP modbus (my inverter is with LCD, so no SetApp) without success

The only thing which working is to remove (physically) the RJ45 (so physical disconnection from the router) then wait until the inverter display the status fault on the TCP/Modbus (failure, no connection on TCP) , then plug again the RJ45 which restore the IP and the dialog on Modbus/TCP

This manipulation restore the TCP/Modbus connection and the dialog restart again with HA

jluc2808 avatar Aug 04 '25 13:08 jluc2808

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 there's anything I can do to help, let me know. Our home energy use is heavily reliant on having the level of control this custom integration gives us so I wouldn't want to see it fall over completely.

There isn't anything I can think of to do with this, and it's worth noting that I don't personally see this problem on my inverters which are both running 0004.0014.0229 which leads me to believe this is a firmware version dependent issue with the inverter.

It's worth noting that the first Modbus/TCP connection needs to be made within 2 minutes or the inverter will close the port, requiring it to be set off and then on again. It's supposed to then leave the port open after the first connection, but I would recommend anyone seeing connection issues that are fixed by cycling the inverter setting to try a maximum of 1 minute polling time in case it's an firmware bug in recent versions that closes the port when it thinks its inactive.

WillCodeForCats avatar Aug 04 '25 17:08 WillCodeForCats

I think you're probably right in thinking this is a firmware version related issue, particularly since your inverters seem to be unaffected. I need to do a couple of follow-up things to see if I can help resolve those for those of us who are affected.

  1. Raise a ticket with Solaredge to see if they can, or will, investigate and possible offer a solution.
  2. Read up on how Modbus/TCP works from a Solaredge perspective.

If you can point me towards any documentation you used when you developed this integration I'd be grateful. I have the Power Control Protocol as well as several other documents, but I'm wondering if there is a comms specific document?

Daverover66 avatar Aug 04 '25 17:08 Daverover66

The latest docs are https://knowledge-center.solaredge.com/sites/kc/files/sunspec-implementation-technical-note.pdf

There's nothing in the latest update to explain what or why they did to cause any issues. As has been noted by many, this was introduced after a firmware update, so it is a SolarEdge issue and not something that can be fixed by this integration.

The problem is on the inverter side as for some reason, it closes the TCP port and stops responding. Nothing can be done about that externally once the port is non-responsive as physical access is required to force it to re-enable with two methods that are reported to work:

a) Manually putting the inverter into it's config mode (using the switch) and then connecting and disabling/re-enabling Modbus over TCP.

b) Physically removing the ethernet cable

For a) there's no way to do this remotely - physical access is required.

For b) depending on your networking gear, HA skills and programming ability you MAY be able to detect and automate the reset (for those with managed switches, logically doing so by disabling the port, waiting and re-enabling will achieve the same thing), but I suspect few have the capability (or the will) to do so.

cyberkryten avatar Aug 04 '25 17:08 cyberkryten

two methods that are reported to work: Physically removing the ethernet cable

I'm pretty sure I tried this the first time I lost the connection and it didn't do anything 🤔

However if this works:

depending on your networking gear, HA skills and programming ability you MAY be able to detect and automate the reset (for those with managed switches, logically doing so by disabling the port, waiting and re-enabling will achieve the same thing), but I suspect few have the capability (or the will) to do so.

Then I have both the capability and the will 😁 so thanks for that suggestion.

Daverover66 avatar Aug 04 '25 18:08 Daverover66

Where is the firmware version listed? I only cause so far (knocking on wood as I type this) I am not having this issue. I would like to confirm if I am on the same firmware version as you

On Mon, Aug 4, 2025, 2:06 PM Daverover66 @.***> wrote:

Daverover66 left a comment (WillCodeForCats/solaredge-modbus-multi#859) https://github.com/WillCodeForCats/solaredge-modbus-multi/issues/859#issuecomment-3151852727

two methods that are reported to work: Physically removing the ethernet cable

I'm pretty sure I tried this the first time I lost the connection and it didn't do anything 🤔

However if this works:

depending on your networking gear, HA skills and programming ability you MAY be able to detect and automate the reset (for those with managed switches, logically doing so by disabling the port, waiting and re-enabling will achieve the same thing), but I suspect few have the capability (or the will) to do so.

Then I have both the capability and the will 😁 so thanks for that suggestion.

— Reply to this email directly, view it on GitHub https://github.com/WillCodeForCats/solaredge-modbus-multi/issues/859#issuecomment-3151852727, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHOXQZ4ISOTRUH2GB4TWE6T3L6OKJAVCNFSM6AAAAACBHFWTGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNJRHA2TENZSG4 . You are receiving this because you authored the thread.Message ID: @.***>

Menz01 avatar Aug 04 '25 18:08 Menz01

It should be an entity in the integration. Mine is sensor.solaredge_i1_version and gives me 0004.0023.0036

Daverover66 avatar Aug 04 '25 18:08 Daverover66

FW version is an entity and in the device info.

WillCodeForCats avatar Aug 04 '25 19:08 WillCodeForCats

Of course mine is now having issues 😕 I have 2 inverters which are slightly different models and each one has a different firmware.

One is 0004.0022.0044

The other is 0004.0023.0027

On Mon, Aug 4, 2025, 3:14 PM Seth @.***> wrote:

WillCodeForCats left a comment (WillCodeForCats/solaredge-modbus-multi#859) https://github.com/WillCodeForCats/solaredge-modbus-multi/issues/859#issuecomment-3152041874

FW version is an entity and in the device info.

— Reply to this email directly, view it on GitHub https://github.com/WillCodeForCats/solaredge-modbus-multi/issues/859#issuecomment-3152041874, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHOXQZ2RNNVNDOXLMBFG2H33L6WJLAVCNFSM6AAAAACBHFWTGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNJSGA2DCOBXGQ . You are receiving this because you authored the thread.Message ID: @.***>

Menz01 avatar Aug 04 '25 21:08 Menz01

My inverter received an update tonight and connected again afterwards. It is now on version 0004.0023.0036. Last working before the issue starting two nights ago was 0004.0022.0044. I guess in between it picked one up that was buggy.

tleichtw avatar Aug 05 '25 04:08 tleichtw

I have 2 inverters as well. Master is on 0004.0023.0036 same as yours. I've had 2 dropped connections today so far. Pulling the ethernet cable and reconnecting does not fix the connection for me. Nor does disabling the network switch port and re-enabling it. The only thing that fixes it for me is to reset it in SetApp. I've raised a support case with Solaredge. The case number is 5988422 you can check progress or reference it in your own case if you have access to the Solaredge Support service.

Daverover66 avatar Aug 05 '25 13:08 Daverover66

@Daverover66 when i disable the connection on the router part, it's not enough, i need to wait until the TCP/Modbus display a fault message of failure in the TCP connect screen of the inverter and then i could reanable the port on the router part, generally the LAN screen will take some seconds (10 or 15) to reenable all the control and re-establish the IP address within the TCP/Modbus parameter.

sometime i need to recharge the modbus solaredge on the HA part.

jluc2808 avatar Aug 05 '25 13:08 jluc2808

I've seen strange behavior with my battery in the last 24 hours. The battery is just completely not being used and just staying at 58% even though it's set to maximize self-consumption. Backup is set to 10%

joelegg avatar Aug 06 '25 00:08 joelegg

I've seen strange behavior with my battery in the last 24 hours. The battery is just completely not being used and just staying at 58% even though it's set to maximize self-consumption. Backup is set to 10%

Are any of the parameters being updated like the Status and Logbook in HA? When mine failed the Status changed to Unknown and Logbook showed B_STATUS_OFF but the SOC constantly reported the same value.

Have a look at the indicator lights (you have to take the plastic side panel off) or logging into the SE portal and going to the faults page to see if there's anything there.

Might be worth powering off Inverter, breakers and battery for a while, then powering back up to see if that restores it, otherwise contact SE support

cyberkryten avatar Aug 06 '25 00:08 cyberkryten

Might be worth powering off Inverter, breakers and battery for a while, then powering back up to see if that restores it, otherwise contact SE support

i'm not comfy doing this - isn't there a particlar order?

i am seeing data in home assisant - no unknowns but the data is wrong.

checking sstatus of inveter no errors appearing when i logged into the site locally (wifi) but the green light is sflashing on inverter and the battery.

joelegg avatar Aug 06 '25 00:08 joelegg

Might be worth powering off Inverter, breakers and battery for a while, then powering back up to see if that restores it, otherwise contact SE support

i'm not comfy doing this - isn't there a particlar order?

i am seeing data in home assisant - no unknowns but the data is wrong.

checking sstatus of inveter no errors appearing when i logged into the site locally (wifi) but the green light is sflashing on inverter and the battery.

data on monitorng.solaredge are wrong when i look at the number (prodution and consume) because they only take the data when the inverter is producing and forget info while the solar production is 0, so all the caculation of % is wrong, otherwise the data show inside the graphic is OK. I see that data filled in the data from inverter/energy meter are either not completed , either wrong (according with the wrong calc of monitoring.solaredge) especially imported and exported data

This append, for me, just after the support apply the new release (3.2537) - my inverter is a SE5K and the previous release was 3.2251 (with a good return)

This is exactly the same time where i encounter the problem with brake of connection

jluc2808 avatar Aug 06 '25 06:08 jluc2808

I've opened a case with solar Red so hopefully they get back to me. My electricity provider is having an electricity Spike. I'm on variable pricing. Amber tomorrow so hopefully it's fixed by then.

On Wed, Aug 6, 2025, 4:14 PM jluc2808 @.***> wrote:

jluc2808 left a comment (WillCodeForCats/solaredge-modbus-multi#859) https://github.com/WillCodeForCats/solaredge-modbus-multi/issues/859#issuecomment-3157537402

Might be worth powering off Inverter, breakers and battery for a while, then powering back up to see if that restores it, otherwise contact SE support

i'm not comfy doing this - isn't there a particlar order?

i am seeing data in home assisant - no unknowns but the data is wrong.

checking sstatus of inveter no errors appearing when i logged into the site locally (wifi) but the green light is sflashing on inverter and the battery.

data on monitorng.solaredge are wrong when i look at the number (prodution and consume) because they only take the data when the inverter is producing and forget info while the solar production is 0, so all the caculation of % is wrong, otherwise the data show inside the graphic is OK. I see that data filled in the data from inverter/energy meter are either not completed , either wrong (according with the wrong calc of monitoring.solaredge) especially imported and exported data

This append, for me, just after the support apply the new release (3.2537)

  • my inverter is a SE5K and the previous release was 3.2251 (with a good return)

This is exactly the same time where i encounter the problem with brake of connection

— Reply to this email directly, view it on GitHub https://github.com/WillCodeForCats/solaredge-modbus-multi/issues/859#issuecomment-3157537402, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7LMIVOAWQ4UQ62DEIXCT33MGMNVAVCNFSM6AAAAACBHFWTGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNJXGUZTONBQGI . You are receiving this because you commented.Message ID: @.***>

joelegg avatar Aug 06 '25 06:08 joelegg

Might be worth powering off Inverter, breakers and battery for a while, then powering back up to see if that restores it, otherwise contact SE support

i'm not comfy doing this - isn't there a particlar order?

There is indeed

Image

Checking the Vdc is not crucial, but if you wait 5 minutes after moving the inverter switch to 0 it should be safe.

Once the battery is off, you can turn the main AC (and DC if you have them) rotary disconnector for your system to turn off the inverter as well. Wait a minute or so then revervse the operation. So main AC (and DCif you have them) rotary disconnector to on wait for the inverter to boot up then power on the battery.

Daverover66 avatar Aug 06 '25 08:08 Daverover66