Open djfanatix opened 1 month ago
Turn off the "Keep Modbus Open" option.
I also need you to upload your diagnostic file and turn on pymodbus
debugging:
https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Integration-Diagnostics
The issue appears to be that pymodbus
isn't connected after sending a connect call:
2024-10-12 07:02:40.521 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Connecting to 192.168.1.120:1502 ...
2024-10-12 07:02:40.527 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] coordinator timeout is 10.8
2024-10-12 07:02:46.532 ERROR (MainThread) [pymodbus.logging] Cancel send, because not connected!
2024-10-12 07:02:46.532 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Disconnectng from 192.168.1.120:1502 (clear_client=False).
home-assistant_solaredge_modbus_multi_2024-10-13T19-34-18.165Z.log
Hereby with Pymodbus logs attached.
The issue appears to be that
pymodbus
isn't connected after sending a connect call:2024-10-12 07:02:40.521 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Connecting to 192.168.1.120:1502 ... 2024-10-12 07:02:40.527 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] coordinator timeout is 10.8 2024-10-12 07:02:46.532 ERROR (MainThread) [pymodbus.logging] Cancel send, because not connected! 2024-10-12 07:02:46.532 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Disconnectng from 192.168.1.120:1502 (clear_client=False).
I think I have the same problem. Appeard first time a few days ago and today again.
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: pymodbus.logging
Quelle: custom_components/solaredge_modbus_multi/hub.py:506
Integration: SolarEdge Modbus Multi (Dokumentation, Probleme)
Erstmals aufgetreten: 11:41:15 (152 Vorkommnisse)
Zuletzt protokolliert: 15:40:11
Cancel send, because not connected!
Here my diagnostic file and logs, maybe it can help you to find the problem
config_entry-solaredge_modbus_multi-01JBEQY3F3CQFE50B72DWABGRF (1).json home-assistant_solaredge_modbus_multi_2024-11-05T15-12-34.479Z.log
The update of the Inline Meter to 1.0.90 fix the bug within my homeassistsnt environment
How to update the inline Meter? My has Firmware: 1.0.81
Am So., 24. Nov. 2024 um 17:46 Uhr schrieb GpdVatter < @.***>:
The update of the Inline Meter to 1.0.90 fix the bug within my homeassistsnt environment
— Reply to this email directly, view it on GitHub https://github.com/WillCodeForCats/solaredge-modbus-multi/issues/687#issuecomment-2496102935, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHUEKP4KKQMKDTZQ5R3Z6N32CH7HNAVCNFSM6AAAAABP2EMCSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJWGEYDEOJTGU . You are receiving this because you are subscribed to this thread.Message ID: @.*** com>
Describe the bug
As discussed on the HA community forum, hereby some logs when Solaredge modbus crashes. I have an inverter with display (upgraded with Setapp, latest FW), a meter and Storedge.
I use a modbus proxy, but the crashes also when I tested the integration with a direct connection without other modbus interface. I know have an automation to restart the modbus proxy when the freezing occurs.
Expected behavior
work fine
Screenshots
No response
Diagnostic File
solaredgelog.log
Debug logs
Home Assistant Version
2024.10.2
solaredge-modbus-multi Version
3.0.0
Installation Type
HAOS
Read the Instructions
Additional Context
No response