JGB

Just a quick update that might help others with intermittent RS485 communication problems. I discovered that the cable (USB) I was using to power my RPi was rubbish. The RPi was not getting enough power, which was causing the USB interface that the RS485 adaptor was connected on to restart. Replaced the cable ... problems sorted. Picked it up from dmesg in SSH connection to the host OS .

@_terminal Thanks. I tried to set the Modbus SN as suggested, but it didn't make a difference. @kellerza I'm pretty sure the cabling is good. I crimped a RJ45 on both ends of the cable, tested it (with a network cable tester) and then cut the one end off to connect to the USB (https://www.robotics.org.za/RS485-3P). I used a twisted pair (1 + 2) for B and A and also used the ground (3). I'll give that Waveshare USB a try, although at this point, I think my problem may not be related to the choice of RS485 adaptor. I'm getting the following in the logs: Debug shows it polls a few times and then "freezes" for around 10 seconds followed by the "Timeout reading:" entry. I think there may be some other hardware problem, perhaps with the USB Interface on the Pi. I am getting data from the inverter. It's enough to have a useful dashboard, but it is slightly delayed with all the 10 second pauses related to the timeouts. More importantly, it is gnawing at me knowing these timeouts are occurring

Has anybody got the Waveshare RS485/CAN Hat (https://www.waveshare.com/rs485-can-hat.htm) working with Home Assistant OS? I have a working setup using a USB interface but I'm getting lots of Timeout errors, as discussed extensively on this thread. I've got access to the host OS and have managed to get the hat configured as a CAN interface (as a test). I'm struggling to get RS485 working. Does anybody have any pointers? ps: @kellerza I am very impressed with your Sunsynk add-on. That combined with the HA built in Energy Management and the power-distribution-card is very useful.