Neo Coolcam PIR sensor not generating motion sensor detections

Setup, Configuration and Use Beginners
21

Sensitivity is set at 12 and PIR motion detection in enabled; should be OK. However - still nothing appearing in logfile other than entry i just sent you

22

Ha - Node 4 just appeared again in logfile - and that is the one we need according to paper UI. Lot of entries after I pushed activitation button and made some motions. No clue what to conclude from log at first sight.

2019-02-15 14:38:31.098 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update received

2019-02-15 14:38:31.106 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored binding_cmdrepollperiod to 1500 (BigDecimal)

2019-02-15 14:38:31.108 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_10_1 to 1 (BigDecimal)

2019-02-15 14:38:31.111 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update set group_4 to null (null)

2019-02-15 14:38:31.115 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Current Members ZWaveAssociationGroup [index=4, name=null, profile1=null, profile2=null, associations=[]]

2019-02-15 14:38:31.118 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: New Members ZWaveAssociationGroup [index=4, name=null, profile1=null, profile2=null, associations=[]]

2019-02-15 14:38:31.121 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: New Members ZWaveAssociationGroup [index=4, name=null, profile1=null, profile2=null, associations=[]]

2019-02-15 14:38:31.123 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Controller is master - forcing associations

2019-02-15 14:38:31.128 [DEBUG] [ndclass.ZWaveAssociationCommandClass] - NODE 4: Creating new message for application command ASSOCIATIONCMD_REMOVE group=4, node=all

2019-02-15 14:38:31.131 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported

2019-02-15 14:38:31.134 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Command Class COMMAND_CLASS_ASSOCIATION is NOT required to be secured

2019-02-15 14:38:31.136 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Bump transaction 122 priority from Config to Immediate

2019-02-15 14:38:31.139 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Adding to device queue

2019-02-15 14:38:31.142 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Transaction already in queue - removed original

2019-02-15 14:38:31.145 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Added 122 to queue - size 12

2019-02-15 14:38:31.148 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-02-15 14:38:31.152 [DEBUG] [ndclass.ZWaveAssociationCommandClass] - NODE 4: Creating new message for application command ASSOCIATIONCMD_GET group 4

2019-02-15 14:38:31.155 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported

2019-02-15 14:38:31.158 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Command Class COMMAND_CLASS_ASSOCIATION is NOT required to be secured

2019-02-15 14:38:31.161 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Bump transaction 123 priority from Config to Immediate

2019-02-15 14:38:31.164 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Adding to device queue

2019-02-15 14:38:31.167 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Transaction already in queue - removed original

2019-02-15 14:38:31.170 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Added 123 to queue - size 12

2019-02-15 14:38:31.173 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-02-15 14:38:31.177 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored action_failed to false (Boolean)

2019-02-15 14:38:31.181 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored wakeup_interval to 43200 (BigDecimal)

2019-02-15 14:38:31.184 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored group_1 to controller (String)

2019-02-15 14:38:31.187 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored action_remove to false (Boolean)

2019-02-15 14:38:31.190 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update set group_3 to null (null)

2019-02-15 14:38:31.194 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Current Members ZWaveAssociationGroup [index=3, name=null, profile1=null, profile2=null, associations=[]]

2019-02-15 14:38:31.197 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: New Members ZWaveAssociationGroup [index=3, name=null, profile1=null, profile2=null, associations=[]]

2019-02-15 14:38:31.200 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: New Members ZWaveAssociationGroup [index=3, name=null, profile1=null, profile2=null, associations=[]]

2019-02-15 14:38:31.203 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Controller is master - forcing associations

2019-02-15 14:38:31.208 [DEBUG] [ndclass.ZWaveAssociationCommandClass] - NODE 4: Creating new message for application command ASSOCIATIONCMD_REMOVE group=3, node=all

2019-02-15 14:38:31.211 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported

2019-02-15 14:38:31.214 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Command Class COMMAND_CLASS_ASSOCIATION is NOT required to be secured

2019-02-15 14:38:31.217 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Bump transaction 124 priority from Config to Immediate

2019-02-15 14:38:31.220 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Adding to device queue

2019-02-15 14:38:31.223 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Transaction already in queue - removed original

2019-02-15 14:38:31.227 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Added 124 to queue - size 12

2019-02-15 14:38:31.230 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-02-15 14:38:31.234 [DEBUG] [ndclass.ZWaveAssociationCommandClass] - NODE 4: Creating new message for application command ASSOCIATIONCMD_GET group 3

2019-02-15 14:38:31.237 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported

2019-02-15 14:38:31.241 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Command Class COMMAND_CLASS_ASSOCIATION is NOT required to be secured

2019-02-15 14:38:31.245 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Bump transaction 125 priority from Config to Immediate

2019-02-15 14:38:31.248 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Adding to device queue

2019-02-15 14:38:31.251 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Transaction already in queue - removed original

2019-02-15 14:38:31.254 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Added 125 to queue - size 12

2019-02-15 14:38:31.261 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-02-15 14:38:31.265 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored binding_pollperiod to 86400 (BigDecimal)

2019-02-15 14:38:31.268 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update set group_2 to null (null)

2019-02-15 14:38:31.271 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Current Members ZWaveAssociationGroup [index=2, name=null, profile1=null, profile2=null, associations=[]]

2019-02-15 14:38:31.274 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: New Members ZWaveAssociationGroup [index=2, name=null, profile1=null, profile2=null, associations=[]]

2019-02-15 14:38:31.278 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: New Members ZWaveAssociationGroup [index=2, name=null, profile1=null, profile2=null, associations=[]]

2019-02-15 14:38:31.281 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Controller is master - forcing associations

2019-02-15 14:38:31.285 [DEBUG] [ndclass.ZWaveAssociationCommandClass] - NODE 4: Creating new message for application command ASSOCIATIONCMD_REMOVE group=2, node=all

2019-02-15 14:38:31.288 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported

2019-02-15 14:38:31.292 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Command Class COMMAND_CLASS_ASSOCIATION is NOT required to be secured

2019-02-15 14:38:31.295 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Bump transaction 126 priority from Config to Immediate

2019-02-15 14:38:31.298 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Adding to device queue

2019-02-15 14:38:31.301 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Transaction already in queue - removed original

2019-02-15 14:38:31.303 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Added 126 to queue - size 12

2019-02-15 14:38:31.306 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-02-15 14:38:31.309 [DEBUG] [ndclass.ZWaveAssociationCommandClass] - NODE 4: Creating new message for application command ASSOCIATIONCMD_GET group 2

2019-02-15 14:38:31.311 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported

2019-02-15 14:38:31.314 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Command Class COMMAND_CLASS_ASSOCIATION is NOT required to be secured

2019-02-15 14:38:31.316 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Bump transaction 127 priority from Config to Immediate

2019-02-15 14:38:31.319 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Adding to device queue

2019-02-15 14:38:31.322 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Transaction already in queue - removed original

2019-02-15 14:38:31.324 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Added 127 to queue - size 12

2019-02-15 14:38:31.327 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-02-15 14:38:31.330 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored action_heal to false (Boolean)

2019-02-15 14:38:31.333 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_1_1 to 12 (BigDecimal)

2019-02-15 14:38:31.335 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored wakeup_node to 1 (BigDecimal)

2019-02-15 14:38:31.338 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_7_2 to 180 (BigDecimal)

2019-02-15 14:38:31.340 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_8_1 to 0 (BigDecimal)

2019-02-15 14:38:31.343 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_9_2 to 100 (BigDecimal)

2019-02-15 14:38:31.346 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_2_2 to 30 (BigDecimal)

2019-02-15 14:38:31.348 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_3_1 to 255 (BigDecimal)

2019-02-15 14:38:31.351 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_4_1 to 255 (BigDecimal)

2019-02-15 14:38:31.353 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored node_id to 4 (BigDecimal)

2019-02-15 14:38:31.356 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_5_2 to 100 (BigDecimal)

2019-02-15 14:38:31.358 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_6_1 to 8 (BigDecimal)

2019-02-15 14:38:31.361 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_99_2 to 5320 (BigDecimal)

==> /var/log/openhab2/events.log <==

2019-02-15 14:38:31.385 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:f9036393:node4' has been updated.

2019-02-15 14:38:31.392 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=group_4, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_3_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_3, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_2, type=PE

Can you make any sense of this? @chris

23

This is the configuration of the device, which in general looks fine. The PIR is enabled, and the sensitivity is set to the default value. Group 1 association also looks fine.

So, it must work :wink:

24

How can i share configuration of rule using the PIR motion sensor with you - the rule still says that is in idle mode all the time, according to Paper UI?

25

At the moment, we still donā€™t see any notifications in the log - until we actually see the PIR notifications in the ZWave log, the rule wonā€™t do anything so I donā€™t think thatā€™s where we need to focus.

26

Ah; what can i do next make notifications appear?

27

Well, thatā€™s the real question, but unfortunately, Iā€™ve run out of suggestions.

It should work if -:

  1. The PIR is enabled
  2. The associations are set
  3. The sensitivity level is ok

All of these look fine, and the device is reporting temperature, so it is correctly configured to report.

28

so reinstallation openhab2 and starting with complete clean config file would not help either? better to get another motion PIR and try that one out?

29

Better to try it out with another motion sensor?

30

No - I donā€™t believe that it would help. As far as I can see, everything appears to be configured ok, and the device is reporting - itā€™s just not reporting PIR.

I thought Iā€™d seen messages in the past about these sensors having problems, but I canā€™t find anything now.

Maybe, but this sensor should also work. Your device might just have a fault of courseā€¦

31

Logviewer is also seeing a node 8 which looks like a pir sensor also. Could it be that that is creating the blockade - two nodes configured for one and the same sensor?

32

I can send you the logfiles so you can take a look at them and see what else might be wrong?

33

Please feel free to provide the log and Iā€™ll have a quick look, but I canā€™t really see how the node can be reporting via two different node Idsā€¦

34

I have the same problems with this Neo CoolCam PIR Device.
Sometimes it helps when you wake it up several (10) times with the button inside.

35

Pjotr, thanks for reply. What does an entry in log look like when:
a. you use wakeup button
b. when sensor registers motion and passes it on to OH2?

36

And Pjotr - any suggestion for a good motion sensor where I will have more luck instead of the NEO CoolCam?
Pieter

37

@Pjotr500
Pjotr, thanks for reply. What does an entry in log look like when:
a. you use wakeup button
b. when sensor registers motion and passes it on to OH2?

38

@Pjotr500
Pjotr, thanks for reply. What does an entry in log look like when:
a. you use wakeup button
b. when sensor registers motion and passes it on to OH2?

39

When the sensor registers a motion, it behaves like a switch

2019-02-19 09:44:48.332 [vent.ItemStateChangedEvent] - GF_Kitchen_Motion changed from OFF to ON

When you push the button, the Thing receives an update. You will receive this in your logfile:

2019-02-19 09:54:59.448 [me.event.ThingUpdatedEvent] - Thing ā€˜zwave:device:d9e17137:node14ā€™ has been updated.

It helps sometimes to do this 10 times within 2 or 3 minutes. But after some time of inactivity, I have to repeat this. (about once a month)

It is not a very stable device. In the past I obtained a different Z-Wave PIR sensor from AliExpress, but itā€™s unfortunately sold out.