Neo Coolcam PIR sensor not generating motion sensor detections


(Pieter Tjebbes) #1
  • Platform information:
    RPI3
    openHAB version: 2
  • Issue of the topic: sensor is not generating motion detections when it should be. Sensor shows up in logfile and is online, however no motion signals generated or show up in logfile. What could be wrong?
  • Please post configurations (if applicable):
  • If logs where generated please post these here using code fences:

(Chris Jackson) #2

Which version are you using?


(Pieter Tjebbes) #3

I am using Openhab 2.4.0 release build


(Pieter Tjebbes) #4

PIR motion sensor is configured as a switch in OpenHab. I read in another trace that it should be as a contact. Does not help. Node appears in log, updates also appear, however activitation or motions do not. A rule using the sensor’s motion item/channel as trigger does not work either.
What could be wrong here? Sensor could be bust … it does not generate a blink when motion is made in range of sensor either.


(Pieter Tjebbes) #5

@chris - any clue as to what could be wrong here - see also my previous post for more details.


(Chris Jackson) #6

Please provide the debug log showing what is received. I would also recommend changing the 2.5 version of the binding which should ensure that the association can not be removed.


(Pieter Tjebbes) #7

OK - let me work with that - thanks.


(Pieter Tjebbes) #8

chris, you mentioned 2.5 version of zwave binding - where can i get this and how do i get to install it in Openhab 2.4?


(Pieter Tjebbes) #9

Managed to 2.5 version of zwave binding, however it does not appear in Openhab as yet.
Logfile produces following errors:

2019-02-11 07:58:52.420 [ERROR] [org.openhab.binding.zwave           ] - FrameworkEvent ERROR - org.openhab.binding.zwave

org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [303]

2019-02-11 08:00:04.507 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode004MotionSensorPIRMotionSensor_BatteryLevel-zwave:device:918814ff:node4:battery-level' has been added.

2019-02-11 08:00:04.515 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode004MotionSensorPIRMotionSensor_AlarmMotion-zwave:device:918814ff:node4:alarm_motion' has been added.

2019-02-11 08:00:04.524 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode004MotionSensorPIRMotionSensor_SensorTemperature-zwave:device:918814ff:node4:sensor_temperature' has been added.

2019-02-11 08:00:04.530 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode004MotionSensorPIRMotionSensor_SensorLuminance-zwave:device:918814ff:node4:sensor_luminance' has been added.

2019-02-11 08:00:04.564 [.ItemChannelLinkAddedEvent] - Link 'zwave_serial_zstick_918814ff_serial_nak-zwave:serial_zstick:918814ff:serial_nak' has been added.

2019-02-11 08:00:04.572 [.ItemChannelLinkAddedEvent] - Link 'Fietshok_Motion_Sensor-zwave:device:918814ff:node4:alarm_motion' has been added.

2019-02-11 08:00:04.575 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_918814ff_node6_alarm_power-zwave:device:918814ff:node6:alarm_power' has been added.

2019-02-11 08:00:04.583 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_918814ff_node6_meter_kwh-zwave:device:918814ff:node6:meter_kwh' has been added.

2019-02-11 08:00:04.588 [.ItemChannelLinkAddedEvent] - Link 'zwave_serial_zstick_918814ff_serial_cse-zwave:serial_zstick:918814ff:serial_cse' has been added.

2019-02-11 08:00:04.590 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_918814ff_node6_switch_binary-zwave:device:918814ff:node6:switch_binary' has been added.

2019-02-11 08:00:04.592 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_918814ff_node6_meter_voltage-zwave:device:918814ff:node6:meter_voltage' has been added.

2019-02-11 08:00:04.594 [.ItemChannelLinkAddedEvent] - Link 'zwave_serial_zstick_918814ff_serial_ack-zwave:serial_zstick:918814ff:serial_ack' has been added.

2019-02-11 08:00:04.596 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_918814ff_node6_meter_current-zwave:device:918814ff:node6:meter_current' has been added.

2019-02-11 08:00:04.598 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_918814ff_node4_battery_level-zwave:device:918814ff:node4:battery-level' has been added.

2019-02-11 08:00:04.600 [.ItemChannelLinkAddedEvent] - Link 'zwave_serial_zstick_918814ff_serial_can-zwave:serial_zstick:918814ff:serial_can' has been added.

2019-02-11 08:00:04.602 [.ItemChannelLinkAddedEvent] - Link 'zwave_serial_zstick_918814ff_serial_sof-zwave:serial_zstick:918814ff:serial_sof' has been added.

2019-02-11 08:00:04.610 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_918814ff_node4_sensor_luminance-zwave:device:918814ff:node4:sensor_luminance' has been added.

2019-02-11 08:00:04.614 [.ItemChannelLinkAddedEvent] - Link 'zwave_serial_zstick_918814ff_serial_oof-zwave:serial_zstick:918814ff:serial_oof' has been added.

2019-02-11 08:00:04.617 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_918814ff_node6_meter_watts-zwave:device:918814ff:node6:meter_watts' has been added.

2019-02-11 08:00:04.620 [.ItemChannelLinkAddedEvent] - Link 'Test_switch-zwave:device:918814ff:node6:switch_binary' has been added.

2019-02-11 08:00:04.625 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_918814ff_node4_alarm_motion-zwave:device:918814ff:node4:alarm_motion' has been added.

2019-02-11 08:00:04.626 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_918814ff_node4_sensor_temperature-zwave:device:918814ff:node4:sensor_temperature' has been added.

2019-02-11 08:00:45.004 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab2/addons/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar

org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [303]


(Pieter Tjebbes) #10

@chris - any clue what I did wrong - managed to install zwave binding 2.5 - however it does not appear in Openhab. See also logfile above.


(Chris Jackson) #11

The error means that the binding is not installed - or at least not running. So, either the binding bundle, or one of its dependencies are unresolved. It could be that the serial bundle is not installed?


(Pieter Tjebbes) #12

Yes, binding shows in Karaf as installed, not active. What is a serial bundle, where can I get it and where do I install it? Together with 2.5 jar in \openHAB-share\openhab2-addons\ ?


(Pieter Tjebbes) #13

@chris

Chris,
Found the feature:install instruction on the community and ran it in Karaf. This returned the following error:

Exception in org.eclipse.smarthome.io.rest.sse.internal.SseActivator.start() of bundle org.eclipse.smarthome.io.rest.sse.

Any clue?
Pieter Tjebbes


(Pieter Tjebbes) #14

Restarted Openhab and it looks like 2.5 zwave binding is active now - at least a new version of binding is active (where can i find version number in paper ui?) and according to Karaf version 2.5 is now active!


(Chris Jackson) #15

I’m not sure if it’s listed in the UI if you install manually - the best place is to either confirm using Karaf, or, the binding logs the version when it starts into the openhab.log file.


(Pieter Tjebbes) #16

Chris,

The PIR motion sensor seems to show up, however I can not see in logfile which is which.
I have created a rule using the motion item related to the sensor, using the Paper UI which is supposed to turn on a wall switch. Rule stays in idle mode all the time however. Hitting execute rule button in Paper UI does not help. What could be wrong? Lot of suggestion on community to use text editor - however not too familiar with text editor
Pieter


(Pieter Tjebbes) #17

@chris - managed to setup PIR sensor, it looks like it is showing up in logfile, but rule using the motion sensor remains idle in openhab ui?


(Chris Jackson) #18

Can you provide a log which shows the reception of the PIR motion notification?


(Pieter Tjebbes) #19

Chris,
tried to activate PIR motion sensor and generate notification but nothing appears in logs since today’s last entry for zwave devices see below

2019-02-15 13:29:39.510 [vent.ItemStateChangedEvent] - zwave_serial_zstick_f9036393_serial_sof changed from 528 to 529

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

2019-02-15 13:29:39.511 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0E 00 04 04 08 06 31 05 03 0A 00 AD D4 00 BB 

2019-02-15 13:29:39.523 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=8, callback=4, payload=04 08 06 31 05 03 0A 00 AD D4 00 

2019-02-15 13:29:39.528 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=8, callback=4, payload=04 08 06 31 05 03 0A 00 AD D4 00 

2019-02-15 13:29:39.532 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null

2019-02-15 13:29:39.534 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 8: Application Command Request (ALIVE:REQUEST_NIF)

2019-02-15 13:29:39.537 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 8: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0

2019-02-15 13:29:39.540 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 8: SECURITY not supported

2019-02-15 13:29:39.542 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 8: Received COMMAND_CLASS_SENSOR_MULTILEVEL V0 SENSOR_MULTILEVEL_REPORT

2019-02-15 13:29:39.545 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 8: Sensor Type = Luminance(3), Scale = 1

2019-02-15 13:29:39.548 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 8: Sensor Value = 173

2019-02-15 13:29:39.550 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 8: Commands processed 1.

2019-02-15 13:29:39.553 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 8: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@2632be.

2019-02-15 13:29:39.556 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2019-02-15 13:29:39.558 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2019-02-15 13:29:39.561 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2019-02-15 13:29:39.563 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.


I will check again later - noticed that there might be some time lag in the log files.


(Chris Jackson) #20

Can you check that just above this log there is not a message being sent to the device? ie I want to check that this message was sent unsolicited from the device, and not polled.

If it was sent unsolicited, then this means that the lifeline is configured correctly, and this also should mean that the device should report motion…

I would then suggest to check the configuration - I see there are some parameters that can influence the PIR - parameters 1 and 4 being the main ones I would look at (sensitivity and PIR enable).