No event from door sensor

I have door sensors from Sensative which is included in my zwave network. I have installed the 2.1 version of the z-wave binding for the support for security.
When opening and closing doors I get no event from the door strips but when I enable debug log I see this. Node 33 is one of the strips.

2017-05-18 13:10:06.950 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 21 0A 71 05 00 00 00 FF 06 17 00 00 5A 
2017-05-18 13:10:06.965 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
2017-05-18 13:10:06.971 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage inputMessage: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=33, callback=0, payload=00 21 0A 71 05 00 00 00 FF 06 17 00 00 
2017-05-18 13:10:06.977 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lockMessage: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=33, callback=0, payload=00 21 0A 71 05 00 00 00 FF 06 17 00 00 
2017-05-18 13:10:06.985 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], dest=33, callback=0, payload=00 21 0A 71 05 00 00 00 FF 06 17 00 00 
2017-05-18 13:10:06.989 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2017-05-18 13:10:06.993 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Application Command Request (ALIVE:DONE)
2017-05-18 13:10:06.997 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: resetResendCount initComplete=true isDead=false
2017-05-18 13:10:07.001 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2017-05-18 13:10:07.005 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 33: SECURITY not supported
2017-05-18 13:10:07.008 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 33: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2017-05-18 13:10:07.029 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Commands processed 1.
2017-05-18 13:10:07.041 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 33: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@52d78a.
2017-05-18 13:10:07.053 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2017-05-18 13:10:07.055 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2017-05-18 13:10:07.057 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2017-05-18 13:10:07.060 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start

Can @chris see what is wrong?

I have a gut feeling that my installation of the 2.1 z-wave binding may not be running. When looking in the paper UI addons section under bindings I have the z-wave binding 2.0 installed! I also have the 2.1 jar file in the /usr/share/openhab2/addons directory.
Can I uninstall the 2.0 binding from paper UI and reboot without all things and items being deleted?

You have to uninstall the old binding, also make sure you don’t have that binding configured for loading in your addons.cfg

When switching from stable/snapshot binding to development binding you have to delete all things and add them again, see the main thread:

Also note that you may need to install the serial transport binding manually:

And don’t forget: if you want to go back to the old zwave binding, you will have to delete and readd all your things again.

To verify if you have the correct zwave binding running, go to karaf console and do a bundle:list, the result will show you the exact version of your bindings.

This is the output of bundle:list right now:

195 | Active    |  80 |    | ZWave Binding
197 | Installed |  80 | 2.0.0                 | ZWave Binding

What does that tell you @sihui? Which one is running?

It is a bit weird that two zwave bindings are listed, but because only one (the newer one) is active, I assume it is okay.
Still I would do a
bundle:uninstall 197 just to make sure …

That’s not uncommon - if you have 2 bindings, then they will be listed like this - only the Active one will run.

@Martin_Larsson just to say that you don’t need to use the security binding to get the Sensative strips working (maybe you were changing to this version anyway - although the one you are using is quite old so I’m not sure exactly what it is).

So I unistalled the 2.0 binding. Restarted openhab but still the same log when opening the door and no real event. The item does not change state.

Do I need to remove the device and re-add it?

@chris I need the security binding for another device. Where do I find a newer version of the binding?

If you’ve recently updated the binding, then you should try to delete the thing, and add it back again. The reason is that this will ensure that the binding is using the latest version of the thing definition. IF you don’t do this, and the things have been updated (ie the database) then they won’t take affect.

You can download it from the security thread.

@chris do you think upgrading the binging will make my stips work? There is some work involved in excluding and including devices that are mounted on doors where I drag around my RPi with ethernet and power cable.
I am positive that those devices were included with the 2.1 binding build 201704171736. Is there any major changes in the latest build compared to my old one that will make thing much better?

No, as I said earlier, you don’t need to use the security / development binding - the strips devices work fine in the master snapshot as well.

I need the security binding for my Vision PIR sensor.

So what can I do to make the strips work? Does the log tell you anything?

I doubt that it’s needed for a PIR sensor. It should work fine without the security - nearly all devices will work without security (except locks of course).

Anyway, I misunderstood your question - yes, I would use a newer version.

Strips should work fine - it’s been tested by many people, and I’m using it here. Have you deleted the thing and added it back again as I mentioned earlier?