Domoticz package not supporting RFLink USB device

[david284]

Is this a new Bug?

• I checked that the bug hasn't been reported before

Package Name

Domoticz

Package Version

v2020.2-10

Device Model

DS216j

Device Architecture

ARMv7

Firmware Version

6.2.4-25556 Update 7

What happened?

After updating Domoticz to v2020.2-10, Domoticz no longer shows a serial port for my RFLink device attached via USB

My previous install of Domoticz was a manual install from a prebuilt package from some called jadahl, which other comments suggest that it contained the right serial drivers for RFLink. Unfortunately the website for this is no longer available

Should the package contain the serial drivers? - or does there need to be instructions on how to add the right serial drivers (and where to get them from)
Domoticz does support RFLink natively, so I would expect a 'synology' package of this to also support RFLink 'out the box'

Reproduction steps

...
Uninstalled previous version of Domoticz - installed new version v202.2-10
Domoticz log shows RFLink fails to open serial port
Hardware menu option for RFLink doesn't show any serial port to select
RFLink device has been separately tested on a PC using RFLink loader and is working correctly
Synology info center shows a USB serial adapter - but not as an RFLink device
No tty appears to be assigned to it
I've added some extra details in 'other logs' of me trying to find out more about the usb devices - but I'm no linux expert

domitcz.edited.log

Install Log

Installation log: /var/log/packages/domoticz.log

Service Log

No response

Other Logs

lsusb
|__usb1          1d6b:0002:0310 09  2.00  480MBit/s 0mA 1IF  (Linux 3.10.105 xhci-hcd xHCI Host Controller f10f0000.usb3) hub
  |__1-1         1a86:7523:0254 ff  1.10   12MBit/s 96mA 1IF  ( d8b9d0a2c794b989a795d784d1)
|__usb2          1d6b:0003:0310 09  3.00 5000MBit/s 0mA 1IF  (Linux 3.10.105 xhci-hcd xHCI Host Controller f10f0000.usb3) hub
|__usb3          1d6b:0002:0310 09  2.00  480MBit/s 0mA 1IF  (Linux 3.10.105 xhci-hcd xHCI Host Controller f10f8000.usb3) hub
  |__3-1         1058:0910:0106 00  2.00  480MBit/s 2mA 1IF  (Western Digital  External HDD     574341505733373836343634)
|__usb4          1d6b:0003:0310 09  3.00 5000MBit/s 0mA 1IF  (Linux 3.10.105 xhci-hcd xHCI Host Controller f10f8000.usb3) hub
|__usb5          1d6b:0002:0310 09  2.00  480MBit/s 0mA 1IF  (ehci_hcd f1058000.usb) hub


 ll /sys/class/tty
total 0
drwxr-xr-x  2 root root 0 May 17 19:31 .
drwxr-xr-x 37 root root 0 May 16 22:09 ..
lrwxrwxrwx  1 root root 0 May 17 19:31 console -> ../../devices/virtual/tty/console
lrwxrwxrwx  1 root root 0 May 17 19:31 ptmx -> ../../devices/virtual/tty/ptmx
lrwxrwxrwx  1 root root 0 May 17 19:31 tty -> ../../devices/virtual/tty/tty
lrwxrwxrwx  1 root root 0 May 17 19:31 ttyS0 -> ../../devices/soc.0/internal-regs.1/f1012000.serial/tty/ttyS0
lrwxrwxrwx  1 root root 0 May 17 19:31 ttyS1 -> ../../devices/soc.0/internal-regs.1/f1012100.serial/tty/ttyS1
lrwxrwxrwx  1 root root 0 May 17 19:31 ttyS2 -> ../../devices/platform/serial8250/tty/ttyS2
lrwxrwxrwx  1 root root 0 May 17 19:31 ttyS3 -> ../../devices/platform/serial8250/tty/ttyS3


 dmesg | grep tty
[    0.000000] Kernel command line: console=ttyS0,115200 ip=off initrd=0x3000000 root=/dev/md0 rw syno_hw_version=DS216j hd_power_on_seq=2 ihd_num=2 netif_num=1 syno_hdd_enable=15,16 flash_size=8
[    3.548199] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 44) is a 16550A
[    4.357721] console [ttyS0] enabled
[    4.381893] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 45) is a 16550A
[   31.655031] synobios open /dev/ttyS1 success
[   59.592209] synobios open /dev/ttyS1 success
[   60.529565] synobios open /dev/ttyS1 success


 cat /proc/tty/drivers
/dev/tty             /dev/tty        5       0 system:/dev/tty
/dev/console         /dev/console    5       1 system:console
/dev/ptmx            /dev/ptmx       5       2 system
serial               /dev/ttyS       4 64-67 serial
pty_slave            /dev/pts      136 0-1048575 pty:slave
pty_master           /dev/ptm      128 0-1048575 pty:master



dmesg | grep usb
[   31.046687] usbcore: registered new interface driver usbfs
[   31.055413] usbcore: registered new interface driver hub
[   31.063509] usbcore: registered new device driver usb
[   31.186932] xhci-hcd f10f0000.usb3: USB2 Vbus gpio 58
[   31.192020] xhci-hcd f10f0000.usb3: power control enabled
[   31.197482] xhci-hcd f10f0000.usb3: xHCI Host Controller
[   31.202834] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 1
[   31.210658] xhci-hcd f10f0000.usb3: irq 48, io mem 0xf10f0000
[   31.225290] xhci-hcd f10f0000.usb3: USB3 Vbus gpio 58
[   31.230374] xhci-hcd f10f0000.usb3: power control enabled
[   31.235833] xhci-hcd f10f0000.usb3: xHCI Host Controller
[   31.241187] xhci-hcd f10f0000.usb3: new USB bus registered, assigned bus number 2
[   31.260236] xhci-hcd f10f8000.usb3: USB2 Vbus gpio 59
[   31.265344] xhci-hcd f10f8000.usb3: power control enabled
[   31.270780] xhci-hcd f10f8000.usb3: xHCI Host Controller
[   31.276167] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 3
[   31.286406] xhci-hcd f10f8000.usb3: irq 49, io mem 0xf10f8000
[   31.317598] xhci-hcd f10f8000.usb3: USB3 Vbus gpio 59
[   31.322686] xhci-hcd f10f8000.usb3: power control enabled
[   31.328167] xhci-hcd f10f8000.usb3: xHCI Host Controller
[   31.333536] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 4
[   31.454433] orion-ehci f1058000.usb: failed to get Vbus gpio
[   31.460137] orion-ehci f1058000.usb: USB2 Vbus gpio -1
[   31.465325] orion-ehci f1058000.usb: power control disabled
[   31.470923] orion-ehci f1058000.usb: EHCI Host Controller
[   31.476370] orion-ehci f1058000.usb: new USB bus registered, assigned bus number 5
[   31.484068] orion-ehci f1058000.usb: irq 50, io mem 0xf1058000
[   31.503049] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00
[   32.593050] usb 1-1: new full-speed USB device number 2 using xhci-hcd
[   33.783054] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[   83.025008] usb-storage 3-1:1.0: USB Mass Storage device detected
[   83.063244] scsi2 : usb-storage 3-1:1.0
[   83.067343] usbcore: registered new interface driver usb-storage
[   83.341386] usbcore: registered new interface driver usblp
[   83.594082] usbcore: registered new interface driver usbhid
[   83.599683] usbhid: USB HID core driver
[67254.386858] usb 1-1: USB disconnect, device number 2
[69846.643081] usb 1-1: new full-speed USB device number 3 using xhci-hcd

[hgy59]

@th0ma7 does our SynoKernel USB Serial drivers package support this kind of device (RFLink USB device) - or can we update that package?

[th0ma7]

Good question. You definitively need the usbserial driver anyhow to get this working so a link tthat package along with instructions would help.

[david284]

Hi Guys, Where would I get the driver from? I've tried the community 'usb serial drivers' without any luck - I believe my RFLink running on an Arduino clone uses a CH340 chipset, and the community serial driver package I've loaded states it supports the CH341, so I suspect it wont work with CH340 The author of the package says it's based on the jadahl drivers he's been able to retrieve, but it looks like it's limited to what it does support I hope you can help me progress this Regards David

…

On 18/05/2023 10:48, Vincent Fortier wrote: Good question. You definitively need the usbserial driver anyhow to get this working so a link tthat package along with instructions would help. — Reply to this email directly, view it on GitHub <#5735 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANUGDYMDUJ7FHH2C3BHLDXTXGXV6VANCNFSM6AAAAAAYGDB5RM>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[david284]

Good question. You definitively need the usbserial driver anyhow to get this working so a link tthat package along with instructions would help.

@th0ma7

I've tried SynoKernel USB Serial drivers package, but it doesn't appear to work on my DS216j - I've raised a separate issue for that (#5743 )
If that where to work it would be the best solution