I am thinking about adding a lock to my system (right now I am still on OpenHab 1.8). Specifically, I am looking at the Schlage BE369NX.
I’ve been searching around and I am having a hard time finding information if OpenHab connects to this or any locks.
Has anyone been able to bind to this lock or any others? Also any advice on a good lock to get would be very much appreciated. It needs to be controlled by the non-techies in the house, but also allow for a cleaning service to come in without needing a key.
Z-wave locks require the Security Command Class. There is some experimental support for it (see here) but it is not yet part of the main baseline and based on that thread they can be a little flakey when joining.
It will be added to the binding at some point in the near future but chris is stretched pretty thin I suspect so couldn’t begin to guess when.
The way people a lot of people include locks like this right now is though another hub, such as Vera and then integrating that hub with OH.
Personally, I have a couple of locks like these. It is pretty easy to create new codes for it and they automatically lock after 30 seconds. That coupled with door sensors means I know that if the door is closed I know it is locked. When I have house guests I can create a new code and then get rid of that code when they no longer need it. So far I’ve never encountered a situation where I wish I had the ability to unlock the door remotely so if I ever do include mine into the zwave network it will be strictly to get battery levels.
Based on some recent publications in the computer security press, I would recommend staying far far away from bluetooth and wifi enabled locks. These are currently incredibly insecure as implemented.
Thank you for the quick response, I really appreciate it. So if I understand you correctly, OpenHAB doesn’t yet have any compatibility with z-wave locks. If that right?
The only “hub” I have is an Aeotec Z-Wave USB Stick. So does that mean, for now, I can’t integrate any door locks? While opening and closing the locks would be an interesting thing, I am more interested in knowing the state of the lock and what code was entered to determine who opened the door.
Thank you again for the advice.
That is correct, there is no support in the main OH zwave bindings for locks. By “another hub” I mean something like a Vera or Wink Hub, not just a controller like your Aeotec.
I have had 6 Yale YRD-220s running on the patched 1.9 with security for a few months now without problems.
Thank you. I guess I’ll wait for now.
I’ll definitely look into that. Thank you for the information.
If I try the patched 1.9 binding in OH2, do you need to create a separate config file for it to enter your Zwave Network Key?
Assuming you also disabled any existing 2.0 binding, etc.
Since the patched 1.9 binding is not an “official” binding, I think you need to follow the directions for using the 1.x compatibility layer:
Just want to report that I did try the patched 1.9 binding with OH2 and get an error in the log of a Framework error.
2016-10-11 20:18:45.908 [ERROR] [org.openhab.binding.zwave ] - FrameworkEvent ERROR - org.openhab.binding.zwave
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave 
Unresolved requirement: Import-Package: gnu.io
In trying to troubleshoot that, I found this post to here
and ran the following in Karaf. feature:install openhab-transport-serial
After that, is appears in the log the Patched 1.9 binding started, but having some troubles with Habmin and Paper UI in seeing any devices. And the log also still shows
NODE 4: Invalid state! secure inclusion has not completed and we are not in inclusion mode, aborting
So, my guess is the Patched 1.9 binding is not working with OH2.
You need to manually handle the dependancies. In this case you need to add the serial package into the addons folder - this is the same as if it is running under OH1.
Ok, I manually added the serial binding to the addons folder and then enabled in the PaperUI and then also restarted OH2. But Habmin still does not see the ability to add the Zwave Controller. When looking in the log, I do see the controller and the nodes found. And node 4 would be the lock, but still shows the “Secure Inclusion Not Completed”
This is with a lock that is already securely included via OpenZwave. I can control the lock there. And setup the same network key in my Zwave.cfg file for OH2 in my services folder.
Not sure why Habmin would not want to see the controller though. Perhaps has to do with a being a patched 1.9 manually added binding?
Here’s a piece of the log file.
2016-10-12 13:49:24.544 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /ui
2016-10-12 13:49:24.811 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at /start
2016-10-12 13:49:24.936 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
2016-10-12 13:49:25.956 [INFO ] [ng.zwave.internal.ZWaveActiveBinding] - Update config, port = /dev/ttyACM0
2016-10-12 13:49:25.957 [INFO ] [ng.zwave.internal.ZWaveActiveBinding] - Update config, masterController = true
2016-10-12 13:49:25.998 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - Update networkKey
2016-10-12 13:49:26.087 [INFO ] [b.core.service.AbstractActiveService] - ZWave Refresh Service has been started
2016-10-12 13:49:26.106 [INFO ] [ve.internal.protocol.ZWaveController] - Starting Z-Wave controller
2016-10-12 13:49:26.107 [INFO ] [ve.internal.protocol.ZWaveController] - Z-Wave timeout is set to 5000ms. Soft reset is false.
2016-10-12 13:49:26.107 [INFO ] [ve.internal.protocol.ZWaveController] - Connecting to serial port /dev/ttyACM0
2016-10-12 13:49:26.619 [INFO ] [ve.internal.protocol.ZWaveController] - Serial port is initialized
2016-10-12 13:49:26.822 [INFO ] [binding.hue.handler.HueBridgeHandler] - Creating new user on Hue bridge 192.168.11.148 - please press the pairing button on the bridge.
2016-10-12 13:49:26.948 [INFO ] [ng.zwave.internal.ZWaveActiveBinding] - ZWave 'updated' with null config
2016-10-12 13:49:30.012 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 1: Node found
2016-10-12 13:49:30.014 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 3: Node found
2016-10-12 13:49:30.015 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 4: Node found
2016-10-12 13:49:30.016 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller using Controller API
2016-10-12 13:49:30.018 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller is Primary Controller
2016-10-12 13:49:30.018 [INFO ] [age.SerialApiGetInitDataMessageClass] - ------------Number of Nodes Found Registered to ZWave Controller------------
2016-10-12 13:49:30.020 [INFO ] [age.SerialApiGetInitDataMessageClass] - # Nodes = 3
2016-10-12 13:49:30.020 [INFO ] [age.SerialApiGetInitDataMessageClass] - ----------------------------------------------------------------------------
2016-10-12 13:49:30.302 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - NODE 4: setupNetworkKey useSchemeZero=false
2016-10-12 13:49:30.463 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 3: Unsupported command class SCENE_ACTUATOR_CONF
2016-10-12 13:49:32.230 [ERROR] [curityCommandClassWithInitialization] - NODE 4: Invalid state! secure inclusion has not completed and we are not in inclusion mode, aborting
2016-10-12 13:49:32.276 [INFO ] [nitialization.ZWaveNodeStageAdvancer] - NODE 3: does not support SECURITY_REPORT, proceeding to next stage.
It won’t - that’s an OH2 feature - you’re now running an OH1 binding.
So I think I did everything correct in trying out the patched 1.9 binding to test for the lock. No idea why I can’t get it work, but I’ll maybe try it all again a complete uninstall and reinstall of OH2 to the latest build. Perhaps