Z-wave (Schlage) Lock Support on OH1

I cant get the locks to sync… attached

zwave.log.xml (846.5 KB)

not really xml but I had to to upload them

Sorry for my tardy response, I dont have the inclusion log… where woudl that be ? I have logs going WAAAYYY back as I am splunking this as well … I just dont know where the log would reside… its not in /var/log/openhab

Hi @dbadia,

I have been testing the user code function (Yale lock) and it works well with 3 codes, after I add the 4th it seems like it doesn’t add it to the lock memory.

Also I have tried to add multiple user codes at once and the door lock memory doesn’t get updated ass well.

Do you have any pointers on this?

EDIT: If I add muptiple codes (in this test I added 5) only the last one worked…

I am using OH2 beta4. Z-wave binding shows that my Schlage deadbolt lock is on supported thing type list. Security key is already presetup (according to HABmin). However, after paring lock, HABmin still shows that device has not been fully discovered by binding.

I am just wondering is there is some special setup process that I am missing. Please, help!

Thanks,
Tadey

OH2 doesn’t support security at this time.

@chris
Thank you for clarifying that. I wasn’t sure after seeing zwave security code in binding settings of HABmin, and device in support list.

Is it on the horizon of to-do features, or something that not even possible to achieve?

Yes - it is high on the “todo” list. Hopefully I will look at this soon as other code I’ve been working on is looking like it’s nearly there (I hope! ;)).

Does anyone know where I can find the latest build of the Z-wave binding with security enabled? This thread is huge, and I couldn’t identify where I could get this. This still points to a version compiled 7 months ago.

Any assistance in getting the latest build that works with 1.8.3 would be greatly appreciated.

Give me a couple of days and I’ll merge this into the master branch.

3 Likes

I forgot to mention this, but the security classes were merged into the master in OH1 a few days back. Any feedback welcome…

Awesome! I’ll see if I can figure out how to get a working binary.

Just use the nightly snapshot version from cloudbees.

1 Like

Really great news about the merge Chris! I will give it a shot as I am prepping my house for holiday automation

@wificordon
I will look into this. I remember working a similar bug was fixed awhile back, not sure if I ever committed it

I got my Kwikset 910 paired, having issues with actual control. Logs make it seem like it is working. Will be messing with it more today.

I have an existing KwikSet 916 Zwave lock that I have previously paired with OZCP, and added that security key into my OH1 Binding zwave.cfg file.

Like Nolan above, it appears correct, but can’t get control of it. And I can control it if I turn off OH and use OZCP.

Here is some log info when using the 1.x binding in OH2 (with the 2.0 binding uninstalled of course)

2016-11-13 16:36:04.222 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
2016-11-13 16:36:04.228 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - Update networkKey
2016-11-13 16:36:04.236 [WARN ] [WaveSerialHandler$ZWaveReceiveThread] - Protocol error (OOF). Got 0x00.
2016-11-13 16:36:04.236 [WARN ] [WaveSerialHandler$ZWaveReceiveThread] - Protocol error (OOF). Got 0x11.
2016-11-13 16:36:04.237 [WARN ] [WaveSerialHandler$ZWaveReceiveThread] - Protocol error (OOF). Got 0x02.
2016-11-13 16:36:04.237 [WARN ] [WaveSerialHandler$ZWaveReceiveThread] - Protocol error (OOF). Got 0x84.
2016-11-13 16:36:04.291 [WARN ] [WaveSerialHandler$ZWaveReceiveThread] - Protocol error (OOF). Got 0x07.
2016-11-13 16:36:04.292 [WARN ] [WaveSerialHandler$ZWaveReceiveThread] - Protocol error (OOF). Got 0x63.
2016-11-13 16:36:04.481 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2016-11-13 16:36:04.481 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2016-11-13 16:36:08.117 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 1: Node found
2016-11-13 16:36:08.123 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 2: Node found
2016-11-13 16:36:08.123 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 3: Node found
2016-11-13 16:36:08.123 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 4: Node found
2016-11-13 16:36:08.123 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 5: Node found
2016-11-13 16:36:08.124 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 6: Node found
2016-11-13 16:36:08.124 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 7: Node found
2016-11-13 16:36:08.124 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 8: Node found
2016-11-13 16:36:08.124 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 9: Node found
2016-11-13 16:36:08.124 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 10: Node found
2016-11-13 16:36:08.124 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 11: Node found
2016-11-13 16:36:08.125 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 12: Node found
2016-11-13 16:36:08.125 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 13: Node found
2016-11-13 16:36:08.125 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 14: Node found
2016-11-13 16:36:08.125 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 15: Node found
2016-11-13 16:36:08.125 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 16: Node found
2016-11-13 16:36:08.125 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 17: Node found
2016-11-13 16:36:08.126 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller using Controller API
2016-11-13 16:36:08.126 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller is Primary Controller
2016-11-13 16:36:08.126 [INFO ] [age.SerialApiGetInitDataMessageClass] - ------------Number of Nodes Found Registered to ZWave Controller------------
2016-11-13 16:36:08.126 [INFO ] [age.SerialApiGetInitDataMessageClass] - # Nodes = 17
2016-11-13 16:36:08.126 [INFO ] [age.SerialApiGetInitDataMessageClass] - ----------------------------------------------------------------------------
2016-11-13 16:36:08.235 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Initialising Thing Node...
2016-11-13 16:36:08.235 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Initialising Thing Node...
2016-11-13 16:36:08.235 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 14: Initialising Thing Node...
2016-11-13 16:36:08.235 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Initialising Thing Node...
2016-11-13 16:36:08.235 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Initialising Thing Node...
2016-11-13 16:36:08.276 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Initialising Thing Node...
2016-11-13 16:36:08.277 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 16: Initialising Thing Node...
2016-11-13 16:36:08.278 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 17: Initialising Thing Node...
2016-11-13 16:36:08.283 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising Thing Node...
2016-11-13 16:36:08.284 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Initialising Thing Node...
2016-11-13 16:36:08.284 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising Thing Node...
2016-11-13 16:36:08.284 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising Thing Node...
2016-11-13 16:36:08.285 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising Thing Node...
2016-11-13 16:36:08.286 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Initialising Thing Node...
2016-11-13 16:36:08.284 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Initialising Thing Node...
2016-11-13 16:36:08.291 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Initialising Thing Node...
2016-11-13 16:36:08.936 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Device discovery could not resolve to a thingType! 001D:1001:0334::0.7
2016-11-13 16:36:09.093 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - NODE 2: setupNetworkKey useSchemeZero=false
2016-11-13 16:36:09.222 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - NODE 2: setupNetworkKey useSchemeZero=false

And then further below trying to control it

2016-11-13 17:16:15.892 [DEBUG] [l.ZWaveController$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
2016-11-13 17:16:15.895 [DEBUG] [l.ZWaveController$ZWaveReceiveThread] - Receive queue ADD: Length=1
2016-11-13 17:16:15.895 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-11-13 17:16:15.895 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
2016-11-13 17:16:15.895 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
2016-11-13 17:16:15.895 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class = SendData (0x13), type = Response (0x01), payload = 01 , callbackid = 0
2016-11-13 17:16:15.895 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: Sent Data successfully placed on stack.
2016-11-13 17:16:17.300 [DEBUG] [l.ZWaveController$ZWaveReceiveThread] - Receive Message = 01 07 00 13 3D 00 00 8D 5B 
2016-11-13 17:16:17.304 [DEBUG] [l.ZWaveController$ZWaveReceiveThread] - Receive queue ADD: Length=1
2016-11-13 17:16:17.304 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-11-13 17:16:17.304 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 3D 00 00 8D 00 00 55 
2016-11-13 17:16:17.304 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 3D 00 00 8D 00 00 55 
2016-11-13 17:16:17.304 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class = SendData (0x13), type = Request (0x00), payload = 3D 00 00 8D , callbackid = 0
2016-11-13 17:16:17.304 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: SendData Request. CallBack ID = 61, Status = Transmission complete and ACK received(0)
2016-11-13 17:16:17.304 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 02 02 62 02 , callbackid = 61
2016-11-13 17:16:17.304 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Recv message Message: class = SendData (0x13), type = Request (0x00), payload = 3D 00 00 8D , callbackid = 0
2016-11-13 17:16:17.304 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 02 02 62 02 , callbackid = 61
2016-11-13 17:16:17.304 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv message Message: class = SendData (0x13), type = Request (0x00), payload = 3D 00 00 8D , callbackid = 0
2016-11-13 17:16:17.305 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=61, expected=ApplicationCommandHandler, cancelled=false      mismatch

I got my 910 working, but can’t get my 916 working. Logs here. Nodes 95-100 are all attempts.

Got the 916’s working as well. The trick? Just keep trying and keep the lock assembly as close to the z-wave controller as possible. Touching might not be close enough, you may need to touch them together at the right point. Don’t be discouraged - it took me 14 attempts to successfully pair 2 916 locks.

@wificordon @Nicholas_Waterton

The user code issue (only last being applied) has been fixed in this PR

That’s interesting that you got them working. That is with OH2 and the 1.9 binding? My 916 is actually already secured paired to the controller being done with open zwave control panel. And I can control and lock/unlock the door using open zwave control panel as well. All I need (or should need to do) to use with OpenHab is add the network key to the 1.9 binding zwave.cfg file which I did do but could not control the door.

I can give it another try later tonight. But I should not actually need to remove and reinclude the device, although I can give that a try as well.