Neo Coolcam Pir motion sensor

Jeroen_K · July 31, 2019, 3:30pm

Hello,

I’ve a Neo Coolcam Pir Motion Sensor. I’ve added it to Openhab and it is regonized as : PD03Z. My controller is a Z-Stick Gen5 from Aeotec.

My controller is a Z-Stick Gen5 from Aeotec.

But I get no events from the motion.

> 2019-07-31 16:46:19.700 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=4, payload=04 04 06 31 05 01 22 00 FA 
> 
> 2019-07-31 16:46:19.703 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
> 
> 2019-07-31 16:46:19.706 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Application Command Request (ALIVE:VERSION)
> 
> 2019-07-31 16:46:19.709 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
> 
> 2019-07-31 16:46:19.711 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported
> 
> 2019-07-31 16:46:19.713 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 4: Received COMMAND_CLASS_SENSOR_MULTILEVEL V0 SENSOR_MULTILEVEL_REPORT
> 
> 2019-07-31 16:46:19.716 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 4: Sensor Type = Temperature(1), Scale = 0
> 
> 2019-07-31 16:46:19.718 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 4: Sensor Value = 25
> 
> 2019-07-31 16:46:19.721 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
> 
> 2019-07-31 16:46:19.724 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 25
> 
> 2019-07-31 16:46:19.727 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Updating channel state zwave:device:ZwaveController:node4:sensor_temperature to 25 °C [QuantityType]
> 
> 2019-07-31 16:46:19.735 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Commands processed 1.
> 
> 2019-07-31 16:46:19.738 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@16acd30.
> 
> 2019-07-31 16:46:19.741 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
> 
> 2019-07-31 16:46:19.745 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
> 
> 2019-07-31 16:46:19.749 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
> 
> 2019-07-31 16:46:19.752 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
> 
> ==> /mnt/shares/Openhablog/events.log <==
> 
> 2019-07-31 16:46:19.694 [vent.ItemStateChangedEvent] - zwave_serial_zstick_ZwaveController_serial_sof changed from 233 to 234
> 
> 2019-07-31 16:46:19.753 [vent.ItemStateChangedEvent] - zwave_device_ZwaveController_node4_sensor_temperature changed from 25.5 °C to 25 °C

The temperature is updating wel.

I tried the following rules:

    rule "Beweging keuken"
    when
    	Item zwave_device_ZwaveController_node4_alarm_motion changed to ON
    then
    	sendTelegram("jeroen","Beweging in de keuken")
   end

and this one:

rule "Beweging keuken"
when
	Channel 'zwave:device:ZwaveController:node4:alarm_motion' triggered ON
then
	sendTelegram("jeroen","Beweging in de keuken")
end

Both with no luck. Anyone who can help me?

Assosiations Group is empty and when I configure ‘controller’ I get the following message:

2019-07-31 16:49:40.313 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update set group_1 to controller (String)

2019-07-31 16:49:40.319 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Unknown association group 1

Bruce_Osborne · July 31, 2019, 4:56pm

You may want to turn off the daily network heal and restart the sensor. I believe there is an issue where the network heal can hang for battery devices and never complete.
After turning off the daily heal and removing & replacing the battery, my sensor behaves properly.
I remember @chris discussing possible daily healing issues with battery devices.

When you get to the channels screen on the controller, click the pencil icon at the top. From that screen you can disable the daily network heal.

Jeroen_K · July 31, 2019, 5:55pm

Thanks for your reply. I tried that but it’s still the same. Temperature is working but I see no event at motion.

> 2019-07-31 19:53:17.600 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=4, payload=04 04 06 31 05 01 22 01 08 
> 
> 2019-07-31 19:53:17.603 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
> 
> 2019-07-31 19:53:17.605 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Application Command Request (ALIVE:VERSION)
> 
> 2019-07-31 19:53:17.608 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
> 
> 2019-07-31 19:53:17.610 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported
> 
> 2019-07-31 19:53:17.613 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 4: Received COMMAND_CLASS_SENSOR_MULTILEVEL V0 SENSOR_MULTILEVEL_REPORT
> 
> 2019-07-31 19:53:17.615 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 4: Sensor Type = Temperature(1), Scale = 0
> 
> 2019-07-31 19:53:17.617 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 4: Sensor Value = 26.4
> 
> 2019-07-31 19:53:17.620 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
> 
> 2019-07-31 19:53:17.623 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 26.4
> 
> 2019-07-31 19:53:17.627 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Updating channel state zwave:device:ZwaveController:node4:sensor_temperature to 26.4 °C [QuantityType]
> 
> 2019-07-31 19:53:17.633 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Commands processed 1.
> 
> 2019-07-31 19:53:17.635 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1032fba.
> 
> 2019-07-31 19:53:17.639 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
> 
> 2019-07-31 19:53:17.643 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
> 
> 2019-07-31 19:53:17.645 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
> 
> 2019-07-31 19:53:17.649 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
> 
> ==> /mnt/shares/Openhablog/events.log <==
> 
> 2019-07-31 19:53:17.074 [vent.ItemStateChangedEvent] - zwave_serial_zstick_ZwaveController_serial_sof changed from 287 to 288
> 
> 2019-07-31 19:53:17.132 [vent.ItemStateChangedEvent] - zwave_device_ZwaveController_node3_sensor_temperature changed from 24.9 °C to 25.5 °C
> 
> 2019-07-31 19:53:17.592 [vent.ItemStateChangedEvent] - zwave_serial_zstick_ZwaveController_serial_sof changed from 288 to 289
> 
> 2019-07-31 19:53:17.647 [vent.ItemStateChangedEvent] - zwave_device_ZwaveController_node4_sensor_temperature changed from 25.6 °C to 26.4 °C

Bruce_Osborne · July 31, 2019, 6:08pm

I have my sensor joined insecurely. I see your DEBUG message saying security is not supported.

Does the sensor flash indicating motion? I believe that is the default configuration.

Jeroen_K · July 31, 2019, 6:12pm

Yes the sensor is flashing when motion is detected.

Jeroen_K · July 31, 2019, 8:29pm

I still getting this :

2019-07-31 22:07:42.081 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Configuration update set group_1 to controller (String)

2019-07-31 22:07:42.084 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Unknown association group 1

What I see is that on the frist line It’s

group_1

and the second line `

group 1

` whitout underscore

Jeroen_K · July 31, 2019, 8:53pm

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/973

Can someone check if the settings in the database are correct?

 "zwave:device:c93d58f4:node2": {
    "class": "org.eclipse.smarthome.core.thing.internal.ThingImpl",
    "value": {
      "label": "Bewegingssensor Trap",
      "bridgeUID": {
        "segments": [
          "zwave",
          "serial_zstick",
          "c93d58f4"
        ]
      },
      "channels": [
        {
          "acceptedItemType": "Number",
          "kind": "STATE",
          "uid": {
            "segments": [
              "zwave",
              "device",
              "c93d58f4",
              "node2",
              "sensor_luminance"
            ]
          },
          "channelTypeUID": {
            "segments": [
              "zwave",
              "sensor_luminance"
            ]
          },
          "label": "Luminance Sensor",
          "description": "Indicates the current light reading",
          "configuration": {
            "properties": {}
          },
          "properties": {
            "binding:*:DecimalType": "COMMAND_CLASS_SENSOR_MULTILEVEL;type\u003dLUMINANCE"
          },
          "defaultTags": []
        },
        {
          "acceptedItemType": "Number:Temperature",
          "kind": "STATE",
          "uid": {
            "segments": [
              "zwave",
              "device",
              "c93d58f4",
              "node2",
              "sensor_temperature"
            ]
          },
          "channelTypeUID": {
            "segments": [
              "zwave",
              "sensor_temperature"
            ]
          },
          "label": "Temperature Sensor",
          "description": "Indicates the current temperature",
          "configuration": {
            "properties": {}
          },
          "properties": {
            "binding:*:QuantityType": "COMMAND_CLASS_SENSOR_MULTILEVEL;type\u003dTEMPERATURE"
          },
          "defaultTags": []
        },
        {
          "acceptedItemType": "Switch",
          "kind": "STATE",
          "uid": {
            "segments": [
              "zwave",
              "device",
              "c93d58f4",
              "node2",
              "alarm_motion"
            ]
          },
          "channelTypeUID": {
            "segments": [
              "zwave",
              "alarm_motion"
            ]
          },
          "label": "Motion Alarm",
          "description": "Indicates if a motion alarm is triggered",
          "configuration": {
            "properties": {}
          },
          "properties": {
            "binding:*:OnOffType": "COMMAND_CLASS_ALARM;type\u003dBURGLAR"
          },
          "defaultTags": []
        },
        {
          "acceptedItemType": "Number",
          "kind": "STATE",
          "uid": {
            "segments": [
              "zwave",
              "device",
              "c93d58f4",
              "node2",
              "battery-level"
            ]
          },
          "channelTypeUID": {
            "segments": [
              "system",
              "battery-level"
            ]
          },
          "label": "Battery Level",
          "configuration": {
            "properties": {}
          },
          "properties": {
            "binding:*:PercentType": "COMMAND_CLASS_BATTERY"
          },
          "defaultTags": []
        }
      ],
      "configuration": {
        "properties": {
          "binding_cmdrepollperiod": 1500,
          "config_11_1": 1,
          "config_10_1": 5,
          "group_4": [],
          "group_1": "",
          "group_3": [],
          "group_2": [],
          "wakeup_node": 0,
          "config_12_1": 1,
          "config_99_2": 1000,
          "action_failed": false,
          "wakeup_interval": 0,
          "action_remove": false,
          "binding_pollperiod": 86400,
          "action_heal": false,
          "config_1_1": 12,
          "config_7_2": 180,
          "config_8_1": 0,
          "config_9_2": 100,
          "config_2_2": 30,
          "config_3_1": 255,
          "config_4_1": 255,
          "node_id": 2,
          "config_5_2": 100,
          "config_6_1": 8
        }
      },
      "properties": {
        "zwave_class_basic": "BASIC_TYPE_ROUTING_SLAVE",
        "zwave_class_generic": "GENERIC_TYPE_SENSOR_NOTIFICATION",
        "zwave_frequent": "false",
        "zwave_neighbours": "",
        "modelId": "PD03Z",
        "zwave_version": "3.80",
        "zwave_listening": "false",
        "manufacturerId": "0258",
        "manufacturerRef": "0003:108D",
        "dbReference": "973",
        "zwave_deviceid": "4237",
        "zwave_nodeid": "2",
        "vendor": "Shenzhen Neo Electronics Co., Ltd",
        "defaultAssociations": "1",
        "zwave_routing": "true",
        "zwave_beaming": "true",
        "zwave_secure": "false",
        "zwave_class_specific": "SPECIFIC_TYPE_NOTIFICATION_SENSOR",
        "zwave_manufacturer": "600",
        "zwave_devicetype": "3"
      },
      "uid": {
        "segments": [
          "zwave",
          "device",
          "c93d58f4",
          "node2"
        ]
      },
      "thingTypeUID": {
        "segments": [
          "zwave",
          "shenzhen_pd03z_00_000"
        ]
      },
      "location": "Overloop"
    }
  },

and if the right sensor is decteted? Motion sensor Z-wave Plus NEO Coolcam is what I have.

Could it be that the wrong one is detected? References (Type:Id) 0003:108D,0003:208D

chris · July 31, 2019, 9:31pm

That’s fine.

This looks correct based on the database link you provided.

Has the device finished initialisation? Can you provide the XML file generated by your system for this device please?

Bruce_Osborne · July 31, 2019, 9:42pm

Did you look at the configuration options in the database? This may be your issue.

My sensor has a different ID & database entry.

Jeroen_K · July 31, 2019, 10:13pm

I changed it to “0” but it doesn’t do the trick.
When I trigger the motionsensor it get the following log:

2019-08-01 00:09:01.107 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=4, payload=04 02 06 31 05 01 22 01 1A 

2019-08-01 00:09:01.110 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null

2019-08-01 00:09:01.113 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:VERSION)

2019-08-01 00:09:01.115 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0

2019-08-01 00:09:01.118 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported

2019-08-01 00:09:01.120 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_SENSOR_MULTILEVEL V0 SENSOR_MULTILEVEL_REPORT

2019-08-01 00:09:01.123 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Type = Temperature(1), Scale = 0

2019-08-01 00:09:01.125 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Value = 28.2

2019-08-01 00:09:01.128 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent

2019-08-01 00:09:01.130 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 28.2

2019-08-01 00:09:01.134 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:jeroen:node2:sensor_temperature to 28.2 °C [QuantityType]

2019-08-01 00:09:01.139 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.

2019-08-01 00:09:01.142 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@747017.

2019-08-01 00:09:01.167 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2019-08-01 00:09:01.181 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2019-08-01 00:09:01.184 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2019-08-01 00:09:01.186 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

==> /mnt/shares/Openhablog/events.log <==

2019-08-01 00:09:01.074 [vent.ItemStateChangedEvent] - zwave_serial_zstick_jeroen_serial_sof changed from 70 to 71

2019-08-01 00:09:01.154 [vent.ItemStateChangedEvent] - zwave_device_jeroen_node2_sensor_temperature changed from 28.9 °C to 28.2 °C

But no motion event.

chris · July 31, 2019, 10:16pm

You don’t say what version of the binding you’re using?

Please can you provide the XML file that the binding generates?

Jeroen_K · July 31, 2019, 10:29pm

The binding I use is binding-zwave - 2.5.0.M1

You mean this XML file?

<node>
  <homeId>0xf7dcf9b4</homeId>
  <nodeId>1</nodeId>
  <version>4</version>
  <manufacturer>0x86</manufacturer>
  <deviceId>0x5a</deviceId>
  <deviceType>0x1</deviceType>
  <listening>true</listening>
  <frequentlyListening>false</frequentlyListening>
  <routing>false</routing>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>
  <sleepDelay>1000</sleepDelay>
  <associationGroups class="concurrent-hash-map"/>
  <endpoints class="concurrent-hash-map">
    <entry>
      <int>0</int>
      <endPoint>
        <deviceClass>
          <basicDeviceClass>BASIC_TYPE_STATIC_CONTROLLER</basicDeviceClass>
          <genericDeviceClass>GENERIC_TYPE_STATIC_CONTROLLER</genericDeviceClass>
          <specificDeviceClass>SPECIFIC_TYPE_PC_CONTROLLER</specificDeviceClass>
        </deviceClass>
        <endpointId>0</endpointId>
        <secureCommandClasses/>
        <supportedCommandClasses class="concurrent-hash-map">
          <entry>
            <commandClass>COMMAND_CLASS_NO_OPERATION</commandClass>
            <COMMAND__CLASS__NO__OPERATION>
              <version>1</version>
              <instances>0</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
            </COMMAND__CLASS__NO__OPERATION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_BASIC</commandClass>
            <COMMAND__CLASS__BASIC>
              <version>0</version>
              <instances>0</instances>
              <control>false</control>
              <versionSupported>0</versionSupported>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__BASIC>
          </entry>
        </supportedCommandClasses>
      </endPoint>
    </entry>
  </endpoints>
  <nodeNeighbors/>
</node>

Bruce_Osborne · July 31, 2019, 10:31pm

that is fir the controller. @chris meant for the PIR sensor.

Jeroen_K · July 31, 2019, 10:51pm

Could you tell me where I can find that file?

Bruce_Osborne · July 31, 2019, 11:27pm

The file should be in /var/lib/openhab2/zwave and the name will end in _node_4.xml.

Jeroen_K · August 1, 2019, 6:58am

There is no such file these are the files in the dir:

chris · August 1, 2019, 7:37am

So that means that the device is not discovered, and this is why you are getting the errors.

You will need to wake the device up so it can be discovered. If it’s not working, then please provide a debug log showing what happens when you wake up the device.

Jeroen_K · August 1, 2019, 11:02am

The binding doesn’t generate a xml when a node is discovered. This is the only file it generates:

The discovery did find the motion sensor:

the temperature sensor is working as you can see but the motion sensor is not sending anything.

I deleted everything several times and add it again but stil the same. Reset the controller. Tried it whit Paper UI and with Habmin.

Bruce_Osborne · August 1, 2019, 11:05am

It sould not really matter, but are you discovering through the PaperUI or through HABmin?
HABmin is recommended for zwave configuration & discovery.

Jeroen_K · August 1, 2019, 11:06am

Habmin