If there was a lock_status channel in the past, I don’t know what it is as it doesn’t exist (and I think has never existed) in the code .
My Yale lock doesn’t send an update to the lock status when the door changes state which I agree is really anoying. It sends an alarm message which can be used to provide a status somewhere, but it probably can’t easily be linked to the door_lock channel.
If your device is sending a status update, then please let me know what it is and I’ll take a look.
I guess you can do the same thing in OH2 - this is the same channel that you should have now (ie door_lock). It should be the same - if the device provides the information through an association etc, then it will update - if not, you need to use polling - same as OH1.
Well we need to capture the polling of this device. This will happen during initialisation, or you could increase the polling and just grab another time which is likely to be easier (eg set the polling the 20 seconds, and then grab a minute from the log and it should be there).
I’m hoping someone can provide a summary of the latest status on Z-wave locks. It seems like most of the info is in this thread, the “Z-wave (Schlage) Lock Support”, and the “Z-Wave refactoring and testing… and SECURITY” one, but that’s literally 700+ posts to read through.
Can anyone provide a step-by-step guide to getting a Z-wave lock included and working (mine is a Schlage BE469), including:
can z-wave locks be used with OH 2.0 out of the box, without the security bindings
is habmin needed to do the install, which version, and how to use it
is the new 2.1.0 z-wave binding needed, and is it reliable
how to install that binding
what uninstalling/reinstalling of Things, bindings, etc. is needed
what functionality will be there / missing
Or, just a pointer to a single post or shorter thread with a summary on it?
I want to shoot myself in the head after trying to plow through the posts on this for the last couple of nights!
@iiigoiii - welcome! I would suggest that if you advertise as being a ‘noob’, you should definitely take the time to start from the top and scroll through the other topic. You will learn A LOT by reading through those comments. Even when it doesn’t make sense at first, when you get into the weeds of testing and using a newer and unsupported binding, you can navigate safely through and at least recall some things you read through. So my advice, definitely click on and read from the top on the referenced thread. At a minimum, you will need to find where the link is for the new binding.
No, currently the ZWave binding included with the currently released versions of OH, DO NOT include support of the Security class for ZWave.
I don’t know that HABmin is required, but in my opinion, it’s the better tool to use with this setup. I don’t believe there is a “version” of HABmin that is required. You should be able to just enable the binding and then the UI will appear on the drop page with the UI choices.
Yes, it is required, and it is not “supported” in OpenHAB yet. Currently the thread you mentioned is the “support” for it and managed by a very generous contributor here @chris. He spends a lot of time and puts a lot of work into this for the good of the community. Please do your due diligence in reading and researching how to use the binding, locks, devices, etc, before trying to bombard him on that thread. Many things have already been handled and answered, and that thread is for folks testing this new binding and finding the bugs/issues with it. That said, don’t be scared to report something that doesn’t seem to be working as expected, and be prepared (aka learn how to) enable DEBUG logging and pull these logs.
Instructions for installation are outlined many time throughout the thread referenced. I’ll give you the short snippet version, but if something doesn’t make sense, please read through the thread. The search option is your friend to use keywords necessary to jump to what you need.
Uninstall the current ZWave binding if already installed
Verify the Serial binding IS installed (ZWave binding may remove it or if not installed it may be missing)
Remove existing ZWave Things (you can leave items and remap afterward)
Stop currently running OpenHAB instance
Download the latest test binding
Copy it into the /openhab/addons folder in your installation
Verify ZWave binding is installed/available
I don’t believe this is any missing functionality, there is only new more advanced functionality to support the Security Class for ZWave devices.
Thanks @shawnmix for the info, really appreciate it.
(Believe me - I did plow my way through the evolving info in those threads, and read everything I could find on the bindings & devices…hours & hours worth! There’s huge value in someone putting the pieces together in one place - I’ll do the same when I find out what works for me.)
My first question was not if the released zwave binding would work for security, but rather if locks could be used without the security bindings in the first place. Guessing not since I was able to associate the lock with OH as released, but it didn’t function.
I’m making slow progress anyway with the new binding, now have a secure association but the device is unknown, even though the device was known and correct under the 2.0.0 zwave binding. Will post about that in the other threads.
@iiigoiii - got ya. Well as you found yes the answer is that it will NOT work with the regular binding at all. It shows up and may identify the device, but since it isn’t SECURE included, it won’t communicate properly for the Security Classes you need. Essentially making it useless.
If you are noticing that the device is shown as unknown, I often find this happening as well. Delete the ZWave Thing and then run the re-scan of ZWave devices. It won’t delete from the controller, but for some reason the second scan works on identifying the details of the item. You also need to be sure that it did in fact securely include (aka see the green bar message in HABmin when including). If not, it’s very likely it did fail. I had this problem the first few times with my Schlage BE469.
Well, it finally worked…I think it was your hint to rescan without excluding that might have done the trick.
I reset everything and scanned for devices with a secure inclusion, and the lock showed up again as an unknown device. I then deleted the lock thing without excluding it or removing it from the controller stick, and then re-scanned. The second scan showed the device as known with the correct manufacturer and device params.
Or who knows, maybe it was just luck on the 11th try.
No problem, glad you got it to work. I think there is something funky where it seems to kind of take a bit of a forced refresh at times to pick the actual device when it’s secure included. Not sure why. Probably just a side effect of something. I’m sure Chris will get it fixed. Just make sure to validate that under the Attributes section, you get the green checkmark for Using Security. That will be the indicator that it should be properly included.
Hi Chris! Since there are a lot of things that might go wrong, I wonder if I’m supposed to receive any status updates from a Yale YRD210 lock for now? I’m using a snapshot of the binding with security classes implemented dated Dec 30, 2017. Lock should use Alarms to report status, but either I use them incorrectly or there is another issue I’m not aware of. Based on your advice I’ll stop or keep digging Thanks !