HUSBZB Zigbee setup

jered6323 · June 27, 2018, 7:06pm

I don’t know if it’s the correct one or not, it’s from the guide I followed that I posted in my second post. I’m starting to think it might be a driver problem. Here’s what it looks like in Device Manager.
Capture
COM3 is the one that was HubZ Z-Wave Com Port, and COM4 is the one that was HubZ ZigBee Com Port. After manually installing the driver on each (the guide I followed had me select the same driver for each, and that is suspect in my mind) they showed up as the above.

Here is the log from the point I enabled trace logging onward. Set channel to 25 and reset controller, shutdown the pc, unplugged/plugged the stick, then started everything up.

2018-06-27 14:45:39.897 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration received (Coordinator).
2018-06-27 14:45:39.898 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_initialise >> true.
2018-06-27 14:45:39.898 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_channel >> 25.
2018-06-27 14:45:39.899 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_panid >> 40903.
2018-06-27 14:45:39.899 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_extendedpanid >> D767A8513BC83A06.
2018-06-27 14:45:39.899 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_networkkey >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00.
2018-06-27 14:45:39.905 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Creating ZigBee persistence folder C:\openHAB2\userdata/zigbee
2018-06-27 14:45:39.915 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: Start.
2018-06-27 14:45:39.918 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: Done.
2018-06-27 14:45:39.919 [DEBUG] [bee.internal.ZigBeeNetworkDiscoverer] - Network discovery task shutdown
2018-06-27 14:45:39.935 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler exited.
2018-06-27 14:45:39.934 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port 'COM4' closed.
2018-06-27 14:45:39.937 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler close.
2018-06-27 14:45:39.937 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler close complete.
2018-06-27 14:45:39.937 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network [zigbee:coordinator_ember:d0f84d4e] closed.
2018-06-27 14:45:39.938 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - Initializing ZigBee Ember serial bridge handler.
2018-06-27 14:45:39.938 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_ember:d0f84d4e].
2018-06-27 14:45:39.938 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel 25
2018-06-27 14:45:39.938 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 40903
2018-06-27 14:45:39.938 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID D767A8513BC83A06
2018-06-27 14:45:39.939 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2018-06-27 14:45:39.939 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising network
2018-06-27 14:45:39.944 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2018-06-27 14:45:39.945 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised 79945A97B1E61E37B28E2C3B52A9D1BB
2018-06-27 14:45:39.945 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array 79945A97B1E61E37B28E2C3B52A9D1BB
2018-06-27 14:45:39.946 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - ZigBee Ember Coordinator opening Port:'COM4' PAN:9fc7, EPAN:D767A8513BC83A06, Channel:25
2018-06-27 14:45:39.946 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
2018-06-27 14:45:40.947 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
2018-06-27 14:45:40.948 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
2018-06-27 14:45:40.948 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise 79945A97B1E61E37B28E2C3B52A9D1BB
2018-06-27 14:45:40.948 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EZSP dongle initialize with protocol ASH2.
2018-06-27 14:45:40.949 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [COM4] at 57600 baud, flow control FLOWCONTROL_OUT_XONOFF.
2018-06-27 14:45:40.963 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [COM4] is initialized.
2018-06-27 14:45:40.964 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameRst []
2018-06-27 14:45:40.965 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler thread started
2018-06-27 14:45:40.967 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: TX EZSP queue: 1
2018-06-27 14:47:18.543 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration received (Coordinator).
2018-06-27 14:47:18.544 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_initialise >> true.
2018-06-27 14:47:18.545 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_channel >> -1.
2018-06-27 14:47:18.545 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_panid >> 40903.
2018-06-27 14:47:18.545 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_extendedpanid >> D767A8513BC83A06.
2018-06-27 14:47:18.546 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_networkkey >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00.
2018-06-27 14:47:18.551 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: Start.
2018-06-27 14:47:18.553 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: Done.
2018-06-27 14:47:18.554 [DEBUG] [bee.internal.ZigBeeNetworkDiscoverer] - Network discovery task shutdown
2018-06-27 14:47:18.558 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler exited.
2018-06-27 14:47:18.558 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port 'COM4' closed.
2018-06-27 14:47:18.558 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler close.
2018-06-27 14:47:18.559 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler close complete.
2018-06-27 14:47:18.559 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network [zigbee:coordinator_ember:d0f84d4e] closed.
2018-06-27 14:47:18.559 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - Initializing ZigBee Ember serial bridge handler.
2018-06-27 14:47:18.560 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_ember:d0f84d4e].
2018-06-27 14:47:18.560 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel -1
2018-06-27 14:47:18.560 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 40903
2018-06-27 14:47:18.560 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID D767A8513BC83A06
2018-06-27 14:47:18.561 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2018-06-27 14:47:18.561 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising network
2018-06-27 14:47:18.564 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2018-06-27 14:47:18.567 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised F63C49E2D0D182C96CEA64C279B52220
2018-06-27 14:47:18.568 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array F63C49E2D0D182C96CEA64C279B52220
2018-06-27 14:47:18.569 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - ZigBee Ember Coordinator opening Port:'COM4' PAN:9fc7, EPAN:D767A8513BC83A06, Channel:-1
2018-06-27 14:47:18.569 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
2018-06-27 14:47:19.571 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
2018-06-27 14:47:19.572 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
2018-06-27 14:47:19.572 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise F63C49E2D0D182C96CEA64C279B52220
2018-06-27 14:47:19.572 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EZSP dongle initialize with protocol ASH2.
2018-06-27 14:47:19.573 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [COM4] at 57600 baud, flow control FLOWCONTROL_OUT_XONOFF.
2018-06-27 14:47:19.590 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [COM4] is initialized.
2018-06-27 14:47:19.590 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameRst []
2018-06-27 14:47:19.591 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler thread started
2018-06-27 14:47:19.592 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: TX EZSP queue: 1
2018-06-27 14:48:30.426 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Configuration received (Coordinator).
2018-06-27 14:48:30.427 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_initialise >> true.
2018-06-27 14:48:30.428 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_channel >> 25.
2018-06-27 14:48:30.428 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_panid >> 40903.
2018-06-27 14:48:30.429 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_extendedpanid >> D767A8513BC83A06.
2018-06-27 14:48:30.430 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: Unhandled configuration parameter zigbee_networkkey >> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00.
2018-06-27 14:48:30.433 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: Start.
2018-06-27 14:48:30.435 [DEBUG] [nal.ZigBeeNetworkStateSerializerImpl] - Saving ZigBee network state: Done.
2018-06-27 14:48:30.436 [DEBUG] [bee.internal.ZigBeeNetworkDiscoverer] - Network discovery task shutdown
2018-06-27 14:48:30.442 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port 'COM4' closed.
2018-06-27 14:48:30.442 [TRACE] [e.ember.internal.ash.AshFrameHandler] - ASH RX: FFFFFFFF
2018-06-27 14:48:30.442 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler exited.
2018-06-27 14:48:30.442 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler close.
2018-06-27 14:48:30.443 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler close complete.
2018-06-27 14:48:30.443 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network [zigbee:coordinator_ember:d0f84d4e] closed.
2018-06-27 14:48:30.444 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - Initializing ZigBee Ember serial bridge handler.
2018-06-27 14:48:30.444 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_ember:d0f84d4e].
2018-06-27 14:48:30.445 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel 25
2018-06-27 14:48:30.445 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 40903
2018-06-27 14:48:30.445 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID D767A8513BC83A06
2018-06-27 14:48:30.446 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2018-06-27 14:48:30.446 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising network
2018-06-27 14:48:30.449 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2018-06-27 14:48:30.449 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised D37877E4952531705A50E092F1947FEC
2018-06-27 14:48:30.449 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array D37877E4952531705A50E092F1947FEC
2018-06-27 14:48:30.450 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - ZigBee Ember Coordinator opening Port:'COM4' PAN:9fc7, EPAN:D767A8513BC83A06, Channel:25
2018-06-27 14:48:30.451 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
2018-06-27 14:48:31.452 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
2018-06-27 14:48:31.452 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
2018-06-27 14:48:31.453 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise D37877E4952531705A50E092F1947FEC
2018-06-27 14:48:31.453 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EZSP dongle initialize with protocol ASH2.
2018-06-27 14:48:31.454 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [COM4] at 57600 baud, flow control FLOWCONTROL_OUT_XONOFF.
2018-06-27 14:48:31.469 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [COM4] is initialized.
2018-06-27 14:48:31.470 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameRst []
2018-06-27 14:48:31.470 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler thread started
2018-06-27 14:48:31.471 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: TX EZSP queue: 1
2018-06-27 14:48:43.859 [INFO ] [basic.internal.servlet.WebAppServlet] - Stopped Basic UI
2018-06-27 14:58:45.044 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=114, service.bundleid=200, service.scope=bundle, component.name=org.openhab.binding.zigbee.cc2531.internal.CC2531HandlerFactory, component.id=9} - org.openhab.binding.zigbee.cc2531
2018-06-27 14:58:45.060 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - BundleEvent STARTING - org.openhab.binding.zigbee.cc2531
2018-06-27 14:58:45.061 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - BundleEvent STARTED - org.openhab.binding.zigbee.cc2531
2018-06-27 14:58:45.080 [DEBUG] [org.openhab.binding.zigbee          ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=115, service.bundleid=199, service.scope=bundle, component.name=org.openhab.binding.zigbee.internal.ZigBeeHandlerFactory, component.id=10} - org.openhab.binding.zigbee
2018-06-27 14:58:45.082 [DEBUG] [org.openhab.binding.zigbee          ] - BundleEvent STARTING - org.openhab.binding.zigbee
2018-06-27 14:58:45.084 [DEBUG] [org.openhab.binding.zigbee          ] - BundleEvent STARTED - org.openhab.binding.zigbee
2018-06-27 14:58:45.098 [DEBUG] [org.openhab.binding.zigbee          ] - BundleEvent [unknown:512] - org.openhab.binding.zigbee
2018-06-27 14:58:45.100 [DEBUG] [org.openhab.binding.zigbee.cc2531   ] - BundleEvent [unknown:512] - org.openhab.binding.zigbee.cc2531
2018-06-27 14:58:45.105 [DEBUG] [org.openhab.binding.zigbee.telegesis] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.usbserial.UsbSerialDiscoveryParticipant}={service.id=116, service.bundleid=202, service.scope=bundle, component.name=org.openhab.binding.zigbee.telegesis.internal.discovery.ZigBeeTelegesisUsbSerialDiscoveryParticipant, component.id=11} - org.openhab.binding.zigbee.telegesis
2018-06-27 14:58:45.108 [DEBUG] [org.openhab.binding.zigbee.telegesis] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=117, service.bundleid=202, service.scope=bundle, component.name=org.openhab.binding.zigbee.telegesis.internal.TelegesisHandlerFactory, component.id=12} - org.openhab.binding.zigbee.telegesis
2018-06-27 14:58:45.110 [DEBUG] [org.openhab.binding.zigbee.telegesis] - BundleEvent STARTING - org.openhab.binding.zigbee.telegesis
2018-06-27 14:58:45.111 [DEBUG] [org.openhab.binding.zigbee.telegesis] - BundleEvent STARTED - org.openhab.binding.zigbee.telegesis
2018-06-27 14:58:45.114 [DEBUG] [org.openhab.binding.zigbee.telegesis] - BundleEvent [unknown:512] - org.openhab.binding.zigbee.telegesis
2018-06-27 14:58:45.118 [DEBUG] [org.openhab.binding.zigbee.xbee     ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=118, service.bundleid=203, service.scope=bundle, component.name=org.openhab.binding.zigbee.xbee.internal.XBeeHandlerFactory, component.id=13} - org.openhab.binding.zigbee.xbee
2018-06-27 14:58:45.156 [DEBUG] [org.openhab.binding.zigbee.xbee     ] - BundleEvent STARTING - org.openhab.binding.zigbee.xbee
2018-06-27 14:58:45.157 [DEBUG] [org.openhab.binding.zigbee.xbee     ] - BundleEvent STARTED - org.openhab.binding.zigbee.xbee
2018-06-27 14:58:45.160 [DEBUG] [org.openhab.binding.zigbee.xbee     ] - BundleEvent [unknown:512] - org.openhab.binding.zigbee.xbee
2018-06-27 14:58:45.557 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2018-06-27 14:58:45.624 [INFO ] [er.internal.HomeBuilderDashboardTile] - Started Home Builder at /homebuilder
2018-06-27 14:58:48.225 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at http://192.168.1.112:8080
2018-06-27 14:58:48.226 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at https://192.168.1.112:8443
2018-06-27 14:58:52.981 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2018-06-27 14:58:53.469 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model '(1)_lighton.rules' has errors, therefore ignoring it: [13,1]: no viable alternative at input 'then'
[14,14]: no viable alternative at input 'Item'
[14,22]: extraneous input ')' expecting 'end'

2018-06-27 14:58:54.337 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
2018-06-27 14:58:54.379 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2018-06-27 14:58:54.402 [INFO ] [sysfs.internal.SysfsUsbSerialScanner] - Cannot perform scans with this configuration: sysfsTtyDevicesDirectory: /sys/class/tty, devDirectory: /dev
2018-06-27 14:58:54.408 [INFO ] [sfs.internal.PollingUsbSerialScanner] - Do not start background scanning, as the configured USB-Serial scanner cannot perform scans on this system
2018-06-27 14:58:54.409 [INFO ] [sfs.internal.PollingUsbSerialScanner] - Do not start background scanning, as the configured USB-Serial scanner cannot perform scans on this system
2018-06-27 14:58:54.621 [DEBUG] [com.zsmartsystems.zigbee            ] - BundleEvent STARTING - com.zsmartsystems.zigbee
2018-06-27 14:58:54.624 [DEBUG] [com.zsmartsystems.zigbee            ] - BundleEvent STARTED - com.zsmartsystems.zigbee
2018-06-27 14:58:54.627 [DEBUG] [m.zsmartsystems.zigbee.dongle.cc2531] - BundleEvent STARTING - com.zsmartsystems.zigbee.dongle.cc2531
2018-06-27 14:58:54.628 [DEBUG] [m.zsmartsystems.zigbee.dongle.cc2531] - BundleEvent STARTED - com.zsmartsystems.zigbee.dongle.cc2531
2018-06-27 14:58:54.630 [DEBUG] [om.zsmartsystems.zigbee.dongle.ember] - BundleEvent STARTING - com.zsmartsystems.zigbee.dongle.ember
2018-06-27 14:58:54.633 [DEBUG] [om.zsmartsystems.zigbee.dongle.ember] - BundleEvent STARTED - com.zsmartsystems.zigbee.dongle.ember
2018-06-27 14:58:54.634 [DEBUG] [smartsystems.zigbee.dongle.telegesis] - BundleEvent STARTING - com.zsmartsystems.zigbee.dongle.telegesis
2018-06-27 14:58:54.636 [DEBUG] [smartsystems.zigbee.dongle.telegesis] - BundleEvent STARTED - com.zsmartsystems.zigbee.dongle.telegesis
2018-06-27 14:58:54.637 [DEBUG] [com.zsmartsystems.zigbee.dongle.xbee] - BundleEvent STARTING - com.zsmartsystems.zigbee.dongle.xbee
2018-06-27 14:58:54.638 [DEBUG] [com.zsmartsystems.zigbee.dongle.xbee] - BundleEvent STARTED - com.zsmartsystems.zigbee.dongle.xbee
2018-06-27 14:58:54.641 [DEBUG] [org.openhab.binding.zigbee.ember    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.usbserial.UsbSerialDiscoveryParticipant}={service.id=324, service.bundleid=201, service.scope=bundle, component.name=org.openhab.binding.zigbee.ember.internal.discovery.ZigBeeEmberUsbSerialDiscoveryParticipant, component.id=202} - org.openhab.binding.zigbee.ember
2018-06-27 14:58:54.652 [DEBUG] [org.openhab.binding.zigbee.ember    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=325, service.bundleid=201, service.scope=bundle, component.name=org.openhab.binding.zigbee.ember.internal.EmberHandlerFactory, component.id=203} - org.openhab.binding.zigbee.ember
2018-06-27 14:58:54.661 [DEBUG] [org.openhab.binding.zigbee.ember    ] - BundleEvent STARTING - org.openhab.binding.zigbee.ember
2018-06-27 14:58:54.662 [DEBUG] [org.openhab.binding.zigbee.ember    ] - BundleEvent STARTED - org.openhab.binding.zigbee.ember
2018-06-27 14:58:54.737 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
2018-06-27 14:58:54.740 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Creating ZigBee discovery service for zigbee:coordinator_ember:d0f84d4e
2018-06-27 14:58:54.741 [DEBUG] [bee.discovery.ZigBeeDiscoveryService] - Activating ZigBee discovery service for zigbee:coordinator_ember:d0f84d4e
2018-06-27 14:58:54.742 [DEBUG] [org.openhab.binding.zigbee.ember    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=333, service.bundleid=201, service.scope=singleton} - org.openhab.binding.zigbee.ember
2018-06-27 14:58:54.823 [DEBUG] [org.openhab.binding.zigbee.ember    ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.core.thing.binding.firmware.FirmwareUpdateHandler}={service.id=334, service.bundleid=201, service.scope=singleton} - org.openhab.binding.zigbee.ember
2018-06-27 14:58:58.060 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - Initializing ZigBee Ember serial bridge handler.
2018-06-27 14:58:58.063 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initializing ZigBee network [zigbee:coordinator_ember:d0f84d4e].
2018-06-27 14:58:58.064 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Channel 25
2018-06-27 14:58:58.066 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - PANID 40903
2018-06-27 14:58:58.066 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - EPANID D767A8513BC83A06
2018-06-27 14:58:58.073 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port 'COM3'
2018-06-27 14:58:58.074 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2018-06-27 14:58:58.075 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key String 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2018-06-27 14:58:58.078 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialised 6C31BE1E5F6D772FF55E04443C06A078
2018-06-27 14:58:58.079 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key final array 6C31BE1E5F6D772FF55E04443C06A078
2018-06-27 14:58:58.093 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
2018-06-27 14:58:58.099 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - Update networkKey
2018-06-27 14:58:58.111 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2018-06-27 14:58:58.111 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2018-06-27 14:58:58.120 [DEBUG] [ng.zigbee.ember.handler.EmberHandler] - ZigBee Ember Coordinator opening Port:'COM4' PAN:9fc7, EPAN:D767A8513BC83A06, Channel:25
2018-06-27 14:58:58.124 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Scheduling ZigBee start
2018-06-27 14:58:59.125 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee network starting
2018-06-27 14:58:59.126 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Initialising ZigBee coordinator
2018-06-27 14:58:59.149 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - Key initialise 6C31BE1E5F6D772FF55E04443C06A078
2018-06-27 14:58:59.151 [DEBUG] [zigbee.dongle.ember.ZigBeeDongleEzsp] - EZSP dongle initialize with protocol ASH2.
2018-06-27 14:58:59.155 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Connecting to serial port [COM4] at 57600 baud, flow control FLOWCONTROL_OUT_XONOFF.
2018-06-27 14:58:59.170 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port [COM4] is initialized.
2018-06-27 14:58:59.186 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - AshFrameHandler thread started
2018-06-27 14:58:59.187 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - --> TX ASH frame: AshFrameRst []
2018-06-27 14:58:59.205 [DEBUG] [e.ember.internal.ash.AshFrameHandler] - ASH: TX EZSP queue: 1
2018-06-27 14:59:01.211 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 1: Node found
2018-06-27 14:59:01.212 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 2: Node found
2018-06-27 14:59:01.212 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller using Controller API
2018-06-27 14:59:01.212 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller is Primary Controller
2018-06-27 14:59:01.213 [INFO ] [age.SerialApiGetInitDataMessageClass] - ------------Number of Nodes Found Registered to ZWave Controller------------
2018-06-27 14:59:01.213 [INFO ] [age.SerialApiGetInitDataMessageClass] - # Nodes = 2
2018-06-27 14:59:01.213 [INFO ] [age.SerialApiGetInitDataMessageClass] - ----------------------------------------------------------------------------

5iver · June 27, 2018, 7:53pm

This looks like the correct one. And you’ve confirmed that it is installed for both ports (this stick is basically a USB to serial dongle, with two serial devices attached to it). You can get the driver from Siicon Labs here… CP210x USB to UART Bridge VCP Drivers - Silicon Labs.

Your logging doesn’t appear to show anything new, so trace logging didn’t help. I’m scraping the bottom of the barrel as far as helping out! I can think of two more things to try… 1) delete the current coordinator Thing and start from scratch, 2) set up Docker and see if you can get it to work in Linux.

I haven’t tried using my stick in Windows yet. MS forced the Fall Creators Update to my laptop and it is completely unrecoverable. I’ve been using Fedora since then and wish I had moved sooner. I need to get Windows reinstalled, so once I do that I’ll test it out.

5iver · June 27, 2018, 11:13pm

My wife has Win10 on her laptop. With her local admin account, I downloaded the manual install of OH snapshot, downloaded and installed the drivers from SiLabs that I had linked to, plugged in the quickstick, configured it to use those drivers, configured baud, flow control and power management for the Zigbee port, started OH, installed Zigbee, created the Ember coordinator with the settings used on our server, and the coordinator stayed offline. Restarted OH and it came online. Her account also has UAC turned off, in case that matters. I launched OH from start.bat (maybe you’re running as a service?).

The only thing that stands out is that you are using COM4 for Zigbee, but mine came up as COM3. Your Zwave seems to come up properly on COM3, so maybe mine just came up on different ports than yours. Is your Zwave working?

jered6323 · June 28, 2018, 3:26am

Yea, I’m scratching my head too. I already tried deleting the Ember Thing and starting over with it, with no luck.
I’m currently updating an old Ubuntu virtual machine to give it a shot there and see where I get. I also have a Raspberry Pi coming tomorrow that I’ll give it a try on. I was hoping to keep everything on one machine, since it’s running my security/surveillance stuff already, but oh well.

I tried on another Windows 10 machine earlier this evening, with the same results I’ve been getting (status stays at Unknown). The drivers you linked to are the ones I’m using. I also have been using start.bat, I haven’t set it up as a service yet. So it looks like everything you did, I did the same. The only thing that is different is that I still have UAC on. I’ll try turning that off and see if it gets me anywhere.

Yep, Zwave seems to be working correctly. I’ve only added one dimmer light from my old setup so far, but I’m able to control it. I tried switching the COM ports for Zwave and Zigbee in their Thing configuration just to humor myself, and switching Zwave to COM4 reports it as Offline, and switching Zigbee to COM3 reports it to Offline instead of Unknown, so I’m assuming yours just came up on different ports.

jered6323 · June 28, 2018, 4:26am

Well the Ubuntu install doesn’t want to go the straightforward route, so I’m not messing with that tonight.

I deleted everything and unplugged the stick, rebooted, turned UAC off, rebooted, and then set everything up again from scratch. Even reconfigured the COM ports so that Zwave was COM4 and Zigbee was COM3, just in case Zigbee needed to come first. Still shows as Unknown. However, I was looking through the events log and saw this:

2018-06-28 00:19:05.183 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:7c197793' changed from UNINITIALIZED to INITIALIZING
2018-06-28 00:19:05.211 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_ember:7c197793' changed from INITIALIZING to UNKNOWN
2018-06-28 00:19:50.507 [nt.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:coordinator_ember:7c197793 changed to UNKNOWN.

Is the firmware of the stick possibly an issue? Is there anyway to update it?

chris · June 28, 2018, 8:45am

I would have assumed that all HUSB devices have the same firmware. In any case, the binding will be compatible with basically any firmware that is possible. If another firmware is programmed, you could try using 115k2 baud rate to see if that works.

Yes, but only if you can communicate with it in the first place. You also need to have access to the firmware which I’m probably not meant to distribute.

Kirt_Hills · June 28, 2018, 11:10am

I have been following this thread with the same issues as Jeremy.

Kirt_Hills · June 28, 2018, 11:32am

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

Kirt_Hills · June 28, 2018, 11:38am

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

chris · June 28, 2018, 12:02pm

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.

jered6323 · June 28, 2018, 3:38pm

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.

jimmyt · June 28, 2018, 3:46pm

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

Kirt_Hills · June 28, 2018, 4:01pm

I purchased it from Amazon, which was sold by Express Goods as a reseller.

Get Outlook for iOS

jimmyt · June 28, 2018, 5:36pm

Home Controls Inc - via Amazon

5iver · June 28, 2018, 5:45pm

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.

jimmyt · June 28, 2018, 6:08pm

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…

5iver · June 28, 2018, 6:40pm

Configuration> Things> coordinator> Attributes

chris · June 28, 2018, 7:10pm

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!).

jimmyt · June 28, 2018, 7:16pm

interesting… I don’t see the attributes section… maybe thats my problem

chris · June 28, 2018, 7:19pm

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.