Z-Wave Notification DriverFailed : {'notificationType': 'DriverFailed', 'homeId': 0, 'nodeId': 255}

Configuration Z-Wave
1

New here. I have Hassio 0.86.2 installed on a Raspberry Pi 3 with a Aeotec Gen 5 USB stick. I checked my hardware and got:

serial:

  • /dev/ttyAMA0
  • /dev/ttyACM0

configuration.yaml file reads:

zwave:
usb_path: /dev/ttyACM0
network_key: “0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10”

switch:

  • platform: command_line
    switches:
    aeotec_zstick_disco_light:
    friendly_name: ‘Aeotec Z-Stick Disco Light’
    command_on: ‘echo -e -n “\x01\x08\x00\xF2\x51\x01\x01\x05\x01\x50” > /dev/serial/by-id/usb-0658_0200-if00’
    command_off: ‘echo -e -n “\x01\x08\x00\xF2\x51\x01\x00\x05\x01\x51” > /dev/serial/by-id/usb-0658_0200-if00’

I also tried usb_path: /dev/ttyAMA0 and got same error.

I can turn on and off the disco lights. Not sure why I am getting this error or what I am doing wrong.

2

I believe I was able to get it working. Navigated to /config/.storage/core.config_entries changed “usb_path”: “/dev/ttyACM0” to “usb_path”: “/dev/ttyAMA0”

I also changed the configuration.yaml file to read:

usb_path: /dev/ttyACM0

3

The path setting in configuration.yaml is irrelevant once it has been imported into the core.config_entries file. Changing it afterwards has no effect, until you delete the integration (Configuration -> Integrations), then restart HA, where it will be re-imported again.

4

So what switch are your lights connected to? Have you added that zwave switch to your zwave fabric?

5

I am trying to setup a Yale Assure Lock.

6

I don’t have any locks, but I would expect the process would be to go to the ‘add node secure’ option in configuration > zwave panel. After that, you can use the zwave panel to set options on the device.

7

That worked. I removed the node, rebooted and added the Yale Lock via the secure option. Thanks.