Closed rzulian closed 1 year ago
@rzulian
Do you by any chance have something else in the network that tries to connect to the modbus server? If you have the chance then sniff (tcpdump?) as close to the port of the inverter as possible if there might be something else that tries to connect. Is your inverter connected via wifi or lan? As first step you can run a continuous ping from the system that runs your HA (or even configure a ping sensor) to at least rule out that there is a network problem.
Thank you for your suggestions. Double checking the inverter I think I've found the problem. For some unknown reason, maybe a firmware update, the inverter was without the subnet mask. Now it's working correctly. Thank you for your support!
I was experiencing a lot of timeouts and errors, while reading from the modbus using the solaredge_modbus component. Sometime ago I wasn't getting those errors, so I was thinking that the problem was on the HA releases, but I've tried different versions and I still have errors. I've tried to use your proxy, but I'm getting errors as well. A lot less to be fair. Now I think that either I've got a firmware update from Solaredge, that is interfering with the modbus. Or that the new network (Unifi router and switches) is doing something wrong. Do you have suggestions on how I can investigate this?
Those are the errors in the proxy