I will do perform some updates for the Device.
I will re read/test the params and maybe perform some changes. As I have some minor strange issues.
@Chris do you agree to remove 0003:108D from the OLD device, and also remove the Temperature support?
And add the 0003:108D as the Temperature device?
@RoyJacobs Can you try to Disable PIR (parameter 4) and wake the device 2 times… then try your motion events
If you can also remove the firmware limits, but instead treat 108D as a separate device, then I will be able to test the snapshot binding as well without disabling my old 1083 devices.
If I disable PIR on the 108D then it will simply not detect any motion at all (also the LED won’t flash when I trigger it), which is to be expected, I would say?
If I enable PIR then the LED will flash when triggered, but nothing shows up in the ZWave debug logs. It is happily sending temperature reports, though.
Please try to also set Controller 1 as lifeline!
I tried setting the lifeline and that indeed triggered the device once. I had to “Enable PIR” though. However, it doesn’t reset itself to “OK” state after 120 seconds.
The logs:
2018-12-22 19:39:13.164 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=25, callback=0, payload=00 19 04 30 03 FF 0C
2018-12-22 19:39:13.168 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-12-22 19:39:13.172 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 25: Application Command Request (ALIVE:DONE)
2018-12-22 19:39:13.175 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 25: resetResendCount initComplete=true isDead=false
2018-12-22 19:39:13.178 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 25: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2018-12-22 19:39:13.181 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 25: SECURITY not supported
2018-12-22 19:39:13.184 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 25: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
2018-12-22 19:39:13.187 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Processing Sensor Type 12
2018-12-22 19:39:13.189 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Sensor Type is MOTION
2018-12-22 19:39:13.193 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 25: Sensor Binary report, type=Motion, value=255
2018-12-22 19:39:13.197 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2018-12-22 19:39:13.199 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_BINARY, value = 255
2018-12-22 19:39:13.202 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 25: Commands processed 1.
I couldn’t reset the switch state manually either:
2018-12-22 19:43:25.074 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Command received zwave:device:9c1948c3:node25:alarm_motion --> OFF [OnOffType]
2018-12-22 19:43:25.077 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 25: No event found with name 'eventOFF'
2018-12-22 19:43:25.079 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: No messages returned from converter
@chris I Updated the 401 device and 973
at 973 I did a mistake and added (before) an endpoint. I do not know how to delete it 
can you help me with this?
I removed version limits from both devices. and removed the 0003:108D from the Old device.
Yes, let’s do that, but please make a note in the comments, and link to this thread so when/if someone complains that we’ve broken their device, we can try and work out what to do next 
Cool! Will do on both devices.
Did you receive my log from the yesterdays startup?
I think so - I’ve not had the chance to take a look yet, but will do so shortly. Thanks.
I just deployed a new build of the zwave binding, and I can confirm that the new motion sensor is now being picked up correctly! I’ve been able to disable the flashing LED and it’s now triggering correct alarms. I also didn’t need to manually set the assocation group.
Nice one - thanks for the feedback 
I am also going to deploy soon… in 10 minutes or so
Great suff - thanks for working this through…
@billias and others, I have made a post about problems with the NEO Coolcam PIR PD01. I read that the problems are over? Are the Luminance sensor values and the On/Off duration working fine? See the post " Neo Coolcam Motion Sensor PD01 problems"
Hi JP
I am more than happy to test specific issue on my sensors.
Can you elaborate a bit ?
Hi Billias,
If you download the latest Snapshot 2.5.0-SNAPSHOT (https://ci.openhab.org/job/openHAB2-Bundles/lastSuccessfulBuild/artifact/bindings/org.openhab.binding.zwave/target/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar)
You should be able to use this device.
Can you link me to the post too?
Thank you
Note that this data is from the database - it’s not the data for your device.
Where can i find this information?