As requested, please provide a debug log showing what is happening during discovery.
Please wake up the device manually so I can see what is happening. It may also be worth doing a rediscovery (this is an option in HABmin menu).
This is the log:
and when I wake up the device this is the log:
2019-08-01 13:33:57.783 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 04 02 06 31 05 03 0A 00 0C C6
2019-08-01 13:33:57.801 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=4, payload=04 02 06 31 05 03 0A 00 0C
2019-08-01 13:33:57.805 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=4, payload=04 02 06 31 05 03 0A 00 0C
2019-08-01 13:33:57.808 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-08-01 13:33:57.811 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:VERSION)
2019-08-01 13:33:57.813 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
2019-08-01 13:33:57.830 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2019-08-01 13:33:57.832 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_SENSOR_MULTILEVEL V0 SENSOR_MULTILEVEL_REPORT
2019-08-01 13:33:57.834 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Type = Luminance(3), Scale = 1
2019-08-01 13:33:57.837 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Value = 12
2019-08-01 13:33:57.839 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2019-08-01 13:33:57.841 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 12
2019-08-01 13:33:57.844 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:16c4ca8d72e:node2:sensor_luminance to 12 % [QuantityType]
2019-08-01 13:33:57.848 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2019-08-01 13:33:57.855 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1d2777e.
2019-08-01 13:33:57.858 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-08-01 13:33:57.860 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-08-01 13:33:57.862 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-08-01 13:33:57.866 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-08-01 13:33:57.782 [vent.ItemStateChangedEvent] - zwave_serial_zstick_16c4ca8d72e_serial_sof changed from 61 to 62
2019-08-01 13:33:57.853 [vent.ItemStateChangedEvent] - zwave_device_16c4ca8d72e_node2_sensor_luminance changed from 120 to 12But there are no files in the zwave dir besides the …node_1.xml file
This is just showing up in my log:
2019-08-01 13:44:38.772 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Handler disposed. Unregistering listener.
2019-08-01 13:44:38.931 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 2: Serialise aborted as static stages not complete
2019-08-01 13:44:38.934 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:16c4ca8d72e:node2.
2019-08-01 13:44:38.939 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Controller status changed to ONLINE.
2019-08-01 13:44:38.942 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Controller is ONLINE. Starting device initialisation.
2019-08-01 13:44:38.947 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating node properties.
2019-08-01 13:44:38.950 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating node properties. MAN=600
2019-08-01 13:44:38.954 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating node properties. MAN=600. SET. Was 600
2019-08-01 13:44:38.957 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Properties synchronised
2019-08-01 13:44:39.098 [DEBUG] [ve.internal.protocol.ZWaveController] - Event listener added.
2019-08-01 13:44:39.100 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising Thing Node...
2019-08-01 13:44:39.104 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising cmd channel zwave:device:16c4ca8d72e:node2:sensor_luminance for DecimalType
2019-08-01 13:44:39.106 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising state channel zwave:device:16c4ca8d72e:node2:sensor_luminance for DecimalType
2019-08-01 13:44:39.109 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising cmd channel zwave:device:16c4ca8d72e:node2:sensor_temperature for QuantityType
2019-08-01 13:44:39.112 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising state channel zwave:device:16c4ca8d72e:node2:sensor_temperature for QuantityType
2019-08-01 13:44:39.115 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising cmd channel zwave:device:16c4ca8d72e:node2:alarm_motion for OnOffType
2019-08-01 13:44:39.118 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising state channel zwave:device:16c4ca8d72e:node2:alarm_motion for OnOffType
2019-08-01 13:44:39.121 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising cmd channel zwave:device:16c4ca8d72e:node2:battery-level for PercentType
2019-08-01 13:44:39.123 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising state channel zwave:device:16c4ca8d72e:node2:battery-level for PercentType
2019-08-01 13:44:39.126 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling intialised at 86400 seconds - start in 24278400 milliseconds.
2019-08-01 13:44:39.128 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Device initialisation complete.
and this one:
2019-08-01 13:49:43.609 [DEBUG] [g.zwave.internal.ZWaveConfigProvider] - No bridgeUID found in getConfigDescription thing:zwave:serial_zstick:16c4ca8d72e
2019-08-01 13:50:15.812 [DEBUG] [g.zwave.internal.ZWaveConfigProvider] - No bridgeUID found in getConfigDescription thing:zwave:serial_zstick:16c4ca8d72eI had the exact same issues with all of my four neo coolcams. What helped me was reinitializing the device (using the edit tab of the thing and select more). After you saved, hit the button on the coolcam every few seconds until it is online again (goes through a few stages like get config and static values). Then, and this is the most important step, never touch the configuration again 
As soon as I modified a parameter and hit save, every type would come in, except for motion.
I also have exact the same issues with my neo coolscam devices. How did you trigger reinitializing the device? I can’t find a button or something else labeled “reinitialize”.
What devices?
My PIR sensor has a button under the rear cover. My sockets have a lightes button on the face.
My devices are one PD03Z PIR Motion Sensor and two NEO COOLCAM NAS-DS01Z Window Sensors. As described by the thread opener, my PD03Z also only reports temperature and luminance, but no motion and battery level events. I know the buttons of the neo devices, but i do not find the reinitialize “button” in openhab as described by Gert-Jan.
In Habmin of you go to Configuration -> Things -> the pir node -> you have a tools button on the upper right corner. Next click Show advanced, go to the Tools again and now the Reinitialise the device is available.
I had this problem too. When the pairing process didn’t went well the motion doesn’t send any signal. You can check in \var\lib\openhab2\zwave\ if the binding generates a xml file other than …_node_1.xml. This is the file for the controller. If you don’t have any other file then this you have to pair again . I did the pairing with Zwave PC Controller under Windows 10.
I am using openhab version 2.5 snapshot, which only shows the three other advanced settings, but not the Reinitialise the device entry. What is your openhab version? I remember, that the reinitialise feature has been removed some time ago.
I have a slightly different version of that sensor. I needed to turn off the daily heal on the controller. I then pulled & reinserted the battery on the sensor.
There is an issue where some battery powered zwave devices hang during the daily heal.
I use openHAB 2.5.0 Build #1650. And
108 x Active x 80 x 2.5.0.201908020447 x openHAB Add-ons :: Bundles :: ZWave Binding
In that case, you can execute the command through the rest API. Select things, [PUT][/things/{thingUID}/config], set thinguid (for example zwave:device:bf8beee4:node31) of the device and set the body: {“action_reinit”: true}
Thanks for your tip, but unfortunately still no motion event is sent. It looks like the NEO sensor doesn’t really work with openhab.
I have 3 of them working. Sometimes the daily network heal causes them to hang.Ypu then need to pull & re-insert the battery. If yor network is stable the daily heal can be turned of.
Sometimes, in order to be fully included into the network they need to be factory reset first.
Hard to believe. I’ve made at leat 5 times a factory reset followed by re-includeing the device and the battery contacts are worn out from removing the battery , but no motion events are sent.
I’m running the latest 2.5 snapshot.
I have been running 2.5M3 for about the last week. Before that, I was on 2.5M2.
Perhaps something else is happening on your Z-Wave network. Have you followed the troubleshooting steps listed in the documentation?
Which troubleshooting steps do you mean? How do you define your things? With a .things file or via PaperUI? I’m using the PaperUI.
Ideally, ZWave is managed from HABmin although discovering Things in the Paper UI works too.
If you did not read and follow the official documentation, how do you know zwave is set up properly??