Adding Qivicon to Docker Installation

Hi. I am the proud owner of a Qvicon zigbee stick. I want to now get my Openhab installation talking to the Qivicon. I have found from the NAS OS that the device is on Bus1 and Device 4, aka 10c4:89fb.

Within the Docker I have enable access to the TTY devices. But, now a I am at a loss of how to get the Openhab to connect to the write device!

How can I see what tty devices are available?

Is any additional configuration needed?

Are there any commands that I can use in Karaf to find out what the device is?

Many thanks, George

  • Platform information:
    • Hardware: QNAP TS-453Be NAS using Docker
    • OS: Linux Docker
    • openHAB version: 2.4.0
2019-08-02 17:17:05.117 [ERROR] [ding.zigbee.handler.ZigBeeSerialPort] - Serial Error: Port /dev/ttyACM0 does not exist.
2019-08-02 17:17:05.118 [ERROR] [ngle.telegesis.ZigBeeDongleTelegesis] - Unable to open Telegesis serial port

Just map the device into the container using the --device option when using docker run or add a devices section in your docker compose file if you use that.

See:

If you still have issues please post your docker run command or compose file. :slight_smile:

Okay, thank you very much. I am currently using the Dockert GUI, which handles the yaml file for me.

I will figure out how to recreate the Docker containers with a YML file and post it. I do not currently know how to do that.

This will take me a few days, so bear with me!

Meanwhile I also found blog that makes much sense for using the openHAB Docker container on a QNAP NAS:

I don’t use a QNAP NAS myself so I don’t know if it’s still up to date. :slight_smile:

In the Advanced installation – connect with a Z-wave device section there are also some instructions for using a serial port.

Right. Some progress… I have created a new fresh install of a openhab docker using a docker file, which is below. I have put the file onto a single line, which works fine.

From within OH the thing just appears with a OFFLINE - COMMUNICATION_ERROR error. I also get the port error below.

I did need to manually create the /dev/ttyACM0 after installing the mod into the kernel. It has rights of rw-rw-rw. I have not restarted the QNAP, but I don’t think that I should as the modules wil not persist.

How can I tell that the USB stick is actually on the /dev/ttyACM0? It does appear when I do a lsusb

Is there anyway that I can tell that the QIVICON stick is working?

I have this feeling that the Qivicon is only compatible with USB2 ports, and my NAS only has blue USB3 ones. Could this be the case?

If so, then it is most annoying as I tried so hard to research and buy the correct stick!

Anything else?

Many thanks, George

[/share/CACHEDEV1_DATA/Container] # lsusb
Bus 001 Device 011: ID 10c4:89fb Cygnal Integrated Products, Inc.
Bus 001 Device 002: ID 1c05:2074
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 1c05:3074
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

[567363.887794] usb 1-2.3: USB disconnect, device number 9
[567363.931279] [usb.001.009] /sys/devices/pci0000:00/0000:00:15.0/usb1/1-2/1-2.3 removed.
[567369.451780] usb 1-2.1: new full-speed USB device number 10 using xhci_hcd
[567369.585312] [usb.001.010] /sys/devices/pci0000:00/0000:00:15.0/usb1/1-2/1-2.1 added.
[567690.658289] usb 1-2.1: USB disconnect, device number 10
[567690.702992] [usb.001.010] /sys/devices/pci0000:00/0000:00:15.0/usb1/1-2/1-2.1 removed.
[567700.319575] usb 1-2.3: new full-speed USB device number 11 using xhci_hcd
[567700.470692] [usb.001.011] /sys/devices/pci0000:00/0000:00:15.0/usb1/1-2/1-2.3 added.

2019-08-03 18:45:43.811 [ERROR] [ding.zigbee.handler.ZigBeeSerialPort] - Serial Error:                                  Port /dev/ttyACM0 does not exist.
2019-08-03 18:45:43.812 [ERROR] [ngle.telegesis.ZigBeeDongleTelegesis] - Unable to open                                  Telegesis serial port

docker run --name=openhab-zwave 
-p 18080:8080 -p 8443:8443 -p 5555:5555 
-v /share/Container/openhab/addons/:/openhab/addons 
-v /share/Container/openhab/userdata/:/openhab/userdata  
-v /share/Container/openhab/conf/:/openhab/conf  
--device=/dev/ttyACM0 
--privileged  
--tty openhab/openhab:latest

Maybe the port shows up in the output of the dmesg command when you reinsert it? This is what I see when inserting an FTDI chip based USB Stick on Ubuntu:

[44163.908533] usb 1-2: USB disconnect, device number 2
[44163.909387] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[44163.909453] ftdi_sio 1-2:1.0: device disconnected
...
[44198.761677] ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected
[44198.761773] usb 1-2: Detected FT232RL
[44198.762644] usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0

It also shows after issuing the following command:

$ ls -l /sys/class/tty/ttyUSB0
lrwxrwxrwx 1 root root 0 aug  4 00:12 /sys/class/tty/ttyUSB0 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/ttyUSB0/tty/ttyUSB0

Maybe @clel has some ideas about this?

I did try connecting via a USB hub in an old monitor. I still do not get presented with a /dev/tty* device


[ 1437.382082] usbcore: registered new interface driver cdc_acm
[ 1437.387788] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 1449.081435] usb 1-1.4: USB disconnect, device number 6
[ 1449.146238] [usb.001.006] /sys/devices/pci0000:00/0000:00:15.0/usb1/1-1/1-1.4 removed.
[ 1452.843422] usb 1-1.3: new full-speed USB device number 7 using xhci_hcd
[ 1453.009224] [usb.001.007] /sys/devices/pci0000:00/0000:00:15.0/usb1/1-1/1-1.3 added.