Paired Schlage lock won't lock

Configuration Z-Wave
1

I just installed a Schlage Connect (omg no more keyyyyyyyys!) and am trying to get it set up with HA.

I’m using an Aeon stick with open zwave and HA. I paired it with the stick via the normal way: by bringing the stick over to the lock, pressing the button on it to go into pairing mode and then putting the lock into pairing mode. It paired right away.

I plugged the stick back into my raspberry pi, rebooted it, and then checked HA. HA shows the lock. But when I try to command it to lock, nothing happens. The toggle goes to “on” and then switches back to “off”.

I tried to play with it with Open Zwave Control Panel. I tried to make it lock, and it didn’t do anything. I did see this in the logs:

2016-07-29 03:59:47.283 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)

I understand that there’s another way to pair this lock with OZW, but you have to do it securely. It seems really really involved, so before I went down that road I was hoping there might be something I’m missing or an easier way to do this.

So is anyone else using the Schlage lock like I am? How’d you get it set up? Any help would be awesome, thanks!

2

I have had a similar experience with a Kwikset lock and running HA + Zstick on ubuntu 14.04.

As you say, you have to pair the lock securely. What I ended up doing was an instance of Domoticz as it comes with the OZW Control Panel. Domotics seemed a lot easier to install then trying to do the OZWCP by itself. I then shutdown HA, fired up Domoticz, added the Z-stick. Under node management or the OZWCP, I was able to do a Add Node (Secure), pair the lock and Vola! Once I verified that I lock/unlock the lock from the control panel, I shutdown domoticz and started HA. Lock was found after a few minutes, and I was able to issue a lock and unlock from HA successfully.

Just make sure to set the same network key in the options.xml for both the openzwave configurations. IE the one that is installed by domoticz and the one used by HA if they are separate instances.

Now my problem is range…

1 Like
3

OK, I think I got it paired securely with open zwave control panel. I followed the instructions in their repo and added a network key and the pairing gave me back a device with significantly more information and settings. I used these instructions.

But I still can’t seem to control/lock the lock.

Here are the zwave logs when I try to lock the lock with HA:

INFO:homeassistant.core:Bus:Handling <Event call_service[L]: domain=lock, service_data=entity_id=lock.schlage_unknown_type6349_id5044_locked_7, service_call_id=1980941712-2, service=lock>
2016-07-29 16:07:56.844 Info, Node007, Value::Set - COMMAND_CLASS_DOOR_LOCK - Locked - 0 - 1 - True
2016-07-29 16:07:56.844 Info, Node007, Value_Lock::Set - Requesting lock to be Locked
2016-07-29 16:07:56.844 Detail, Node007, Queuing (Send) DoorLockCmd_Set (Node=7): 0x01, 0x0a, 0x00, 0x13, 0x07, 0x03, 0x62, 0x01, 0xff, 0x25, 0x23, 0x78
2016-07-29 16:07:56.844 Detail, Node007, Queuing (Send) DoorLockCmd_Get (Node=7): 0x01, 0x09, 0x00, 0x13, 0x07, 0x02, 0x62, 0x02, 0x25, 0x24, 0x81
2016-07-29 16:07:56.844 Detail, 
2016-07-29 16:07:56.845 Info, Node007, Sending (Send) message (Callback ID=0x23, Expected Reply=0x04) - DoorLockCmd_Set (Node=7): 0x01, 0x0a, 0x00, 0x13, 0x07, 0x03, 0x62, 0x01, 0xff, 0x25, 0x23, 0x78
INFO:homeassistant.core:Bus:Handling <Event service_executed[L]: service_call_id=1980941712-2>
2016-07-29 16:07:56.853 Detail, Node007,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-07-29 16:07:56.853 Detail, Node007,   ZW_SEND_DATA delivered to Z-Wave stack
2016-07-29 16:07:58.101 Detail, Node007,   Received: 0x01, 0x07, 0x00, 0x13, 0x23, 0x00, 0x00, 0x7e, 0xb6
2016-07-29 16:07:58.101 Detail, Node007,   ZW_SEND_DATA Request with callback ID 0x23 received (expected 0x23)
2016-07-29 16:07:58.101 Info, Node007, Request RTT 1257 Average Request RTT 1257
2016-07-29 16:07:58.101 Detail,   Expected callbackId was received
2016-07-29 16:08:06.845 Error, Node007, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-07-29 16:08:06.845 Detail, Node007, Removing current message
2016-07-29 16:08:06.845 Detail, Node007, Notification: Notification - TimeOut
4

There could be two things:

  1. Range
  2. Since you have tried adding it before, you should unpair the lock, and do a hard reset of the lock. The manual will tell you how. Then secure add it through ozwcp and test lock and unlock in ozwcp. Still the same, then it’s no.1.
5

Ok. I got it working in ozwcp. I rebuilt both python-openzwave and ozwcp and could finally lock/unlock it. I was able to rename it too.

I saved the config and moved it to my home assistant config. I restarted HA and the new name appeared as well as all the extra sensors, success!!

But, when I tried to lock it, it failed. I got the same error.

ERROR: Dropping command, expected response not received after 1 attempt

It worked under ozwcp, why isn’t it working in HA? I’ll look at what my range is. But it’s honestly not that far. The zstick is in the kitchen which is like 4 steps away from the front door.

6

If i have it working in ozwcp like described, would doing a full reset still be something I might need to do? It seems like it’s working correctly, it’s just being funny.

7

If it works in ozwcp it should work in ha too. Let me have a look at your zwcfg.

8

Do you have a snippet from ozw.log too when doing lock from ozwcp?

9

zwcfg: https://gist.github.com/maddox/d2d04c7a8557dc64f3745d4c21323c62

2016-07-29 17:25:18.751 Info, Node008, Value_Lock::Set - Requesting lock to be Unlocked
2016-07-29 17:25:18.751 Detail, Node008, Queuing (Send) DoorLockCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x62, 0x01, 0x00, 0x25, 0x2b, 0x80
2016-07-29 17:25:18.752 Detail, Node008, Queuing (Send) DoorLockCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x62, 0x02, 0x25, 0x2c, 0x86
2016-07-29 17:25:18.752 Detail, 
2016-07-29 17:25:18.752 Info, Node008, Sending (Send) message (Callback ID=0x2b, Expected Reply=0x04) - DoorLockCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x62, 0x01, 0x00, 0x25, 0x2b, 0x80
INFO:homeassistant.core:Bus:Handling <Event service_executed[L]: service_call_id=1981379984-3>
2016-07-29 17:25:18.761 Detail, Node008,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-07-29 17:25:18.761 Detail, Node008,   ZW_SEND_DATA delivered to Z-Wave stack
2016-07-29 17:25:20.107 Detail, Node008,   Received: 0x01, 0x07, 0x00, 0x13, 0x2b, 0x00, 0x00, 0x87, 0x47
2016-07-29 17:25:20.108 Detail, Node008,   ZW_SEND_DATA Request with callback ID 0x2b received (expected 0x2b)
2016-07-29 17:25:20.108 Info, Node008, Request RTT 1356 Average Request RTT 1416
2016-07-29 17:25:20.108 Detail,   Expected callbackId was received
INFO:homeassistant.components.http:Successful login/request from 192.168.1.179
INFO:homeassistant.components.http:Successful login/request from 192.168.1.179
INFO:homeassistant.components.http:Successful login/request from 192.168.1.179
2016-07-29 17:25:28.752 Error, Node008, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-07-29 17:25:28.752 Detail, Node008, Removing current message
2016-07-29 17:25:28.753 Detail, Node008, Notification: Notification - TimeOut

SIGNAL ***** Notification

2016-07-29 17:25:28.754 Detail, 
2016-07-29 17:25:28.754 Info, Node008, Sending (Send) message (Callback ID=0x2c, Expected Reply=0x04) - DoorLockCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x62, 0x02, 0x25, 0x2c, 0x86
2016-07-29 17:25:28.762 Detail, Node008,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-07-29 17:25:28.763 Detail, Node008,   ZW_SEND_DATA delivered to Z-Wave stack
2016-07-29 17:25:30.160 Detail, Node008,   Received: 0x01, 0x07, 0x00, 0x13, 0x2c, 0x00, 0x00, 0x8d, 0x4a
2016-07-29 17:25:30.161 Detail, Node008,   ZW_SEND_DATA Request with callback ID 0x2c received (expected 0x2c)
2016-07-29 17:25:30.161 Info, Node008, Request RTT 1407 Average Request RTT 1411
2016-07-29 17:25:30.161 Detail,   Expected callbackId was received
2016-07-29 17:25:36.297 Detail, Node003,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x03, 0x06, 0x31, 0x05, 0x01, 0x2a, 0x03, 0x02, 0xec
2016-07-29 17:25:36.297 Detail,
10

Your zwcfg looks good. That ozw.log snippet is from trying to lock from HASS not ozwcp. Could you post that too?

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!