Q-Cells Q.Home+ RS485 not working, help needed

[MrRickwi]

Hi, I have a Q-Cells G3 Inverter which is the same as the Solax X3 Hybrid G4. I'm using a Raspberry Pi 4 with an USB adapter to connect to Modbus. However, the solar-modbus integration doesn't read any values. Using dmesg I see that /dev/ttyUSB0 is an ch341-uart device. However, the log of HomeAssistant states that solax-modbus is unable to read anything from that device. Before I buy a Waveshare RS485 to TCP adapter: Do you have any hints if this should work? Any ideas how to debug? Thanks in advance. Wilfried

homeassststant.log:

2023-03-31 06:39:10.638 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX: reading serial number from address 0x0 failed; other address may succeed
2023-03-31 06:39:10.650 WARNING (MainThread) [homeassistant.util.async_] Detected blocking call to sleep inside the event loop. This is causing stability issues. Please report issue to the custom integration author for solax_modbus doing blocking calls at custom_components/solax_modbus/init.py, line 318: return self.client.read_holding_registers(address, count, **kwargs)
2023-03-31 06:39:10.657 WARNING (MainThread) [homeassistant.util.async] Detected blocking call to sleep inside the event loop. This is causing stability issues. Please report issue to the custom integration author for solax_modbus doing blocking calls at custom_components/solax_modbus/init.py, line 318: return self.client.read_holding_registers(address, count, **kwargs)
2023-03-31 06:39:10.671 WARNING (MainThread) [homeassistant.util.async] Detected blocking call to sleep inside the event loop. This is causing stability issues. Please report issue to the custom integration author for solax_modbus doing blocking calls at custom_components/solax_modbus/init.py, line 318: return self.client.read_holding_registers(address, count, **kwargs)
2023-03-31 06:39:10.686 WARNING (MainThread) [homeassistant.util.async] Detected blocking call to sleep inside the event loop. This is causing stability issues. Please report issue to the custom integration author for solax_modbus doing blocking calls at custom_components/solax_modbus/init.py, line 318: return self._client.read_holding_registers(address, count, **kwargs)
2023-03-31 06:39:13.705 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX: reading serial number from address 0x300 failed; other address may succeed
2023-03-31 06:39:13.708 ERROR (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX: cannot find serial number, even not for MIC
2023-03-31 06:39:13.711 ERROR (MainThread) [custom_components.solax_modbus.plugin_solax] unrecognized inverter type - serial number : unknown

dmesg | grep -i usb:

[ 0.000000] Kernel command line: zram.enabled=1 zram.num_devices=3 apparmor=1 security=apparmor rootwait systemd.machine_id=632782d2a89346e59a3d4390e44322c9 cgroup_enable=memory fsck.repair=yes coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=DC:A6:32:8D:46:1B vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=tty1 usb-storage.quirks=174c:55aa:u,2109:0715:u,152d:0578:u,152d:0579:u,152d:1561:u,174c:0829:u,14b0:0206:u root=PARTUUID=8d3d53e3-6d49-4c38-8349-aff6859e82fd rootfstype=squashfs ro rauc.slot=A
[ 0.167366] usbcore: registered new interface driver usbfs
[ 0.167432] usbcore: registered new interface driver hub
[ 0.167520] usbcore: registered new device driver usb
[ 0.167847] usb_phy_generic phy: supply vcc not found, using dummy regulator
[ 0.168050] usb_phy_generic phy: dummy supplies not allowed for exclusive requests
[ 1.253254] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[ 1.254770] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[ 1.254806] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[ 1.255191] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[ 1.255228] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.255256] usb usb1: Product: xHCI Host Controller
[ 1.255280] usb usb1: Manufacturer: Linux 5.15.84-v8 xhci-hcd
[ 1.255303] usb usb1: SerialNumber: 0000:01:00.0
[ 1.256029] hub 1-0:1.0: USB hub found
[ 1.257101] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15
[ 1.257139] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.257167] usb usb2: Product: xHCI Host Controller
[ 1.257190] usb usb2: Manufacturer: Linux 5.15.84-v8 xhci-hcd
[ 1.257213] usb usb2: SerialNumber: 0000:01:00.0
[ 1.257854] hub 2-0:1.0: USB hub found
[ 1.260452] usbcore: registered new interface driver uas
[ 1.260572] usbcore: registered new interface driver usb-storage
[ 1.260711] usbcore: registered new interface driver usbserial_generic
[ 1.260759] usbserial: USB Serial support registered for generic
[ 1.271423] usbcore: registered new interface driver usbhid
[ 1.271433] usbhid: USB HID core driver
[ 1.514251] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 1.664960] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
[ 1.665004] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1.665021] usb 1-1: Product: USB2.0 Hub
[ 1.666428] hub 1-1:1.0: USB hub found
[ 1.962239] usb 1-1.2: new full-speed USB device number 3 using xhci_hcd
[ 2.067683] usb 1-1.2: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[ 2.067731] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.067749] usb 1-1.2: Product: CP2102 USB to UART Bridge Controller
[ 2.067765] usb 1-1.2: Manufacturer: Silicon Labs
[ 2.067780] usb 1-1.2: SerialNumber: 0057
[ 2.150261] usb 1-1.4: new full-speed USB device number 4 using xhci_hcd
[ 2.256508] usb 1-1.4: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64
[ 2.256542] usb 1-1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 2.256555] usb 1-1.4: Product: USB Serial
[ 3.288660] usbcore: registered new interface driver ch341
[ 3.288746] usbserial: USB Serial support registered for ch341-uart
[ 3.290201] usbcore: registered new interface driver cp210x
[ 3.292046] usbserial: USB Serial support registered for cp210x
[ 3.299131] usb 1-1.4: ch341-uart converter now attached to ttyUSB0
[ 3.299793] usb 1-1.2: cp210x converter now attached to ttyUSB1
[ 4.200545] usbcore: registered new interface driver brcmfmac

[wills106]

Have you tried swapping the A&B wire round? They need to go A-A & B-B, they don't need crossing over like you would do in some RS232 situations.
Also are you using a Baud of 19200?

[MrRickwi]

Sorry, forgot to mention: I tried swapping A and B, doesn't help. I also double-checked the baud rate at my device and in the config, both are 19200, slave ID 1. Interesting: If I do cat /dev/ttyUSB0, after starting Home Assistant, it hangs. If I do this later, it outputs nothing. I have a second RS485 device (a EDL21 SmartMeter IR device) which is connected to /dev/ttyUSB1, and this one works pretty cool. I ordered now another USB stick, now from Waveshare, which has Power/TX/RX diodes, will see if it works better than the 9€ USB stick.

BTW, thanks for your cool add-in!

[MrRickwi]

If all else fails, I will order the RS485 to Ethernet connector. Must search for a free port for it ;-)

[MrRickwi]

Solved by using a different RS485 adapter.