Hello I am using the nortek security and control husbz b - 1 stick for zigbee connectivity. According to my raspberry pi, when I plug the USB into the computer it identifies on ttyusb1 and ttyusb2. I added those extra interfaces into the Java options for openhab. From the debug logs I can see it initialises on whichever option I select from the serial Port configuration dropdown of my zigbee controller. But when I try and search for zigbee devices, I get an error that it failed to communicate regardless of which option I pick from the drop-down. I’ve read many articles of people having similar issues but no concrete answers. It should be noted that my zwave through my razberry works very well although that is on my ttyAMA0 interface. Let me know what logs I can provide to assist.
The husbz1 is a combo zwave/zigbee device. The Zigbee coordinator is the second device (ttyUSB2).
Are the file ownership or permissions different on /dev/ttyUSB2 and /dev/ttyAMA0?
Do you have a /dev/ttyUSB0?
ok I had figured ZigBee would be the second device (in my case ttyUSB2). I don’t have anything else plugged into the usb ports but I do not see a ttyUSB0.
When examining permissions I noticed something interesting: check this out…no serial listed as there is for AMA0?
[18:01:40] openhabian@openHABianPi:/dev$ ls -la | grep ttyUSB2
crw-rw---- 1 root dialout 188, 2 Feb 7 18:01 ttyUSB2
[18:01:53] openhabian@openHABianPi:/dev$ ls -la | grep ttyAMA0
lrwxrwxrwx 1 root root 7 Jan 9 15:17 serial0 -> ttyAMA0
crw-rw---- 1 root dialout 204, 64 Feb 7 17:27 ttyAMA0
Also here is my debug log if it helps:
18:00:04.039 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
18:00:04.050 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - null: networkStateUpdated called with state=UNINITIALISED
18:00:04.050 [DEBUG] [nding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyUSB2] at 57600 baud, flow control FLOWCONTROL_OUT_XONOFF.
18:00:04.062 [DEBUG] [nding.zigbee.handler.ZigBeeSerialPort] - Serial port [/dev/ttyUSB2] is initialized.
18:00:26.339 [DEBUG] [gbee.discovery.ZigBeeDiscoveryService] - Starting ZigBee scan for zigbee:coordinator_ember:168c59a9821
18:00:26.347 [DEBUG] [gbee.handler.ZigBeeCoordinatorHandler] - ZigBee coordinator is offline - aborted scan for zigbee:coordinator_ember:168c59a9821
It’s odd that you aren’t seeing both. I use udev rules, but consistently see them come up on ttyUSB0 (zwave) and ttyUSB1 (zigbee). What do you see when you run dmesg -T | grep tty? And id openhab?
First Command:
[Wed Jan 9 15:16:58 2019] Kernel command line: 8250.nr_uarts=1 bcm2708_fb.fbwid th=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 vc_mem. mem_base=0x3ea00000 vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=tt 1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[Wed Jan 9 15:16:58 2019] console [tty1] enabled
[Wed Jan 9 15:16:58 2019] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87 , base_baud = 0) is a PL011 rev2
[Wed Jan 9 15:16:58 2019] 3f215040.serial: ttyS0 at MMIO 0x0 (irq = 220, base_b aud = 50000000) is a 16550
[Wed Feb 6 15:52:43 2019] usb 1-1.5: cp210x converter now attached to ttyUSB0
[Wed Feb 6 15:52:43 2019] usb 1-1.5: cp210x converter now attached to ttyUSB1
[Wed Feb 6 18:07:48 2019] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[Wed Feb 6 18:07:48 2019] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[Wed Feb 6 18:07:48 2019] cp210x ttyUSB0: failed get req 0x8 size 1 status: -32
[Wed Feb 6 18:07:48 2019] cp210x ttyUSB0: failed set request 0x12 status: -19
[Wed Feb 6 18:07:48 2019] cp210x ttyUSB0: failed set request 0x0 status: -19
[Wed Feb 6 18:07:48 2019] cp210x ttyUSB0: cp210x converter now disconnected fro m ttyUSB0
[Wed Feb 6 18:07:48 2019] cp210x ttyUSB1: cp210x converter now disconnected fro m ttyUSB1
[Wed Feb 6 18:08:12 2019] usb 1-1.5: cp210x converter now attached to ttyUSB1
[Wed Feb 6 18:08:12 2019] usb 1-1.5: cp210x converter now attached to ttyUSB2
[Wed Feb 6 18:08:40 2019] cp210x ttyUSB1: cp210x converter now disconnected fro m ttyUSB1
[Wed Feb 6 18:08:40 2019] cp210x ttyUSB2: cp210x converter now disconnected fro m ttyUSB2
[Wed Feb 6 18:09:55 2019] usb 1-1.5: cp210x converter now attached to ttyUSB1
[Wed Feb 6 18:09:55 2019] usb 1-1.5: cp210x converter now attached to ttyUSB2
[Wed Feb 6 18:48:33 2019] cp210x ttyUSB1: cp210x converter now disconnected fro m ttyUSB1
[Wed Feb 6 18:48:33 2019] cp210x ttyUSB2: cp210x converter now disconnected fro m ttyUSB2
[Wed Feb 6 18:48:37 2019] usb 1-1.5: cp210x converter now attached to ttyUSB0
[Wed Feb 6 18:48:37 2019] usb 1-1.5: cp210x converter now attached to ttyUSB1
[Wed Feb 6 19:05:06 2019] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[Wed Feb 6 19:05:06 2019] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[Wed Feb 6 19:05:06 2019] cp210x ttyUSB0: failed get req 0x8 size 1 status: -32
[Wed Feb 6 19:05:06 2019] cp210x ttyUSB0: failed set request 0x12 status: -19
[Wed Feb 6 19:05:06 2019] cp210x ttyUSB0: failed set request 0x0 status: -19
[Wed Feb 6 19:05:06 2019] cp210x ttyUSB0: cp210x converter now disconnected fro m ttyUSB0
[Wed Feb 6 19:05:06 2019] cp210x ttyUSB1: cp210x converter now disconnected fro m ttyUSB1
[Wed Feb 6 19:05:49 2019] usb 1-1.5: cp210x converter now attached to ttyUSB1
[Wed Feb 6 19:05:49 2019] usb 1-1.5: cp210x converter now attached to ttyUSB2
[Wed Feb 6 19:52:52 2019] cp210x ttyUSB2: failed set request 0x7 status: -32
[Wed Feb 6 19:53:01 2019] cp210x ttyUSB2: failed set request 0x7 status: -32
[Wed Feb 6 19:53:01 2019] cp210x ttyUSB2: failed set request 0x7 status: -32
[Wed Feb 6 19:53:01 2019] cp210x ttyUSB2: failed set request 0x7 status: -32
[Wed Feb 6 19:53:01 2019] cp210x ttyUSB2: failed set request 0x7 status: -32
Second Command:
uid=109(openhab) gid=114(openhab) groups=114(openhab),5(tty),20(dialout),29(audio),113(bluetooth),997(gpio)It looks like they are coming up on ttyUSB0 and ttyUSB1, but then they shift. Have you been unplugging the stick? Just to prove it works, you should completely power down the Pi, and restart it. Then try zigbee on ttyUSB1, and don’t unplug the stick, or the ports will change.
Once you get it all working, search the forum for udev rules… I’m sure I’ve posted them for this device.
Found them…
No dice, thank you for the help though. I’m considering just switching to a different controller that is purely zigbee. Maybe it will work better…come to think of it I was never able to get zwave working either and when it did partially work it didn’t have necessary security protocol for deadbolt locks.
OH is not able to communicate with your serial ports, so I don’t understand how a different controller would be any different.
If you’d still like some help, please post details of your hardware, OH version, Java version, the EXTRA_JAVA_OPTS, how you configured them, and if you created an /etc/default/openhab2 file, what the permissions are on it.
BTW, security was included in the OH 2.4 stable zwave binding.
I can confirm what Scott said. I have this exact same dongle and it works great, including two zwave deadbolts. The problem you are having looks a lot like it is OS related so I see no reason to believe a different controller would work better.