I have been following this thread with the same issues as Jeremy.
I have tried using diffirent baud rates, also changing the baud rate to match on the windows machine. Tried taking off flow control. Still the log gets up to that “QUEUE” ine
2018-06-28 07:29:56.246 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - Initializing ZigBee Ember serial bridge handler.
2018-06-28 07:29:56.247 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_ember:a27a85ac].
2018-06-28 07:29:56.248 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel 25
2018-06-28 07:29:56.249 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 4969
2018-06-28 07:29:56.250 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID 32117E7629945762
2018-06-28 07:29:56.251 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2018-06-28 07:29:56.252 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising network
2018-06-28 07:29:56.254 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2018-06-28 07:29:56.255 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised FC7459D6210D9E1424A743935644B5E5
2018-06-28 07:29:56.257 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array FC7459D6210D9E1424A743935644B5E5
2018-06-28 07:29:56.258 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - ZigBee Ember Coordinator opening Port:‘COM12’ PAN:1369, EPAN:32117E7629945762, Channel:25
2018-06-28 07:29:56.258 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
2018-06-28 07:29:57.261 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
2018-06-28 07:29:57.263 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
2018-06-28 07:29:57.264 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise FC7459D6210D9E1424A743935644B5E5
2018-06-28 07:29:57.265 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EZSP dongle initialize with protocol ASH2.
2018-06-28 07:29:57.266 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [COM12] at 38400 baud, flow control FLOWCONTROL_OUT_NONE.
2018-06-28 07:29:57.280 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [COM12] is initialized.
2018-06-28 07:29:57.281 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameRst []
2018-06-28 07:29:57.281 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler thread started
2018-06-28 07:29:57.283 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: TX EZSP queue: 1
I am wondering if the port settings from DATA BITS, PARITY and STOP BITS must be adjusted. Currently set at DATA BITS = 8, PARITY = none, STOP BITS = 1
No - these should be fine. I have tested this with many different versions of the Silabs firmware so I really don’t think there is any issue with this.
I’ll let you all know how I fair with the Raspberry Pi later today.
Out of curiosity, where did you all purchase your HUSBZB-1 stick from? I wonder if there’s a bad batch/reseller somewhere.
I have been following this thread… as I am having a similar problem with the pi 
see my thread here: HUSBZB - getting zigbee to work / openhabian
Home Controls Inc - via Amazon
Habmin shows my firmware as 5.4.1.0. I also purchase from Home Controls through Amazon, but it’s been a year or so.
how do you get to see the firmware version? In habadmin if I look under configuration ->things -> I see Ember EM35X Coordinator then when I click through it I see nothing under properties or configuration that shows me any version numbers…
I really doubt that the firmware version is an issue - unless there is a custom version of the firmware (VERY unlikely) in use, I’ve tested the binding with versions from 5.2 to 6.3 (the current version released only a week or two back!).
This is likely because there aren’t any.
As I said above, you can’t upgrade the firmware before you have a working communications link. You also can’t find out what version of the firmware you have, or any other attributes, until you have a working communications link as the binding is unable to get this information until it can communicate with the device.
what bundle is “s.zigbee.dongle.ember.internal.ash.AshFrameHandler”? Maybe we didnt install that?
That is in com.zsmartsystems.zigbee.dongle.ember. This is installed along with the Zigbee binding when installed through PaperUI. You’ll see it if you run list |grep -i zig in Karaf.
Well, I feel totally defeated. Raspberry Pi arrived today, so I went through everything and got it set up and running OpenHABian, and plugged the HUSBZB-1 stick in. Got Zwave up and running no problem. Went and tried to add Zigbee, and am still getting the same error I was on Windows with the status staying as Unknown. The only thing I can think of now is that this stick is bad and I need to return it. Any other ideas or thoughts?
Right there with you… same thing on my end. If you read the topic I started 5iver gave a suggestion on udev rules… I may try that this weekend… need to figure out exactly how to create the rule… but will get to it soon
I just put this into /etc/udev/rules.d/99-server.rules (the location for your syste may be different)…
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”
Did you add the openhab account to the dialout and tty groups? Are your logs any different?
A couple days ago, I deleted the zigbee jars in my addons folder and installed through PaperUI, in order to get the latest. I’ve been having trouble losing control of my devices. The latest version in Cloudbees is actually a couple versions behind, so I downloaded the latest and my issues are gone. If your still having no luck, you could try them out, or maybe @chris could update what is on Cloudbees (1.0.11 vs 1.0.13).