Philio Motion Sensor PSP05 - Help to get working

zwave
Tags: #<Tag:0x00007f1e653a9ac8>
(John Butt) #1

Hi,

I’m a newbie to openHAB so please be gentle with me! I have a Philio Motion Sensor PSP05 I’m trying to get running on openHAB2. The device is initialised OK and is visible as a thing on the paper ui, but I can’t get any sort of event to trigger when motion is detected. I know the sensor is working, as if I put it into “test mode” the led lights to show motion is detected.
I’ve cranked logging up to trace and have pasted the last set of log points below. The PSP05 is node 3. I notice one of the last log points for node 3 is “Is sleeping”, is this to be expected?
I’m I missing any sort of setup I need to execute on the device first before I can expect motion events (via the sensor_binary) to be triggered?
Thanks,
John B

18:48:19.913 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Checksum matched
18:48:19.928 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Message payload = 01
18:48:19.930 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Message is valid, sending ACK
18:48:19.933 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT
18:48:19.935 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
18:48:19.935 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Received SOF
18:48:19.936 [TRACE] [wave.internal.protocol.SerialMessage] - Calculated checksum = 0xE8
18:48:19.937 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
18:48:19.939 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
18:48:19.940 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
18:48:19.941 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 44 00 00 02 AD
18:48:19.942 [TRACE] [ve.internal.protocol.ZWaveController] - Incoming Message type = RESPONSE
18:48:19.943 [TRACE] [l.serialmessage.SendDataMessageClass] - Handle Message Send Data Response
18:48:19.944 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 01 07 00 13 44 00 00 02 AD
18:48:19.944 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: Sent Data successfully placed on stack.
18:48:19.945 [TRACE] [wave.internal.protocol.SerialMessage] - Ack Pending cleared
18:48:19.945 [TRACE] [wave.internal.protocol.SerialMessage] - Calculated checksum = 0xAD
18:48:19.946 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Checksum matched
18:48:19.947 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Message payload = 44 00 00 02
18:48:19.947 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Message is valid, sending ACK
18:48:19.948 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_d4888985_serial_sof changed from 186 to 187
18:48:19.948 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT
18:48:19.951 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
18:48:19.952 [TRACE] [wave.internal.protocol.SerialMessage] - Calculated checksum = 0xA3
18:48:19.954 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 44 00 00 02 00 00 A3
18:48:19.956 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 44 00 00 02 00 00 A3
18:48:19.958 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=44 00 00 02
18:48:19.959 [TRACE] [ve.internal.protocol.ZWaveController] - Incoming Message type = REQUEST
18:48:19.960 [TRACE] [l.serialmessage.SendDataMessageClass] - Handle Message Send Data Request
18:48:19.961 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: SendData Request. CallBack ID = 68, Status = Transmission complete and ACK received(0)
18:48:19.962 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Starting initialisation from DONE
18:48:19.963 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@b189d1 already registered
18:48:19.965 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=3, callback=68, payload=03 02 84 08
18:48:19.967 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=44 00 00 02
18:48:19.968 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=68, expected=SendData, cancelled=false transaction complete!
18:48:19.968 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
18:48:19.970 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 3: Went to sleep
18:48:19.971 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 3: Is sleeping
18:48:19.972 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
18:48:19.973 [DEBUG] [curityCommandClassWithInitialization] - NODE 3: updating lastSentMessageTimestamp
18:48:19.973 [TRACE] [ve.internal.protocol.ZWaveController] - Released. Transaction completed permit count -> 1
18:48:19.973 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 3: Response processed after 84ms/864ms.
18:48:19.974 [TRACE] [ocol.ZWaveController$ZWaveSendThread] - Acquired. Transaction completed permit count -> 0

0 Likes

(Marcel Becker) #2

Hi John,

sorry can’t help, but also looking for binding the Philio Motion Sensor.

Are you already further?

Best geetings
Marcello

0 Likes

(John Butt) #3

Hi Marcello,

Unfortunately, I’ve not managed to get the sensor to trigger even using the latest beta version of openHAB, which does fix the binding.

Let me know if you make any progress!

Best regards,

John B

0 Likes

(Nokyyz) #4

Hi all,

I encounter the same problem as you. My Philio sensor PSP05 has been discovered on Paper UI and the channels sensor_binary, alarm_burglar & battery-level are linked to items. When a motion is detected, there is no event in OpenHab. However, sometimes Openhab receives events (see events.log file and corresponding openhab.log file)… maybe due to wake up message ?

I don’t understand the problem. @chris Can you help us ?

Thanks

events.log

2017-12-12 23:50:39.950 [ItemChannelLinkAddedEvent ] - Link 'Detector52_Burglar-zwave:device:AEO_ZW090_C:node52:alarm_burglar' has been added.
2017-12-12 23:50:40.014 [ItemChannelLinkAddedEvent ] - Link 'Detector52_Battery-zwave:device:AEO_ZW090_C:node52:battery-level' has been added.
2017-12-12 23:50:40.030 [ItemChannelLinkAddedEvent ] - Link 'Detector52_Movement-zwave:device:AEO_ZW090_C:node52:sensor_binary' has been added.
2017-12-12 23:50:48.218 [ItemStateChangedEvent     ] - Detector52_Movement changed from NULL to OFF
2017-12-12 23:50:48.220 [ItemStateChangedEvent     ] - Detector52_Burglar changed from NULL to OFF
2017-12-12 23:50:48.225 [ItemStateChangedEvent     ] - Detector52_Battery changed from NULL to 100
2017-12-13 21:40:53.340 [ItemStateChangedEvent     ] - Detector52_Movement changed from OFF to ON
2017-12-14 08:47:58.865 [ItemStateChangedEvent     ] - Detector52_Movement changed from ON to OFF

openhab.log

2017-12-14 08:47:51.334 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 6: Transaction not completed: node address inconsistent.  lastSent=6, incoming=255
2017-12-14 08:47:58.825 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 00 34 02 84 07 46 
2017-12-14 08:47:58.825 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-12-14 08:47:58.825 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 04 00 34 02 84 07 46 
2017-12-14 08:47:58.825 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 08 00 04 00 34 02 84 07 46 
2017-12-14 08:47:58.825 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 34 02 84 07 
2017-12-14 08:47:58.825 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 52: Application Command Request (ALIVE:DONE)
2017-12-14 08:47:58.826 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 52: Starting initialisation from DONE
2017-12-14 08:47:58.826 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@4550c418 already registered
2017-12-14 08:47:58.826 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 52: Incoming command class WAKE_UP
2017-12-14 08:47:58.826 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 52: Received Wake Up Request
2017-12-14 08:47:58.826 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 52: Received WAKE_UP_NOTIFICATION
2017-12-14 08:47:58.826 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 52: Is awake with 2 messages in the wake-up queue.
2017-12-14 08:47:58.826 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
2017-12-14 08:47:58.826 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Got an event from Z-Wave network: ZWaveWakeUpEvent
2017-12-14 08:47:58.826 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-12-14 08:47:58.826 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-12-14 08:47:58.826 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 6: Transaction not completed: node address inconsistent.  lastSent=6, incoming=255
2017-12-14 08:47:58.826 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 34 02 30 02 25 08 CC 
2017-12-14 08:47:58.826 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 52: Sending REQUEST Message = 01 09 00 13 34 02 30 02 25 08 CC 
2017-12-14 08:47:58.835 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
2017-12-14 08:47:58.835 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-12-14 08:47:58.835 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
2017-12-14 08:47:58.835 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
2017-12-14 08:47:58.835 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
2017-12-14 08:47:58.835 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 52: Sent Data successfully placed on stack.
2017-12-14 08:47:58.851 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 08 00 00 02 E1 
2017-12-14 08:47:58.851 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-12-14 08:47:58.851 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 08 00 00 02 00 00 EF 
2017-12-14 08:47:58.851 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 08 00 00 02 00 00 EF 
2017-12-14 08:47:58.851 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=08 00 00 02 
2017-12-14 08:47:58.851 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 52: SendData Request. CallBack ID = 8, Status = Transmission complete and ACK received(0)
2017-12-14 08:47:58.851 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 52: Starting initialisation from DONE
2017-12-14 08:47:58.852 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@4550c418 already registered
2017-12-14 08:47:58.852 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=52, callback=8, payload=34 02 30 02 
2017-12-14 08:47:58.852 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=08 00 00 02 
2017-12-14 08:47:58.852 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=8, expected=ApplicationCommandHandler, cancelled=false      MISMATCH
2017-12-14 08:47:58.862 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 34 03 30 03 00 F6 
2017-12-14 08:47:58.862 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-12-14 08:47:58.862 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 34 03 30 03 00 F6 
2017-12-14 08:47:58.862 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 34 03 30 03 00 F6 
2017-12-14 08:47:58.863 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 34 03 30 03 00 
2017-12-14 08:47:58.863 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 52: Application Command Request (ALIVE:DONE)
2017-12-14 08:47:58.863 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 52: Starting initialisation from DONE
2017-12-14 08:47:58.863 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@4550c418 already registered
2017-12-14 08:47:58.863 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 52: Incoming command class SENSOR_BINARY
2017-12-14 08:47:58.863 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 52: Received SENSOR_BINARY command V2
2017-12-14 08:47:58.863 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 52: Sensor Binary report, type=Unknown, value=0
2017-12-14 08:47:58.863 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveBinarySensorValueEvent
2017-12-14 08:47:58.863 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2017-12-14 08:47:58.863 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_BINARY, value = 0
2017-12-14 08:47:58.863 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Updating channel state zwave:device:AEO_ZW090_C:node52:sensor_binary to OFF [OnOffType]
2017-12-14 08:47:58.864 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=52, callback=8, payload=34 02 30 02 
2017-12-14 08:47:58.864 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 34 03 30 03 00 
2017-12-14 08:47:58.864 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=8, expected=ApplicationCommandHandler, cancelled=false        transaction complete!
2017-12-14 08:47:58.865 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2017-12-14 08:47:58.865 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-12-14 08:47:58.865 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2017-12-14 08:47:58.865 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 52: Response processed after 38ms/4554ms.
2017-12-14 08:47:58.865 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-12-14 08:47:58.865 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 34 02 80 02 25 09 7D 
2017-12-14 08:47:58.865 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 52: Sending REQUEST Message = 01 09 00 13 34 02 80 02 25 09 7D 
2017-12-14 08:47:58.873 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
2017-12-14 08:47:58.873 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-12-14 08:47:58.873 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
2017-12-14 08:47:58.874 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
2017-12-14 08:47:58.874 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
2017-12-14 08:47:58.874 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 52: Sent Data successfully placed on stack.
2017-12-14 08:47:58.889 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 09 00 00 02 E0 
2017-12-14 08:47:58.889 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-12-14 08:47:58.889 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 09 00 00 02 00 00 EE 
2017-12-14 08:47:58.889 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 09 00 00 02 00 00 EE 
2017-12-14 08:47:58.890 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=09 00 00 02 
2017-12-14 08:47:58.890 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 52: SendData Request. CallBack ID = 9, Status = Transmission complete and ACK received(0)
2017-12-14 08:47:58.890 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 52: Starting initialisation from DONE
2017-12-14 08:47:58.890 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@4550c418 already registered
2017-12-14 08:47:58.890 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=52, callback=9, payload=34 02 80 02 
2017-12-14 08:47:58.890 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=09 00 00 02 
2017-12-14 08:47:58.890 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=9, expected=ApplicationCommandHandler, cancelled=false      MISMATCH
2017-12-14 08:47:58.900 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 34 03 80 03 64 22 
2017-12-14 08:47:58.901 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-12-14 08:47:58.901 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 34 03 80 03 64 22 
2017-12-14 08:47:58.901 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 34 03 80 03 64 22 
2017-12-14 08:47:58.901 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 34 03 80 03 64 
2017-12-14 08:47:58.901 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 52: Application Command Request (ALIVE:DONE)
2017-12-14 08:47:58.901 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 52: Starting initialisation from DONE
2017-12-14 08:47:58.901 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@4550c418 already registered
2017-12-14 08:47:58.901 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 52: Incoming command class BATTERY
2017-12-14 08:47:58.901 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 52: Received Battery Request
2017-12-14 08:47:58.901 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 52: Battery report value = 100
2017-12-14 08:47:58.901 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2017-12-14 08:47:58.901 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-12-14 08:47:58.901 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
2017-12-14 08:47:58.902 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Updating channel state zwave:device:AEO_ZW090_C:node52:battery-level to 100 [DecimalType]
2017-12-14 08:47:58.903 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=52, callback=9, payload=34 02 80 02 
2017-12-14 08:47:58.903 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 34 03 80 03 64 
2017-12-14 08:47:58.903 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=9, expected=ApplicationCommandHandler, cancelled=false        transaction complete!
2017-12-14 08:47:58.903 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2017-12-14 08:47:58.903 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 52: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2017-12-14 08:47:58.903 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 52: Response processed after 38ms/4554ms.
2017-12-14 08:47:59.332 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 03 06 31 05 04 22 00 2E CE 
2017-12-14 08:47:59.333 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-12-14 08:47:59.333 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0C 00 04 00 03 06 31 05 04 22 00 2E CE 
2017-12-14 08:47:59.333 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0C 00 04 00 03 06 31 05 04 22 00 2E CE 
2017-12-14 08:47:59.333 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 03 06 31 05 04 22 00 2E 
0 Likes

(Michael) #5

Hi John

Did you solve your problem? I’m in the same situation as you - a newbie with a Philio PSP05 motion sensor which is dificult to get working in OpenHAB.

pls update your findings if any :wink:
Thaks
Michael

0 Likes

(John Butt) #6

Hi Michael,

Unfortunately I still can’t get the Philio PSP05 to trigger an event when motion is detected. I’d be very interested to hear any suggestions on how to debug the issue.

John B

0 Likes

(Alex Forrow) #7

@johnb Your log doesn’t show a command being received about motion being detected. Do you know if the association group is configured for the device? (i.e. telling the device to send motion events to OpenHAB)

@nokyyz What do you mean by ‘there is no event in OpenHab?’ The Detector52_Movement changed message in events.log suggest its all working.

0 Likes

(Marcel Becker) #8

In my openhab.log i only got 2 entries from the Motion Sensor:
2018-01-08 21:42:22.114 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:Razberry2:node22’ has been updated.
2018-01-08 21:42:22.305 [vent.ItemStateChangedEvent] - g_te_bs_motion changed from 0 to 1
2018-01-08 21:42:47.168 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:Razberry2:node22’ has been updated.

Maybe i push the trigger on the backside.

The Motion state switches to “1” but don’t came back to “0”.
…waiting 30 min… but no change of state and no more entries in the openhab.log

My configuration:

How could i get more information from the Motion Senor / Openhab?

0 Likes

(John Butt) #9

Hi Alex,

The device information for the Philio PSP05 shows there’s no association group configured for the device.

Can I setup an association group or does the device database need to be updated? Sorry for the newbie questions.

Thanks,

John B

0 Likes

(Alex Forrow) #10

@Marcello87 Your screenshot suggests you’ve enabled the required option (Motion OFF Reporting). Have you tried waking up the device a few times? (and is ‘Send Report’ still showing as the selected option on that page?)

@johnb The database appears to be incorrect. According to the manual it has two association groups. You should have group 1 set to your controller, though if OpenHAB doesn’t know about the groups, I don’t know how you’d do this. Do you have HABmin installed?

0 Likes

(John Butt) #11

Hi Alex,

I do have HABmin installed and can use it to check the configuration of the PSP05, but I can’t see a way of adding/editing association groups. As you say, it looks like the database needs to be updated. Do you know how this is done?

Thanks,

John B

0 Likes

(Michael) #12

Hi John
I managed to get my PSP05 to work!

In HABmin I changed the ITEM 7 “Notification Type” to BINARY.

It is at little tricky to save the value due to the battery powered PSP05 ! :wink:

  1. change the value in HABmin (dont save!)
  2. push the little thing on the backside of the PSP05
  3. instantly save in HABmin
    4 push the little thing on the backside of the PSP05 again
  4. Hope for the best and check after a couple of minutes.

rg
Michael

0 Likes

(Marcel Becker) #13

Hi Alex,

yes and “Send Report” seems to be fix, it don’t change.

@Michael60: I’ve tried your solution but on the first and second try it don’t save the setting. I will try it again.
How long takes on your setting to save the new configuration, and how near you stood to the zwave controller?

Best regards,
Marcello

0 Likes

(Michael) #14

Hi Marcello

I have usb stick zwave controller, so it was apx. 10 cm away when I paired the devices. But is was mounted and running on the raspberry when I changed the parameters.

I only waited a couple of minutes before is was functioning.

Rg
Michael

0 Likes

(John Butt) #15

Hi Michael,

I’ve managed to change ITEM 7 “Notification Type” to BINARY, but I still don’t get a “motion on” (or “motion off”) log point in /var/log/openhab2/events.log or /var/log/openhab2/ZWave.log or /var/log/openhab2/openhab.log. Do you see entries in one of these logs when the PSP05 detects motion?

Thanks,

John B

0 Likes

(Jörg Schreiner) #16

Hi,
I also have issues in getting this sensor to work.
I dont see any motion logs in the events.log despite motion detection by device led.
Thing is configured as mentioned and items are assigned.

0 Likes

(Nokyyz) #17

Hi all,

I succeeded in configuring my PSP05 sensors to detect motions ! :slight_smile:
To configure the parameter n°7 to “Binary” value, I have used another Zwave software: Home assistant. I have set the “Customer function switch” (parameter 7) to 22 value according to OZW recommandations.
For information, the documentation of this parameter in Home Assistant is:

Customer function switch, using bit control.
Bit 0: Reserve.
Bit 1: Enable sending motion OFF report (0:Disable, 1:Enable). Note: Depends on the Bit4, 0: Report Notification CC, Type: 0x07, Event: 0xFE 1: Sensor Binary Report, Type: 0x0C, Value: 0x00.
Bit 2: Enable PIR super sensitivity mode (0:Disable, 1:Enable).
Bit 3: Reserve.
Bit 4: Notification Type (0: Notification Report, 1: Sensor Binary Report).
Bit 5: Disable Multi CC in auto report (1:Disable, 0:Enable).
Bit 6: Disable to report battery state when the device triggered (1:Disable, 0:Enable)
Bit 7: Reserve.
ozw recommended setting: 00010110 : 22

To force the wake up of sensors, I have pressed once the external button near to the zwave USB controller (and wait 10 seconds).

Regards,
Nokyyz

0 Likes

(Mathias Knop) #18

Did you find a solution to do this with Openhab?

I really like the design of this product but I cannot get it working to report motion.
I already turned on all Z-Wave debugging and motion just doesn’t report anything.

0 Likes

(autoit) #19

Got this sensor as well since it looked like at least some people have got it to work. Unfortunately I’m not so lucky. All I get is the battery level but no motion or tamper, no matter what I try. I’m running openHAB 2.2.0-1. Box says “PSP05-EU-D” and sensor has “20170315” written on it, presumably a date of manufacture?

I can post whatever logs are needed. Surely we should all get this to work somehow. Can @chris advice how to troubleshoot further?

0 Likes

(Chris Jackson) #20

I would suggest to try the latest binding which has better support for the notification class -:

https://community.openhab.org/t/oh2-z-wave-refactoring-and-testing-and-security

Note that this needs to be manually installed (see the first few messages in the thread) and it will need the 2.4 snapshot (or at least 2.3 stable) to run.

If you have problems, then post the debug logs and the XML file generated and I’ll take a look.

0 Likes