Network state stuck on "Driver initialised"

Configuration Z-Wave
1

Hi,

I’m trying to get Z-Wave working on Home Assistant. However, the Z-Wave network state gets perpetually stuck on “Driver initialised”. Eventually, hass gives up and continues onwards.

However, as the network gets stuck in this state it’s not possible to send out Z-Wave commands (e.g. switch on). Z-Wave information from sensors can be received without issue.

I’ve tried both using a Docker image and a Python virtualenv, set up as per the instructions. If I shut down hass and start up Open Z Wave Control Panel, I am able to send Z-Wave commands successfully.

Any ideas what might be going on?

16-05-08 21:54:47 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:54:48 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:54:49 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:54:50 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:54:51 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:54:52 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:54:53 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:54:54 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:54:55 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:54:56 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:54:57 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:54:58 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:54:59 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:00 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:01 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:02 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:03 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:04 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:05 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:06 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:07 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:08 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:09 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:10 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:11 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:12 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:13 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:14 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] network state: 5 Driver initialised 16-05-08 21:55:15 WARNING (ThreadPool Worker 11) [homeassistant.components.zwave] zwave not ready after 30 seconds, continuing anyway 16-05-08 21:55:15 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] final network state: 5 Driver initialised 16-05-08 21:55:15 INFO (ThreadPool Worker 11) [homeassistant.components.zwave] zwave polling interval set to 60000 ms

2

How many devices do you have? I have 20 or so, and I get an initialized message for each one. Also, most times, HA will give you the 30 second message because initializing each one takes a second or two and you get to the point where it times out. The timeout isn’t harmful however, it will continue to initialize the devices in the background, You know it has finished when you see something like:

May 08 21:14:05 homeassistant hass[30670]: 16-05-08 21:14:05 INFO (ThreadPool Worker 15) [homeassistant.components.zwave] zwave polling interval set to 30000 ms
May 08 21:14:05 homeassistant hass[30670]: 16-05-08 21:14:05 INFO (ThreadPool Worker 15) [homeassistant.core] Bus:Handling <Event service_registered[L]: service=add_node, domain=zwave>
May 08 21:14:05 homeassistant hass[30670]: 16-05-08 21:14:05 INFO (ThreadPool Worker 15) [homeassistant.core] Bus:Handling <Event service_registered[L]: service=remove_node, domain=zwav>
May 08 21:14:05 homeassistant hass[30670]: 16-05-08 21:14:05 INFO (ThreadPool Worker 15) [homeassistant.core] Bus:Handling <Event service_registered[L]: service=heal_network, domain=zwave>
May 08 21:14:05 homeassistant hass[30670]: 16-05-08 21:14:05 INFO (ThreadPool Worker 15) [homeassistant.core] Bus:Handling <Event service_registered[L]: service=soft_reset, domain=zwave>
May 08 21:14:05 homeassistant hass[30670]: 16-05-08 21:14:05 INFO (ThreadPool Worker 15) [homeassistant.core] Bus:Handling <Event service_registered[L]: service=test_network, domain=zwav
3

I’ve only got three devices (two switches and one sensor). I remember seeing those messages previously so it must have fully initialised. I’ve just tried running hass again but weirdly this time around the initialisation completes before the 30 second limit. I’ve changed absolutely nothing so this is a little perplexing!

INFO:homeassistant.components.zwave:network state: 5 Driver initialised INFO:homeassistant.components.zwave:network state: 10 Network ready INFO:homeassistant.components.zwave:zwave ready after 13 seconds INFO:homeassistant.components.zwave:zwave polling interval set to 60000 ms INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=zwave, service=add_node> INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=zwave, service=remove_node> INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=zwave, service=heal_network> INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=zwave, service=soft_reset> INFO:homeassistant.core:Bus:Handling <Event service_registered[L]: domain=zwave, service=test_network>

However, only one of my switches seems to be working. Looking at the OZW_log.txt log file, whenever I try and toggle the non-working switch’s state the command is dropped because the node is presumed dead. I’ve tried toggling a heal but to no avail - any ideas?

2016-05-08 22:53:53.408 Info, Node003, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - False 2016-05-08 22:53:53.408 Info, Node003, SwitchBinary::Set - Setting node 3 to Off 2016-05-08 22:53:53.408 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x25, 0x01, 0x00, 0x25, 0x38, 0xdf 2016-05-08 22:53:53.408 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x25, 0x02, 0x25, 0x39, 0xdf 2016-05-08 22:53:53.408 Error, Node003, ERROR: Dropping command because node is presumed dead 2016-05-08 22:53:53.408 Detail, Node003, Removing current message 2016-05-08 22:53:53.408 Error, Node003, ERROR: Dropping command because node is presumed dead 2016-05-08 22:53:53.408 Detail, Node003, Removing current message

Thanks for your help! :slight_smile:

Edit: After manually activating and deactivating the switch using the button on it, it appears to have been marked as revived and I can now control the state through the hass UI;

2016-05-08 23:25:57.859 Error, Node003, WARNING: node revived 2016-05-08 23:25:57.859 Info, Node003, Received SwitchBinary report from node 3: level=On 2016-05-08 23:25:57.859 Detail, Node003, Refreshed Value: old value=true, new value=true, type=bool 2016-05-08 23:25:57.859 Detail, Node003, Changes to this value are not verified 2016-05-08 23:25:57.859 Detail, Node003, Notification: Notification - Node Alive 2016-05-08 23:25:57.859 Detail, Node003, Notification: ValueChanged

4

Great, sounds like you are in good shape :slight_smile:

5

What is the cause of this 5 driver warning? I keep getting this error and after one or two times of using the switch in my HASS, the switch stops working and is “presumed dead”. It seems to happen on a restart of HASS