home_assistant_solarman: Increasing number of CLOSE_WAIT TCP connections plus increasing number of connection errors in the ha log

Hello,

SOLIS Hybrid 3K Inverter. I use solarman to get the values from the inverter and solismod through mqtt to poke some of the settings for battery charging etc. I’m running HA core 2024.2, upgraded last week.

I’ve seen more mqtt failures in the past week since the upgrade (a failure being the setting does not change as expected.) In the solismod log I’m seeing connection errors to the inverter (connection refused). I’m seeing similar in the solarman ha log:

2024-02-23 03:03:31.324 WARNING (SyncWorker_10) [custom_components.solarman.solarman] Querying [33029 - 33095] failed, [1] retry attempts left
2024-02-23 03:03:31.324 INFO (SyncWorker_10) [custom_components.solarman.solarman] Connecting to solarman data logger 192.168.10.121:8899
2024-02-23 03:03:31.329 WARNING (SyncWorker_10) [custom_components.solarman.solarman] Querying [33029 - 33095] failed with exception [NoSocketAvailableError: Connection closed on read]
2024-02-23 03:03:31.329 INFO (SyncWorker_10) [custom_components.solarman.solarman] Disconnecting from solarman data logger 192.168.10.121:8899
2024-02-23 03:03:31.332 WARNING (SyncWorker_10) [custom_components.solarman.solarman] Querying [33029 - 33095] failed, [0] retry attempts left
2024-02-23 03:03:31.332 WARNING (SyncWorker_10) [custom_components.solarman.solarman] Querying registers [33029 - 33095] failed, aborting.
2024-02-23 03:04:01.128 INFO (SyncWorker_36) [custom_components.solarman.solarman] Connecting to solarman data logger 192.168.10.121:8899
2024-02-23 03:04:01.134 WARNING (SyncWorker_36) [custom_components.solarman.solarman] Querying [33029 - 33095] failed with exception [NoSocketAvailableError: Connection closed on read]
2024-02-23 03:04:01.135 INFO (SyncWorker_36) [custom_components.solarman.solarman] Disconnecting from solarman data logger 192.168.10.121:8899
2024-02-23 03:04:01.138 WARNING (SyncWorker_36) [custom_components.solarman.solarman] Querying [33029 - 33095] failed, [1] retry attempts left
2024-02-23 03:04:01.138 INFO (SyncWorker_36) [custom_components.solarman.solarman] Connecting to solarman data logger 192.168.10.121:8899
2024-02-23 03:04:01.142 WARNING (SyncWorker_36) [custom_components.solarman.solarman] Querying [33029 - 33095] failed with exception [NoSocketAvailableError: Connection closed on read]
2024-02-23 03:04:01.142 INFO (SyncWorker_36) [custom_components.solarman.solarman] Disconnecting from solarman data logger 192.168.10.121:8899
2024-02-23 03:04:01.145 WARNING (SyncWorker_36) [custom_components.solarman.solarman] Querying [33029 - 33095] failed, [0] retry attempts left
2024-02-23 03:04:01.146 WARNING (SyncWorker_36) [custom_components.solarman.solarman] Querying registers [33029 - 33095] failed, aborting.
2024-02-23 03:04:31.130 INFO (SyncWorker_30) [custom_components.solarman.solarman] Connecting to solarman data logger 192.168.10.121:8899
2024-02-23 03:04:31.225 WARNING (SyncWorker_30) [custom_components.solarman.solarman] Querying [33029 - 33095] failed with exception [NoSocketAvailableError: Connection closed on read]
2024-02-23 03:04:31.225 INFO (SyncWorker_30) [custom_components.solarman.solarman] Disconnecting from solarman data logger 192.168.10.121:8899
2024-02-23 03:04:31.227 WARNING (SyncWorker_30) [custom_components.solarman.solarman] Querying [33029 - 33095] failed, [1] retry attempts left
2024-02-23 03:04:31.227 INFO (SyncWorker_30) [custom_components.solarman.solarman] Connecting to solarman data logger 192.168.10.121:8899
2024-02-23 03:04:31.232 WARNING (SyncWorker_30) [custom_components.solarman.solarman] Querying [33029 - 33095] failed with exception [NoSocketAvailableError: Connection closed on read]
2024-02-23 03:04:31.233 INFO (SyncWorker_30) [custom_components.solarman.solarman] Disconnecting from solarman data logger 192.168.10.121:8899
2024-02-23 03:04:31.235 WARNING (SyncWorker_30) [custom_components.solarman.solarman] Querying [33029 - 33095] failed, [0] retry attempts left
2024-02-23 03:04:31.235 WARNING (SyncWorker_30) [custom_components.solarman.solarman] Querying registers [33029 - 33095] failed, aborting.
2024-02-23 03:05:01.131 INFO (SyncWorker_3) [custom_components.solarman.solarman] Connecting to solarman data logger 192.168.10.121:8899
2024-02-23 03:30:01.189 WARNING (SyncWorker_18) [custom_components.solarman.solarman] Querying [33029 - 33095] failed with exception [NoSocketAvailableError: Connection closed on read]
2024-02-23 03:30:01.189 INFO (SyncWorker_18) [custom_components.solarman.solarman] Disconnecting from solarman data logger 192.168.10.121:8899
2024-02-23 03:30:01.195 WARNING (SyncWorker_18) [custom_components.solarman.solarman] Querying [33029 - 33095] failed, [1] retry attempts left
2024-02-23 03:30:01.195 INFO (SyncWorker_18) [custom_components.solarman.solarman] Connecting to solarman data logger 192.168.10.121:8899
2024-02-23 04:00:03.868 WARNING (SyncWorker_29) [custom_components.solarman.solarman] Querying [33029 - 33095] failed with exception [V5FrameError: V5 frame contains invalid sequence number]
2024-02-23 04:00:03.869 INFO (SyncWorker_29) [custom_components.solarman.solarman] Disconnecting from solarman data logger 192.168.10.121:8899
2024-02-23 04:00:04.369 WARNING (SyncWorker_29) [custom_components.solarman.solarman] Querying [33029 - 33095] failed, [1] retry attempts left
2024-02-23 04:00:04.369 INFO (SyncWorker_29) [custom_components.solarman.solarman] Connecting to solarman data logger 192.168.10.121:8899
2024-02-23 06:30:01.996 WARNING (SyncWorker_12) [custom_components.solarman.solarman] Querying [33029 - 33095] failed with exception [NoSocketAvailableError: Connection closed on read]
2024-02-23 06:30:01.996 INFO (SyncWorker_12) [custom_components.solarman.solarman] Disconnecting from solarman data logger 192.168.10.121:8899
2024-02-23 06:30:01.999 WARNING (SyncWorker_12) [custom_components.solarman.solarman] Querying inverter 4075426842 at 192.168.10.121:8899 failed on connection start with exception [KeyError: '41 is not registered']

As well as some other errors.

When I look for CLOSE_WAIT connections I see that most of them are from homeassistant (presumably solarman) to the inverter.

tcp     5589      0 192.168.10.1:45888      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:36970      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp       32      0 192.168.0.10:41218      3.123.196.97:443        CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:41340      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:54490      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:43524      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:58760      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:36948      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:47424      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp     5589      0 192.168.10.1:42606      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:41324      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp       32      0 192.168.0.10:42870      3.123.196.97:443        CLOSE_WAIT  317193/python3.11   
tcp     6145      0 192.168.10.1:42502      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:43500      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:58780      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp     5589      0 192.168.10.1:39312      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp     5575      0 192.168.10.1:58458      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:33450      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:56920      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:44642      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:56952      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:33470      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:44630      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:47410      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   
tcp        1      0 192.168.10.1:54510      192.168.10.121:8899     CLOSE_WAIT  317193/python3.11   

These go away when I restart homeassistant, and the connection errors do too. I restarted 24 hours ago, and these are the CLOSE_WAIT accumulated in that time. The network connection seem stable, I’ve been running a ping every 30 seconds for the past 24 hrs, and have seen no drops. My best guess is the excessive connections is overloading the logger in some way and causing it to become unreliable?

Is anyone else seeing this? I am running custom parameters, which was running successfully for a few months before the upgrade to the latest version last week.

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Comments: 35 (3 by maintainers)

Commits related to this issue

Most upvoted comments

But how do I update it in HomeAssistant? Do I just update the library in the HA terminal with ➜ ~ “pip install pysolarmanv5” ?

I have done this by rebuilding the HA core. That pulls in the (latest) dependencies. So ha core rebuild on the command line.

You can check what version of pysolarman is in use in the HA instance e.g. this way:

  1. Start the terminal to get to the command line
  2. Start a bash shell in the homeassistant container: docker exec -it homeassistant /bin/bash
  3. List packages in use and check pysolarman python3 -m pip list | grep pysolarman