Firstly, there’s a difference between alarms and notifications. The (old) alarm command class just has a single alarm type. The notification command class has a notification type, and an event type (sort of a sub type). The notification command class also reports what’s called a V1 alarm type (so the old type) which is what is reported as 19 in the log above.
Depending on the type, it reports different things. In the alarm it reports the alarm type, and in the notification it reports the event.
SECURITY_RXD 71 05 13 01 00 FF 06 06 01 01
In your log above, we have notification type 6, which is access control, and event type 6 which means keypad unlock, or we might have event 5 which is keypad lock (again, it’s an access control notification). In all with the notification class, there are around 150 event types…
So, I guess the convoluted answer is that we are ignoring the V1 event type and using the notification types in this example. The way the binding is written is it will try to use the highest version.
I see now! The event from my BE469 was alarm v3 (Received COMMAND_CLASS_ALARM V3 NOTIFICATION_REPORT), and the event from @rgerrans’ lock was alarm v1 (Received COMMAND_CLASS_ALARM V1 NOTIFICATION_REPORT). The 1.10 binding must have not used ALARMv3, since I was getting the alarm v1 reports and had to change my rules after moving to this binding. Which reminds me… I should post a topic on how I scraped the 1.10 binding log to get user codes.
Thank very much to all of your. I installed this binding. Here is the procedure
1, check the version. The binding-zwave - 2.2.0.SNAPSHOT.jar was installed with the openhab 2.2 snapshot. But it doesn’t support secure inclusion for locks.
user@server:~$ ssh -p 8101 openhab@localhost
openhab> bundle:list -s | grep zwave
186 | Active | 80 | 2.2.0.201708041402 | ZWave Binding | org.openhab.binding.zwave
2, uninstall the binding-zwave - 2.2.0.SNAPSHOT.jar at Paper UI / Add-ons / BINDINGS
3, downloaded this development binding-zwave - 2.1.0.SNAPSHOT.jar at this thread.
4, move the jar to the openhab server /etc/openhab2/ with samba
After restarting, openhab may install the binding-zwave by itself, and will show up at Paper UI / Configuration /Bindings. But it doesn’t show up at my situation.
5, Login the karaf terminal to check the version again. The status of 194 is Installed not Active.
user@server:~$ ssh -p 8101 openhab@localhost
openhab> bundle:list -s | grep zwave
194 | Installed | 80 | 2.1.0.201708041056 | ZWave Binding | org.openhab.binding.zwave
6, Try to start it manually, find the problem, and fix it.
openhab> bundle:start org.openhab.binding.zwave
Error executing command: Error executing command on bundles:
Error starting bundle 194: Could not resolve module: org.openhab.binding.zwave [194]
Unresolved requirement: Import-Package: gnu.io
How often is the database of zwave devices updated in the snapshot? I’ve got some devices that are in the database but aren’t being recognised by openhab.
OK, I’ve been messing around with this for a while (months), and still haven’t gotten it working. Over the last few days I’ve made a big push, but no luck so far. So… looking for some help.
Basics:
Openhab 2.1.0 running on a Centos server. Updated this morning.
Zwave downloaded from the head of the thread today (0804 version) and installed and activated; other zwave bindings gone. A Network Security Key is set.
I have about 60 devices in the ZWave network. All the non-secure items work fine
I have a Kwiset 916 lock that I’m trying to get securely added. I’ve pulled it from the door, and it’s sitting about a foot from the USB ZWave controller, so range isn’t an issue.
I set debug logging for the zwave component: log:set DEBUG org.openhab.binding.zwave
So, what I’ve tried… Excluding the lock from the network, and then, via Habmin, putting the zwave controller in add mode. The device is found, but then the red ‘zwave.event.inclusion_securefailed’ box pops up. It’s identified as the 914TRL, which seems to be normal. The ‘Using Security’ Attribute is a red x. I’ve tried this about 10 times, including start/stop openhab, or let things sit to be as quiet as possible, or any other variations I can think of.
I have a debug trace, but it’s pretty long… if it’s helpful and someone can suggest a place to put it I can provide it.
I have the same lock and was able to get it included securely. I have a Aeon zstick and I think I did the inclusion directly with the stick vs. using Openhab. I had to drop it off my network yesterday so will be (hopefully) adding it back today so will try from Openhab and if that doesn’t work directly with the stick and will report back
I’ve had terrible problems with my locks and secure inclusion. If you happen to have a mains powered device that you can include securely try that. I’ve included 4 securely (first 4 nodes are aeotec multisensors) and this made secure inclusion MUCH more reliable.
I’ve found that if you in-securely include devices, include secure battery powered devices before including a secure mains powered device then dealing with secure inclusion is just a pain.
There’s a document by honeywell which explained how to fill out a z-wave network and once I followed that almost all my problems went away.
would you mind posting a sample config of NGD00Z-4.
I just got it secure included. There are many channels listed. Which one is to open/close the door? Barrier State ?
@Brent_Chartrand Just to report back, I was able to add it back through normal inclusion from Habmin with no issues. Do you have your Network Security Key entered in your Zwave Controller?
I posted some setup info in the following thread. The only channel that I could get values for was BARRIER_STATE. I believe the other channels should not have been included for the device because it does not support the ALARM CC. I was waiting for the OP for that thread before asking Chris about them. But I think they should be removed.
