Closed Cha40s closed 8 months ago
I honestly have no clue what could be wrong
I would try to use a modbus proxy, just because I don't know what else to try ...
OK I try with modbus proxy. It worked for almost a year without one. I'll keep you informed.
Maybe you could check the HA ModBus documentation. There are a few changes with HA 2023.9 and 2023.10. Maybe you have to change the settings for error retries, error discovery, ...
If it started after the HA update to 2023.9 or 2023.10 I would give it a try before switching to a modbus proxy.
Hi, I do have exactly the same issue. Does anyone have new infos or better a solution? THX
Modbus Proxy solved my issue. Took me 10 Minutes to set up.
Ok thanks for that hint. Never did this before. May I kindly ask you @Cha40s to give me some advice how to set it up? Many thanks in advance!
Sure I use this add on for home assistant. https://github.com/Akulatraxas/ha-modbusproxy/ it’s outdated but still works. Just install it and change the ip in the add on configuration tab to your Sungrows ip. After that change the ip for the mqtt configuration in the sugrow yaml to 127.0.0.1. If you want to use an additional program like Evcc just get the data from the proxy by using the ha ip with port 502.
Thanks a lot! I will give it try and yes I am also using EVCC 😉 so also great that you anticipated that already
@Cha40s thanks again I got it working! For now using the proxy seems indeed to have a more stable connection. Fingers crossed 🤞
Describe the bug After a few hours the modbus connection stoped working. The last value of the sensors dosnt change anymore.
Your Sungrow inverter:
Home Assistant :
modbus_sungrow.yaml:
Inverter Firmware Status:
To Reproduce Steps to reproduce the behavior: Occurs after a few hours.