Zwave network won't start

Tags: #<Tag:0x00007f7c619f7d08>

I had an issues where my door lock wasn’t working, so I stopped my Zwave network. Now I can’t get it started again. Here is my OZW log.

I’m running Virtualbox on a Windows 10 host, and my guest is Unbuntu 18.04. I’ve exposed my USB Z-wave dongle.

2019-12-02 16:53:25.157 Always, OpenZwave Version 1.4.3440 Starting Up
2019-12-02 16:54:08.993 Info, Setting Up Provided Network Key for Secure Communications
2019-12-02 16:54:08.993 Info, mgr,     Added driver for controller /dev/ttyACM0
2019-12-02 16:54:09.003 Info,   Opening controller /dev/ttyACM0
2019-12-02 16:54:09.003 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
2019-12-02 16:54:09.007 Info, Serial port /dev/ttyACM0 opened (attempt 1)
2019-12-02 16:54:09.008 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-12-02 16:54:09.008 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-12-02 16:54:09.008 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-12-02 16:54:09.008 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-12-02 16:54:09.008 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-12-02 16:54:09.008 Detail,
2019-12-02 16:54:09.008 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-12-02 16:54:10.008 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-02 16:54:10.008 Detail, contrlr, Removing current message
2019-12-02 16:54:10.008 Detail, contrlr, Notification: Notification - TimeOut
2019-12-02 16:54:10.019 Detail,
2019-12-02 16:54:10.019 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-12-02 16:54:11.019 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-02 16:54:11.019 Detail, contrlr, Removing current message
2019-12-02 16:54:11.019 Detail, contrlr, Notification: Notification - TimeOut
2019-12-02 16:54:11.025 Detail,
2019-12-02 16:54:11.025 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-12-02 16:54:12.027 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-02 16:54:12.027 Detail, contrlr, Removing current message
2019-12-02 16:54:12.027 Detail, contrlr, Notification: Notification - TimeOut
2019-12-02 16:54:12.048 Detail,
2019-12-02 16:54:12.048 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-12-02 16:54:13.048 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-02 16:54:13.048 Detail, contrlr, Removing current message
2019-12-02 16:54:13.048 Detail, contrlr, Notification: Notification - TimeOut
2019-12-02 16:54:13.089 Detail,
2019-12-02 16:54:13.089 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-12-02 16:54:14.089 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-02 16:54:14.089 Detail, contrlr, Removing current message
2019-12-02 16:54:14.089 Detail, contrlr, Notification: Notification - TimeOut

The USB stick is MIA per the log.

I am having the same issue, did you get it to start? If so how did you fix it?

Have you disabled or uninstalled ModemManager?

I changed slots and it’s kind of working again. It shouldn’t make a difference though? It’s being recognized in the Host OS.

I’m running Hass.io OS on a RP 3b+ I tried the commands in the docs to disable modem manager and got errors that command does not exist. If this OS is made for HA, shouldn’t that be disabled by default?

He means running them from the Ubuntu guest(host)

I’ve never used docker before…my understanding is that Hass.io is a docker container within an Ubuntu install. Is that correct? So when I SSH to the RP then I am in the docker container? If so how do I get to the actual OS?

My question was in response to OP, who said their OS is Ubuntu. Ubuntu seems to come with ModemManager enabled by default. It is a common problem for Z-Wave, so much so that a fix was pushed to OZW 1.4 to deal with it.

Hass.io is not Ubuntu. The Hass.io docs say “powered by HassOS and Docker”. The HassOS project says “Hass.io OS based on buildroot”. Buildroot is not Ubuntu. Buildroot does have a modemmanager package, however Hass.io does not install it these days.

I should note that you can install Hass.io in a generic linux install, where the host OS might be Ubuntu, but that’s different than using a Hass.io image. If you’ve chosen that method you would probably know how to access the host OS.

Zwave network still won’t start, here is my OZW Log:

2019-12-01 22:57:24.134 Always, OpenZwave Version 1.4.3440 Starting Up
2019-12-01 22:57:33.158 Info, Setting Up Provided Network Key for Secure Communications
2019-12-01 22:57:33.159 Info, mgr,     Added driver for controller /dev/ttyUSB1
2019-12-01 22:57:33.159 Info,   Opening controller /dev/ttyUSB1
2019-12-01 22:57:33.159 Info, Trying to open serial port /dev/ttyUSB1 (attempt 1)
2019-12-01 22:57:33.162 Info, Serial port /dev/ttyUSB1 opened (attempt 1)
2019-12-01 22:57:33.164 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-12-01 22:57:33.164 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-12-01 22:57:33.164 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-12-01 22:57:33.164 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-12-01 22:57:33.164 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-12-01 22:57:33.164 Detail,
2019-12-01 22:57:33.165 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0x>
2019-12-01 22:57:34.165 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-01 22:57:34.165 Detail, contrlr, Removing current message
2019-12-01 22:57:34.165 Detail, contrlr, Notification: Notification - TimeOut
2019-12-01 22:57:34.173 Detail,
2019-12-01 22:57:34.173 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, >
2019-12-01 22:57:35.174 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-01 22:57:35.174 Detail, contrlr, Removing current message
2019-12-01 22:57:35.174 Detail, contrlr, Notification: Notification - TimeOut
2019-12-01 22:57:35.175 Detail,
2019-12-01 22:57:35.175 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03>
2019-12-01 22:57:36.175 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-01 22:57:36.176 Detail, contrlr, Removing current message
2019-12-01 22:57:36.176 Detail, contrlr, Notification: Notification - TimeOut
2019-12-01 22:57:36.176 Detail,
2019-12-01 22:57:36.176 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0>
2019-12-01 22:57:37.177 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-01 22:57:37.177 Detail, contrlr, Removing current message
2019-12-01 22:57:37.177 Detail, contrlr, Notification: Notification - TimeOut
2019-12-01 22:57:37.178 Detail,
2019-12-01 22:57:37.178 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56>
2019-12-01 22:57:38.178 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-12-01 22:57:38.707 Detail, contrlr, Removing current message
2019-12-01 22:57:38.707 Detail, contrlr, Notification: Notification - TimeOut

Seems like /dev/ttyUSB1 is the wrong path.

The Nortek USB combo stick is showing as /dev/ttyUSB0 and /dev/ttyUSB1. The Zigbee controller won’t work or configure for ZHA either. I’ll try USB0 for the zwave but it did not work before. If that does not work, I’m giving up on HA and trying something else.

Even if the host recognizes the device, the guest OS needs drivers and such as well.
Try the ModemManager fix in your Ubuntu (Guest OS) likely will fix your issue.