Open fwolter opened 3 years ago
I read that the inverter does only support one TCP connection at a time.
I can confirm that the binding uses at most one connection to interface with the slave.
Having said this, it is possible that user has some other tool establishing second connection.
Hi @fwolter,
I can confirm, that solaredge devices I know are pretty slow devices, so it is normal to increase timeouts and polling interval.
However the parameter you mentioned is a Modbus binding default, wich is shared among lot of other devices not just sunspec things. So adding a higher default value could break (or slow down) many others.
So I guess the best would be to add this information to the documentation.
I will file a documentation PR. The parameter is not binding wide, but Bridge specific. As you would use the TCP slave bridge only for the connection to one SolarEdge inverter, I think setting the parameter has low side effects.
Not sure if the documentation was ever changed, would be nice to either follow up on this or close it. Possible related PR's: https://github.com/openhab/openhab-addons/pulls?q=is%3Apr+sunspec+is%3Aclosed+
@mrbig @ssalonen The discovery of a SolarEdge inverter doesn't work with the default TCP slave transaction time of 60ms. Setting it to 1000ms works. I read that the inverter does only support one TCP connection at a time. So, I don't know if this is an issue of the binding, of the inverter or if it simply needs to be documented.
Here is the log when the discovery fails: