HUSBZB - getting zigbee to work / openhabian

[jimmyt (Greg)]

Like most, the zwave portion of this adapter is fine. Rasp pi 3+ with the nortek husbzb-1 stick. Its zigbee where I cant get it working. I have read as much as I think I can find and the controller keeps saying “unknown” In my case, its set to run on /dev/ttyAMA0. I have hardware flow control set and the baud rate is 57600. I have added the openhab user to the dialout and tty goups. If I run some of the basic commands, it all seems to report like it should… Is there anything I am missing that anyone can see in the logs? thanks!

dmesg | grep tty
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=d2deeea0-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[    0.000827] console [tty1] enabled
[    0.754364] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[    3.706646] usb 1-1.2: cp210x converter now attached to ttyUSB0
[    3.714256] usb 1-1.2: cp210x converter now attached to ttyUSB1

ls /dev/tty*
/dev/tty    /dev/tty13  /dev/tty19  /dev/tty24  /dev/tty3   /dev/tty35  /dev/tty40  /dev/tty46  /dev/tty51  /dev/tty57  /dev/tty62    /dev/ttyprintk
/dev/tty0   /dev/tty14  /dev/tty2   /dev/tty25  /dev/tty30  /dev/tty36  /dev/tty41  /dev/tty47  /dev/tty52  /dev/tty58  /dev/tty63    /dev/ttyUSB0
/dev/tty1   /dev/tty15  /dev/tty20  /dev/tty26  /dev/tty31  /dev/tty37  /dev/tty42  /dev/tty48  /dev/tty53  /dev/tty59  /dev/tty7     /dev/ttyUSB1
/dev/tty10  /dev/tty16  /dev/tty21  /dev/tty27  /dev/tty32  /dev/tty38  /dev/tty43  /dev/tty49  /dev/tty54  /dev/tty6   /dev/tty8
/dev/tty11  /dev/tty17  /dev/tty22  /dev/tty28  /dev/tty33  /dev/tty39  /dev/tty44  /dev/tty5   /dev/tty55  /dev/tty60  /dev/tty9
/dev/tty12  /dev/tty18  /dev/tty23  /dev/tty29  /dev/tty34  /dev/tty4   /dev/tty45  /dev/tty50  /dev/tty56  /dev/tty61  /dev/ttyAMA0

I added the extra java opts - EXTRA_JAVA_OPTS="-Dgnu.io.rxtx.SerialPorts=/dev/ttyAMA0"

and now for the debug logs…

2018-06-25 08:22:51.305 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised 5398A403C02453A539464809E4D7086A
2018-06-25 08:22:51.310 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array 5398A403C02453A539464809E4D7086A
2018-06-25 08:22:51.313 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - ZigBee Ember Coordinator opening Port:'/dev/ttyAMA0' PAN:539f, EPAN:907585F9084B6CD9, Channel:-1
2018-06-25 08:22:51.317 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
2018-06-25 08:22:52.326 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
2018-06-25 08:22:52.331 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
2018-06-25 08:22:52.338 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise 5398A403C02453A539464809E4D7086A
2018-06-25 08:22:52.343 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EZSP dongle initialize with protocol ASH2.
2018-06-25 08:22:52.349 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyAMA0] at 57600 baud, flow control FLOWCONTROL_OUT_RTSCTS.
2018-06-25 08:22:52.359 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [/dev/ttyAMA0] is initialized.
2018-06-25 08:22:52.371 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameRst []
2018-06-25 08:22:52.370 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler thread started
2018-06-25 08:22:52.384 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: TX EZSP queue: 1

[hr3 (Harry)]

Linear HUSBZB-1

I am looking to control GE Zigbee bulbs. This sticks seems to support Zigbee. Does this work with openhab?

Setup HUSBZB-1 (EMBER EM35x Coordinator) Help Please

Greetings, I’m having some difficulty on my Linux Mint 18.2 system with ZULU Java installed. OpenHAB 2. A friend tried on his Windows machine with similar issues, so I could use a step by step to get this newbie up and running, please!! The controller… First, this is what $ dmesg | grep tty shows… [ 0.000000] console [tty0] enabled [ 25.691024] usb 8-1.1: cp210x converter now attached to ttyUSB0 [ 25.704233] usb 8-1.1: cp210x converter now attached to ttyUSB1 [ 26.218733] cp210x…

[chris (Chris Jackson)]

@jimmyt

I have hardware flow control set and the baud rate is 57600

You should use software flow control with 57600. I’m not sure that will really make much difference, but hardware is strictly not correct.

[jimmyt (Greg)]

thanks… made the change to software flow control and this is what I get… still says “unknown” even rebooted… the last line after the reboot is curious since there is nothing else beyond the firmware status - 8 seconds after the events, etc start… now I am really confused…

2018-06-25 10:34:57.990 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: Start.

2018-06-25 10:34:57.997 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: Done.

2018-06-25 10:34:58.000 [DEBUG] [bee.internal.ZigBeeNetworkDiscoverer] - Network discovery task shutdown

2018-06-25 10:34:58.021 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler exited.

2018-06-25 10:34:58.023 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port '/dev/ttyAMA0' closed.

2018-06-25 10:34:58.026 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler close.

2018-06-25 10:34:58.030 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler close complete.

2018-06-25 10:34:58.033 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network [zigbee:coordinator_ember:9c44f932] closed.

2018-06-25 10:34:58.036 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - Initializing ZigBee Ember serial bridge handler.

2018-06-25 10:34:58.039 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_ember:9c44f932].

2018-06-25 10:34:58.043 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel -1

2018-06-25 10:34:58.046 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 21407

2018-06-25 10:34:58.049 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID 907585F9084B6CD9

2018-06-25 10:34:58.052 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

2018-06-25 10:34:58.055 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

2018-06-25 10:34:58.060 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised 9AC2803B844B7DF8E8CFC70F22F94088

2018-06-25 10:34:58.064 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array 9AC2803B844B7DF8E8CFC70F22F94088

2018-06-25 10:34:58.069 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - ZigBee Ember Coordinator opening Port:'/dev/ttyAMA0' PAN:539f, EPAN:907585F9084B6CD9, Channel:-1

2018-06-25 10:34:58.073 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start

2018-06-25 10:34:59.078 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting

2018-06-25 10:34:59.084 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator

2018-06-25 10:34:59.091 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise 9AC2803B844B7DF8E8CFC70F22F94088

2018-06-25 10:34:59.094 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EZSP dongle initialize with protocol ASH2.

2018-06-25 10:34:59.098 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyAMA0] at 57600 baud, flow control FLOWCONTROL_OUT_XONOFF.

2018-06-25 10:34:59.108 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [/dev/ttyAMA0] is initialized.

2018-06-25 10:34:59.115 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameRst []

2018-06-25 10:34:59.116 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler thread started

2018-06-25 10:34:59.124 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: TX EZSP queue: 1

then I rebooted the pi -

2018-06-25 10:39:33.196 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=121, service.bundleid=256, service.scope=bundle, component.name=org.openhab.binding.zigbee.internal.ZigBeeHandlerFactory, component.id=20} - org.openhab.binding.zigbee

2018-06-25 10:39:33.223 [DEBUG] [org.openhab.binding.zigbee          ] - BundleEvent STARTING - org.openhab.binding.zigbee

2018-06-25 10:39:33.226 [DEBUG] [org.openhab.binding.zigbee          ] - BundleEvent STARTED - org.openhab.binding.zigbee

2018-06-25 10:39:33.256 [DEBUG] [org.openhab.binding.zigbee          ] - BundleEvent [unknown:512] - org.openhab.binding.zigbee

2018-06-25 10:39:33.265 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=122, service.bundleid=257, service.scope=bundle, component.name=org.openhab.binding.zigbee.cc2531.internal.CC2531HandlerFactory, component.id=21} - org.openhab.binding.zigbee.cc2531

2018-06-25 10:39:33.269 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - BundleEvent STARTING - org.openhab.binding.zigbee.cc2531

2018-06-25 10:39:33.272 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - BundleEvent STARTED - org.openhab.binding.zigbee.cc2531

2018-06-25 10:39:33.291 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - BundleEvent [unknown:512] - org.openhab.binding.zigbee.cc2531

2018-06-25 10:39:33.303 [DEBUG] [org.openhab.binding.zigbee.ember    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.usbserial.UsbSerialDiscoveryParticipant}={service.id=123, service.bundleid=258, service.scope=bundle, component.name=org.openhab.binding.zigbee.ember.internal.discovery.ZigBeeEmberUsbSerialDiscoveryParticipant, component.id=22} - org.openhab.binding.zigbee.ember

2018-06-25 10:39:33.307 [DEBUG] [org.openhab.binding.zigbee.ember    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=124, service.bundleid=258, service.scope=bundle, component.name=org.openhab.binding.zigbee.ember.internal.EmberHandlerFactory, component.id=23} - org.openhab.binding.zigbee.ember

2018-06-25 10:39:33.311 [DEBUG] [org.openhab.binding.zigbee.ember    ] - BundleEvent STARTING - org.openhab.binding.zigbee.ember

2018-06-25 10:39:33.314 [DEBUG] [org.openhab.binding.zigbee.ember    ] - BundleEvent STARTED - org.openhab.binding.zigbee.ember

2018-06-25 10:39:33.322 [DEBUG] [org.openhab.binding.zigbee.ember    ] - BundleEvent [unknown:512] - org.openhab.binding.zigbee.ember

2018-06-25 10:39:33.334 [DEBUG] [org.openhab.binding.zigbee.telegesis] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=125, service.bundleid=259, service.scope=bundle, component.name=org.openhab.binding.zigbee.telegesis.internal.TelegesisHandlerFactory, component.id=24} - org.openhab.binding.zigbee.telegesis

2018-06-25 10:39:33.338 [DEBUG] [org.openhab.binding.zigbee.telegesis] - BundleEvent STARTING - org.openhab.binding.zigbee.telegesis

2018-06-25 10:39:33.341 [DEBUG] [org.openhab.binding.zigbee.telegesis] - BundleEvent STARTED - org.openhab.binding.zigbee.telegesis

2018-06-25 10:39:33.348 [DEBUG] [org.openhab.binding.zigbee.telegesis] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.usbserial.UsbSerialDiscoveryParticipant}={service.id=126, service.bundleid=259, service.scope=bundle, component.name=org.openhab.binding.zigbee.telegesis.internal.discovery.ZigBeeTelegesisUsbSerialDiscoveryParticipant, component.id=25} - org.openhab.binding.zigbee.telegesis

2018-06-25 10:39:33.350 [DEBUG] [org.openhab.binding.zigbee.telegesis] - BundleEvent [unknown:512] - org.openhab.binding.zigbee.telegesis

2018-06-25 10:39:33.360 [DEBUG] [org.openhab.binding.zigbee.xbee     ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=127, service.bundleid=260, service.scope=bundle, component.name=org.openhab.binding.zigbee.xbee.internal.XBeeHandlerFactory, component.id=26} - org.openhab.binding.zigbee.xbee

2018-06-25 10:39:33.363 [DEBUG] [org.openhab.binding.zigbee.xbee     ] - BundleEvent STARTING - org.openhab.binding.zigbee.xbee

2018-06-25 10:39:33.366 [DEBUG] [org.openhab.binding.zigbee.xbee     ] - BundleEvent STARTED - org.openhab.binding.zigbee.xbee

2018-06-25 10:39:33.373 [DEBUG] [org.openhab.binding.zigbee.xbee     ] - BundleEvent [unknown:512] - org.openhab.binding.zigbee.xbee

2018-06-25 10:40:03.994 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Creating ZigBee discovery service for zigbee:coordinator_ember:9c44f932

2018-06-25 10:40:03.996 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Activating ZigBee discovery service for zigbee:coordinator_ember:9c44f932

2018-06-25 10:40:04.001 [DEBUG] [org.openhab.binding.zigbee.ember    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=285, service.bundleid=258, service.scope=singleton} - org.openhab.binding.zigbee.ember

2018-06-25 10:40:04.014 [DEBUG] [org.openhab.binding.zigbee.ember    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=286, service.bundleid=258, service.scope=singleton} - org.openhab.binding.zigbee.ember

2018-06-25 10:40:04.056 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - Initializing ZigBee Ember serial bridge handler.

2018-06-25 10:40:04.058 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_ember:9c44f932].

2018-06-25 10:40:04.061 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel -1

2018-06-25 10:40:04.063 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 21407

2018-06-25 10:40:04.065 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID 907585F9084B6CD9

2018-06-25 10:40:04.072 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

2018-06-25 10:40:04.074 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

2018-06-25 10:40:04.081 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised E92133C72371D13C5A13B3E4B2975294

2018-06-25 10:40:04.083 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array E92133C72371D13C5A13B3E4B2975294

2018-06-25 10:40:04.169 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - ZigBee Ember Coordinator opening Port:'/dev/ttyAMA0' PAN:539f, EPAN:907585F9084B6CD9, Channel:-1

2018-06-25 10:40:04.180 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start

2018-06-25 10:40:05.187 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting

2018-06-25 10:40:05.189 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator

2018-06-25 10:40:05.239 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise E92133C72371D13C5A13B3E4B2975294

2018-06-25 10:40:05.243 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EZSP dongle initialize with protocol ASH2.

2018-06-25 10:40:05.255 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [/dev/ttyAMA0] at 57600 baud, flow control FLOWCONTROL_OUT_XONOFF.

2018-06-25 10:40:05.360 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [/dev/ttyAMA0] is initialized.

2018-06-25 10:40:06.970 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameRst []

2018-06-25 10:40:06.971 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler thread started

2018-06-25 10:40:08.077 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: TX EZSP queue: 1

2018-06-25 10:40:10.369 [DEBUG] [com.zsmartsystems.zigbee            ] - BundleEvent STARTING - com.zsmartsystems.zigbee

2018-06-25 10:40:10.385 [DEBUG] [com.zsmartsystems.zigbee            ] - BundleEvent STARTED - com.zsmartsystems.zigbee

2018-06-25 10:40:10.398 [DEBUG] [m.zsmartsystems.zigbee.dongle.cc2531] - BundleEvent STARTING - com.zsmartsystems.zigbee.dongle.cc2531

2018-06-25 10:40:10.425 [DEBUG] [m.zsmartsystems.zigbee.dongle.cc2531] - BundleEvent STARTED - com.zsmartsystems.zigbee.dongle.cc2531

2018-06-25 10:40:10.437 [DEBUG] [om.zsmartsystems.zigbee.dongle.ember] - BundleEvent STARTING - com.zsmartsystems.zigbee.dongle.ember

2018-06-25 10:40:10.446 [DEBUG] [om.zsmartsystems.zigbee.dongle.ember] - BundleEvent STARTED - com.zsmartsystems.zigbee.dongle.ember

2018-06-25 10:40:10.474 [DEBUG] [smartsystems.zigbee.dongle.telegesis] - BundleEvent STARTING - com.zsmartsystems.zigbee.dongle.telegesis

2018-06-25 10:40:10.479 [DEBUG] [smartsystems.zigbee.dongle.telegesis] - BundleEvent STARTED - com.zsmartsystems.zigbee.dongle.telegesis

2018-06-25 10:40:10.553 [DEBUG] [com.zsmartsystems.zigbee.dongle.xbee] - BundleEvent STARTING - com.zsmartsystems.zigbee.dongle.xbee

2018-06-25 10:40:10.571 [DEBUG] [com.zsmartsystems.zigbee.dongle.xbee] - BundleEvent STARTED - com.zsmartsystems.zigbee.dongle.xbee

2018-06-25 10:48:33.612 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:coordinator_ember:9c44f932 changed to UNKNOWN.```

[jimmyt (Greg)]

watched the log while the pi was rebooting and saw this as one of the first entries -

2018-06-25 11:02:17.248 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:9c44f932' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)

does that indicate a problem with the dongle or something in the setup ?

[jswim788 (John Schmitz)]

Isn’t the Zigbee at /dev/ttyUSB1? On mine the Z-wave is /dev/ttyUSB0 and the Zigbee is /dev/ttyUSB1.

[jimmyt (Greg)]

thats the thing on mine… usb0 is zwave and zigbee (i am assuming) is AMA0 - I only have 2 choices… ama0 and usb0 in the dropdown

[5iver (Scott Rushworth)]

This should show you the devices… dmesg -T|grep tty. If your zwave is working on ttyUSB0, try ttyUSB1 for the zigbee. It would also be good to setup udev rules in case these change.

Linear HUSBZB-1

UDEV rules for this device can be a little tricky. Here is what worked for me (although I specified an order to them): KERNEL==“ttyUSB[0-9]", ATTRS{interface}==“HubZ Z-Wave Com Port”, SYMLINK+=“ttyUSB-5”, GROUP=“dialout”, MODE="0666" KERNEL=="ttyUSB[0-9]”, ATTRS{interface}==“HubZ ZigBee Com Port”, SYMLINK+=“ttyUSB-55”, GROUP=“dialout”, MODE=“0666” Note: On Linux; the extra Java command-line property is not required if you choose a symlink name that matches a standard Linux comm port prefix an…

[jimmyt (Greg)]

so, being a luinx rookie (whos good at following cookbook) here is what dmesg yields.

dmesg -T|grep tty
[Mon Jun 25 11:02:44 2018] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000  dwc_otg.lpm_enable=0 console ttyS0,115200 console=tty1 root=PARTUUID=d2deeea0-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[Mon Jun 25 11:02:44 2018] console [tty1] enabled
[Mon Jun 25 11:02:44 2018] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[Mon Jun 25 11:02:47 2018] usb 1-1.2: cp210x converter now attached to ttyUSB0
[Mon Jun 25 11:02:47 2018] usb 1-1.2: cp210x converter now attached to ttyUSB1

in my zigbee port optionsI see /dev/ttyAMA0 and /dev/ttyUSB1

usb1 is zwave so I am assuming AMA0 is zigbee simply because there are no other choices. I am reading about udev and hope to mess with it soon… any advice for a newbie ?

thanks!

[kmccmk9 (Kyle Corsi)]

Hey, were you able to get this working? I’m having the exact same problem.