Unresponsive z-wave Yale lock

[peterclark (peter)]

I am running Home Assistant on a Docker server alongside openzwave and mqtt (all as distinct docker instances) — I am using a HUS-BZB-1 USB stick.

I get incredibly intermittent interactions from my new Yale Zwave lock:

Sometimes it will lose the name of the device (sometimes it just says a weird manufacturers name) and other times it just gets reported as “dead”

Even when it is correctly identified, I am unable to actually lock or unlock the device. Nothing happens when I press the button. I am wondering if maybe this is because of the network key? Although I added one on both integrations and get same behaviour…

I get the exact same behaviour regardless of if i am running the open zwave beta integration or the regular home assistant behaviour. I have tried healing the network and added/removed the device about a dozen times.

i am wondering what could cause this? my only theory is signal strength, but I am not sure how to test that?

[tmjpugh]

I use open zwave in HA and it provides a sent failed/rcvd count for each zwave device in developer tools>>states. Lots of failed messages has been a pretty good indicator of signal issues for me in the past.

[chemgeek (Brian)]

I had issues with two of the Yale locks you have. The secure connection doesn’t seem to like to pass through a repeater. I tried to even secure connect a few repeaters to no avail. I ended up just putting an old SmartThings hub near the locks and connecting to them without a zwave repeater. Yes, it goes through the cloud that way, but has worked really well.

[peterclark (peter)]

hmm. I have tried with and without repeaters. this is what the z-wave logs say in home assistant, and i get same thing with openzwave beta:

2020-12-02 01:31:19.194 Info, Node007, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - True
2020-12-02 01:31:19.194 Info, Node007, Value_Lock::Set - Requesting lock to be Locked
2020-12-02 01:31:19.194 Detail, Node007, Queuing (Send) DoorLockCmd_Set (Node=7): 0x01, 0x0a, 0x00, 0x13, 0x07, 0x03, 0x62, 0x01, 0xff, 0x25, 0x3f, 0x64
2020-12-02 01:31:19.194 Detail, Node007, Queuing (Send) DoorLockCmd_Get (Node=7): 0x01, 0x09, 0x00, 0x13, 0x07, 0x02, 0x62, 0x02, 0x25, 0x40, 0xe5
2020-12-02 01:31:19.194 Error, Node007, ERROR: Dropping command because node is presumed dead
2020-12-02 01:31:19.194 Detail, Node007, Removing current message
2020-12-02 01:31:19.194 Error, Node007, ERROR: Dropping command because node is presumed dead
2020-12-02 01:31:19.194 Detail, Node007, Removing current message