Powered Zwave Devices Marked as Dead

I have a Kwikset 910 works perfectly fine. I also have additional powered devices on my network. My lock is never flagged dead. My Zwave stick is the Aeotec tho.

I may native HA again since I’m sure there’s been some updates to OpenZwave since I last tried it. From your diagram it looks like all your devices are in range of your controller (Aeotec stick)? My problem may be related to the fact that the stick and the lock weren’t directly connected but only through powered nodes.

My devices are all varying distances from the USB stick. The lock is closest, about 10 feet. The energy meter is outside next to the breaker box and that has to pass through 1 interior wall and 1 exterior stucco wall. I very rarely see the diagram show nodes having to mesh, which i consider a good thing.

I also have this device about 10ft away. I tried a few experiments. I paired the lock, left it 1ft away from the stick, several hours go by and I’m able to “lock” several times (as it errors out attempting to actually lock it since it can go around full circle). I move it within a few feet from the actual door (like 8ft from the stick). After several hours, HA is still showing it and allowing me to “lock” it. I finally put it on the door itself and the same thing happens every time… it lets me lock it then won’t let me unlock it and calls it dead. If I bring it back towards the stick and push the pairing button again (without requesting HA to search for it) it will start initializing and come back. Here is the OZW logs. I’ve already changed my network keys for prod, so, not worried.

 2018-06-15 04:55:32.030 Info, Node003, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - False
2018-06-15 04:55:32.030 Info, Node003, Value_Lock::Set - Requesting lock to be Unlocked
2018-06-15 04:55:32.030 Detail, Node003, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-06-15 04:55:32.031 Detail, Node003, Queuing (Send) DoorLockCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x62, 0x01, 0x00, 0x25, 0x75, 0xd5
2018-06-15 04:55:32.031 Detail, Node003, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-06-15 04:55:32.031 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x76, 0xd7
2018-06-15 04:55:32.031 Detail,
2018-06-15 04:55:32.031 Info, Node003, Processing (Send) Nonce Request message (Callback ID=0x75, Expected Reply=0x04)
2018-06-15 04:55:32.031 Info, Node003, Sending (Send) message (Callback ID=0x75, Expected Reply=0x04) - Nonce_Get(DoorLockCmd_Set) - 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x98, 0x40, 0x05, 0x02:
2018-06-15 04:55:32.037 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-06-15 04:55:32.037 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2018-06-15 04:55:33.308 Detail, Node003,   Received: 0x01, 0x05, 0x00, 0x13, 0x02, 0x00, 0xeb
2018-06-15 04:55:33.309 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2018-06-15 04:55:33.309 Info, Node003, Request RTT 1277 Average Request RTT 1221
2018-06-15 04:55:33.321 Detail, Node003,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x03, 0x0a, 0x98, 0x80, 0xc3, 0x9d, 0xb8, 0x5b, 0x9f, 0xee, 0xf2, 0xdb, 0x1f
2018-06-15 04:55:33.321 Info, Node003, Received SecurityCmd_NonceReport from node 3
2018-06-15 04:55:33.321 Info, Node003, Sending (Send) message (Callback ID=0x77, Expected Reply=0x04) - DoorLockCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x62, 0x01, 0x00, 0x25, 0x77, 0xd7
2018-06-15 04:55:33.331 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-06-15 04:55:33.331 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2018-06-15 04:55:33.351 Detail, Node003,   Received: 0x01, 0x05, 0x00, 0x13, 0x77, 0x00, 0x9e
2018-06-15 04:55:33.352 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x77 received (expected 0x77)
2018-06-15 04:55:33.352 Info, Node003, Request RTT 1320 Average Request RTT 1270
2018-06-15 04:55:33.352 Detail,   Expected callbackId was received
2018-06-15 04:55:34.562 Detail, Node003,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x03, 0x02, 0x98, 0x40, 0x2a
2018-06-15 04:55:34.562 Info, Node003, Received SecurityCmd_NonceGet from node 3
2018-06-15 04:55:34.562 Info, NONCES: 0xc1, 0x5b, 0xff, 0x09, 0x86, 0x33, 0xa9, 0xb3
2018-06-15 04:55:34.562 Info, NONCES: 0xae, 0xe7, 0x50, 0xc0, 0x4c, 0xcf, 0x30, 0x97
2018-06-15 04:55:34.562 Info, NONCES: 0x77, 0x70, 0xd9, 0xf3, 0xf2, 0xe6, 0xc4, 0x55
2018-06-15 04:55:34.562 Info, NONCES: 0x75, 0xc7, 0xc4, 0xe7, 0x41, 0xc2, 0xf6, 0x54
2018-06-15 04:55:34.562 Info, NONCES: 0xea, 0x35, 0x9b, 0xdd, 0x1c, 0x5f, 0x32, 0xa5
2018-06-15 04:55:34.563 Info, NONCES: 0x58, 0x02, 0xec, 0x99, 0xc5, 0xe3, 0xee, 0x2c
2018-06-15 04:55:34.563 Info, NONCES: 0x5e, 0xe6, 0xbf, 0x79, 0x45, 0xf2, 0x1f, 0xdd
2018-06-15 04:55:34.563 Info, NONCES: 0x2d, 0x20, 0x3a, 0xf2, 0x03, 0x29, 0x1e, 0x76
2018-06-15 04:55:34.563 Info, Node003, Sending (Send) message (Callback ID=0x01, Expected Reply=0x04) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x03, 0x0a, 0x98, 0x80, 0xae, 0xe7, 0x50, 0xc0, 0x4c, 0xcf, 0x30, 0x97, 0x05, 0x01, 0x15:
2018-06-15 04:55:34.570 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-06-15 04:55:34.571 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2018-06-15 04:55:34.588 Detail, Node003,   Received: 0x01, 0x05, 0x00, 0x13, 0x01, 0x00, 0xe8
2018-06-15 04:55:34.588 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2018-06-15 04:55:34.588 Info, Node003, Request RTT 2557 Average Request RTT 1913
2018-06-15 04:55:34.642 Detail, Node003,   Received: 0x01, 0x1e, 0x00, 0x04, 0x00, 0x03, 0x18, 0x98, 0x81, 0x56, 0xe0, 0x18, 0xb6, 0xa4, 0x36, 0xf2, 0x7e, 0xeb, 0xc0, 0x43, 0xb8, 0xac, 0xae, 0xfa, 0x62, 0x34, 0xe4, 0xe0, 0x7c, 0xf5, 0xeb, 0xf9
2018-06-15 04:55:34.642 Info, Raw: 0x98, 0x81, 0x56, 0xe0, 0x18, 0xb6, 0xa4, 0x36, 0xf2, 0x7e, 0xeb, 0xc0, 0x43, 0xb8, 0xac, 0xae, 0xfa, 0x62, 0x34, 0xe4, 0xe0, 0x7c, 0xf5, 0xeb, 0xf9
2018-06-15 04:55:34.642 Detail, Node003, Decrypted Packet: 0x00, 0x71, 0x05, 0x19, 0x01
2018-06-15 04:55:34.643 Detail,
2018-06-15 04:55:34.643 Info, Node003, Response RTT 2611 Average Response RTT 2302
2018-06-15 04:55:34.643 Info, Node003, Received Alarm report: type=25, level=1
2018-06-15 04:55:34.643 Detail, Node003, Refreshed Value: old value=24, new value=25, type=byte
2018-06-15 04:55:34.643 Detail, Node003, Changes to this value are not verified
2018-06-15 04:55:34.643 Detail, Node003, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-06-15 04:55:34.643 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x78, 0xd9
2018-06-15 04:55:34.643 Detail, Node003, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-06-15 04:55:34.643 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x79, 0xd8
2018-06-15 04:55:34.644 Detail, Node003, Refreshed Value: old value=1, new value=1, type=byte
2018-06-15 04:55:34.644 Detail, Node003, Changes to this value are not verified
2018-06-15 04:55:34.644 Detail, Node003, Notification: ValueChanged
2018-06-15 04:55:34.652 Detail, Node003, Notification: ValueChanged
2018-06-15 04:55:42.032 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-06-15 04:55:42.032 Detail, Node003, Removing current message
2018-06-15 04:55:42.032 Detail, Node003, Notification: Notification - TimeOut
2018-06-15 04:55:42.039 Detail,
2018-06-15 04:55:42.039 Info, Node003, Processing (Send) Nonce Request message (Callback ID=0x76, Expected Reply=0x04)
2018-06-15 04:55:42.039 Info, Node003, Sending (Send) message (Callback ID=0x76, Expected Reply=0x04) - Nonce_Get(DoorLockCmd_Get) - 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x98, 0x40, 0x05, 0x02:
2018-06-15 04:55:42.046 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-06-15 04:55:42.046 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2018-06-15 04:55:52.039 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-06-15 04:55:52.040 Detail, Node003, Removing current message
2018-06-15 04:55:52.040 Detail, Node003, Notification: Notification - TimeOut
2018-06-15 04:55:52.046 Detail,
2018-06-15 04:55:52.046 Info, Node003, Processing (Send) Nonce Request message (Callback ID=0x78, Expected Reply=0x04)
2018-06-15 04:55:52.046 Info, Node003, Sending (Send) message (Callback ID=0x78, Expected Reply=0x04) - Nonce_Get(DoorLockCmd_Get) - 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x98, 0x40, 0x05, 0x02:
2018-06-15 04:55:52.054 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-06-15 04:55:52.054 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2018-06-15 04:55:52.651 Detail, Node003,   Received: 0x01, 0x05, 0x00, 0x13, 0x02, 0x01, 0xea
2018-06-15 04:55:52.652 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2018-06-15 04:55:52.652 Info, Node003, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2018-06-15 04:55:52.652 Warning, Node003, WARNING: Device is not a sleeping node.
2018-06-15 04:55:53.195 Info, Node003, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - False
2018-06-15 04:55:53.195 Info, Node003, Value_Lock::Set - Requesting lock to be Unlocked
2018-06-15 04:55:53.196 Detail, Node003, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-06-15 04:55:53.196 Detail, Node003, Queuing (Send) DoorLockCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x62, 0x01, 0x00, 0x25, 0x7a, 0xda
2018-06-15 04:55:53.196 Detail, Node003, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-06-15 04:55:53.196 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x7b, 0xda
2018-06-15 04:55:59.601 Detail, Node003,   Received: 0x01, 0x05, 0x00, 0x13, 0x02, 0x01, 0xea
2018-06-15 04:55:59.602 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2018-06-15 04:55:59.602 Info, Node003, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2018-06-15 04:55:59.602 Warning, Node003, WARNING: Device is not a sleeping node.
2018-06-15 04:56:01.812 Info, Node003, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - False
2018-06-15 04:56:01.813 Info, Node003, Value_Lock::Set - Requesting lock to be Unlocked
2018-06-15 04:56:01.813 Detail, Node003, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-06-15 04:56:01.813 Detail, Node003, Queuing (Send) DoorLockCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x62, 0x01, 0x00, 0x25, 0x7c, 0xdc
2018-06-15 04:56:01.813 Detail, Node003, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-06-15 04:56:01.813 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x7d, 0xdc
2018-06-15 04:56:02.047 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-06-15 04:56:02.047 Detail, Node003, Removing current message
2018-06-15 04:56:02.047 Detail, Node003, Notification: Notification - TimeOut
2018-06-15 04:56:02.053 Detail,
2018-06-15 04:56:02.053 Info, Node003, Processing (Send) Nonce Request message (Callback ID=0x79, Expected Reply=0x04)
2018-06-15 04:56:02.053 Info, Node003, Sending (Send) message (Callback ID=0x79, Expected Reply=0x04) - Nonce_Get(DoorLockCmd_Get) - 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x98, 0x40, 0x05, 0x02:
2018-06-15 04:56:02.061 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-06-15 04:56:02.062 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2018-06-15 04:56:09.042 Detail, Node003,   Received: 0x01, 0x05, 0x00, 0x13, 0x02, 0x01, 0xea
2018-06-15 04:56:09.042 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2018-06-15 04:56:09.042 Info, Node003, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2018-06-15 04:56:09.042 Warning, Node003, WARNING: Device is not a sleeping node.
2018-06-15 04:56:09.042 Error, Node003, ERROR: node presumed dead
2018-06-15 04:56:09.042 Detail, Node003, Notification: Notification - Node Dead
2018-06-15 04:56:12.053 Error, Node003, ERROR: Dropping command because node is presumed dead
2018-06-15 04:56:12.053 Detail, Node003, Removing current message
2018-06-15 04:56:12.054 Detail, Node003, Notification: Notification - TimeOut
2018-06-15 04:56:12.059 Error, Node003, ERROR: Dropping command because node is presumed dead
2018-06-15 04:56:12.060 Detail, Node003, Removing current message
2018-06-15 04:56:12.060 Error, Node003, ERROR: Dropping command because node is presumed dead
2018-06-15 04:56:12.060 Detail, Node003, Removing current message
2018-06-15 04:56:12.060 Error, Node003, ERROR: Dropping command because node is presumed dead
2018-06-15 04:56:12.060 Detail, Node003, Removing current message
2018-06-15 04:56:12.060 Error, Node003, ERROR: Dropping command because node is presumed dead
2018-06-15 04:56:12.060 Detail, Node003, Removing current message

That is start to finish from it recognizing it again (fresh) locking it on the actual door, and then refusing to relock. I’m curious about this block right here, more specifically:

2018-06-15 04:55:34.643 Info, Node003, Response RTT 2611 Average Response RTT 2302
2018-06-15 04:55:34.643 Info, Node003, Received Alarm report: type=25, level=1
2018-06-15 04:55:34.643 Detail, Node003, Refreshed Value: old value=24, new value=25, type=byte
2018-06-15 04:55:34.643 Detail, Node003, Changes to this value are not verified
2018-06-15 04:55:34.643 Detail, Node003, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-06-15 04:55:34.643 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x78, 0xd9
2018-06-15 04:55:34.643 Detail, Node003, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-06-15 04:55:34.643 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x79, 0xd8
2018-06-15 04:55:34.644 Detail, Node003, Refreshed Value: old value=1, new value=1, type=byte
2018-06-15 04:55:34.644 Detail, Node003, Changes to this value are not verified
2018-06-15 04:55:34.644 Detail, Node003, Notification: ValueChanged
2018-06-15 04:55:34.652 Detail, Node003, Notification: ValueChanged
2018-06-15 04:55:42.032 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-06-15 04:55:42.032 Detail, Node003, Removing current message
2018-06-15 04:55:42.032 Detail, Node003, Notification: Notification - TimeOut

I’m not as familiar with HA or OZW logs, but, this doesn’t seem to be a get/post based on something I command. It looks like a post-lock command ran automatically and it is failing.

… that said, no matter if its technical or not–there is definitely a weird range issue (as I’m able to get it back up by simply moving it over 2-4ft from where it currently sits…I’ll take a picture… this thing is maybe 10-12ft from the stick… My “test” had it sitting on top of the desk for several hours and on the coffee table in the left part of the pic before being put on the door.

As I stated before, I’m using a different stick than yall, so, its possible its that… Anyone have anymore thoughts?

When a Zwave device is listed as dead, it means the whatever it is can no longer be seen by the Zwave controller. Absolute distance is a meaningless number. You must think direct line of site from the device and controller perspective, not from your perspective standing near the device. You have clearly demonstrated that something is preventing the radio signal from going to / from the controller when you move it to the installed location.
Zwave radios are very low power and especially battery powered ones and ANYTHING and I mean ANYTHING between the controller and device severely cuts that power. That is why the Zwave mesh is so important. You may be able to reposition the Zwave controller. Move the HA device or use a long USB cable. Or better yet, add additional line powered Zwave devices. Build out from the hub keeping line of site in mind.

Yeah… and I don’t mean this in an offensive way–to you or the community–more therapeutic whining, but, it is incredibly tough to really go with the blind faith of “its not a range issue, buy more, expand your z-wave mesh [which, to me, is range, but I hear you], itll be fine”…

As someone who is actively building a home right now and making a million and one decisions, building my smart home is a pretty frustrating process with this type of sentiment. I see tons of closed loop systems that “just work” but lack a feature or two, the ability to truly customize, don’t play nice with X, cost Y up front or Z subscription and are online only or ping the mothership… if I do it myself with HA I get all that back but I’m wading through a sea of “maybe, just give it a try” products.

I was actually told by a rep for a commercial MQTT product installer using CQC that I should pay the X fee and “just try it out…” or my money back. Its like, dude, I have to have the house wired a certain way for half of these systems. If, for example, Z-wave doesn’t work, my wife will ream me for pushing for these changes (read: $$$)


That rant doesn’t need a reply, just had to get it off my chest.

To the actual discussion points: If you see in the photo linked in my last, there is a ton of WiFi devices right around it (I’ve got my router, switch, wired XB1, Sonos BOOST, Hue bridge, Smartthings, a printer off-screen, 2 mobile devices, and right behind the couch next to the desk) is my Sonos SUB. Other than that, its a Z-wave door sensor and the lock just 10ft away. Other than ST, does WiFi or any other protocol (Zigbee, Bluetooth, etc.) interfere with Z-wave?

I do consider this a range issue–I just interpret your answer as defining a solution for it as putting in more wired Z-wave devices. I just worry about signal strength, then, now. Do I need to have a z-wave recepticle in between every 10-15ft segment of my house? Will it not push to the second floor sensors (in the new home)? My intent is to use Z-wave for plug-in light recepticles, 4x door locks (3x on main floor, one right below the RPi 3 B+ in the basement), and the various window/door sensors. I am planning on using Lutron Caseta for the lights and possibly shades and/or fans (that was hard for me to give up control of but I don’t think Z-wave quite has it yet for lights, IMO and I don’t want to just use Hue bulbs).

Can anyone tell me what that log is telling me in the second code block of my last comment?

2018-06-15 04:55:34.643 Info, Node003, Response RTT 2611 Average Response RTT 2302
Response time from the lock (normal due to sleeping node)

2018-06-15 04:55:34.643 Info, Node003, Received Alarm report: type=25, level=1
2018-06-15 04:55:34.643 Detail, Node003, Refreshed Value: old value=24, new value=25, type=byte
2018-06-15 04:55:34.643 Detail, Node003, Changes to this value are not verified

Alarm type switched from 24 to 25, this is from the lock changing state from Zwave, physical turn, or entered code.

2018-06-15 04:55:34.643 Detail, Node003, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-06-15 04:55:34.643 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x78, 0xd9
2018-06-15 04:55:34.643 Detail, Node003, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2018-06-15 04:55:34.643 Detail, Node003, Queuing (Send) DoorLockCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x62, 0x02, 0x25, 0x79, 0xd8
2018-06-15 04:55:34.644 Detail, Node003, Refreshed Value: old value=1, new value=1, type=byte
2018-06-15 04:55:34.644 Detail, Node003, Changes to this value are not verified
2018-06-15 04:55:34.644 Detail, Node003, Notification: ValueChanged
2018-06-15 04:55:34.652 Detail, Node003, Notification: ValueChanged

Changing the “locked” state from 1 to 1, seems like it was out of sync, usually this is something like 0 to 1 or 1 to 0 for “locked/unlocked”

2018-06-15 04:55:42.032 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-06-15 04:55:42.032 Detail, Node003, Removing current message
2018-06-15 04:55:42.032 Detail, Node003, Notification: Notification - TimeOut

Zwave stack has lost connection to the node and Timed it out, this could be a command you sent to unlock or lock the door via Zwave or a configuration change.

Thanks @firstof9. That is likely what it is. It was just the block that failed and I didn’t see the unlock command in there.

I do suggest moving your radio away from others. Even tho they are on different frequencies they can cause noise. For example don’t place your zwave stick next to your wifi router/access point.

2 Likes

I / we have no idea what your layout looks like, how many and type of devices you have etc. Sadly, you can not timidly add Zwave devices and expect to have a failsafe network. You need a plan and that means starting with a hard look at what the Zwave signal may pass through and what other things may interfere with good reception. Strategically add devices or maneuver what you have.
I suffered “dead” issues with the first 2 or 3 devices in my home. Things got better as I added devices. Then there was a device, I called the magic device and my network became rock solid. In hindsight, I should have seen the hole and added the device sooner.
I am deeply sorry you are having issues. I will say that no matter which direction you might take, what technology you adopt, there will be issues. If you use WiFi because you already have it, you will find dead spots in your home or property. ZigBee has some of the same issues as Zwave and can sometimes be affected by WiFi. 433 same,etc etc. There will be problems and you will need to track down issues with all of them.
I started with X10 devices almost 25 years ago. If you want a platform that will drive you crazy tracking down connectivity issues, give that one a try.

1 Like

Have a similar story where my schlage connect locks were Rock solid on the smart things hub for 28 months, now with open zwave and the husbzb device, it seems they flake out every few days. I have 2 powered switches between the hub and the door so connectivity shouldn’t be an issue, and the door isnr that far away.

One thing though is my hub is pretty close to my wireless router, maybe I’ll try running a longer extension cable to get the USB device a bit further away.

I hit a similar problem this week where almost all of my powered zwave devices started showing up dead. I have ~20 devices (5 switches, 4 bulbs, 2 mirco-switches, 2 outdoor plugs, then several door/window and motion sensors). Using the Aeotec stick connected to RPi running Hass.io. This setup has been working fine for several months. Now, none of the switches/plugs work and only 1 bulb can be controlled with HA.

General distance from the controller shouldn’t be an issue. The zwave mesh has worked fine for months and the powered switches are spread out across the house.

The only changes I’ve had recently were adding a battery door-window sensor, moving to lovelace, and adding the synology camera platform. I can’t imagine that the issue is with lovelace or adding a platform in HA.

I tried adding a security key as suggested above, but that didn’t seem to help. I also tried adding another previously-paired plug (typically only use for Christmas lights) last night. HA detected it right away and I was able to turn it on/off. This morning it is showing up dead.

Could one actually dead device be bringing down the whole mesh? I’ve had some trouble with one of the micro-switches, but I believe that has more to do with the fan it is controlling.

Have you tried a heal network?

Thanks for the response. Yes, I’ve tried heal network, test network, stop/start. I tried to re-add one of the dead devices as mentioned earlier, but it just comes up dead.

Almost sounds like a bad device on your network or a device that needs a “reboot”, you could attempt to reset breakers on the devices connected to your mains power to see if that helps, aka turn it off and back on again.

I gave that a shot to no avail. After that I removed one of the micro switches that I thought could be the problem (removed failed node, then restarted everything). That didn’t help so I tried removing the plug and doing a full restore. Excluding, restore, then including again brought it back to life. Funny thing is after I did that, one of the dead light switches started responding again.

Unfortunately at this point I think I’m just going to have to start removing nodes and re-including them.

Well, I spoke too soon. A couple hours later and now the devices that were working are dead again.

Just coming back to this to say this was likely user error. I think I adjusted an automation after removing the dead switch. After correcting that everything has been working fine.

I randomly have this particular powered device show up as failed.

Power cycle the failed device > in Hassio Zwave > “Replace Failed Node” > On the device press the button combo to add the device (3 taps or press & hold depending on device) .
Viola!