Assa Abloy Yale Assure YRD426 Z-wave No Control

Aussybob · December 8, 2018, 9:46am

have been trying to add the lock to HASS for the past couple of hours and I can see sensors and lock but no control or status. Connecting to a Aeotec USB Z-wave Gen 5 controller.

Followed the add secure node with Network Key, tried add/ remove multiple retarts but no joy.

The UI shows 2 sensors and 1 lock line.

The info stats look good…

When I press the “lock” this is the OWZ log

2018-12-08 20:41:04.976 Info, Node026, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - True
2018-12-08 20:41:04.976 Info, Node026, Value_Lock::Set - Requesting lock to be Locked
2018-12-08 20:41:04.976 Detail, Node026, Queuing (Send) DoorLockCmd_Set (Node=26): 0x01, 0x0a, 0x00, 0x13, 0x1a, 0x03, 0x62, 0x01, 0xff, 0x25, 0xaa, 0xec
2018-12-08 20:41:04.976 Detail, Node026, Queuing (Send) DoorLockCmd_Get (Node=26): 0x01, 0x09, 0x00, 0x13, 0x1a, 0x02, 0x62, 0x02, 0x25, 0xab, 0x13
2018-12-08 20:41:04.976 Detail,
2018-12-08 20:41:04.976 Info, Node026, Sending (Send) message (Callback ID=0xaa, Expected Reply=0x04) - DoorLockCmd_Set (Node=26): 0x01, 0x0a, 0x00, 0x13, 0x1a, 0x03, 0x62, 0x01, 0xff, 0x25, 0xaa, 0xec
2018-12-08 20:41:04.986 Detail, Node026, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-12-08 20:41:04.986 Detail, Node026, ZW_SEND_DATA delivered to Z-Wave stack
2018-12-08 20:41:06.268 Detail, Node026, Received: 0x01, 0x07, 0x00, 0x13, 0xaa, 0x00, 0x00, 0x81, 0xc0
2018-12-08 20:41:06.268 Detail, Node026, ZW_SEND_DATA Request with callback ID 0xaa received (expected 0xaa)
2018-12-08 20:41:06.268 Info, Node026, Request RTT 1292 Average Request RTT 1283
2018-12-08 20:41:06.268 Detail, Expected callbackId was received
2018-12-08 20:41:14.976 Error, Node026, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-12-08 20:41:14.976 Detail, Node026, Removing current message
2018-12-08 20:41:14.976 Detail, Node026, Notification: Notification - TimeOut
2018-12-08 20:41:14.978 Detail,
2018-12-08 20:41:14.979 Info, Node026, Sending (Send) message (Callback ID=0xab, Expected Reply=0x04) - DoorLockCmd_Get (Node=26): 0x01, 0x09, 0x00, 0x13, 0x1a, 0x02, 0x62, 0x02, 0x25, 0xab, 0x13
2018-12-08 20:41:14.988 Detail, Node026, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-12-08 20:41:14.988 Detail, Node026, ZW_SEND_DATA delivered to Z-Wave stack
2018-12-08 20:41:16.253 Detail, Node026, Received: 0x01, 0x07, 0x00, 0x13, 0xab, 0x00, 0x00, 0x80, 0xc0
2018-12-08 20:41:16.253 Detail, Node026, ZW_SEND_DATA Request with callback ID 0xab received (expected 0xab)
2018-12-08 20:41:16.253 Info, Node026, Request RTT 1275 Average Request RTT 1279
2018-12-08 20:41:16.253 Detail, Expected callbackId was received
2018-12-08 20:41:24.978 Error, Node026, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-12-08 20:41:24.979 Detail, Node026, Removing current message
2018-12-08 20:41:24.979 Detail, Node026, Notification: Notification - TimeOut

I’m thinking maybe its a Z-Wave support (lack off ) issue, maybe.

Never added a secure z-wave node, any help appreciated.

Anyone else have this model working?

Aussybob · December 10, 2018, 9:38am

I have noticed that the zwave product id in HASS is appearing as YRD446 but the actual device is a YRD426. Don’t know whether this would be a problem.

I have trawling through the forums and google tonight and there seem to be a lot of mixed reports about Yale locks in particular the zwave integration. Looks like a lot of people have been experiencing similar problems but no-one had a definative fix, more of a fluke…

Aussybob · December 12, 2018, 8:10am

I have solved this… well maybe not ideal but I have a working lock with status.

For anyone else having similar issues, this was my process (after much-trawling forums and thanks to a HASS forum member for giving the clue, sorry can’t remember the name or post because of pc reboots )

ensure to exclude the lock from hass zwave network and stop network
Insert the USB Zwave stick to a PC and run up Domoticz YEP (massive shoutout to those folks!!!)
go to hardware settings and add the usb stick (mine was com7) and copy the network_key from hass to the security section. wait for the system to pick up all the nodes.
Use the add secure node and follow the procedure for the lock, when complete you should get a bunch of entities pop up. I tested it from here and the lock was functioning! the stats were also working.
shutdown domoticz remove the usb stick and return to HASS machine and start network. after a few minutes the states should pop up in the HASS UI but to get everything up I done a restart and hey presto everything was working perfectly!

Pretty happy it’s working… but not happy about the process to get there. I don’t know if this is a bug but I know a lot of people have been having similar issues with the Yale locks, so I hope this helps someone.

Zed · September 5, 2019, 12:17pm

Aussybob

I signed up an account just to say thanks!! I love you!

i spent 3 days googling finally stumbled on your link, and it finally works.
I have a different lock, the vision deadbolt zm1701, but the exact solution worked well
i think it must be the z-stick not retaining the security code i set in hassio

Thanks!!

Aussybob · September 9, 2019, 9:32am

@Zed Glad to hear it helped someone! shame something that should be simple can get so complicated.
Welcome to the community.

rasputin · September 19, 2019, 3:55am

How do I remove the lock from the network? I’m trying to do it from the lock but it basically errors. I go back into the zwave control on the lock and it still only provides the ‘leave network’ option.

Aussybob · September 19, 2019, 11:50pm

depends on the zwave controller and the lock… you need to find the instructions from the respective manufacturers and follow them. last time I removed a device I used the Zwave network management tool from HA and pressed the action button on the device.

rasputin · September 21, 2019, 5:35am

I have Domoticz setup and I can add my locks to the network but communication seems to go dead after that.

@Aussybob - What config do you have for your locks?

rasputin · September 22, 2019, 12:34am

OWZ logs - you can see the lock is very quickly added and then unreachable. At least thats what I see

gist.github.com

https://gist.github.com/mattkime/77ea42384f012010afe658de3e5bc776

gistfile1.txt

2019-09-22 01:30:00.881 Detail,   Received: 0x01, 0x07, 0x00, 0x4a, 0x22, 0x02, 0x00, 0x00, 0x92
2019-09-22 01:30:00.881 Detail,
2019-09-22 01:30:00.881 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2019-09-22 01:30:00.881 Info, ADD_NODE_STATUS_NODE_FOUND
2019-09-22 01:30:00.881 Detail, Notification: ControllerCommand - InProgress
2019-09-22 01:30:01.062 Detail,   Received: 0x01, 0x10, 0x00, 0x4a, 0x22, 0x03, 0x23, 0x09, 0x04, 0x40, 0x03, 0x5e, 0x72, 0x98, 0x5a, 0x73, 0x86, 0xf2
2019-09-22 01:30:01.063 Detail,
2019-09-22 01:30:01.063 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2019-09-22 01:30:01.063 Info, ADD_NODE_STATUS_ADDING_SLAVE
2019-09-22 01:30:01.063 Info, Adding node ID 35 - Secure

This file has been truncated. show original

I see a few errors in there but I’m uncertain which ones are meaningful

rasputin · September 22, 2019, 5:07am

This looks like some progress but I can’t open or close the locks remotely or view feedback regarding lock status.

Aussybob · September 22, 2019, 12:05pm

looks like the security key is incorrect… could you control the lock from Domoticz?

rasputin · September 22, 2019, 3:06pm

could you control the lock from Domoticz?

Nope, although Domoticz shows the security key correctly set on the usb controller.

How could the security code be ‘wrong’? I thought it was a randomly generated number on the controller.

rasputin · September 22, 2019, 7:46pm

Which version of ozw are you running?

Aussybob · September 22, 2019, 11:11pm

OpenZwave Version 1.4.3440. but doubt this would be an issue.

You need to define a security key, have you read this?

Security key needs to be defined in your configuration.yaml file

rasputin · September 23, 2019, 12:28am

network_key is definitely in place.

rasputin · September 23, 2019, 1:55am

I wonder what other config bits we can pick at. perhaps that ozw xml cache? have anything related to your lock in there?

rasputin · September 23, 2019, 2:45am

Oooooh - I figured it out! I needed to enable the network key in options.xml

I’m sure I’ll have more questions about getting this set up. I need to improve the user interface in HASS and would like to have a way to manage keys.

What sort of interface do you have configured?

BigBri41 · November 1, 2020, 5:52pm

I was having trouble getting my Yale locks communicating with my installation also. I’m using an Aeotec Z-Stick Gen5 and a Raspberry Pi 4. I have two YRD220 locks and one YRD210 lock. They would connect to the network fine, but would sit there saying initializing. They also made the rest of the Z-wave network unresponsive. I tried adding a network key in the options.yaml file and that didn’t resolve the problem. When I added the network key in the zwave section of configuration.yaml (following this documentation https://www.home-assistant.io/docs/z-wave/installation/) and rebooted, everything started working though. I used the “add secure node” option in the zwave panel in Home Assistant.

Aussybob · November 2, 2020, 12:23am

Hey @BigBri41
Welcome mate.
Hope you solved your issue.
BTW my Yale lock has been rock solid i would recommend them.
It is easily the most used smart device.