PD03Z PIR - Only getting temperature

Add-ons Bindings
1

I’m currently running open OH3 having upgraded from OH2 last month - thankfully the upgrade went well and my Z-Wave network consisting of a door sensor, LED bulb and a Fibaro PIR sensor just worked.

I have this week purchased a new PIR sensor with a temperature sensor from Amazon - which when joined to the network is identified as a “PD03Z PIR Motion Sensor with Temperature Sensor” and appearing correctly as NODE 10 - however the only channel I can get working is the temperature channel.

I’ve read some of the existing posts on this sensor but these are more related to OH2, making suggestions such as:

  1. Check discovery has finished by looking for an XML file with the node name
  2. Remove and re-add the Thing using HabMin not the PaperUI

I am thinking both of these are no longer valid for OH3? Please correct me if I’m wrong.

I’ve also had a go at increasing the log level for the Z Wave binding to DEBUG, however the only messages received for NODE 10 relate to the temperature channel:

2021-01-27 20:40:45.584 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Application Command Request (ALIVE:REQUEST_NIF)

2021-01-27 20:40:45.585 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0

2021-01-27 20:40:45.597 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: SECURITY not supported

2021-01-27 20:40:45.599 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Received COMMAND_CLASS_SENSOR_MULTILEVEL V0 SENSOR_MULTILEVEL_REPORT

2021-01-27 20:40:45.601 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 10: Sensor Type = Temperature(1), Scale = 0

2021-01-27 20:40:45.602 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 10: Sensor Value = 27.7

2021-01-27 20:40:45.604 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent

2021-01-27 20:40:45.605 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_MULTILEVEL, value=27.7

2021-01-27 20:40:45.607 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Updating channel state zwave:device:f5fcc3ad:node10:sensor_temperature to 27.7 °C [QuantityType]

2021-01-27 20:40:45.609 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Commands processed 1.

2021-01-27 20:40:45.612 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1c95e92.

Interestingly, I will get this message every time the sensor detects motion (I assume because it wakes up the device) - but alas it’s the only message.

I suppose I have two questions:

  1. How in OH3 can I tell Z-Wave discovery has completed?
  2. Because I’m not seeing a message about the MOTION command on the DEBUG log does this imply the device is faulty?

Any idea where I can go from here?

2

Ah yes! the cheap Chinese Neo coolcam sensors. I have a few.

I retired one for being a battery hog. I want to replace my other 2 because they do not wake up reliably to detect motion. I found you sometimes need to factory reset these devices before they would include properly into the network,.

I think you need an Item linked to the channel to see that in the log.

1 Like
3

I knew I’d regret trying to save £20 over the Fibaro sensor :grimacing:

I’ll keep persisting with including, excluding and resetting.

I have created a item already :slight_smile:

4

Right now I am balking at the price of better sensors. I will eventually replace them though.