Unable to add z-wave devices

Configuration Z-Wave
1

I recently purchased Linear HUSBZB-1. But I can’t get it too connect correctly. I’m running the latest home assistant in a freenas jail. These are the logs in the z wave logs:

2017-08-11 16:42:06.528 Always, OpenZwave Version 1.4.2508 Starting Up
2017-08-11 16:42:09.994 Info, Setting Up Provided Network Key for Secure Communications
2017-08-11 16:42:09.994 Warning, Failed - Network Key Not Set
2017-08-11 16:42:09.994 Info, mgr, Added driver for controller /dev/cuau0
2017-08-11 16:42:09.994 Info, Opening controller /dev/cuau0
2017-08-11 16:42:09.994 Info, Trying to open serial port /dev/cuau0 (attempt 1)
2017-08-11 16:42:09.994 Info, Serial port /dev/cuau0 opened (attempt 1)
2017-08-11 16:42:09.994 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2017-08-11 16:42:09.994 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2017-08-11 16:42:09.994 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2017-08-11 16:42:09.994 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2017-08-11 16:42:09.994 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2017-08-11 16:42:09.994 Detail,
2017-08-11 16:42:09.994 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2017-08-11 16:42:11.000 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-08-11 16:42:11.000 Detail, contrlr, Removing current message
2017-08-11 16:42:11.000 Detail, contrlr, Notification: Notification - TimeOut
2017-08-11 16:42:11.000 Detail,
2017-08-11 16:42:11.000 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2017-08-11 16:42:12.000 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-08-11 16:42:12.000 Detail, contrlr, Removing current message
2017-08-11 16:42:12.000 Detail, contrlr, Notification: Notification - TimeOut
2017-08-11 16:42:12.000 Detail,
2017-08-11 16:42:12.000 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2017-08-11 16:42:13.001 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-08-11 16:42:13.001 Detail, contrlr, Removing current message
2017-08-11 16:42:13.001 Detail, contrlr, Notification: Notification - TimeOut
2017-08-11 16:42:13.001 Detail,
2017-08-11 16:42:13.001 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2017-08-11 16:42:14.002 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-08-11 16:42:14.002 Detail, contrlr, Removing current message
2017-08-11 16:42:14.002 Detail, contrlr, Notification: Notification - TimeOut
2017-08-11 16:42:14.002 Detail,
2017-08-11 16:42:14.002 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2017-08-11 16:42:15.004 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-08-11 16:42:15.004 Detail, contrlr, Removing current message
2017-08-11 16:42:15.004 Detail, contrlr, Notification: Notification - TimeOut

Does anyone have any idea what the issue is?

2

In a nutshell it says your controller isn’t responding to commands.
What type of controller is it?

3

It’s a Linear HUSBZB-1.

4

Try /dev/cuau1 instead, pretty sure /dev/cuau0 is the Zigbee radio.

1 Like
5

Oddly, there is cuau0 and cuau2. Both of those produce the same results.

6

what does this command show you: ls -al /dev/tty*

7

I found on a freebsd board that ucom drivers need to be

Here is what I get with that command:

ls -al /dev/tty*
crw------- 1 root wheel 0x34 Aug 13 07:34 /dev/ttyu0
crw------- 1 root wheel 0x35 Aug 13 07:34 /dev/ttyu0.init
crw------- 1 root wheel 0x36 Aug 13 07:34 /dev/ttyu0.lock
crw------- 1 root wheel 0x2d Aug 13 07:40 /dev/ttyu2
crw------- 1 root wheel 0x2e Aug 13 07:34 /dev/ttyu2.init
crw------- 1 root wheel 0x2f Aug 13 07:34 /dev/ttyu2.lock
crw------- 1 root wheel 0x3a Aug 13 07:40 /dev/ttyv0
crw------- 1 root wheel 0x3b Aug 13 07:40 /dev/ttyv1
crw------- 1 root wheel 0x3c Aug 13 07:40 /dev/ttyv2
crw------- 1 root wheel 0x3d Aug 13 07:40 /dev/ttyv3
crw------- 1 root wheel 0x3e Aug 13 07:40 /dev/ttyv4
crw------- 1 root wheel 0x3f Aug 13 07:40 /dev/ttyv5
crw------- 1 root wheel 0x40 Aug 13 07:40 /dev/ttyv6
crw------- 1 root wheel 0x41 Aug 13 07:40 /dev/ttyv7
crw------- 1 root wheel 0x42 Aug 13 07:34 /dev/ttyv8
crw------- 1 root wheel 0x43 Aug 13 07:34 /dev/ttyv9
crw------- 1 root wheel 0x44 Aug 13 07:34 /dev/ttyva
crw------- 1 root wheel 0x45 Aug 13 07:34 /dev/ttyvb
crw------- 1 root wheel 0x46 Aug 13 07:34 /dev/ttyvc
crw------- 1 root wheel 0x47 Aug 13 07:34 /dev/ttyvd
crw------- 1 root wheel 0x48 Aug 13 07:34 /dev/ttyve
crw------- 1 root wheel 0x49 Aug 13 07:34 /dev/ttyvf

8

Well it looks like the real devices are /dev/ttyu0 and /dev/ttyu2 I’m not sure why they both give you the same results unless the jail isn’t mapping the USB device correctly for you.

9

Thanks for your help. I couldn’t get it to work. From what I was reading the USB should be cuaU0 when loaded. For some reason the system was seeing the device, but not loading it. I decided with how cheap an rpi is, it wasn’t worth any more time.

1 Like