unable to connect to Inverter using TCP (WiFi-RS485)

LionBS76 commented 1 month ago

System Health details

System Information

version	core-2024.9.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.12.4
os_name	Linux
os_version	6.6.46-haos
arch	x86_64
timezone	Europe/Kyiv
config_dir	/config

Home Assistant Community Store

Home Assistant Cloud

Home Assistant Supervisor

Dashboards

Recorder

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue

Beforehand thanks for Your work!!! :)

I have invertor Must PV18-3224 that I want to monitor with HA. HA and Invertor are on some distance from each other so I can't connect it directly by USB Serial cable. To connect to Invertor remotely I use handmade WiFi-to-Serial adaptor (ESP-01 + esp-link software on it + rs485-to-UART adaptor). I can use SolarPowerMonitor (origin software from Must) and HW Virtual Serial Port software, on PC where SolarMonitor installed, to connect to my ESP and monitor Invertor.

So, my handmade adaptor shouldn't be the issue because origin soft SolarPowerMonitor is working fine.

I added Must Plugin to HA. When I try to add Invertor device by TCP (use IP of ESP) that doesn't work.

My handmade WiFi-to-Serial like the one you used before (on DIN rail) in your post

On the ESP (esp-link software) I can see some Debug. When using Virtual Serial Port and origin Solar Monitor I see in log that soft make one connection (suppose 19200 baud) then close it. After that make one new connection and communicate through it all time.

Your HA Must plugin makes 5 connections and didn't close them. And Esp-link soft can't make more simultaneous connections.

Reproduction steps

Connect WiFi-to-Serial to Must Invertor
Add Invrtor device by TCP option into HA Must plugin
Doesn't add any devices
Using the same TCP info for connecting origin software Solar Power Monitor thiough Virtual Serial Port works fine ...

Debug logs

From HA log:
2024-09-28 17:21:34.991 ERROR (MainThread) [custom_components.must_inverter] error reading modbus data at address 15201: Exception Response(166, 38, None)
2024-09-28 17:21:42.996 ERROR (MainThread) [custom_components.must_inverter] error reading modbus data at address 20000
Traceback (most recent call last):
  File "/config/custom_components/must_inverter/__init__.py", line 239, in read_modbus_data
    response = await self._client.read_holding_registers(address=start, count=count, slave=0x04)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/pymodbus/client/base.py", line 175, in async_execute
    raise ModbusIOException(
pymodbus.exceptions.ModbusIOException: Modbus Error: [Input/Output] ERROR: No response received after 3 retries
2024-09-28 17:21:46.010 ERROR (MainThread) [custom_components.must_inverter] error reading modbus data at address 20101
Traceback (most recent call last):
  File "/config/custom_components/must_inverter/__init__.py", line 239, in read_modbus_data
    response = await self._client.read_holding_registers(address=start, count=count, slave=0x04)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/pymodbus/client/base.py", line 167, in async_execute
    resp = await asyncio.wait_for(
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/asyncio/tasks.py", line 520, in wait_for
    return await fut
           ^^^^^^^^^
pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Connection lost during request
2024-09-28 17:21:46.013 ERROR (MainThread) [custom_components.must_inverter] error reading modbus data at address 25201
Traceback (most recent call last):
  File "/config/custom_components/must_inverter/__init__.py", line 239, in read_modbus_data
    response = await self._client.read_holding_registers(address=start, count=count, slave=0x04)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/pymodbus/client/base.py", line 167, in async_execute
    resp = await asyncio.wait_for(
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/asyncio/tasks.py", line 520, in wait_for
    return await fut
           ^^^^^^^^^
pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Connection lost during request

Diagnostics dump

No response

mukaschultze commented 1 month ago

@LionBS76 what happens if you change the integration configuration so it doesn't reconnect too fast? Maybe the ESP can't handle the fast reconnect after the first error. Use something like in the screenshot below:

LionBS76 commented 1 month ago

@LionBS76 what happens if you change the integration configuration so it doesn't reconnect too fast? Maybe the ESP can't handle the fast reconnect after the first error. Use something like in the screenshot below:

I have tried such configuration parameters with no success.

LionBS76 commented 1 month ago

How can I get more debug for You to analyze ?

mukaschultze / ha-must-inverter