Issue with Zigbee binding in openhab3

did a fresh install of centos 8 with zulu11
i installed openhab3 and configured the java options for my ember controller
No communication ports found, cannot connect to [/dev/ttyUSB1]

i get the USB ports in my drop down so I do not believe the java options is an issue
The permissions for the file have the dialout group
openhab is a member of dialout group

I’m stumped never had this sort of issue with 2.x

Try removing the Java options they may no longer be needed. I have a test OH3 system with a coordinator. I may test mine later.

EDIT I just added my Ember based coordinator in OH3 with no Java options and no issues.

Thanks Ill try that now

2020-11-08 15:43:32.720 [DEBUG] [nding.zigbee.serial.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyUSB0] at 57600 baud, flow control FLOWCONTROL_OUT_RTSCTS.
2020-11-08 15:43:32.723 [DEBUG] [nding.zigbee.serial.ZigBeeSerialPort] - No communication ports found, cannot connect to [/dev/ttyUSB0]

same issue tried various baud rates and hardware/software flow control
currently running
Centos 8
Openhab 3.0.0.M2

the dongle is a Nortek husbzb-1 which i have been using for over a year without issue on openhab2

What does dmesg | grep tty show? The OS needs to recognize the device first. For example here is mine with a zigbee & zwave stick using .dev.ttyUSB0 and /dev/ttyUSB1

pi@raspberrypi:~ $ dmesg | grep tty
[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p7 rootfstype=ext4 elevator=deadline rootwait
[    0.000876] printk: console [tty1] enabled
[    2.523364] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 81, base_baud = 0) is a PL011 rev2
[    7.283286] usb 1-1.1.3: cp210x converter now attached to ttyUSB0
[    7.295514] usb 1-1.1.3: cp210x converter now attached to ttyUSB1

yeah it shows the cp210x converter and shows it as ttyUSB0 and ttyUSB1

[ 14.706534] usb 1-1: cp210x converter now attached to ttyUSB0
[ 14.708492] usb 1-1: cp210x converter now attached to ttyUSB1

the tty’s show as devices with correct permissions

crw-rw----. 1 root dialout 188, 0 Nov 8 18:24 /dev/ttyUSB0
crw-rw----. 1 root dialout 188, 1 Nov 8 18:24 /dev/ttyUSB1

openhab is in the correct groups

[nozlaf@localhost ~]# sudo groups openhab
openhab : openhab tty dialout audio

I am currently using that same dongle in my test system, a Raspberry Pi running the latest OH3 snapshot in Docker container. Both Zwave and Zigbee are recognized by the bindings. Perhaps something different is happening with security permissions in RedHat based distributions. You may want to try selinux in permissive mode.

what baud rate etc… do you use
i am using 57600 software with USB1 on openhab2

ill try it again on openhab3, i am sure i had selinux disabled but will confirm

same machine openhab2 works fine
openhab3 doesnt

fml going back to openhab 2.5 for now

1 Like

@chris any idea about what is going on here?
with openhab 2.5 i have no issues but 3.0 m2 installed via yum on centos 8 it doesnt work

I can uninstall 3.0 and install 2.5 and it works perfectly

Sorry - I’m not really sure why the serial ports wouldn’t work. From the binding perspective there’s no change between OH2 and OH3 and certainly in my tests here I’ve had no problems. Unfortunately I’m not really sure what else to suggest - sorry.

If it would help, I may be able to spin up a CentOS VM on my old laptop to verify connectivity to my coordinator.

I have confirmed the issue. events.log states

2020-11-21 09:28:13.785 [INFO ] [me.event.ThingStatusInfoChangedEvent] - Thing 'zigbee:coordinator_ember:fb110aa92b' changed from UNKNOWN to OFFLINE: Failed to open communications port

Another VM with OH 2.5.10 works fine. and Z-Wave has a similar issue. This points to something serial port related within OH3 Core.

Thanks for confirming I am not crazy

I am installing debian right now going to see if that works.

can confirm it works with the apt repo using debian 10

1 Like