Okay, it happened again and I have the log file. However, the file size is 5,27 GB. I read the log at the according time, but I don’t understand what is wrong. How can I best send you the file? Or how can I cut out the area that’s of interest to you.
I guess start with around the time the problem occurs and whatever home assistant is doing at that point.
It’s easier to upload files on Github if you can start a new discussion:
I tried to upload it over there, but even my chunk file was way too big. So I zipped it (and encrypted it) and uploaded it on File-Upload again.
Here is the link:
PW is Schlichi83logfileha
Connection to the Inverter was lost at 19:24:47 and came back at 19:26:21.
THANK you in advance!
I see that it tried to connect:
2024-01-31 19:24:35.783 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] coordinator timeout is 10.8
2024-01-31 19:24:35.783 DEBUG (MainThread) [pymodbus.logging] Connecting to 192.168.10.11:502.
2024-01-31 19:24:35.783 DEBUG (MainThread) [pymodbus.logging] Connecting comm
And it waited but there was no response from that IP address so it timed out:
2024-01-31 19:24:47.338 ERROR (MainThread) [custom_components.solaredge_modbus_multi] Timeout fetching SolarEdge Coordinator data
2024-01-31 19:24:47.340 DEBUG (MainThread) [custom_components.solaredge_modbus_multi] Finished fetching SolarEdge Coordinator data in 19.766 seconds (success: False)
If Home Assistant is locking up completely I don’t see evidence of that happening during the almost 20 seconds it waits for the modbus connection because there are log entries of MainThread doing other stuff between those two times. If it was locking then the MainThread would stop completely.
Have you checked logs on what the proxy is doing when it doesn’t respond to the connection attempt?
These are the events leading up to the error, it looks like the proxy stopped responding mid-connection:
2024-01-31 19:24:27.964 DEBUG (MainThread) [pymodbus.logging] send: 0x23 0x92 0x0 0x0 0x0 0x6 0x1 0x3 0x9c 0xfc 0x0 0x6b
2024-01-31 19:24:27.968 DEBUG (MainThread) [pymodbus.logging] Adding transaction 9106
2024-01-31 19:24:28.345 DEBUG (MainThread) [pymodbus.logging] -> transport: received eof
2024-01-31 19:24:28.346 DEBUG (MainThread) [pymodbus.logging] Connection lost comm due to None
2024-01-31 19:24:28.346 DEBUG (MainThread) [pymodbus.logging] Getting transaction 9106
2024-01-31 19:24:28.346 DEBUG (MainThread) [custom_components.solaredge_modbus_multi] Failed data refresh attempt 1
Because the connection dropped the integration waits and tries again:
2024-01-31 19:24:28.354 DEBUG (MainThread) [custom_components.solaredge_modbus_multi] Waiting 800 ms before data refresh attempt 2
2024-01-31 19:24:29.500 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] coordinator timeout is 10.8
2024-01-31 19:24:29.501 DEBUG (MainThread) [pymodbus.logging] Connecting to 192.168.10.11:502.
2024-01-31 19:24:29.501 DEBUG (MainThread) [pymodbus.logging] Connecting comm
2024-01-31 19:24:32.036 DEBUG (MainThread) [custom_components.solaredge_modbus_multi] Failed data refresh attempt 2
2024-01-31 19:24:32.036 DEBUG (MainThread) [custom_components.solaredge_modbus_multi] Waiting 2400 ms before data refresh attempt 3
2024-01-31 19:24:35.783 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] coordinator timeout is 10.8
2024-01-31 19:24:35.783 DEBUG (MainThread) [pymodbus.logging] Connecting to 192.168.10.11:502.
2024-01-31 19:24:35.783 DEBUG (MainThread) [pymodbus.logging] Connecting comm
2024-01-31 19:24:47.338 ERROR (MainThread) [custom_components.solaredge_modbus_multi] Timeout fetching SolarEdge Coordinator data
2024-01-31 19:24:47.340 DEBUG (MainThread) [custom_components.solaredge_modbus_multi] Finished fetching SolarEdge Coordinator data in 19.766 seconds (success: False)
There’s other modbus stuff running and it’s hard to keep track of all the requests so it’s possible I’m confusing some of these, but I don’t see any evidence the integration is blocking MainThread.
1 Like
I can’t access the log from the proxy from yesterday evening anymore. However, tonight there was another issue, but as it was on 5am I can’t say, if HA was unresponsive at that time.
The proxy log during this time says the following:
2024-02-01 05:25:18,738 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:18,753 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [1/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:18,756 INFO modbus-proxy.ModBus(192.168.10.20:1502): closing connection…
2024-02-01 05:25:18,757 INFO modbus-proxy.ModBus(192.168.10.20:1502): connection closed
2024-02-01 05:25:18,757 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:18,761 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [2/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:18,761 INFO modbus-proxy.Client(192.168.10.11:60588): closing connection…
2024-02-01 05:25:18,762 INFO modbus-proxy.Client(192.168.10.11:60588): connection closed
2024-02-01 05:25:19,410 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:19,413 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [1/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:19,415 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:19,437 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [2/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:19,437 INFO modbus-proxy.Client(192.168.10.11:42081): closing connection…
2024-02-01 05:25:19,438 INFO modbus-proxy.Client(192.168.10.11:42081): connection closed
2024-02-01 05:25:20,248 INFO modbus-proxy.Client(192.168.10.11:59207): new client connection
2024-02-01 05:25:20,250 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:20,253 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [1/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:20,254 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:20,257 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [2/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:20,257 INFO modbus-proxy.Client(192.168.10.11:59207): closing connection…
2024-02-01 05:25:20,260 INFO modbus-proxy.Client(192.168.10.11:59207): connection closed
2024-02-01 05:25:22,663 INFO modbus-proxy.Client(192.168.10.11:37229): new client connection
2024-02-01 05:25:22,665 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:22,668 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [1/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:22,670 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:22,673 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [2/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:22,674 INFO modbus-proxy.Client(192.168.10.11:37229): closing connection…
2024-02-01 05:25:22,675 INFO modbus-proxy.Client(192.168.10.11:37229): connection closed
2024-02-01 05:25:29,882 INFO modbus-proxy.Client(192.168.10.11:34821): new client connection
2024-02-01 05:25:29,883 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:33,766 INFO modbus-proxy.Client(192.168.10.11:48664): new client connection
2024-02-01 05:25:43,962 INFO modbus-proxy.Client(192.168.10.11:55652): new client connection
2024-02-01 05:25:48,179 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [1/2]: OSError(113, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:48,180 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:48,184 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [2/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:48,184 INFO modbus-proxy.Client(192.168.10.11:34821): closing connection…
2024-02-01 05:25:48,185 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:48,188 INFO modbus-proxy.Client(192.168.10.11:34821): connection closed
2024-02-01 05:25:48,190 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [1/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:48,191 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:48,194 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [2/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:48,194 INFO modbus-proxy.Client(192.168.10.11:48664): closing connection…
2024-02-01 05:25:48,195 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:48,197 INFO modbus-proxy.Client(192.168.10.11:48664): connection closed
2024-02-01 05:25:48,220 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [1/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:48,221 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:48,224 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [2/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:48,224 INFO modbus-proxy.Client(192.168.10.11:55652): closing connection…
2024-02-01 05:25:48,227 INFO modbus-proxy.Client(192.168.10.11:55652): connection closed
2024-02-01 05:25:48,995 INFO modbus-proxy.Client(192.168.10.11:56179): new client connection
2024-02-01 05:25:48,996 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:48,999 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [1/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:48,999 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:49,060 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [2/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:49,060 INFO modbus-proxy.Client(192.168.10.11:56179): closing connection…
2024-02-01 05:25:49,061 INFO modbus-proxy.Client(192.168.10.11:56179): connection closed
2024-02-01 05:25:51,501 INFO modbus-proxy.Client(192.168.10.11:48281): new client connection
2024-02-01 05:25:51,503 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:51,507 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [1/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:51,507 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:51,510 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [2/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:51,511 INFO modbus-proxy.Client(192.168.10.11:48281): closing connection…
2024-02-01 05:25:51,512 INFO modbus-proxy.Client(192.168.10.11:48281): connection closed
2024-02-01 05:25:58,717 INFO modbus-proxy.Client(192.168.10.11:43889): new client connection
2024-02-01 05:25:58,719 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:58,722 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [1/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:58,722 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:25:58,725 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [2/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:25:58,726 INFO modbus-proxy.Client(192.168.10.11:43889): closing connection…
2024-02-01 05:25:58,727 INFO modbus-proxy.Client(192.168.10.11:43889): connection closed
2024-02-01 05:26:03,228 INFO modbus-proxy.Client(192.168.10.11:46710): new client connection
2024-02-01 05:26:03,229 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:26:03,231 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [1/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:26:03,232 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:26:03,236 ERROR modbus-proxy.ModBus(192.168.10.20:1502): write_read error [2/2]: ConnectionRefusedError(111, “Connect call failed (‘192.168.10.20’, 1502)”)
2024-02-01 05:26:03,236 INFO modbus-proxy.Client(192.168.10.11:46710): closing connection…
2024-02-01 05:26:03,237 INFO modbus-proxy.Client(192.168.10.11:46710): connection closed
2024-02-01 05:26:18,240 INFO modbus-proxy.Client(192.168.10.11:48350): new client connection
2024-02-01 05:26:18,240 INFO modbus-proxy.ModBus(192.168.10.20:1502): connecting to modbus…
2024-02-01 05:26:18,246 INFO modbus-proxy.ModBus(192.168.10.20:1502): connected!
2024-02-01 05:26:18,247 INFO modbus-proxy.ModBus(192.168.10.20:1502): delay after connect: 0.1e
Yes, my heat pump also works with ModBus.
Do you suggest trying out the integration without the proxy? Is there another proper way to submit the necessary data from HA to EVCC, when EVCC can’t connect directly to my inverter anymore?
What is the link to the modbus proxy you’re using?
This one here:
I will try and look at the proxy and see if there are any ways to improve how the integration handles no connection from the proxy.
1 Like
That would be great! Thank’s a lot!!! 
Hello,
So I was trying to integrate my solaredge setup in the energy dashboard. but the cloud based integration misses the pv energy (I tried the helper integration, but it didn’t look accurate, maybe the granularity of the polling is too low).
Then I tried this integration installing it by hand, which worked fine and I prefer the local connection than the cloud based one. So I also can get notified for too much import in real time.
However in the solaeredge-modbus-multi wiki there’s only instructions on how to setup the tesla card which isn’t standard in HA and it’s power based, there’s no mention on how to configure the core energy based one to track solar production over time.
I found some complex package to add in packages/ that adds a ton of measurements based on this integrations, many values still calculated out of integrals.
All I needed was just the pv energy production. Checking the diagrams in the wiki it was easy to understand where each sensor is placed and in turn to calculate the PV energy with what was already available as energy meter, without having to use integrals.
There’s a catch, the PV energy sensor would appear negative when PV is not producing anything, the negative number happens if energy is going out of the battery but produces less AC energy than what come out in DC. The AC DC or other internal energy losses show up as negative PV production.
So to make it look nicer the sensor is capped to remain monotonic. However if you restart HA, you’re going to get a little negative bump. So the sensor has to be of the total class, not total_increasing. If HA isn’t restarted, the “energy loss” will result in PV energy being slight underestimated the next day when PV energy is produced again.
Overall I don’t care about the little error in the DC AC conversion, it’s just noise as far as I’m concerned.
I couldn’t find a simpler way to get the energy dashboard configured with solaredge.
So assuming modbus is measuring the I+E the full configuration becomes:
Solaredge M1 Imported # grid consumption
Solaredge M1 Exported # return to grid
Solaredge PV Energy # the single below template as solar production
Solaredge B1 Energy Export # energy going into the battery
Solaredge B1 Energy Import # energy coming out of the battery
template:
sensor:
- unique_id: solaredge_pv_energy
name: Solaredge PV Energy
state: >
{% set ac = states('sensor.solaredge_i1_ac_energy') | float %}
{% set b1 = states('sensor.solaredge_b1_energy_export') | float - states('sensor.solaredge_b1_energy_import') | float %}
{% set pv = ac - b1 %}
{% set old_pv = this.state | float(0) %}
{% if pv < old_pv %}
{{ old_pv }}
{% else %}
{{ pv }}
{% endif %}
unit_of_measurement: "kWh"
device_class: energy
state_class: total
icon: mdi:solar-power
Maybe the instruction on how to configure the stock energy dasbhoard with the solaredge-modbus-multi could be added to the wiki too.
Thanks.
After installing Home Assistant 2024.4 I’m seeing a new log-entry for my solaredge-modbus-multi integration v2.4.13.
Logger: homeassistant.const
Source: helpers/deprecation.py:206
First occurred: 08:55:56 (8 occurrences)
Last logged: 08:55:56
FREQUENCY_HERTZ was used from solaredge_modbus_multi, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfFrequency.HERTZ instead, please report it to the author of the 'solaredge_modbus_multi' custom integration
POWER_VOLT_AMPERE was used from solaredge_modbus_multi, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfApparentPower.VOLT_AMPERE instead, please report it to the author of the 'solaredge_modbus_multi' custom integration
POWER_WATT was used from solaredge_modbus_multi, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfPower.WATT instead, please report it to the author of the 'solaredge_modbus_multi' custom integration
TEMP_CELSIUS was used from solaredge_modbus_multi, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please report it to the author of the 'solaredge_modbus_multi' custom integration
TEMP_CELSIUS was used from nest_protect, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please report it to the author of the 'nest_protect' custom integration
Not sure if I should file an issue at the github page…
Those were removed in v2.2.10-pre.4 from January 2023, over a year ago. You would have to still be running v2.2.9 to see those warnings.
1 Like
I’m having a bit of trouble with the integration since I got an inverter replaced today. It has been working for more than a year prior.
I can verify that the modbus-over-tcp is working, both with QModMaster and because when I configure the SunSpec integration… it seems to work (both inverters are connected to the LAN, which is useful for SunSpec at least).
I can verify that the modbus connection is being made by solaredge-modbus-multi, but I get the dreaded (success: False) at the end.
The system is a two-inverter system, each with two LG batteries. One inverter has two meters (production, import/export), and the other only has one (production).
The integration version is v2.4.15
HA is at 2024.05.1
As part of the commissioning of the replacement inverter the firmware was updated to today’s version.
Log snippet (serial numbers replaced)(last few lines look significant. Off by one error in length of something maybe?):
024-05-21 22:43:22.679 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] solaredge_modbus_multi configuration: number_of_inverters=2, start_device_id=1, detect_meters=True, detect_batteries=True, detect_extras=True, keep_modbus_open=False, adv_storage_control=False, adv_site_limit_control=False, allow_battery_energy_reset=True, sleep_after_write=0, battery_rating_adjust=0,
2024-05-21 22:43:22.679 DEBUG (MainThread) [custom_components.solaredge_modbus_multi] Retry limit=5 time=800 ratio=3
2024-05-21 22:43:22.679 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] New client object for 192.168.121.155:1502
2024-05-21 22:43:22.680 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] reconnect_delay=0 reconnect_delay_max=3 retry_on_empty=False timeout=3
2024-05-21 22:43:22.680 DEBUG (MainThread) [pymodbus.logging] Connecting to 192.168.121.155:1502.
2024-05-21 22:43:22.680 DEBUG (MainThread) [pymodbus.logging] Connecting comm
2024-05-21 22:43:22.973 DEBUG (MainThread) [pymodbus.logging] Connected to comm
2024-05-21 22:43:22.973 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-05-21 22:43:22.974 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] coordinator timeout is 31.2
2024-05-21 22:43:22.974 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for inverter at 192.168.121.155 ID 1
2024-05-21 22:43:22.974 DEBUG (MainThread) [pymodbus.logging] Adding transaction 1
2024-05-21 22:43:22.974 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-05-21 22:43:22.975 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x1 0x0 0x0 0x0 0x6 0x1 0x3 0x9c 0x40 0x0 0x45
2024-05-21 22:43:23.081 DEBUG (MainThread) [pymodbus.logging] recv: 0x0 0x1 0x0 0x0 0x0 0x8d 0x1 0x3 0x8a 0x53 0x75 0x6e 0x53 0x0 0x1 0x0 0x41 0x53 0x6f 0x6c 0x61 0x72 0x45 0x64 0x67 0x65 0x20 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x53 0x45 0x31 0x31 0x34 0x30 0x30 0x48 0x2d 0x55 0x53 0x53 0x4e 0x42 0x42 0x4c 0x31 0x34 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x30 0x30 0x30 0x34 0x2e 0x30 0x30 0x32 0x30 0x2e 0x30 0x30 0x33 0x36 0x0 0x0 0x37 0x34 0x30 0x36 0x32 0x34 0x36 0x31 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x1 old_data: addr=None
2024-05-21 22:43:23.081 DEBUG (MainThread) [pymodbus.logging] Processing: 0x0 0x1 0x0 0x0 0x0 0x8d 0x1 0x3 0x8a 0x53 0x75 0x6e 0x53 0x0 0x1 0x0 0x41 0x53 0x6f 0x6c 0x61 0x72 0x45 0x64 0x67 0x65 0x20 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x53 0x45 0x31 0x31 0x34 0x30 0x30 0x48 0x2d 0x55 0x53 0x53 0x4e 0x42 0x42 0x4c 0x31 0x34 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x30 0x30 0x30 0x34 0x2e 0x30 0x30 0x32 0x30 0x2e 0x30 0x30 0x33 0x36 0x0 0x0 0x37 0x34 0x30 0x36 0x32 0x34 0x36 0x31 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x1
2024-05-21 22:43:23.081 DEBUG (MainThread) [pymodbus.logging] Factory Response[ReadHoldingRegistersResponse': 3]
2024-05-21 22:43:23.081 DEBUG (MainThread) [pymodbus.logging] Getting transaction 1
2024-05-21 22:43:23.081 DEBUG (MainThread) [pymodbus.logging] Frame check, no more data!
2024-05-21 22:43:23.083 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Registers received requested : 69 69
2024-05-21 22:43:23.083 DEBUG (MainThread) [pymodbus.logging] [21365, 28243, 1, 65, 21359, 27745, 29253, 25703, 25888, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 21317, 12593, 13360, 12360, 11605, 21331, 20034, 16972, 12596, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 12336, 12340, 11824, 12338, 12334, 12336, 13110, 0, 14132, 12342, 12852, 13873, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1]
2024-05-21 22:43:23.083 DEBUG (MainThread) [pymodbus.logging] handle: [b'Su', b'nS']
2024-05-21 22:43:23.084 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_SunSpec_ID 0x53756e53<class 'int'>
2024-05-21 22:43:23.084 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_SunSpec_DID 0x1<class 'int'>
2024-05-21 22:43:23.084 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_SunSpec_Length 0x41<class 'int'>
2024-05-21 22:43:23.084 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_Manufacturer SolarEdge<class 'str'>
2024-05-21 22:43:23.084 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_Model SE11400H-USSNBBL14<class 'str'>
2024-05-21 22:43:23.084 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_Option <class 'str'>
2024-05-21 22:43:23.084 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_Version 0004.0020.0036<class 'str'>
2024-05-21 22:43:23.084 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_SerialNumber X<class 'str'>
2024-05-21 22:43:23.084 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1: C_Device_address 0x1<class 'int'>
2024-05-21 22:43:23.084 DEBUG (MainThread) [pymodbus.logging] Adding transaction 2
2024-05-21 22:43:23.084 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-05-21 22:43:23.084 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x2 0x0 0x0 0x0 0x6 0x1 0x3 0x9c 0xb9 0x0 0x9
2024-05-21 22:43:23.144 DEBUG (MainThread) [pymodbus.logging] recv: 0x0 0x2 0x0 0x0 0x0 0x15 0x1 0x3 0x12 0x0 0x1 0x0 0x41 0x53 0x6f 0x6c 0x61 0x72 0x45 0x64 0x67 0x65 0x0 0x0 0x0 0x0 0x0 old_data: addr=None
2024-05-21 22:43:23.145 DEBUG (MainThread) [pymodbus.logging] Processing: 0x0 0x2 0x0 0x0 0x0 0x15 0x1 0x3 0x12 0x0 0x1 0x0 0x41 0x53 0x6f 0x6c 0x61 0x72 0x45 0x64 0x67 0x65 0x0 0x0 0x0 0x0 0x0
2024-05-21 22:43:23.145 DEBUG (MainThread) [pymodbus.logging] Factory Response[ReadHoldingRegistersResponse': 3]
2024-05-21 22:43:23.145 DEBUG (MainThread) [pymodbus.logging] Getting transaction 2
2024-05-21 22:43:23.145 DEBUG (MainThread) [pymodbus.logging] Frame check, no more data!
2024-05-21 22:43:23.146 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Registers received requested : 9 9
2024-05-21 22:43:23.146 DEBUG (MainThread) [pymodbus.logging] [1, 65, 21359, 27745, 29253, 25703, 25856, 0, 0]
2024-05-21 22:43:23.146 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1 MMPPT: mmppt_DID 0x1 <class 'int'>
2024-05-21 22:43:23.146 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1 MMPPT: mmppt_Length 0x41 <class 'int'>
2024-05-21 22:43:23.146 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1 MMPPT: mmppt_Units 0x0 <class 'int'>
2024-05-21 22:43:23.146 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1 is NOT Multiple MPPT
2024-05-21 22:43:23.146 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for meter I1M1
2024-05-21 22:43:23.146 DEBUG (MainThread) [pymodbus.logging] Adding transaction 3
2024-05-21 22:43:23.147 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-05-21 22:43:23.147 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x3 0x0 0x0 0x0 0x6 0x1 0x3 0x9c 0xb9 0x0 0x43
2024-05-21 22:43:23.247 DEBUG (MainThread) [pymodbus.logging] recv: 0x0 0x3 0x0 0x0 0x0 0x89 0x1 0x3 0x86 0x0 0x1 0x0 0x41 0x53 0x6f 0x6c 0x61 0x72 0x45 0x64 0x67 0x65 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x53 0x45 0x2d 0x52 0x47 0x4d 0x54 0x52 0x2d 0x31 0x44 0x2d 0x32 0x34 0x30 0x43 0x2d 0x42 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x50 0x72 0x6f 0x64 0x75 0x63 0x74 0x69 0x6f 0x6e 0x0 0x0 0x0 0x0 0x0 0x0 0x31 0x30 0x38 0x31 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x36 0x30 0x36 0x38 0x32 0x34 0x34 0x36 0x31 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x1 old_data: addr=None
2024-05-21 22:43:23.247 DEBUG (MainThread) [pymodbus.logging] Processing: 0x0 0x3 0x0 0x0 0x0 0x89 0x1 0x3 0x86 0x0 0x1 0x0 0x41 0x53 0x6f 0x6c 0x61 0x72 0x45 0x64 0x67 0x65 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x53 0x45 0x2d 0x52 0x47 0x4d 0x54 0x52 0x2d 0x31 0x44 0x2d 0x32 0x34 0x30 0x43 0x2d 0x42 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x50 0x72 0x6f 0x64 0x75 0x63 0x74 0x69 0x6f 0x6e 0x0 0x0 0x0 0x0 0x0 0x0 0x31 0x30 0x38 0x31 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x36 0x30 0x36 0x38 0x32 0x34 0x34 0x36 0x31 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x1
2024-05-21 22:43:23.248 DEBUG (MainThread) [pymodbus.logging] Factory Response[ReadHoldingRegistersResponse': 3]
2024-05-21 22:43:23.248 DEBUG (MainThread) [pymodbus.logging] Getting transaction 3
2024-05-21 22:43:23.248 DEBUG (MainThread) [pymodbus.logging] Frame check, no more data!
2024-05-21 22:43:23.248 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Registers received requested : 67 67
2024-05-21 22:43:23.248 DEBUG (MainThread) [pymodbus.logging] [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, 12592, 14385, 0, 0, 0, 0, 0, 0, 13872, 13880, 12852, 13366, 12544, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1]
2024-05-21 22:43:23.249 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_SunSpec_DID 0x1 <class 'int'>
2024-05-21 22:43:23.249 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_SunSpec_Length 0x41 <class 'int'>
2024-05-21 22:43:23.249 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_Manufacturer SolarEdge <class 'str'>
2024-05-21 22:43:23.249 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_Model SE-RGMTR-1D-240C-B <class 'str'>
2024-05-21 22:43:23.249 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_Option Production <class 'str'>
2024-05-21 22:43:23.249 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_Version 1081 <class 'str'>
2024-05-21 22:43:23.249 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_SerialNumber X<class 'str'>
2024-05-21 22:43:23.249 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M1: C_Device_address 0x1 <class 'int'>
2024-05-21 22:43:23.249 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Found I1M1
2024-05-21 22:43:23.249 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for meter I1M2
2024-05-21 22:43:23.249 DEBUG (MainThread) [pymodbus.logging] Adding transaction 4
2024-05-21 22:43:23.249 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-05-21 22:43:23.250 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x4 0x0 0x0 0x0 0x6 0x1 0x3 0x9d 0x67 0x0 0x43
2024-05-21 22:43:23.385 DEBUG (MainThread) [pymodbus.logging] recv: 0x0 0x4 0x0 0x0 0x0 0x89 0x1 0x3 0x86 0x0 0x1 0x0 0x41 0x53 0x6f 0x6c 0x61 0x72 0x45 0x64 0x67 0x65 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x53 0x45 0x2d 0x4d 0x54 0x52 0x2d 0x33 0x59 0x2d 0x32 0x34 0x30 0x56 0x2d 0x41 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x45 0x78 0x70 0x6f 0x72 0x74 0x2b 0x49 0x6d 0x70 0x6f 0x72 0x74 0x0 0x0 0x0 0x31 0x30 0x38 0x31 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x36 0x30 0x36 0x37 0x39 0x30 0x33 0x38 0x33 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x2 old_data: addr=None
2024-05-21 22:43:23.385 DEBUG (MainThread) [pymodbus.logging] Processing: 0x0 0x4 0x0 0x0 0x0 0x89 0x1 0x3 0x86 0x0 0x1 0x0 0x41 0x53 0x6f 0x6c 0x61 0x72 0x45 0x64 0x67 0x65 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x53 0x45 0x2d 0x4d 0x54 0x52 0x2d 0x33 0x59 0x2d 0x32 0x34 0x30 0x56 0x2d 0x41 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x45 0x78 0x70 0x6f 0x72 0x74 0x2b 0x49 0x6d 0x70 0x6f 0x72 0x74 0x0 0x0 0x0 0x31 0x30 0x38 0x31 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x36 0x30 0x36 0x37 0x39 0x30 0x33 0x38 0x33 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x2
2024-05-21 22:43:23.386 DEBUG (MainThread) [pymodbus.logging] Factory Response[ReadHoldingRegistersResponse': 3]
2024-05-21 22:43:23.386 DEBUG (MainThread) [pymodbus.logging] Getting transaction 4
2024-05-21 22:43:23.386 DEBUG (MainThread) [pymodbus.logging] Frame check, no more data!
2024-05-21 22:43:23.394 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Registers received requested : 67 67
2024-05-21 22:43:23.394 DEBUG (MainThread) [pymodbus.logging] [1, 65, 21359, 27745, 29253, 25703, 25856, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 21317, 11597, 21586, 11571, 22829, 12852, 12374, 11585, 0, 0, 0, 0, 0, 0, 0, 0, 17784, 28783, 29300, 11081, 28016, 28530, 29696, 0, 12592, 14385, 0, 0, 0, 0, 0, 0, 13872, 13879, 14640, 13112, 13056, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2]
2024-05-21 22:43:23.394 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_SunSpec_DID 0x1 <class 'int'>
2024-05-21 22:43:23.394 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_SunSpec_Length 0x41 <class 'int'>
2024-05-21 22:43:23.394 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_Manufacturer SolarEdge <class 'str'>
2024-05-21 22:43:23.395 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_Model SE-MTR-3Y-240V-A <class 'str'>
2024-05-21 22:43:23.395 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_Option Export+Import <class 'str'>
2024-05-21 22:43:23.395 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_Version 1081 <class 'str'>
2024-05-21 22:43:23.395 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_SerialNumber <class 'str'>
2024-05-21 22:43:23.395 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M2: C_Device_address 0x2 <class 'int'>
2024-05-21 22:43:23.395 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Found I1M2
2024-05-21 22:43:23.395 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for meter I1M3
2024-05-21 22:43:23.395 DEBUG (MainThread) [pymodbus.logging] Adding transaction 5
2024-05-21 22:43:23.395 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-05-21 22:43:23.395 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x5 0x0 0x0 0x0 0x6 0x1 0x3 0x9e 0x15 0x0 0x43
2024-05-21 22:43:23.436 DEBUG (MainThread) [pymodbus.logging] recv: 0x0 0x5 0x0 0x0 0x0 0x89 0x1 0x3 0x86 0x2 0xbd 0x0 0x99 0x0 0x1 0x0 0x1 0xff 0xff 0x0 0x1 0x0 0x0 0x0 0x0 0xff 0xff 0xff 0xff 0x0 0x0 0x0 0xb 0x0 0xb 0x0 0x2d 0x80 0x0 0x9 0x5e 0x4 0xaf 0x0 0x0 0xea 0x66 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x80 0x0 0x80 0x0 0x80 0x0 0x80 0x0 0x80 0x0 0x80 0x0 0x80 0x0 0x80 0x0 0x80 0x0 0xff 0xff 0xff 0xff 0xff 0xff 0x9 0x5e 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x80 0x0 0x80 0x0 0x80 0x0 old_data: addr=None
2024-05-21 22:43:23.436 DEBUG (MainThread) [pymodbus.logging] Processing: 0x0 0x5 0x0 0x0 0x0 0x89 0x1 0x3 0x86 0x2 0xbd 0x0 0x99 0x0 0x1 0x0 0x1 0xff 0xff 0x0 0x1 0x0 0x0 0x0 0x0 0xff 0xff 0xff 0xff 0x0 0x0 0x0 0xb 0x0 0xb 0x0 0x2d 0x80 0x0 0x9 0x5e 0x4 0xaf 0x0 0x0 0xea 0x66 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x80 0x0 0x80 0x0 0x80 0x0 0x80 0x0 0x80 0x0 0x80 0x0 0x80 0x0 0x80 0x0 0x80 0x0 0xff 0xff 0xff 0xff 0xff 0xff 0x9 0x5e 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x80 0x0 0x80 0x0 0x80 0x0
2024-05-21 22:43:23.436 DEBUG (MainThread) [pymodbus.logging] Factory Response[ReadHoldingRegistersResponse': 3]
2024-05-21 22:43:23.436 DEBUG (MainThread) [pymodbus.logging] Getting transaction 5
2024-05-21 22:43:23.436 DEBUG (MainThread) [pymodbus.logging] Frame check, no more data!
2024-05-21 22:43:23.437 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Registers received requested : 67 67
2024-05-21 22:43:23.437 DEBUG (MainThread) [pymodbus.logging] [701, 153, 1, 1, 65535, 1, 0, 0, 65535, 65535, 0, 11, 11, 45, 32768, 2398, 1199, 0, 60006, 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, 2398, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 65535, 32768, 32768, 32768]
2024-05-21 22:43:23.437 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_SunSpec_DID 0x2bd <class 'int'>
2024-05-21 22:43:23.437 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_SunSpec_Length 0x99 <class 'int'>
2024-05-21 22:43:23.437 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_Manufacturer - ^ <class 'str'>
2024-05-21 22:43:23.437 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_Model f <class 'str'>
2024-05-21 22:43:23.438 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_Option <class 'str'>
2024-05-21 22:43:23.438 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_Version ^ <class 'str'>
2024-05-21 22:43:23.438 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_SerialNumber <class 'str'>
2024-05-21 22:43:23.438 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: C_Device_address 0x8000 <class 'int'>
2024-05-21 22:43:23.438 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] I1M3: Meter 3 ident incorrect or not installed.
2024-05-21 22:43:23.438 DEBUG (MainThread) [custom_components.solaredge_modbus_multi.hub] Looking for battery I1B1
2024-05-21 22:43:23.438 DEBUG (MainThread) [pymodbus.logging] Adding transaction 6
2024-05-21 22:43:23.438 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-05-21 22:43:23.438 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x6 0x0 0x0 0x0 0x6 0x1 0x3 0xe1 0x0 0x0 0x44
2024-05-21 22:43:26.446 DEBUG (MainThread) [pymodbus.logging] Adding transaction 6
2024-05-21 22:43:26.446 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-05-21 22:43:26.446 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x6 0x0 0x0 0x0 0x6 0x1 0x3 0xe1 0x0 0x0 0x44
2024-05-21 22:43:29.930 DEBUG (MainThread) [pymodbus.logging] Adding transaction 6
2024-05-21 22:43:29.931 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-05-21 22:43:29.931 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x6 0x0 0x0 0x0 0x6 0x1 0x3 0xe1 0x0 0x0 0x44
2024-05-21 22:43:32.976 DEBUG (MainThread) [pymodbus.logging] Adding transaction 6
2024-05-21 22:43:32.977 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer -
2024-05-21 22:43:32.977 DEBUG (MainThread) [pymodbus.logging] send: 0x0 0x6 0x0 0x0 0x0 0x6 0x1 0x3 0xe1 0x0 0x0 0x44
2024-05-21 22:43:37.016 DEBUG (MainThread) [pymodbus.logging] Connection lost comm due to Server not responding
2024-05-21 22:43:37.016 DEBUG (MainThread) [pymodbus.logging] callback_disconnected called: Server not responding
2024-05-21 22:43:37.017 DEBUG (MainThread) [custom_components.solaredge_modbus_multi] Finished fetching SolarEdge Coordinator data in 14.338 seconds (success: False)
Turn off Auto-Detect Batteries and Auto-Detect Additional Entities in the configure options.
It has been reported before that some inverters do not respond to battery or control registers. From the debug logs you can see at the end if sends the request 4 times with no response from the inverter while looking for inverter 1 battery 1.
- Can't find my inverter after install · Issue #573 · WillCodeForCats/solaredge-modbus-multi · GitHub
- Will not connect · WillCodeForCats/solaredge-modbus-multi · Discussion #576 · GitHub
These are two issues reported with inverters that don’t respond to battery registers. I would expect this is a firmware problem in the inverter.
2 Likes
That worked. Thank you!
For future searches, this was working prior to firmware 0004.0020.0036.
Unsure which exact firmware before that worked with the detection options (and battery), but not in this one.
WillCodeForCats, thanks for this. I’m new to the HA platform and got it just so that I could control my SE system. It’s taken bit of learning, but I’m getting there. I’ve installed the program but get the following warning
This is my SE screen :
And this is my Config screen :
If there is anything that you could recommend that would be greatly appreciated
Thanks RH
I don’t have any advice for screen inverters beyond what is written in the instructions that someone contributed. Make sure modbus is enabled. If it is, try rebooting (power cycling) the inverter.