New Zwave controller commands timing out

Configuration Z-Wave
1

Hey all, I’m setting up zwave for the first time on an existing hassio installation on a Raspberry Pi 3, using a new Aeotec z-stick generation 5. In the logs, it looks like the initial commands sent by OpenZwave to the controller (FUNC_ID_ZW_GET_VERSION, FUNC_ID_ZW_MEMORY_GET_ID, etc.) are timing out. Can anyone help troubleshoot this?

Per the docs, I ran:
$ curl -d '{"devices": ["ttyAMA0"]}' http://hassio/homeassistant/options
via SSH, which returned as successful but on restart still had the same problem.

Here are the full logs I’m seeing:

2017-12-13 11:35:20.566 Always, OpenZwave Version 1.4.2586 Starting Up
2017-12-13 11:35:21.845 Info, Setting Up Provided Network Key for Secure Communications
2017-12-13 11:35:21.846 Info, mgr,     Added driver for controller /dev/ttyAMA0
2017-12-13 11:35:21.846 Info,   Opening controller /dev/ttyAMA0
2017-12-13 11:35:21.846 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2017-12-13 11:35:21.855 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2017-12-13 11:35:21.855 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2017-12-13 11:35:21.855 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2017-12-13 11:35:21.855 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2017-12-13 11:35:21.855 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2017-12-13 11:35:21.856 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2017-12-13 11:35:21.856 Detail,
2017-12-13 11:35:21.856 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2017-12-13 11:35:22.856 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-12-13 11:35:22.856 Detail, contrlr, Removing current message
2017-12-13 11:35:22.856 Detail, contrlr, Notification: Notification - TimeOut
2017-12-13 11:35:22.857 Detail,
2017-12-13 11:35:22.857 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2017-12-13 11:35:23.858 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-12-13 11:35:23.858 Detail, contrlr, Removing current message
2017-12-13 11:35:23.858 Detail, contrlr, Notification: Notification - TimeOut
2017-12-13 11:35:23.859 Detail,
2017-12-13 11:35:23.859 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2017-12-13 11:35:24.859 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-12-13 11:35:24.859 Detail, contrlr, Removing current message
2017-12-13 11:35:24.859 Detail, contrlr, Notification: Notification - TimeOut
2017-12-13 11:35:24.860 Detail,
2017-12-13 11:35:24.860 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2017-12-13 11:35:25.860 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-12-13 11:35:25.861 Detail, contrlr, Removing current message
2017-12-13 11:35:25.861 Detail, contrlr, Notification: Notification - TimeOut
2017-12-13 11:35:25.861 Detail,
2017-12-13 11:35:25.862 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2017-12-13 11:35:26.862 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-12-13 11:35:26.862 Detail, contrlr, Removing current message
2017-12-13 11:35:26.862 Detail, contrlr, Notification: Notification - TimeOut

And here is my configuration (I’ve excluded the network key)

zwave:
    usb_path: /dev/ttyAMA0
2

Hi, I am getting the same errors here on Raspian/Pi 2 - and my controller (same Aeotec Z stick gen 5) is not showing up.

Matt

3

In my case, I had the usb_path configured incorrectly. I used the SSH addon and hassio CLI to list my hardware devices, tried a different one, and it worked.

I believe I used the hassio hardware command to list devices.

This is probably an obvious troubleshooting step for most with some experience, but it may be nice to mention this as a configuration step in the documentation, instead of just listing ttyAMA0. Even something like $YOUR_USB_PATH may make it more clear that this is not the same for everyone. Again, obvious in hindsight I guess.

4

Thanks! now solved for me too, I had it as ACM0 (which gave a sensible response to ls -lha /dev/ttyACM0) but ichanging it to /dev/ttyAMA0 made everything fall into place - thanks again