It looks like you are not using the development binding with the changes Chris put in for handling Alarm V2. If you thought you were using the development binding, check with bundle:list | grep -i zwave. It’s could be possible you could have two versions installed, but the older version is running. Does alarm_tamper report anything?
@5iver I continue to appreciate your help. I eventually figured out that I needed to be in Karaf console to enter bundle:list | grep -i zwave so after I did openhab-cli console and used the standard password habopen I was able to issue the command and got back:
199 │ Active │ 80 │ 2.3.0.201803101457 │ ZWave Binding
I only spelled out the steps in case there are others who come across this thread and need help.
I thought I was on the development release but I learned that the snapshot that I’m on is different than the development. I’m using openhabian and openhab-cli console to do the updates.
Should I bother trying to figure out how to switch over to the development release or will those changes soon be on the snapshot release? I do use this openhab setup for our home and I need to maintain the WAF (wife acceptance factor) which has been really good so far.
Thank you,
B34N
You don’t need both channels, since they provide the same information, so I’d say wait. In fact, you’ll find sensor_door comes in just a tiny bit faster (you can see it in the log). 
Just for reference though, the development version of the zwave binding is here…
Was anyone able to get the WADWAZ-1 to work with the external contacts in OH2 ?
Yes! I just updated the database with a new channel for the external switch. I’ve been testing it this weekend. If it works for the WADWAZ-1, then it should work for the other rebranded devices too. If someone would like to try it on one of those devices, just add the channel like in the WADWAZ-1 or I can do it for you.
I tried the binding dated 9th April 2018 from the security page with no luck. Are you using a different .jar binding ?
Yes. The database was just updated, so you will need to wait for it to be exported, merged, and a build to be done. I was hoping Chris would have kicked this off today, but it shouldn’t be long! i finally have functioning leak sensors, and an alert to put salt in the water softener!
The 17th April 2018 binding has the updated support for the external contacts. It also appears that you can use it as a dual sensor now. No need to always have the magnet connected for the external contacts to work!
Just to be sure.
Now all 3 event can be triggered independent?
door open/close
binary switch open/close
alarm
Becasue I want to use door and binary for two different things. door as door and bianry as glas break event wit han external sensor connected.
I haven’t had much luck with this other than getting the open and close to work. I don’t think the battery worked as well for me nor did the tamper. If you can get all 4 channels to work, please post what you did
I’ve upgraded to OH 2.4 snapshot now.
Tamper is no longer working.
Please provide a debug log showing what is received, and also please be explicit with what device we are talking about as there are 3 x ZD2102 in the database from different manufacturers.
I have to vision one.
Only three channels are available:
My config. Note alarm_burglar was working with the old config of z-wave 2.2 binding. Now no longer there
Contact DoorSensor03 "working [MAP(de.map):%s]" {channel="zwave:device:xxx:node6:sensor_door"}
Number DoorSensor03_Battery "working not sure [%d %%]" {channel="zwave:device:xxx:node6:battery-level"}
Switch DoorSensor03_BurglerAlarm "not working [%s]" {channel="zwave:device:xxx:node6:alarm_burglar"}
Switch DoorSensor03_TamperAlarm "not working [%s]" {channel="zwave:device:xxx:node6:alarm_tamper"}
Logs:
tamper open and close - log.txt (21.2 KB)
binary sensor open and close - log.txt (10.5 KB)
door sensor open and close - log.txt (10.5 KB)
I delete and re-add the device and get this error:
2018-11-25 21:48:44.082 [hingStatusInfoChangedEvent] - 'zwave:device:15a7a49f3a6:node6' changed from ONLINE to UNINITIALIZED (HANDLER_INITIALIZING_ERROR): 1
2018-11-25 21:48:44.053 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.initialize()' on 'org.openhab.binding.zwave.handler.ZWaveThingHandler@36b614': 1
java.lang.ArrayIndexOutOfBoundsException: 1
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialiseNode(ZWaveThingHandler.java:226) ~[?:?]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.bridgeStatusChanged(ZWaveThingHandler.java:512) ~[?:?]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialize(ZWaveThingHandler.java:164) ~[?:?]
at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [101:org.eclipse.smarthome.core:0.10.0.201811171951]
at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [101:org.eclipse.smarthome.core:0.10.0.201811171951]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
2018-11-25 21:48:44.080 [ERROR] [core.thing.internal.ThingManagerImpl] - Exception occurred while initializing handler of thing 'zwave:device:15a7a49f3a6:node6': 1
java.lang.ArrayIndexOutOfBoundsException: 1
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialiseNode(ZWaveThingHandler.java:226) ~[?:?]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.bridgeStatusChanged(ZWaveThingHandler.java:512) ~[?:?]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialize(ZWaveThingHandler.java:164) ~[?:?]
at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [101:org.eclipse.smarthome.core:0.10.0.201811171951]
at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [101:org.eclipse.smarthome.core:0.10.0.201811171951]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
maybe this helps
How many channels should there be, and what are they?
I think it should be four:
door open/close
tamper
battery
binary switch (if this is really supported)
But a working tamper will be good. Works before as burglar but is no longer there.
Why four? What do they do? What is the binary switch? For most devices, there are multiple ways to send the same data (eg alarm, and binary sensor) - if you can confirm that there is an external input, or some other feature of this device, then we can add this, but I’m not sure that’s right is it?
Hello chris,
the device has this feature:
door sensor
external binary contact
battery level
tamper
There is another post here. The result of that oen is that the binary switch is hard to implement. Maybe we skip that implementation. But it will be good to get tamper back. (was buglar in earlier bindings). And it looks like there is a general problem with adding the device. See my last log.
I think chris is fighting with this device for a long time in different posts. We should close this post. I think not solvable