Z-wave/zigbee USB stick not recognized by HA Core

Hardware
1

I’m very new to HA. I’m running core on docker in UNRAID. I got my nortek USB stick. Both the z-wave and zigbee integrations seem to not be able to recognize the PATH to the stick. I’ve been scrounging around for answers and info for about 4hrs over a couple days now. Can’t get this stick to work

1253×205 40.9 KB

1020×138 18.8 KB

Jun 1 16:43:01 Tower kernel: cp210x 1-1:1.1: device disconnected
Jun 1 16:43:11 Tower kernel: usb 1-4: new full-speed USB device number 10 using xhci_hcd
Jun 1 16:43:11 Tower kernel: cp210x 1-4:1.0: cp210x converter detected
Jun 1 16:43:11 Tower kernel: usb 1-4: cp210x converter now attached to ttyUSB0
Jun 1 16:43:11 Tower kernel: cp210x 1-4:1.1: cp210x converter detected
Jun 1 16:43:11 Tower kernel: usb 1-4: cp210x converter now attached to ttyUSB1
Jun 1 17:16:32 Tower login[26211]: ROOT LOGIN on '/dev/pts/3'
2

Did you pass the device to the container when you ran the docker command to create the container?

3

I did not do that, but I made some progress. I toggled the “priveleged” setting on docker to on based ona
youtube comment and it ended up recognizing the path and I was able to add the integration. Now I’m stuck at “Starting Z-Wave Network”. Here’s the log:

2020-06-02 02:40:28.475 Always, OpenZwave Version 1.4.3469 Starting Up
2020-06-02 02:40:38.599 Info, Setting Up Provided Network Key for Secure Communications
2020-06-02 02:40:38.599 Info, mgr,     Added driver for controller /dev/ttyUSB1
2020-06-02 02:40:38.600 Info,   Opening controller /dev/ttyUSB1
2020-06-02 02:40:38.600 Info, Trying to open serial port /dev/ttyUSB1 (attempt 1)
2020-06-02 02:40:38.601 Info, Serial port /dev/ttyUSB1 opened (attempt 1)
2020-06-02 02:40:38.601 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-02 02:40:38.601 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-06-02 02:40:38.601 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-06-02 02:40:38.601 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-06-02 02:40:38.601 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-06-02 02:40:38.601 Detail,
2020-06-02 02:40:38.601 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-06-02 02:40:39.601 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-02 02:40:39.601 Detail, contrlr, Removing current message
2020-06-02 02:40:39.601 Detail, contrlr, Notification: Notification - TimeOut
2020-06-02 02:40:39.602 Detail,
2020-06-02 02:40:39.602 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-06-02 02:40:40.602 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-02 02:40:40.602 Detail, contrlr, Removing current message
2020-06-02 02:40:40.602 Detail, contrlr, Notification: Notification - TimeOut
2020-06-02 02:40:40.603 Detail,
2020-06-02 02:40:40.603 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-06-02 02:40:41.603 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-02 02:40:41.603 Detail, contrlr, Removing current message
2020-06-02 02:40:41.603 Detail, contrlr, Notification: Notification - TimeOut
2020-06-02 02:40:41.604 Detail,
2020-06-02 02:40:41.604 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-06-02 02:40:42.604 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-02 02:40:42.604 Detail, contrlr, Removing current message
2020-06-02 02:40:42.604 Detail, contrlr, Notification: Notification - TimeOut
2020-06-02 02:40:42.605 Detail,
2020-06-02 02:40:42.605 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-06-02 02:40:43.605 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-02 02:40:43.605 Detail, contrlr, Removing current message
2020-06-02 02:40:43.605 Detail, contrlr, Notification: Notification - TimeOut
4

We’re you using ooenzwave before?

HA need the xccx.xml file that’s stores zwave config.
If missing, zwave stick will function but all nodes/devices won’t load

EDIT

I should point out that .xml file’s name is unique for each install.

5

I don’t really know what ooenzwave is. I’m doing all of this on a new CORE install.

Is there some kind of documentation post that can give me any insight into this? I’m so lost.

6

Holy moly. Hopefully the following helps someone puzzle it together in the future. I finally got it. It turns out that the path to /dev/ttyUSB1 was for ZIGBEE and the /dev/ttyUSB0 was Z-wave. I’d run some searches in command that led me to believe that tittyUSB1 was the right path. I think that and enabling the privilege toggle in my container settings were the biggest hurdles.