Neo Coolcam Motion Sensor PD02Z and previous models

Sorry, it’s probably prudent to mention that I have been using the official 2.4 binding, NOT the updated snapshot since I wasn’t sure it would keep working with the old device due to the minimum firmware version (which is >3.80 in my 0003:1083). So I’ll refrain from commenting on the behaviour of the 0003:108D until I update to the latest snapshot binding.

This has he same settings as before, it should never be working in the old device.

@Chris can the Command_Class_Alarm version 8 (reported by device) causing the motion detection issue in the newer device?

From @RoyJacobs logs I can clearly assume the old device is sending only binary reports and it should include a binary channel for the motion.

It is confusing as when motion is detected value = 255 and if i read this site https://www.cd-jackson.com/index.php/zwave/zwave-device-database/openhab-2-channel-types | 255 means on alarm_motion. am I reading something wrong?

I’m not sure what you mean? It should work fine I believe - the frame is decoded just fine in your log.

Are you sure that there were no other packets logged that were not presented above? We should be sure about this first and not just assume it is the case?

I don’t understand what is confusing? This seems fine to me?

You are right, I missed another notification in the logs (so, again, of the old 0003:1083 device running Firmware 3.97 using the 2.4 binding):

2018-12-22 14:12:13.270 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=15, callback=0, payload=00 0F 09 71 05 00 00 00 FF 07 08 00 
2018-12-22 14:12:13.273 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-12-22 14:12:13.274 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 15: Application Command Request (ALIVE:DONE)
2018-12-22 14:12:13.276 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 15: resetResendCount initComplete=true isDead=false
2018-12-22 14:12:13.278 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 15: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2018-12-22 14:12:13.280 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 15: SECURITY not supported
2018-12-22 14:12:13.281 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 15: Received COMMAND_CLASS_ALARM V8 NOTIFICATION_REPORT
2018-12-22 14:12:13.283 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 15: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
2018-12-22 14:12:13.285 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0A 00 04 00 0F 04 30 03 FF 0C 3A 
2018-12-22 14:12:13.286 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 15: Alarm Type = BURGLAR (0)
2018-12-22 14:12:13.289 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-12-22 14:12:13.291 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
2018-12-22 14:12:13.292 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=15, callback=0, payload=00 0F 04 30 03 FF 0C 
2018-12-22 14:12:13.294 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 15: Alarm converter processing NOTIFICATION
2018-12-22 14:12:13.297 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 15: Alarm converter NOTIFICATION event is 8, type OnOffType
2018-12-22 14:12:13.300 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 15: Commands processed 1.
2018-12-22 14:12:13.302 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 15: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@133bde.
2018-12-22 14:12:13.304 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-12-22 14:12:13.306 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

I’m also happy to try some things with the snapshot binding, but can you confirm that the old devices will still keep working even though they’re running firmware 3.97?

It’s these lines that worry me, in motionsensor_0_0.xml:

<property name="manufacturerRef">0003:0083,0003:008D,0003:1083,0003:108D</property>
<property name="versionMax">3.79</property>

Full (not chopped) log from my device when detects motion (NEWer model)

2018-12-22 14:40:39.866 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 11 00 04 00 2B 09 71 05 00 00 00 FF 07 08 00 A8 00 E4
2018-12-22 14:40:39.895 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=43, callback=0, payload=00 2B 09 71 05 00 00 00 FF 07 08 00 A8 00
2018-12-22 14:40:39.898 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=43, callback=0, payload=00 2B 09 71 05 00 00 00 FF 07 08 00 A8 00
2018-12-22 14:40:39.899 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-12-22 14:40:39.901 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Application Command Request (ALIVE:DONE)
2018-12-22 14:40:39.902 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: resetResendCount initComplete=true isDead=false
2018-12-22 14:40:39.903 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2018-12-22 14:40:39.905 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: SECURITY not supported
2018-12-22 14:40:39.906 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 43: Received COMMAND_CLASS_ALARM V8 NOTIFICATION_REPORT
2018-12-22 14:40:39.907 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 43: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
2018-12-22 14:40:39.908 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 43: Alarm Type = BURGLAR (0)
2018-12-22 14:40:39.910 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Commands processed 1.
2018-12-22 14:40:39.911 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@c92b19.
2018-12-22 14:40:39.912 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-12-22 14:40:39.913 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-12-22 14:40:39.915 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-12-22 14:40:39.916 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-12-22 14:40:40.020 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 2B 04 30 03 FF 0C AB 00 B3
2018-12-22 14:40:40.055 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=43, callback=0, payload=00 2B 04 30 03 FF 0C AB 00
2018-12-22 14:40:40.057 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=43, callback=0, payload=00 2B 04 30 03 FF 0C AB 00
2018-12-22 14:40:40.061 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-12-22 14:40:40.061 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0E 00 04 00 2B 06 31 05 01 22 00 D1 AB 00 B5
2018-12-22 14:40:40.063 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Application Command Request (ALIVE:DONE)
2018-12-22 14:40:40.065 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: resetResendCount initComplete=true isDead=false
2018-12-22 14:40:40.067 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2018-12-22 14:40:40.068 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: SECURITY not supported
2018-12-22 14:40:40.070 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 43: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
2018-12-22 14:40:40.072 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Processing Sensor Type 12
2018-12-22 14:40:40.074 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Sensor Type is MOTION
2018-12-22 14:40:40.075 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 43: Sensor Binary report, type=Motion, value=255
2018-12-22 14:40:40.077 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Commands processed 1.
2018-12-22 14:40:40.079 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@186ce7b.
2018-12-22 14:40:40.080 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-12-22 14:40:40.082 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-12-22 14:40:40.084 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-12-22 14:40:40.085 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=43, callback=0, payload=00 2B 06 31 05 01 22 00 D1 AB 00
2018-12-22 14:40:40.085 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-12-22 14:40:40.087 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=43, callback=0, payload=00 2B 06 31 05 01 22 00 D1 AB 00
2018-12-22 14:40:40.089 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-12-22 14:40:40.090 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Application Command Request (ALIVE:DONE)
2018-12-22 14:40:40.092 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: resetResendCount initComplete=true isDead=false
2018-12-22 14:40:40.093 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
2018-12-22 14:40:40.095 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 43: SECURITY not supported
2018-12-22 14:40:40.096 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 43: Received COMMAND_CLASS_SENSOR_MULTILEVEL V7 SENSOR_MULTILEVEL_REPORT
2018-12-22 14:40:40.098 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 43: Sensor Type = Temperature(1), Scale = 0
2018-12-22 14:40:40.100 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 43: Sensor Value = 20.9
2018-12-22 14:40:40.101 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Commands processed 1.
2018-12-22 14:40:40.103 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 43: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@df0a00.
2018-12-22 14:40:40.104 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-12-22 14:40:40.106 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-12-22 14:40:40.107 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-12-22 14:40:40.108 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

My Item doesn’t trigger stays OFF in this case

No - they probably won’t at the moment. Let’s sort this all out first and I can do another update later today if we work all this out…

Ok, so this looks fine. The only thing is it doesn’t seem to be processing the channel as I don’t see the channel status update message.

I think that this may be an issue I saw with someone elses system recently where resonses are not being processed. I thing that there is an issue setting up a command listener in the binding - possibly (but this is a guess) due to startup order with the way things are initialised compared to the controller (which is meant to be first according the ESH, but if this is not the case, then notifications will not work properly).

Do you have a full startup log from when you started the binding? If so, can you email it to me (it may be large).

Okay, fair enough.

I don’t, but I guess I can just restart OpenHab and send you the logs? Please note though that this old device is working fine, so there are no issues there. It’s just that the new device is not sending any alarms. If it’s still helpful to send, I can do so.

Can I also just set the log level to debug and restart the binding from Karaf, or something?

Sorry - this question should have been to @billias since I don’t see the following messages in the log where I do from you @RoyJacobs.

This indicates that the ZWave protocol stack is not sending messages to the OH side of the binding and I’d really like to work out why this is as it’s a major bug (not related to the Neo Coolcam although it’s also the reason why the messages aren’t being processed here).

Hmm, that’s odd since node 15 is the old device. What I’ll do is just quickly set the binding to debug, trigger the alarm and send the full logs instead of just copy/pasting snippets. I don’t think I’ve missed anything, but it’s probably easier if I just send the full log instead of having you chase partial data.

I’m not sure what you’re referring to here? What exactly is odd? The text you quoted is not related to your logs, and is not related to the Neo Coolcam devices, so I’m not sure what you refer to as “odd”?

You quoted part of my logs, so I assumed you were talking about something going wrong with node 15 in my ZWave setup. Anyway, for what it’s worth, I’ve sent you the logs for that sensor correctly triggering.

Yes - I was saying though that your logs are ok as they have this log entry, but the logs from @billias do not show this log entry. It should be logged, and the fact that it isn’t logged means there is something wrong with @billias system and I would therefore like to see the full logs from startup from @billias.

Chris I had to restart my openhab. i captured the logs with DEBUG on zwave, where should I send them?

Ok, no problem. I’ll still take a look to see if the error is still there.

I don’t suppose you have the startup logs from when the binding was started previously?

Anyway, send to chris -at- cd-jackson.com.

I will search for these too.

Thanks. The log you just sent appears to be working ok (by which I mean it is processed the events). I don’t see anything from node 43 so can’t confirm if the Coolcam is working, but in general it look ok…

Coolcam is 51 node right now. (The second one) After joining it again it works, I will send the full logs from the previous one. I have the logs from the beginning of time"

Great - I hope it might help find this issue. I’ve only seen it in one other log, but I think the problem is probably during startup, so let’s see.

I know is a bit offtopic, also remember the sensative strips… I still suffer with these :\ only with 2.4 binding. but I will keep it on the other topic