Paired Schlage lock won't lock

Configuration Z-Wave
11

Here’s the log of what happens after I unlock the door from ozwcp, which does in fact unlock it:

post: key=8-DOOR LOCK-user-bool-1-0 data=false size=5
2016-07-30 04:22:21.776 Info, Node008, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - False
2016-07-30 04:22:21.776 Info, Node008, Value_Lock::Set - Requesting lock to be Unlocked
2016-07-30 04:22:21.776 Detail, Node008, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2016-07-30 04:22:21.776 Detail, Node008, Queuing (Send) DoorLockCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x62, 0x01, 0x00, 0x25, 0x3a, 0x91
2016-07-30 04:22:21.776 Detail, Node008, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2016-07-30 04:22:21.776 Detail, Node008, Queuing (Send) DoorLockCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x62, 0x02, 0x25, 0x3b, 0x91
2016-07-30 04:22:21.777 Detail, 
2016-07-30 04:22:21.777 Info, Node008, Processing (Send) Nonce Request message (Callback ID=0x3a, Expected Reply=0x04)
2016-07-30 04:22:21.777 Info, Node008, Sending (Send) message (Callback ID=0x3a, Expected Reply=0x04) - Nonce_Get(DoorLockCmd_Set) - 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x98, 0x40, 0x05, 0x02:
2016-07-30 04:22:21.784 Detail, Node008,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-07-30 04:22:21.784 Detail, Node008,   ZW_SEND_DATA delivered to Z-Wave stack
2016-07-30 04:22:23.182 Detail, Node008,   Received: 0x01, 0x07, 0x00, 0x13, 0x02, 0x00, 0x00, 0x8c, 0x65
2016-07-30 04:22:23.183 Detail, Node008,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2016-07-30 04:22:23.183 Info, Node008, Request RTT 1406 Average Request RTT 1604
2016-07-30 04:22:23.235 Detail, Node008,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x08, 0x0a, 0x98, 0x80, 0xed, 0xd4, 0xfc, 0xa5, 0x6d, 0xd1, 0x21, 0xc9, 0xc5
2016-07-30 04:22:23.235 Info, Node008, Received SecurityCmd_NonceReport from node 8
2016-07-30 04:22:23.236 Info, Node008, Sending (Send) message (Callback ID=0x3c, Expected Reply=0x04) - DoorLockCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x62, 0x01, 0x00, 0x25, 0x3c, 0x97
2016-07-30 04:22:23.248 Detail, Node008,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-07-30 04:22:23.248 Detail, Node008,   ZW_SEND_DATA delivered to Z-Wave stack
2016-07-30 04:22:23.371 Detail, Node008,   Received: 0x01, 0x07, 0x00, 0x13, 0x3c, 0x00, 0x00, 0x0d, 0xda
2016-07-30 04:22:23.371 Detail, Node008,   ZW_SEND_DATA Request with callback ID 0x3c received (expected 0x3c)
2016-07-30 04:22:23.371 Info, Node008, Request RTT 1595 Average Request RTT 1599
2016-07-30 04:22:23.371 Detail,   Expected callbackId was received
12

When I boot up HA, the correct STATE is actually showing for the lock. I just don’t get why I can control it with ozwcp, but when I try with HA, I get timeout errors. I would think that if it was a range issue, both would be affected, no?

13

Check the options.xml in the directory you have specified in your configuration.yaml for zwave. I think maybe you have a different direction than ozwcp is using, and it’s missing the neywork key.

14

Also try to delete the zwcfg.xml in homeassistant directory and let it rebuild. May take a couple of restarts to do that.

15

OH!! Yeah, that was it. It wasn’t linked to the right place so the network key wasn’t there. Boom!

Ok, so now it’s locking/unlocking. There’s just a couple issues:

  1. When I toggle the switch, it will actually switch back to its initial state, then the lock will lock, and then the switch will toggle to its correct new state. This may just be an HA kind of bug though as I’ve seen this happen with some other type of switches.
  2. I use my pi HA install as a slave in a master/slave setup. When I do this, my aetoc multisensor shows up just fine on my main HA. But the new lock does not show up. I’ve seen this with the recently added rf switch component as well so I’m not sure what’s up with that.

Thanks for your help on this!

16

Regarding no.1 this is just latency of the zwave network. It normally gets better after about 10 minutes when the network has settled.

17

OK cool, yeah i’ve seen wackyness with my sensor like this before. This is why I set this up on a pi, so i didn’t have to start my zwave network over and over while I was doing customizations and new automations for my HA setup. Though the way master/slave works, I have to actually still do this because you have to reboot the slave if you reboot the master :frowning:

Speaking of, and #2, I just noticed that none of my zwave stuff is showing up in my master now, so something else funky is going on separate from the issues in this thread.

18

Sorry for reviving this thread, but I seem to be having some of the same problems as you had. Mind looking at my thread (starting around line 12) and seeing if you can find any similarities? Thanks!

20

Hello All,

Thanks to the discussion here, I am happy to report that I was able to lock and unlock my door from HASS. I also have a full set of features that came with the Schlage Connect, like Alarm levels and more… see pictures below:

Thank you!!

21

Can you help me understand what you did to fix this issue? What directory did you point your configuration.yaml file to? I have the options.xml with the key inside but HA doesn’t work. Thank you!

22

If your lock is paired right now, unpair it (called unenroll in the manual, page 13). Then do a factory reset on the lock (manual page 12). Then fire the Home Assistant service “add_node_secure”. Then enroll the lock.

23

Thank you for your suggestion. I decided to remove the device using the open z wave control panel then added it securely. Seemed that the issue was that I wasn’t able to add it securely without first removing it from the control panel. Very odd.

24

Just wanted to confirm here that I successfully connected the Schlage Connect lock (also known as BE469WK) and am now using it in hass. If you already have securely connected a z-wave device (I had connected the linear garage door opener securely), you do NOT (more accurately, I did not, though you probably should not need to either) need to add the network key to the zwcfg file (as explained here, which is what you should do if connecting a secure device for the first time).

All you need to do is be relatively close (my lock is about 10 yards away from the controller), use “Add Node (Secure)” in ozwcp, go to the lock and enter your 6-digit programming code followed by ‘0’ (note that this is for the Schlage Connect – the pairing protocol may be different for another lock and Schlage’s web site will have info on how to put the lock into pairing mode). After it pairs, save the zwcfg file on the ozwcp page (top right), then after exiting, copy the zwcfg… file in your ozwcp directory to your ~/.homeassistant directory, and you will now have a “lock. …” item in hass.

As turbokongen said above, there was a fair amount of latency at first with ALL z-wave devices. But after a minute or two, it is back to normal (for example, on the first try to lock/unlock from hass, it took a good 15 seconds to work, and my z-wave activated lights were about 5 seconds late–but then after a minute or two, it was all back to being near-instantaneous).

1 Like
25

Do you still have questions about this? I am currently testing two approaches for the locks: one using HASS with the z-USB Stick and the other using Wink. I have two locks working using both instances:

With Wink you have more functionality out of the box, like the ability to add and remove users and assign temporary access codes, also it shows your battery levels and it can alert you, if you are running low, etc.
Using the z-stick you can lock and unlock from HASS and create alerts when the lock changes its status and that’s pretty much it. To add the Lock I paired it ( Programming Code + 0) and from HASS. I used the option to add a secure node, I also manually created the key and added it to the options.xml file and copied to the directory where the z-wave is installed: config_path: /srv/hass/hass_venv/lib/python3.4/site-packages/libopenzwave-0.3.1-py3.4-linux-armv7l.egg/config.
Hope this helps!

1 Like
26

following. I am currently having the same issue where the lock shows up but there is no control. I am having issues accessing my OZWCP though so I am going to do a fresh install and then circle back to lock pairing procedure.

27

if i am adding my lock using the latest version of HA with the Zwave utility built in…

should i still need to use openzwave ?

i have my network key in the configurations.yaml file.

i currently also get all the status messages but no control on the lock…

Thanks,

28

I never got my lock to pair succesfully with OZWCP - it would report status but not lock/unlock.

When we got the full ZWave support, I added a security key in my HASS config, unpaired the lock, and repaired with Secure Add and it worked like a dream, first time.

29

thanks, so i cant see how to secure add… maybe i am missing something…

but i did have a Key in my configs removed the lock and re-added…

30

It’s under the ZWave panel:

682×734 27.9 KB

31

interesting idont have add node secure… should i have enabled it somewhere?