Z-Wave Notification DriverFailed

Hello everyone,

after my Hass.io installation crashed and I reinstalled my latest snapshot I experience zwave issues:

This is in my HA.log:

WARNING (Dummy-4) [openzwave] Z-Wave Notification DriverFailed : {'notificationType': 'DriverFailed', 'homeId': 0, 'nodeId': 255}

The Zwave log states as follows:

2018-11-11 21:34:44.298 Always, OpenZwave Version 1.4.3253 Starting Up
2018-11-11 21:35:35.971 Info, Setting Up Provided Network Key for Secure Communications
2018-11-11 21:35:35.971 Info, mgr,     Added driver for controller /dev/ttyAMA0
2018-11-11 21:35:35.971 Info,   Opening controller /dev/ttyAMA0
2018-11-11 21:35:35.971 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2018-11-11 21:35:35.972 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2018-11-11 21:35:35.976 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2018-11-11 21:35:35.976 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2018-11-11 21:35:35.976 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2018-11-11 21:35:35.976 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2018-11-11 21:35:35.976 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2018-11-11 21:35:35.976 Detail,
2018-11-11 21:35:35.976 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2018-11-11 21:35:35.976 Detail, contrlr, Notification: DriverFailed

In Z-Wave/Configuration no commands are possible:

WARNING (MainThread) [homeassistant.core] Unable to find service zwave/test_network

I already tried to reinstall zwave, this is the answer in Terminal:

wget -q -O - http://razberry.z-wave.me/install | sudo bash

core-ssh:~# wget -q -O - http://razberry.z-wave.me/install | sudo bash
-bash: sudo: command not found
wget: server returned error: HTTP/1.1 307 Temporary Redirect

What’s wrong? I’m using the Razberry board.

Do I have to deactivate Bluetooth in order to get the Razberry GPIO running?

If so - how may I access the config.txt?

I’m not able to mount the boot partition of the standard hassio installation.

I even installed Rasbian on my other SD card and plugged my hassio SD into USB.

What’s the terminal command to mount it?

Did you figure this one out @mny?

After upgrading from 0.7something to 0.84 and reloading a snapshot, I got the same DriverFailed problem as you describe in your first post.

I finally managed to figure this one out. What I had done was to completely reinstall HassIO from scratch, and then restoring my latest working snapshot.

What I had forgotten was the tiny detail that when you need the GPIO on Raspberry Pi 3 for your Z-Wave module you have to add dtoverlay=pi3-miniuart-bt to config.txt directly on the SD card. And since this file is “outside” of Hass.io’s container world, it won’t get restored when restoring an old snapshot.

1 Like

No, I did not solve it the way it is meant to be.

What I did is I reinstalled my Pi with an old Resinos image and HASSIO on top of it. Everything works as of now.