After upgrade Zwave entities become unavailable

[nelbs]

Hello,

After installing 0.92 some Zwave devices becomes unavailable. I dont see the nodes in the Zwave console. This problems occured the first time a week ago after updating my Pi and HASS to 0.91.4. I also noticed that the nodes which are recognized are named different (from sensor.neo_coolcam… to sensor.shenzhen…) I read that this had to do with a change of the openzwave package.

so I tried to fix the unavailable nodes to reset all the zwave devices (aotec stick, extender and all battery sensors). After adding all the nodes everything works fine…till now.

It seems that I’m back to the original problem someone an idea??
I get the following messages:

homeassistant log

Z-Wave node 5 not ready after 30 seconds, continuing anyway
Z-Wave node 7 not ready after 30 seconds, continuing anyway

zwave log

2019-04-25 23:36:10.469 Info, Node005, ApplicationCommandHandler - Unhandled Command Class 0x71
2019-04-25 23:36:10.492 Detail, Node005, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x05, 0x04, 0x30, 0x03, 0x00, 0x0c, 0xcf
2019-04-25 23:36:10.492 Detail,
2019-04-25 23:36:10.492 Info, Node005, ApplicationCommandHandler - Unhandled Command Class 0x30
2019-04-25 23:36:11.875 Detail, Node005, Received: 0x01, 0x0f, 0x00, 0x04, 0x00, 0x05, 0x09, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x07, 0x08, 0x00, 0x7c
2019-04-25 23:36:11.875 Detail,
2019-04-25 23:36:11.875 Info, Node005, ApplicationCommandHandler - Unhandled Command Class 0x71
2019-04-25 23:36:11.897 Detail, Node005, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x05, 0x04, 0x30, 0x03, 0xff, 0x0c, 0x30
2019-04-25 23:36:11.897 Detail,
2019-04-25 23:36:11.897 Info, Node005, ApplicationCommandHandler - Unhandled Command Class 0x30
2019-04-25 23:36:42.978 Detail, Node005, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x05, 0x0a, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x07, 0x00, 0x01, 0x08, 0x61
2019-04-25 23:36:42.979 Detail,
2019-04-25 23:36:42.979 Info, Node005, ApplicationCommandHandler - Unhandled Command Class 0x71
2019-04-25 23:36:43.001 Detail, Node005, Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x05, 0x04, 0x30, 0x03, 0x00, 0x0c, 0xcf
2019-04-25 23:36:43.001 Detail,
2019-04-25 23:36:43.001 Info, Node005, ApplicationCommandHandler - Unhandled Command Class 0x30
2019-04-25 23:36:49.114 Detail, Node007, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x07, 0x06, 0x31, 0x05, 0x01, 0x22, 0x00, 0xf1, 0x10
2019-04-25 23:36:49.114 Detail,
2019-04-25 23:36:49.114 Info, Node007, ApplicationCommandHandler - Unhandled Command Class 0x31

[firstof9]

Post the first 10 lines of the OZW_Log.txt file.

[nelbs]

2019-04-25 23:02:04.748 Always, OpenZwave Version 1.4.3440 Starting Up
2019-04-25 23:04:04.180 Info, Setting Up Provided Network Key for Secure Communications
2019-04-25 23:04:04.181 Warning, Failed - Network Key Not Set
2019-04-25 23:04:04.181 Info, mgr,     Added driver for controller /dev/zwave
2019-04-25 23:04:04.181 Info,   Opening controller /dev/zwave
2019-04-25 23:04:04.182 Info, Trying to open serial port /dev/zwave (attempt 1)
2019-04-25 23:04:04.183 Info, Serial port /dev/zwave opened (attempt 1)
2019-04-25 23:04:04.184 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-04-25 23:04:04.184 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-04-25 23:04:04.184 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-04-25 23:04:04.185 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-04-25 23:04:04.185 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-04-25 23:04:04.185 Detail, 
2019-04-25 23:04:04.186 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-04-25 23:04:04.188 Detail, contrlr,   Received: 0x01, 0x10, 0x01, 0x15, 0x5a, 0x2d, 0x57, 0x61, 0x76, 0x65, 0x20, 0x33, 0x2e, 0x39, 0x35, 0x00, 0x01, 0x99
2019-04-25 23:04:04.189 Detail,

[firstof9]

@nelbs

2019-04-25 23:04:04.181 Warning, Failed - Network Key Not Set

You’re missing a network key this will stop any secure nodes (ie: locks, garage door, etc) from connecting.

Everything else looks fine in the log, seems like your config_path may be messed up.
Are you using Hass.io install or venv install?

[nelbs]

Thanks,

I am using Hassbian with the following config path

zwave:
  usb_path: /dev/zwave

[firstof9]

Follow the instructions in this post for finding the config_path:

Z-wave will not pull device info just loads as unknown

If you want to see what the auto-detected config path is set to, you can do it with some python. Run this command, replacing /dev/ttyACM0 with your z-stick’s path: python -c 'from openzwave.option import ZWaveOption; option = ZWaveOption("/dev/ttyACM0"); print(option.config_path)'`. Be sure to use the python where HA is installed, e.g. if it’s a virtualenv make sure you activate it first. Example from my venv. Note that it’s not the default and I installed the configs to /usr/local/etc/openzw…

[nelbs]

This is my config path.

(homeassistant) homeassistant@hassbian:/home/pi $ python -c 'from openzwave.option import ZWaveOption; option = ZWaveOption("/dev/zwave"); print(option.config_path)'`.
>

I dont understand what to do with this?

[firstof9]

There’s a formatting error use this line:

python -c 'from openzwave.option import ZWaveOption; option = ZWaveOption("/dev/ttyACM0"); print(option.config_path)'

[nelbs]

I think I fixed it.

The error “network key not set” did me realize that I never set a key . So I deleted the manual integration and reinstalled it via the integration section. After I upgraded hass to 0.92.1 all entities stays available.

thanks!