githubDante
githubDante
Hi, The problem is caused by the Pysolarman initialization for each new client/connection which at some point leads to semaphore exhaustion (according to the linked posts). Modification of the proxy...
Hi, Can you try [this version](https://github.com/githubDante/pysolarmanv5/blob/musl-fix/utils/solarman_rtu_proxy.py) of the proxy on `alpine` and see how it handles multiple connections/longer operating intervals.
> Hi @githubDante, unfortunately your version does not work at all with evcc as a client. I can see that some data is sent, but I just get IO timeouts...
The connect call was missing. The branch has been updated. I will try to test in docker as well.
Also a fix for the reconnect issue has been added. @ngehrsitz can you try again. Thank you in advance.
Hi, I don't see it locked in my test environment, but I have to admit that I'm using a simple echo server simulating the datalogger socket. Just added lower socket...
> pysolarmanv5 server mode, is it even doable? Definitely doable , the protocol is the same in TCP-Server mode. After the first packet received from the server the logger is...
SYN & ACK packets, maybe that's what you see in addition to the data packet. Anyway, the lack of response could be due to various reasons (internal error, the logger...
[Yes](https://cloud.dantetk.org/index.php/s/3249GCyFnDgd55q) of course.
`service_write_multiple_holding_registers` is not a PysolarmanV5 function. Which integration are you using ?