Cannot get Z-Wave working with hassio

Installation Home Assistant OS
1

Hi!

Noob warning… I tried first install Hassbian and with that I get my z-wave working (Aeon Z-Stick S2). But with hass.io I cannot get it working… I’ve tried to find solution but with no luck ;). Raspberry 2.

Anybody could help?

Here is log:

2019-07-12 14:21:23.961 Always, OpenZwave Version 1.4.3440 Starting Up
2019-07-12 14:21:44.744 Info, Setting Up Provided Network Key for Secure Communications
2019-07-12 14:21:44.745 Info, mgr,     Added driver for controller /dev/ttyAMA0
2019-07-12 14:21:44.745 Info,   Opening controller /dev/ttyAMA0
2019-07-12 14:21:44.746 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2019-07-12 14:21:44.750 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2019-07-12 14:21:44.751 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-07-12 14:21:44.751 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-07-12 14:21:44.752 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-07-12 14:21:44.752 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-07-12 14:21:44.752 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-07-12 14:21:44.752 Detail,
2019-07-12 14:21:44.752 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-07-12 14:21:45.753 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-12 14:21:45.753 Detail, contrlr, Removing current message
2019-07-12 14:21:45.754 Detail, contrlr, Notification: Notification - TimeOut
2019-07-12 14:21:45.754 Detail,
2019-07-12 14:21:45.755 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-07-12 14:21:46.755 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-12 14:21:46.755 Detail, contrlr, Removing current message
2019-07-12 14:21:46.756 Detail, contrlr, Notification: Notification - TimeOut
2019-07-12 14:21:46.757 Detail,
2019-07-12 14:21:46.757 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-07-12 14:21:47.757 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-12 14:21:47.757 Detail, contrlr, Removing current message
2019-07-12 14:21:47.758 Detail, contrlr, Notification: Notification - TimeOut
2019-07-12 14:21:47.758 Detail,
2019-07-12 14:21:47.759 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-07-12 14:21:48.759 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-12 14:21:48.759 Detail, contrlr, Removing current message
2019-07-12 14:21:48.760 Detail, contrlr, Notification: Notification - TimeOut
2019-07-12 14:21:48.760 Detail,
2019-07-12 14:21:48.760 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-07-12 14:21:49.761 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-12 14:21:49.761 Detail, contrlr, Removing current message
2019-07-12 14:21:49.762 Detail, contrlr, Notification: Notification - TimeOut
2

You are using the wrong usb_path. /dev/ttyAMA0 is unlikely to be the Z-Stick, usually /dev/ttyACM0. Better yet, use a /dev/serial/by-id path if available. Recent versions of Hass.io are supposed to expose that one.

3 
[  225.223848] usb 1-1.5: new full-speed USB device number 4 using dwc_otg
[  225.361763] usb 1-1.5: New USB device found, idVendor=10c4, idProduct=ea60
[  225.365755] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  225.369535] usb 1-1.5: Product: CP2102 USB to UART Bridge Controller
[  225.373238] usb 1-1.5: Manufacturer: Silicon Labs
[  225.376923] usb 1-1.5: SerialNumber: 0001
[  225.423157] usbcore: registered new interface driver cp210x
[  225.427474] usbserial: USB Serial support registered for cp210x
[  225.431847] cp210x 1-1.5:1.0: cp210x converter detected
[  225.444208] usb 1-1.5: cp210x converter now attached to ttyUSB0

with /dev/ttyUSB0 I got “Z-Wave validation failed. Is the path to the USB stick correct?”

I really do not know how find real device-id name?

core-ssh:/dev# ls -l /dev/serial/by-id/*
ls: /dev/serial/by-id/*: No such file or directory

4

It’s in the docs. hassio hardware info

5

serial:

  • /dev/ttyAMA0
  • /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0
  • /dev/ttyUSB0
6

It sounds looks like the Aeotec S2 stick reports the idVendor=10c4, idProduct=ea60 (according to here and other places), so either /dev/ttyUSB0 or /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0 (prefer that one) should work.

Is your zstick plugged directly into the RPi?

1 Like
7

Thx… I am trying to this one… Zstick is directly plugged into the RPi. And yesterday I got it working with hassbian (I wanted to test it because I tried before that hassio and did not get it working)…

8

Hmm… add “node secure”

service not found…

9

It means the z-wave component wasn’t loaded successfully so the service is not available. What does the OZW_Log.txt show now? Same thing?

10

Old log before changing USB0 or serial-id (there is nothing new):

2019-07-12 14:21:23.961 Always, OpenZwave Version 1.4.3440 Starting Up
2019-07-12 14:21:44.744 Info, Setting Up Provided Network Key for Secure Communications
2019-07-12 14:21:44.745 Info, mgr,     Added driver for controller /dev/ttyAMA0
2019-07-12 14:21:44.745 Info,   Opening controller /dev/ttyAMA0
2019-07-12 14:21:44.746 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2019-07-12 14:21:44.750 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2019-07-12 14:21:44.751 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-07-12 14:21:44.751 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-07-12 14:21:44.752 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-07-12 14:21:44.752 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-07-12 14:21:44.752 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-07-12 14:21:44.752 Detail,
2019-07-12 14:21:44.752 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-07-12 14:21:45.753 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-12 14:21:45.753 Detail, contrlr, Removing current message
2019-07-12 14:21:45.754 Detail, contrlr, Notification: Notification - TimeOut
2019-07-12 14:21:45.754 Detail,
2019-07-12 14:21:45.755 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-07-12 14:21:46.755 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-12 14:21:46.755 Detail, contrlr, Removing current message
2019-07-12 14:21:46.756 Detail, contrlr, Notification: Notification - TimeOut
2019-07-12 14:21:46.757 Detail,
2019-07-12 14:21:46.757 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-07-12 14:21:47.757 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-12 14:21:47.757 Detail, contrlr, Removing current message
2019-07-12 14:21:47.758 Detail, contrlr, Notification: Notification - TimeOut
2019-07-12 14:21:47.758 Detail,
2019-07-12 14:21:47.759 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-07-12 14:21:48.759 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-12 14:21:48.759 Detail, contrlr, Removing current message
2019-07-12 14:21:48.760 Detail, contrlr, Notification: Notification - TimeOut
2019-07-12 14:21:48.760 Detail,
2019-07-12 14:21:48.760 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-07-12 14:21:49.761 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-07-12 14:21:49.761 Detail, contrlr, Removing current message
2019-07-12 14:21:49.762 Detail, contrlr, Notification: Notification - TimeOut
2019-07-12 20:44:15.613 Error, mgr,     Manager::GetDriver failed - Home ID 0x00000000 is unknown
2019-07-12 20:44:15.614 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver
2019-07-12 20:44:15.614 Info, mgr,     Manager::WriteConfig failed - _homeId 0 not found
2019-07-12 20:44:15.670 Error, mgr,     Manager::GetDriver failed - Home ID 0x00000000 is unknown
2019-07-12 20:44:15.670 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver
2019-07-12 20:44:15.670 Info, mgr,     Manager::WriteConfig failed - _homeId 0 not found
2019-07-12 20:44:16.664 Detail, Notification: DriverRemoved
2019-07-12 20:44:16.665 Always, ***************************************************************************
2019-07-12 20:44:16.665 Always, *********************  Cumulative Network Statistics  *********************
2019-07-12 20:44:16.665 Always, *** General
2019-07-12 20:44:16.665 Always, Driver run time: . .  . 0 days, 6 hours, 22 minutes
2019-07-12 20:44:16.665 Always, Frames processed: . . . . . . . . . . . . . . . . . . . . 0
2019-07-12 20:44:16.665 Always, Total messages successfully received: . . . . . . . . . . 0
2019-07-12 20:44:16.665 Always, Total Messages successfully sent: . . . . . . . . . . . . 5
2019-07-12 20:44:16.665 Always, ACKs received from controller:  . . . . . . . . . . . . . 0
2019-07-12 20:44:16.665 Always, *** Errors
2019-07-12 20:44:16.666 Always, Unsolicited messages received while waiting for ACK:  . . 0
2019-07-12 20:44:16.666 Always, Reads aborted due to timeouts:  . . . . . . . . . . . . . 0
2019-07-12 20:44:16.666 Always, Bad checksum errors:  . . . . . . . . . . . . . . . . . . 0
2019-07-12 20:44:16.666 Always, CANs received from controller:  . . . . . . . . . . . . . 0
2019-07-12 20:44:16.666 Always, NAKs received from controller:  . . . . . . . . . . . . . 0
2019-07-12 20:44:16.666 Always, Out of frame data flow errors:  . . . . . . . . . . . . . 0
2019-07-12 20:44:16.666 Always, Messages retransmitted: . . . . . . . . . . . . . . . . . 0
2019-07-12 20:44:16.666 Always, Messages dropped and not delivered: . . . . . . . . . . . 5
2019-07-12 20:44:16.666 Always, ***************************************************************************
2019-07-12 20:44:16.666 Warning, WARNING: Tried to write driver config with no home ID set
2019-07-12 20:44:16.668 Detail, WriteMsg Wait Timeout m_currentMsg=00000000
2019-07-12 20:44:18.669 Info, mgr,     Driver for controller /dev/ttyAMA0 removed

With Hassbian it worked with /dev/ttyUSB0 inserted by GUI.

11

Hmm… after reboot it started to work… Let’s see how long…

aeon
aeon990×271 41.3 KB

1 Like