-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modbus to Sunsynk inverter communication stops working after a while #359
Comments
Since you have direct serial, try adding the mbusd addon. Then the sunsynk addon uses IP to mbusd adn mbusd connects to the serial interface. Mine is rock solid, and I run mbusd on an old Rpi 1B |
Thanks, will try it. PS. You're an absolute legend for creating and supporting this add-on so well! Thank you! |
I have it running with the mbusd now. So still using pymodbus with port tcp://homeassistant.local:502, is that the best way? Lets see if it resolves my issue. |
Issue still persists with mbusd, I tried to eliminate a couple of environmental variables like different usb port, possible emf interference from other hardware, redoing wire connections. Any suggestions would be welcome. |
What happens if you restart the addon once in this state? Or do you have to unplug it? Seems this can happen with dodgy & fakes serial devices, but in your case you mentioned that it worked for 6 months. see here Might be worth trying a new USB to RS485 adapter, maybe you had a surge/lightning? |
Issue related to
Sunsynk / pymodbus with Home Assistant Add-On, modbus communication stops working after a while.
Describe the issue/bug
My modbus link to Sunsynk Inverter with HA addon was working perfectly for 6 months, until recently I started to get errors (see logs: nonzero urb status: -71) and the communication freezes (readings stay constant). Plugging the USB to RS485 adapter out and back in fixes the comms again. Happens again within 12 to 24 hours after restoring comms.
Your environment
You configuration
Logs
The text was updated successfully, but these errors were encountered: