If you encounter a dependency problem after upgrading see this thread:
to clarify, i an running openhab 2.3 on raspberry pi as manual install (not openhabian image). So openhab is running as a service.
After deleted all the things, i put the zwave 2.4.0 jar file in the add-ons folder, and restarted by pi, i dont see it is showing the error pointed above regarding unresolved requirement. To fix, i am supposed to run
“feature:install openhab-transport-serial” from the openhab console?
when i go to /usr/share/openhab2
and sudo ./start.sh
i get root instance is already running. so i stopped the service using “/bin/systemctl stop openhab2.service”
then i ran sudo openhab-cli start
at the openhab console, i ran
feature:install openhab-transport-serial
thereafter all the things start showing up in my inbox (most of them still showing unknown devices)- i will let this run overnight and see how it goes.
thanks for all the guidance!
Most of the non battery devices and some battery devices have come online and seem to be operating.
However, all the devices are showing red x for security under attributes 
i dont think that secure association has worked.
Door lock is getting recognized as a device however does not respond to lock / unlock commands. Under association group it does not have node 1 or controller- when i try to manually add it, it seems to accept it but after a save when i go back and look at it, it does not retain it,
ZSE40 4in1 sensor is reporting temp/humidity/luminance but does not get triggered on motion.
CT101 thermostat seems to be working which was not with the 2.3 binding 
looking at the openhab log file i am seeing (among others) following warnings and errors:
2018-11-18 23:59:30.630 [INFO ] [alization.ZWaveNodeInitStageAdvancer] - NODE 46: SECURITY_INC State=FAILED, Reason=SECURE_PING
2018-11-19 00:00:25.510 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 46: Command class COMMAND_CLASS_DOOR_LOCK not found
2018-11-19 00:00:31.698 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 46: Command class COMMAND_CLASS_DOOR_LOCK not found
Events.log has the following:
018-11-19 00:02:24.847 [hingStatusInfoChangedEvent] - ‘zwave:device:10722b79:node46’ changed from ONLINE to ONLINE: Node initialising: EMPTYNODE
2018-11-19 00:02:24.858 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:10722b79:node46’ has been updated.
2018-11-19 00:02:24.860 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
2018-11-19 00:02:24.905 [hingStatusInfoChangedEvent] - ‘zwave:device:10722b79:node46’ changed from ONLINE: Node initialising: EMPTYNODE to ONLINE: Node initialising: IDENTIFY_NODE
2018-11-19 00:02:24.912 [vent.ItemStateChangedEvent] - zwave_serial_zstick_10722b79_serial_ack changed from 1980 to 1981
2018-11-19 00:02:24.919 [vent.ItemStateChangedEvent] - zwave_serial_zstick_10722b79_serial_sof changed from 8005 to 8006
2018-11-19 00:02:24.925 [hingStatusInfoChangedEvent] - ‘zwave:device:10722b79:node46’ changed from ONLINE: Node initialising: IDENTIFY_NODE to ONLINE: Node initialising: REQUEST_NIF
2018-11-19 00:02:24.931 [vent.ItemStateChangedEvent] - zwave_serial_zstick_10722b79_serial_ack changed from 1981 to 1982
2018-11-19 00:02:24.935 [vent.ItemStateChangedEvent] - zwave_serial_zstick_10722b79_serial_sof changed from 8006 to 8007
2018-11-19 00:02:26.257 [vent.ItemStateChangedEvent] - zwave_serial_zstick_10722b79_serial_sof changed from 8007 to 8008
2018-11-19 00:02:26.276 [hingStatusInfoChangedEvent] - ‘zwave:device:10722b79:node46’ changed from ONLINE: Node initialising: REQUEST_NIF to ONLINE: Node initialising: SECURITY_REPORT
i am attaching the entire log file if it helps shed some more light.
Also tried removing another door sensor and including it again. This sensor was showing as “unknown device” for over 5 hours. After including it again, it connected to the controller as node 50 and got recognized as correctly ZD2102-5 Door Window Sensor
It was showing following errors openhab logs but eventually after a few minutes it seems to have resolved and it is showing open / closed status correctly. Under Habmin, attributes it shows green check mark for security!!
I am wondering if i will have to remove and reassociate all the devices showing as “unknown” again with openhab since they were initially operating under openremote controller. Would this have anything to do with Network security key?
2018-11-19 00:30:47.953 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:10722b79:node50’ to inbox.
2018-11-19 00:31:01.451 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - NODE 50: Using Scheme0 Network Key for Key Exchange since we are in inclusion mode.
2018-11-19 00:31:01.688 [INFO ] [alization.ZWaveNodeInitStageAdvancer] - NODE 50: SECURITY_INC State=COMPLETE
2018-11-19 00:31:22.474 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method ‘ThingHandler.initialize()’ on ‘org.openhab.binding.zwave.handler.ZWaveThingHandler@1019813’: 1
java.lang.ArrayIndexOutOfBoundsException: 1
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialiseNode(ZWaveThingHandler.java:226) [240:org.openhab.binding.zwave:2.4.0.201811181037]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.bridgeStatusChanged(ZWaveThingHandler.java:512) [240:org.openhab.binding.zwave:2.4.0.201811181037]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialize(ZWaveThingHandler.java:164) [240:org.openhab.binding.zwave:2.4.0.201811181037]
at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:?]
at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [101:org.eclipse.smarthome.core:0.10.0.oh230]
at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [101:org.eclipse.smarthome.core:0.10.0.oh230]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:?]
at java.lang.Thread.run(Thread.java:745) [?:?]
2018-11-19 00:31:22.489 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occurred while initializing handler of thing ‘zwave:device:10722b79:node50’: 1
java.lang.ArrayIndexOutOfBoundsException: 1
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialiseNode(ZWaveThingHandler.java:226) [240:org.openhab.binding.zwave:2.4.0.201811181037]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.bridgeStatusChanged(ZWaveThingHandler.java:512) [240:org.openhab.binding.zwave:2.4.0.201811181037]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialize(ZWaveThingHandler.java:164) [240:org.openhab.binding.zwave:2.4.0.201811181037]
at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:?]
at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [101:org.eclipse.smarthome.core:0.10.0.oh230]
at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [101:org.eclipse.smarthome.core:0.10.0.oh230]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:?]
at java.lang.Thread.run(Thread.java:745) [?:?]
2018-11-19 00:36:39.244 [WARN ] [nal.converter.ZWaveDoorLockConverter] - NODE 46: Command class COMMAND_CLASS_DOOR_LOCK not found
If you don’t have an error, you don’t need to fix it 
You only can include devices securely which support secure inclusion. If they have been included before you need to exclude them and reset to factory default, then perform a secure inclusion.
Mostly a display issue if you are using HABmin, check again with PaperUI.
Check the correct channel and the config settings.
The network security key needs to stay the same and I think I read somewhere that secure inclusion needs to be done again if the device was formerly connected to another zwave network.
Thanks sihui–
these devices have all been connected to the same Gen5 zstick running on the same Raspberry Pi for several years. the only difference is the software controller was OpenRemote which i have turned off now and I am trying out OpenHAB2 on this same raspberry pi. So my questions is does the network key or any other parameters prevent secure communication when software controller is different even though all the hardware has been same all along and are they software controller specific?