Replies: 5 comments 13 replies
-
|
Hi Sellmann, I think you can't do or fix this situation. It's seems for me that the TSUN close has a problem. The proxy has two connection. One is called the "server side", which is the connection to the inverter, and the "client side" which is the connection to the TSUN cloud. The message "connection reset by peer" means that the remote side has disconnected, the connection and in the next line you can read, that the client loop (connection) was stopped. So the TSUN cloud send as an So the only solution ist, don't connect to TSUN and run everything on your own. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your response. I will disable the cloud connection because I don't need it. Instead of Talent Home or Pro App I will use my smart home solution. As you can see the Server Loop also stopped working and the Inverter went offline. Will this happen again without the cloud connection? |
Beta Was this translation helpful? Give feedback.
-
|
Loosing the server connection happens sometime (rarely), especially on GEN3 inverters. In the trace above it seems to me that is a follow up error of 'server not reachable ... 192.168.178.101, 53274'. In this situation the proxy disconnect the connection. That will not happen if you disable connection to the cloud. |
Beta Was this translation helpful? Give feedback.
-
|
I thought a little bit about your traces and found a problem, when the connection to the TSUN cloud get lost, the connection to the inverter will be disconnected by the proxy in some situations. I will open an issue for that |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. Today the inverter is offline most of the time and does not reconnect. I don't think the cause is the proxy but I paste the log in here just in case. I restarted the proxy at 09:23 am and it took until 14:31 pm when the inverter connected. At 15:41 pm the server loop stopped again because the inverter was not rachable any longer. '2024-06-17 09:23:38 INFO | root | Server "tsun-proxy - 0.8.0" will be started' |
Beta Was this translation helpful? Give feedback.
-
|
How good is the connection quality to your inverter? Host unreachable is a hint that you have a connection problem, because the TCP connection was lost due to a routing problem, or an other common problem. |
Beta Was this translation helpful? Give feedback.
-
|
The signal strength is 84% according to the TSUN website and I have a wlan repater in my garden with an individual wlan set where the inverter connects to. I don't know what else to do, the G3 inverter has some flaws including the regular connection drop once a day. I'm a silent reader of the corresonding thread in the photovoltaik forum... |
Beta Was this translation helpful? Give feedback.
-
|
Without the TSUN cloud the connection to the inverter is much more stable. The inverter seems to close the connection in regular intervals (aprox. once in a hour) and connects again like in the log sample below: '2024-06-15 17:12:55 INFO | root | [G3] Accept connection from ('192.168.178.101', 64522)' You don't notice anything and the mqtt topics are still refreshed every minute. |
Beta Was this translation helpful? Give feedback.
-
|
with the next version 0.9.0 comes a unique connection id in the logs. This will help to understand which connection logs which message and which Is the root cause of an action |
Beta Was this translation helpful? Give feedback.
-
|
Maybe I found the problem. |
Beta Was this translation helpful? Give feedback.
-
|
This sounds good. I will update the image as soon as the hotfix is available. I appreciate your help and work. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
I suddenly discovered another strange behavior. I noticed some cpu work on my raspberry pi and the proxy seems to loop, take a look at the log: '2024-06-19 08:40:30 INFO | root | Initialize proxy device on home assistant' The log is full of these entries. I had to stop and restart the container. |
Beta Was this translation helpful? Give feedback.
-
|
Yes. |
Beta Was this translation helpful? Give feedback.
-
|
I also found this type of log entries: |
Beta Was this translation helpful? Give feedback.
-
|
It would be very nice if you can send me the trace.log of this packet. I only need about 3 minutes before and 3 minutes after this packet. |
Beta Was this translation helpful? Give feedback.
-
|
Done |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. I will bring a fix with the next release (0.9.0). You have a newer DSP firmware with version V5.0.17, which brings some new data encodings. |
Beta Was this translation helpful? Give feedback.
-
Hello,
first of all thank you very much for the proxy. Good work!
I'm using the proxy in a docker container on my raspberry pi 4 (arm64 image) together with mosquitto mqtt broker and OpenHab also running in containers. I have added the DNS entry for logger.talent... in my pi-hole and a dns rebind entry into my Fritzbox.
My problem is, that the mqtt transmission (e.g. tsun-topics) stops after a while. In the proxy log there are a lot of connection reset messages and "Host is not reachable". 172.18.0.2 is the IP address of the proxy container (bridge network), 47.254.132.252 seems to be the address of logger.talent:
'2024-06-12 08:55:36 ERROR | conn | [] [Errno 104] Connection reset by peer for l('172.18.0.2', 55086) | r('47.254.132.252', 5005)'
'2024-06-12 08:55:36 INFO | root | [] Client loop stopped for l('172.18.0.2', 55086)'
'2024-06-12 08:57:08 INFO | root | [] Connected to ('logger.talent-monitoring.com', 5005)'
'2024-06-12 09:00:58 ERROR | conn | [] [Errno 104] Connection reset by peer for l('172.18.0.2', 39454) | r('47.254.132.252', 5005)'
'2024-06-12 09:00:58 INFO | root | [] Client loop stopped for l('172.18.0.2', 39454)'
'2024-06-12 09:02:26 INFO | root | [] Connected to ('logger.talent-monitoring.com', 5005)'
'2024-06-12 09:06:20 ERROR | conn | [] [Errno 104] Connection reset by peer for l('172.18.0.2', 59334) | r('47.254.132.252', 5005)'
'2024-06-12 09:06:20 INFO | root | [] Client loop stopped for l('172.18.0.2', 59334)'
'2024-06-12 09:07:40 INFO | root | [] Connected to ('logger.talent-monitoring.com', 5005)'
'2024-06-12 09:11:06 ERROR | conn | [] [Errno 104] Connection reset by peer for l('172.18.0.2', 49476) | r('47.254.132.252', 5005)'
'2024-06-12 09:11:06 INFO | root | [] Client loop stopped for l('172.18.0.2', 49476)'
'2024-06-12 09:12:57 INFO | root | [] Connected to ('logger.talent-monitoring.com', 5005)'
'2024-06-12 09:16:59 ERROR | conn | [] [Errno 104] Connection reset by peer for l('172.18.0.2', 37812) | r('47.254.132.252', 5005)'
'2024-06-12 09:16:59 INFO | root | [] Client loop stopped for l('172.18.0.2', 37812)'
'2024-06-12 09:37:36 ERROR | conn | [] [Errno 113] Host is unreachable for l('172.18.0.2', 5005) | r('192.168.178.101', 53274)'
'2024-06-12 09:37:36 INFO | root | [] Server loop stopped for r('192.168.178.101', 53274)'
What can I do to resolve the issue?
Thank you very much.
Beta Was this translation helpful? Give feedback.
All reactions