Custom Component solaredge-modbus-multi

Hi there.

Since two days, I am reiving incomplete results in the energy tab.

Looks like there ist a hickup in receiving the data in that screen.

Unfortunately I can’t tell exactly what caused the hickup, as I upgrades BOTH Homeassistant (from 2024.6.4 to 2024.7.1) AND the Solaredge (from 2.4.15 to 2.4.16) in one go.

Anybody else experiencing the same issue maybe?


Try reverting back to Home Assistant 2024.6.4 and wait for 2024.8. A lot of people have issues with 2024.7 regarding the Energy Dashboard.

I haven’t seen any issues with energy dashboard on my system.

Is there an easy way to activate pymodbus logging to troubleshoot issues with the integration?

configuration.yaml

logger:
    logs:
        pymodbus: debug
1 Like

Thanks Seth!!

Posted this in Github too, sorry for the crossposting and i can certainly take one down if needed. Here’s the issue i’ve been struggling with.

Describe the bug

System:
1x BUI (Backup Interface)
3 x SE7600H-US
3 x LG RESU 16

Thanks @WillCodeForCats Seth for creating this amazing integration. It’s pretty amazing :slight_smile: However, I’ve been struggling with getting it working. I have a 3 inverter system, each inverter has 1 battery (LG RESU16) connected for a total of 3 inv/3 bat.

All inverters are connected via Ethernet, on the same subnet (initially I had the inverters on a different subnet for IOT stuff but moved them to the same subnet as the HA VM).

All inverters have Modbus TCP on, initially port 1502, and Leader ID set to 1, next inverter Follower ID set to 2, and last inverter Follower set to ID 3.

Batteries were set to ID 15. I tried changing this to troubleshoot, using ID 16 and communication with the inverter failed so I had to restore ID to 15.

On the default settings, the modbus integration fails. I UNCHECKED “auto-detect additional entities” and this did not give a connection either.

The only way I can get an initial connection is to set everything OFF:
image

This works to get all 3 inverters details. Then I can add “Auto-detect Meters” and this will grab the meters:
image

However, I cannot get “Auto-detect batteries” or “Power Control” working to detect at all:
image

In the log files for battery connection, it just fails at “Looking for battery I1B1”. No “IllegalAddress” as per the known issue:

2024-07-12 05:31:40.042 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for battery I1B1
2024-07-12 05:31:52.049 DEBUG (MainThread) [custom_components.solaredge_modbus_multi] Finished fetching SolarEdge Coordinator data in 12.396 seconds (success: False)

2024-07-12 11:12:06.021 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_Device_address 0x8000 <class 'int'>
2024-07-12 11:12:06.021 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: Meter 3 ident incorrect or not installed.
2024-07-12 11:12:06.021 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for battery I1B1
2024-07-12 11:12:06.021 DEBUG (MainThread) [pymodbus.logging] Adding transaction 6
2024-07-12 11:12:06.021 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-07-12 11:12:06.021 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x6 0x0 0x0 0x0 0x6 0x1 0x3 0xe1 0x0 0x0 0x44
2024-07-12 11:12:09.022 DEBUG (MainThread) [pymodbus.logging] Adding transaction 6
2024-07-12 11:12:09.022 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-07-12 11:12:09.022 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x6 0x0 0x0 0x0 0x6 0x1 0x3 0xe1 0x0 0x0 0x44
2024-07-12 11:12:12.023 DEBUG (MainThread) [pymodbus.logging] Adding transaction 6
2024-07-12 11:12:12.023 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-07-12 11:12:12.023 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x6 0x0 0x0 0x0 0x6 0x1 0x3 0xe1 0x0 0x0 0x44
2024-07-12 11:12:15.025 DEBUG (MainThread) [pymodbus.logging] Adding transaction 6
2024-07-12 11:12:15.025 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-07-12 11:12:15.025 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x6 0x0 0x0 0x0 0x6 0x1 0x3 0xe1 0x0 0x0 0x44
2024-07-12 11:12:18.027 DEBUG (MainThread) [pymodbus.logging] Connection lost comm due to Server not responding
2024-07-12 11:12:18.027 DEBUG (MainThread) [pymodbus.logging] callback_disconnected called: Server not responding
2024-07-12 11:12:18.027 DEBUG (MainThread) [custom_components.solaredge_modbus_multi] Finished fetching SolarEdge Coordinator data in 12.297 seconds (success: False)

I tried deleting the integration, redownloading from HACS, and reinstalling, using the alternate modbus port 1503 - same results.

I am ALWAYS able to ping the inverter IP without any issues from the HA VM.

THANK YOU SETH @WillCodeForCats

Expected behavior
Connection to inverter and batteries with power control

Screenshots
IMG_9715
IMG_9708
IMG_9716
IMG_9721
IMG_9723
IMG_9729

Diagnostic File
home-assistant_solaredge_modbus_multi_2024-07-12T09-33-53.189Z.log
home-assistant_solaredge_modbus_multi_2024-07-12T10-03-39.524Z.log
Full HA log with pymodbus:
home-assistant_2024-07-12T15-12-57.733Z.log

Debug logs
No response

Home Assistant Version
2024.7.2 - running on VM in TrueNAS Scale

solaredge-modbus-multi Version
current

Installation Type
HAOS on VM in TrueNAS Scale

Read the Instructions
I have read Home · WillCodeForCats/solaredge-modbus-multi Wiki · GitHub
My configuration follows Configuration · WillCodeForCats/solaredge-modbus-multi Wiki · GitHub
This issue is not about a template error (template errors should not be reported as an issue, read Template Design Notes · WillCodeForCats/solaredge-modbus-multi Wiki · GitHub)
Additional Context
No response