Aeotec Gen5 Stick, "DriverFailed"

Configuration Z-Wave
1

This doesn’t seem like an uncommon problem but i’ve done the basic checks and can’t understand what else could be causing the problem.

OZW log:

2018-12-29 10:57:26.403 Always, OpenZwave Version 1.4.3254 Starting Up

2018-12-29 10:57:48.155 Info, Setting Up Provided Network Key for Secure Communications
2018-12-29 10:57:48.155 Info, mgr, Added driver for controller /dev/ttyAMA0
2018-12-29 10:57:48.156 Info, Opening controller /dev/ttyAMA0
2018-12-29 10:57:48.156 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2018-12-29 10:57:48.157 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2018-12-29 10:57:48.158 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2018-12-29 10:57:48.158 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2018-12-29 10:57:48.158 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2018-12-29 10:57:48.158 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2018-12-29 10:57:48.158 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2018-12-29 10:57:48.159 Detail,
2018-12-29 10:57:48.159 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2018-12-29 10:57:48.160 Detail, contrlr, Notification: DriverFailed

hassio command line:

core-ssh:~# hassio hw info

{
“result”: “ok”,
“data”: {
“serial”: [
“/dev/ttyAMA0”,
“/dev/ttyACM0”
],
“input”: ,
“disk”: ,
“gpio”: [
“gpiochip128”,
“gpiochip0”
],
“audio”: {
“0”: {
“name”: “bcm2835_alsa - bcm2835 ALSA”,
“type”: “ALSA”,
“devices”: [
{
“chan_id”: “0”,
“chan_type”: “digital audio playback”
},
{
“chan_id”: “1”,
“chan_type”: “digital audio playback”
}
]
}
}
}
}

It looks to me that the port is correct, but even after 4 reboots it will not accept the driver. What other suggestions can i try?

2

Try /dev/ttyACM0 likely the correct port.

3

I’ve tried adding both port options into config.yaml but i get the same error message.

zwave:
  usb_path: /dev/ttyACM0

and

zwave:
  usb_path: /dev/ttyAMA0
4

I think I had to unplug the zstick, plug it back in (same usb port) and restart HA to fix this. It was a while ago and I no longer have zwave.

5

I got it working, my fix should it help anyone;

I removed the configuration.yaml zwave integration and port path. I then removed the zwave hassio front end integration. I then rebooted. Once back up, i reconfigured the zwave front end integration and used the port path /dev/ttyACM0. It added the device successfully and i rebooted HA once again. Once back up, the Aeotec stick was found and i have since added a aeotec multisensor and will now try configuring it.

Thanks for your help.

1 Like
6

I was moving from a Razberry hat to a Aeotec Z wave stick. This was just the info I needed.

1 Like
7

Hello,

thanks for the tip, got it working, too.
EDIT: works on my RPi4 with an additional externally powered USB-2 hub (as the Aeotec Gen5 USB stick is not compöiant with the USB specs). Note Aeotec has now a Gen5+ (PLUS) device which is compliant with RPi4. But so i can re-use my old one and do not need to buy a new one…

/ Ralf