Fibaro motion sensor FGMS001 Gen5 (Zwaveplus)

heskja · January 15, 2017, 7:26pm

Any update to this? Have just tried to get my new motion sensor to work, but can’t get any motion events from the sensor.

When adding the device, I see that the Paper UI reports the device as following:

Z-Wave Node 3: FGMS001 Motion Sensor
Unknown Device

Have compared the XML file, and it is similar to the one reported by Edward_Moyse.

The closest I have gotten is that I have seen the alarm_motion-event changed from OFF to ON when I move my hand across the sensor. No binary sensor changes. The alarm_motion changes back to OFF after about a minute, even with motion during that time.

I am also unable to detect the tamper alarm, even if I see the LED blink red, blue and white upon movement.

FraFis · February 5, 2017, 3:26pm

Hi, I can also not include the sensor. It’s unknown.

zwave_class_basic ROUTING_SLAVE
zwave_class_generic SENSOR_NOTIFICATION
zwave_frequent false
zwave_neighbours 1
zwave_version 3.2
zwave_listening false
zwave_plus_devicetype HOME_SECURITY_SENSOR
zwave_deviceid 4097
zwave_nodeid 15
zwave_routing true
zwave_wakeup_time 2017-02-05T15:20:08Z
zwave_beaming true
zwave_class_specific NOTIFICATION_SENSOR
zwave_manufacturer 271
zwave_devicetype 2049

The Logfile:
2017-02-05 16:22:51.651 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 1D 00 49 84 0F 17 04 07 01 5E 20 86 72 5A 59 85 73 84 80 71 56 70 31 8E 22 30 9C 98 7A CA
2017-02-05 16:22:51.658 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-02-05 16:22:53.496 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 1D 00 49 84 0F 17 04 07 01 5E 20 86 72 5A 59 85 73 84 80 71 56 70 31 8E 22 30 9C 98 7A CA
2017-02-05 16:22:53.502 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 1D 00 49 84 0F 17 04 07 01 5E 20 86 72 5A 59 85 73 84 80 71 56 70 31 8E 22 30 9C 98 7A CA
2017-02-05 16:22:53.541 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 0F 17 04 07 01 5E 20 86 72 5A 59 85 73 84 80 71 56 70 31 8E 22 30 9C 98 7A
2017-02-05 16:22:53.543 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 15: Application update request. Node information received.
2017-02-05 16:22:53.545 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 15: Starting initialisation from DONE
2017-02-05 16:22:53.547 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@9e4e0e already registered
2017-02-05 16:22:53.548 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 15: Is awake with 0 messages in the wake-up queue.
2017-02-05 16:22:53.550 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
2017-02-05 16:22:53.552 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Got an event from Z-Wave network: ZWaveWakeUpEvent
2017-02-05 16:22:53.556 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=9, callback=158, payload=09 02 84 08
2017-02-05 16:22:53.561 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 0F 17 04 07 01 5E 20 86 72 5A 59 85 73 84 80 71 56 70 31 8E 22 30 9C 98 7A
2017-02-05 16:22:53.563 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationUpdate, callback id=158, expected=SendData, cancelled=false MISMATCH
2017-02-05 16:22:54.555 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 15: No more messages, go back to sleep
2017-02-05 16:22:54.556 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 15: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2017-02-05 16:22:54.557 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-02-05 16:22:54.557 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-02-05 16:22:54.559 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 0F 02 84 08 25 9F DE
2017-02-05 16:22:54.561 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 15: Sending REQUEST Message = 01 09 00 13 0F 02 84 08 25 9F DE
2017-02-05 16:22:54.572 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
2017-02-05 16:22:54.575 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-02-05 16:22:54.576 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
2017-02-05 16:22:54.577 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
2017-02-05 16:22:54.578 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
2017-02-05 16:22:54.580 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 15: Sent Data successfully placed on stack.
2017-02-05 16:22:54.589 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 9F 00 00 02 76
2017-02-05 16:22:54.592 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-02-05 16:22:54.594 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 9F 00 00 02 00 00 78
2017-02-05 16:22:54.597 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 9F 00 00 02 00 00 78
2017-02-05 16:22:54.599 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=9F 00 00 02
2017-02-05 16:22:54.601 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 15: SendData Request. CallBack ID = 159, Status = Transmission complete and ACK received(0)
2017-02-05 16:22:54.602 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 15: Starting initialisation from DONE
2017-02-05 16:22:54.604 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@9e4e0e already registered
2017-02-05 16:22:54.606 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=15, callback=159, payload=0F 02 84 08
2017-02-05 16:22:54.608 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=9F 00 00 02
2017-02-05 16:22:54.610 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=159, expected=SendData, cancelled=false transaction complete!
2017-02-05 16:22:54.611 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2017-02-05 16:22:54.613 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 15: Went to sleep
2017-02-05 16:22:54.614 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 15: Is sleeping
2017-02-05 16:22:54.615 [DEBUG] [curityCommandClassWithInitialization] - NODE 15: updating lastSentMessageTimestamp
2017-02-05 16:22:54.617 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2017-02-05 16:22:54.618 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 15: Response processed after 56ms/5012ms.
2017-02-05 16:22:55.948 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 00 0F 02 84 07 7D
2017-02-05 16:22:55.951 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-02-05 16:22:55.953 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 04 00 0F 02 84 07 7D
2017-02-05 16:22:55.954 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 08 00 04 00 0F 02 84 07 7D
2017-02-05 16:22:55.957 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0F 02 84 07
2017-02-05 16:22:55.958 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 15: Application Command Request (ALIVE:DONE)
2017-02-05 16:22:55.960 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 15: Starting initialisation from DONE
2017-02-05 16:22:55.961 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@9e4e0e already registered
2017-02-05 16:22:55.963 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 15: Incoming command class WAKE_UP
2017-02-05 16:22:55.964 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 15: Received Wake Up Request
2017-02-05 16:22:55.966 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 15: Received WAKE_UP_NOTIFICATION
2017-02-05 16:22:55.967 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 15: Is awake with 0 messages in the wake-up queue.
2017-02-05 16:22:55.969 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
2017-02-05 16:22:55.970 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Got an event from Z-Wave network: ZWaveWakeUpEvent
2017-02-05 16:22:55.974 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=15, callback=159, payload=0F 02 84 08
2017-02-05 16:22:55.976 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0F 02 84 07
2017-02-05 16:22:55.977 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=159, expected=SendData, cancelled=true MISMATCH
2017-02-05 16:22:56.973 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 15: No more messages, go back to sleep
2017-02-05 16:22:56.974 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 15: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2017-02-05 16:22:56.975 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2017-02-05 16:22:56.975 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-02-05 16:22:56.978 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 0F 02 84 08 25 A0 E1
2017-02-05 16:22:56.980 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 15: Sending REQUEST Message = 01 09 00 13 0F 02 84 08 25 A0 E1
2017-02-05 16:22:56.991 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
2017-02-05 16:22:56.993 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-02-05 16:22:56.994 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
2017-02-05 16:22:56.996 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
2017-02-05 16:22:56.997 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
2017-02-05 16:22:56.998 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 15: Sent Data successfully placed on stack.
2017-02-05 16:22:57.009 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 A0 00 00 02 49
2017-02-05 16:22:57.012 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-02-05 16:22:57.014 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 A0 00 00 02 00 00 47
2017-02-05 16:22:57.016 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 A0 00 00 02 00 00 47
2017-02-05 16:22:57.019 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=A0 00 00 02
2017-02-05 16:22:57.020 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 15: SendData Request. CallBack ID = 160, Status = Transmission complete and ACK received(0)
2017-02-05 16:22:57.020 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 15: Starting initialisation from DONE
2017-02-05 16:22:57.021 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@9e4e0e already registered
2017-02-05 16:22:57.023 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=15, callback=160, payload=0F 02 84 08
2017-02-05 16:22:57.024 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=A0 00 00 02
2017-02-05 16:22:57.025 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=160, expected=SendData, cancelled=false transaction complete!
2017-02-05 16:22:57.026 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2017-02-05 16:22:57.027 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 15: Went to sleep
2017-02-05 16:22:57.027 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 15: Is sleeping
2017-02-05 16:22:57.028 [DEBUG] [curityCommandClassWithInitialization] - NODE 15: updating lastSentMessageTimestamp
2017-02-05 16:22:57.029 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2017-02-05 16:22:57.029 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 15: Response processed after 48ms/5012ms.
2017-02-05 16:22:57.897 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 0F 06 31 05 03 0A 00 30 F3
2017-02-05 16:22:57.900 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-02-05 16:22:57.902 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0C 00 04 00 0F 06 31 05 03 0A 00 30 F3
2017-02-05 16:22:57.905 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0C 00 04 00 0F 06 31 05 03 0A 00 30 F3
2017-02-05 16:22:57.907 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0F 06 31 05 03 0A 00 30
2017-02-05 16:22:57.907 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 15: Application Command Request (ALIVE:DONE)
2017-02-05 16:22:57.908 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 15: Starting initialisation from DONE
2017-02-05 16:22:57.909 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@9e4e0e already registered
2017-02-05 16:22:57.910 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 15: Incoming command class SENSOR_MULTILEVEL
2017-02-05 16:22:57.910 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 15: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V8
2017-02-05 16:22:57.911 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 15: Sensor Multi Level REPORT received
2017-02-05 16:22:57.912 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 15: Sensor Type = Luminance(3), Scale = 1
2017-02-05 16:22:57.913 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 15: Sensor Value = 48
2017-02-05 16:22:57.913 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2017-02-05 16:22:57.914 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2017-02-05 16:22:57.915 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 48
2017-02-05 16:22:57.917 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=15, callback=160, payload=0F 02 84 08
2017-02-05 16:22:57.919 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0F 06 31 05 03 0A 00 30
2017-02-05 16:22:57.919 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=160, expected=SendData, cancelled=false MISMATCH
2017-02-05 16:22:58.057 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 0F 06 31 05 01 22 01 13 FB
2017-02-05 16:22:58.061 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-02-05 16:22:58.064 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0C 00 04 00 0F 06 31 05 01 22 01 13 FB
2017-02-05 16:22:58.065 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0C 00 04 00 0F 06 31 05 01 22 01 13 FB
2017-02-05 16:22:58.068 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0F 06 31 05 01 22 01 13
2017-02-05 16:22:58.068 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 15: Application Command Request (ALIVE:DONE)
2017-02-05 16:22:58.069 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 15: Starting initialisation from DONE
2017-02-05 16:22:58.070 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@9e4e0e already registered
2017-02-05 16:22:58.071 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 15: Incoming command class SENSOR_MULTILEVEL
2017-02-05 16:22:58.072 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 15: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V8
2017-02-05 16:22:58.072 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 15: Sensor Multi Level REPORT received
2017-02-05 16:22:58.073 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 15: Sensor Type = Temperature(1), Scale = 0
2017-02-05 16:22:58.074 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 15: Sensor Value = 27.5
2017-02-05 16:22:58.075 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2017-02-05 16:22:58.075 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2017-02-05 16:22:58.076 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 27.5
2017-02-05 16:22:58.078 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=15, callback=160, payload=0F 02 84 08
2017-02-05 16:22:58.080 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0F 06 31 05 01 22 01 13
2017-02-05 16:22:58.081 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=160, expected=SendData, cancelled=false MISMATCH
2017-02-05 16:22:58.392 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 0F 06 31 05 01 22 01 05 ED
2017-02-05 16:22:58.395 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-02-05 16:22:58.397 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0C 00 04 00 0F 06 31 05 01 22 01 05 ED
2017-02-05 16:22:58.400 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0C 00 04 00 0F 06 31 05 01 22 01 05 ED
2017-02-05 16:22:58.402 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0F 06 31 05 01 22 01 05
2017-02-05 16:22:58.403 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 15: Application Command Request (ALIVE:DONE)
2017-02-05 16:22:58.403 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 15: Starting initialisation from DONE
2017-02-05 16:22:58.404 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@9e4e0e already registered
2017-02-05 16:22:58.405 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 15: Incoming command class SENSOR_MULTILEVEL
2017-02-05 16:22:58.406 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 15: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V8
2017-02-05 16:22:58.406 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 15: Sensor Multi Level REPORT received
2017-02-05 16:22:58.407 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 15: Sensor Type = Temperature(1), Scale = 0
2017-02-05 16:22:58.408 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 15: Sensor Value = 26.1
2017-02-05 16:22:58.409 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2017-02-05 16:22:58.409 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2017-02-05 16:22:58.410 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 26.1
2017-02-05 16:22:58.412 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=15, callback=160, payload=0F 02 84 08
2017-02-05 16:22:58.414 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0F 06 31 05 01 22 01 05
2017-02-05 16:22:58.415 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=160, expected=SendData, cancelled=false MISMATCH

Gerd_Sender · April 14, 2017, 10:25am

@FraFis: Adding the Fibaro Motion Sensor “out of the box” produced an “unknown” thing. So I removed it (Paper UI delete and three button presses on the sensor)

This worked: resetting the sensor (pressing the button until the eye gets yellow), then I searched it with Paper UI inbox. After that I had a sensor in the inbox and added it as a thing. It then showed all channels.

But it does not report anything. All items created show NaN or nothing. No events show in the log.

I found this in the log:

2017-04-14 11:32:07.136 [INFO ] [ome.io.rest.core.thing.ThingResource] - Received HTTP PUT request for update config at 'things/zwave:device:92397a03:node2/config' for the unknown thing 'zwave:device:92397a03:node2'.

2

Paper UI Error
I tried to change parameter 1 to 32 (someone reported this did help) from the Paper UI. This did not work. I found this error in the log:

2017-04-14 11:19:39.640 [INFO ] [ome.io.rest.core.thing.ThingResource] - Received HTTP PUT request for update config at 'things/zwave:device:92397a03:node2/config' for the unknown thing 'zwave:device:92397a03:node2'.
2017-04-14 11:19:39.716 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occured while calling thing updated at ThingHandler 'org.openhab.binding.zwave.handler.ZWaveThingHandler@c939f0': java.lang.NullPointerException
java.util.concurrent.ExecutionException: java.lang.NullPointerException
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)[:1.8.0_121]
	at java.util.concurrent.FutureTask.get(FutureTask.java:206)[:1.8.0_121]
	at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:194)
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:83)
	at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:67)
	at org.eclipse.smarthome.core.thing.internal.ThingManager.thingUpdated(ThingManager.java:506)
	at org.eclipse.smarthome.core.thing.internal.ThingRegistryImpl.notifyTrackers(ThingRegistryImpl.java:227)
	at org.eclipse.smarthome.core.thing.internal.ThingRegistryImpl.notifyListenersAboutUpdatedElement(ThingRegistryImpl.java:150)
	at org.eclipse.smarthome.core.thing.internal.ThingRegistryImpl.notifyListenersAboutUpdatedElement(ThingRegistryImpl.java:1)
	at org.eclipse.smarthome.core.common.registry.AbstractRegistry.updated(AbstractRegistry.java:167)
	at org.eclipse.smarthome.core.common.registry.AbstractProvider.notifyListeners(AbstractProvider.java:57)
	at org.eclipse.smarthome.core.common.registry.AbstractProvider.notifyListenersAboutUpdatedElement(AbstractProvider.java:82)
	at org.eclipse.smarthome.core.common.registry.AbstractManagedProvider.update(AbstractManagedProvider.java:134)
	at org.eclipse.smarthome.io.rest.core.thing.ThingResource.update(ThingResource.java:422)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[:1.8.0_121]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[:1.8.0_121]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.8.0_121]
	at java.lang.reflect.Method.invoke(Method.java:498)[:1.8.0_121]
	at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)[159:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)[159:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)[159:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160)[159:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)[159:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)[159:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)[159:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)[159:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326)[159:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)[158:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)[158:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.internal.Errors.process(Errors.java:315)[158:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.internal.Errors.process(Errors.java:297)[158:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.internal.Errors.process(Errors.java:267)[158:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)[158:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)[159:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)[159:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473)[156:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427)[156:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388)[156:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341)[156:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)[156:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76)[10:com.eclipsesource.jaxrs.publisher:5.3.1.201602281253]
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)[82:org.eclipse.jetty.servlet:9.2.19.v20160908]
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)[82:org.eclipse.jetty.servlet:9.2.19.v20160908]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71)[173:org.ops4j.pax.web.pax-web-jetty:4.3.0]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)[81:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)[80:org.eclipse.jetty.security:9.2.19.v20160908]
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)[81:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)[81:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:287)[173:org.ops4j.pax.web.pax-web-jetty:4.3.0]
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)[82:org.eclipse.jetty.servlet:9.2.19.v20160908]
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)[81:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)[81:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)[81:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80)[173:org.ops4j.pax.web.pax-web-jetty:4.3.0]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)[81:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.Server.handle(Server.java:499)[81:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)[81:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)[81:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)[72:org.eclipse.jetty.io:9.2.19.v20160908]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)[84:org.eclipse.jetty.util:9.2.19.v20160908]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)[84:org.eclipse.jetty.util:9.2.19.v20160908]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
Caused by: java.lang.NullPointerException
	at org.openhab.binding.zwave.handler.ZWaveThingHandler.updateNodeProperties(ZWaveThingHandler.java:1401)[186:org.openhab.binding.zwave:2.1.0.201703310852]
	at org.openhab.binding.zwave.handler.ZWaveThingHandler.bridgeStatusChanged(ZWaveThingHandler.java:457)[186:org.openhab.binding.zwave:2.1.0.201703310852]
	at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialize(ZWaveThingHandler.java:150)[186:org.openhab.binding.zwave:2.1.0.201703310852]
	at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.thingUpdated(BaseThingHandler.java:192)[106:org.eclipse.smarthome.core.thing:0.9.0.201703201701]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$7.call(ThingManager.java:510)[106:org.eclipse.smarthome.core.thing:0.9.0.201703201701]
	at org.eclipse.smarthome.core.thing.internal.ThingManager$7.call(ThingManager.java:1)[106:org.eclipse.smarthome.core.thing:0.9.0.201703201701]
	at org.eclipse.smarthome.core.common.SafeMethodCaller$CallableWrapper.call(SafeMethodCaller.java:181)[99:org.eclipse.smarthome.core:0.9.0.201703201701]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_121]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_121]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_121]
	... 1 more

Changing the parameter with HABMin seems to work.

Still OpenHAB does not show any values from the sensor. Any suggestions what I could try? Thanks.

sihui · April 14, 2017, 2:50pm

I think you messed up your config:

You deleted the thing from openHAB, not the sensor from the controller.

This added the sensor again to your controller, because that performed a new network inclusion, but because the “old” sensor is still referenced in openHAB, you get that error message.

You have to remove all the old references from your first attempt (things, channels, items), then start new with the newly included sensor, add the thing, bind your items to the available channels.

Gerd_Sender · April 16, 2017, 9:52am

@sihui: I think everything worked after the second try. It just took some time for the values (temperature, lux) to show up. Pressing the button made the values immeadiatly available. The motion detection does not show up in the Paper UI, but I expected this.

Summary:

Rresetting the Firbaro Motion Sensor first and then adding it was successful.
When the sensor shows up as unknown: first removing it from the network (with three button presses) and second deleting all reference in Paper UI and third adding it again showed all channels.

How to see motion detection: add a channel for motion detection and then look into the events.log.

tail -f /var/log/openhab2/events.log

ohmicha · June 5, 2017, 10:59am

I found this topic right after I described my own similar problems. Did anyone got the sensor working as expected?

sihui · June 5, 2017, 11:03am

Yes, works since almost three years with all available zwave bindings.

Wake the device up (press the inside button three times quickly) and wait for completing initialization. Do that in close range to the controller.

ohmicha · June 5, 2017, 11:17am

Thank you for the tip, I woke up the device and corresponding to the initialization was completed

I am not able to paste or upload full log here, is there anything in the log that I can look for?

13:05:03.601 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 1D 00 49 84 02 17 04 07 01 5E 20 86 72 5A 59 85 73 84 80 71 56 70 31 8E 22 30 9C 98 7A C7 
13:05:03.602 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
13:05:03.602 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 1D 00 49 84 02 17 04 07 01 5E 20 86 72 5A 59 85 73 84 80 71 56 70 31 8E 22 30 9C 98 7A C7 
13:05:03.603 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 1D 00 49 84 02 17 04 07 01 5E 20 86 72 5A 59 85 73 84 80 71 56 70 31 8E 22 30 9C 98 7A C7 
13:05:03.603 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 02 17 04 07 01 5E 20 86 72 5A 59 85 73 84 80 71 56 70 31 8E 22 30 9C 98 7A 
13:05:03.603 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 2: Application update request. Node information received.
13:05:03.604 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
13:05:03.604 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@269bc29c already registered
13:05:03.604 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Is awake with 6 messages in the wake-up queue.
13:05:03.604 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
13:05:03.605 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
13:05:03.605 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
13:05:03.605 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=2, callback=226, payload=02 02 84 08 
13:05:03.605 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 02 02 30 02 25 E9 1B 
13:05:03.606 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 2: Sending REQUEST Message = 01 09 00 13 02 02 30 02 25 E9 1B 
13:05:03.606 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 02 17 04 07 01 5E 20 86 72 5A 59 85 73 84 80 71 56 70 31 8E 22 30 9C 98 7A 
13:05:03.606 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationUpdate, callback id=226, expected=SendData, cancelled=false      MISMATCH
13:05:03.614 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
13:05:03.614 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
13:05:03.614 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
13:05:03.615 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
13:05:03.615 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
13:05:03.615 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: Sent Data successfully placed on stack.
13:05:03.629 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 E9 00 00 02 00 
13:05:03.630 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
13:05:03.630 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 E9 00 00 02 00 00 0E 
13:05:03.631 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 E9 00 00 02 00 00 0E 
13:05:03.631 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=E9 00 00 02 
13:05:03.631 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: SendData Request. CallBack ID = 233, Status = Transmission complete and ACK received(0)
13:05:03.631 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
13:05:03.632 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@269bc29c already registered
13:05:03.632 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=2, callback=233, payload=02 02 30 02 
13:05:03.632 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=E9 00 00 02 
13:05:03.632 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=233, expected=ApplicationCommandHandler, cancelled=false      MISMATCH
13:05:03.641 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 02 03 30 03 FF 3F 
13:05:03.641 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
13:05:03.642 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 02 03 30 03 FF 3F 
13:05:03.642 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 02 03 30 03 FF 3F 
13:05:03.642 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 03 30 03 FF 
13:05:03.642 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
13:05:03.643 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
13:05:03.643 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@269bc29c already registered
13:05:03.643 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class SENSOR_BINARY
13:05:03.643 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 2: Received SENSOR_BINARY command V1
13:05:03.643 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 2: Sensor Binary report, type=Unknown, value=255
13:05:03.644 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveBinarySensorValueEvent
13:05:03.644 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=2, callback=233, payload=02 02 30 02 
13:05:03.644 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 03 30 03 FF 
13:05:03.644 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=233, expected=ApplicationCommandHandler, cancelled=false        transaction complete!
13:05:03.645 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
13:05:03.645 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
13:05:03.645 [DEBUG] [curityCommandClassWithInitialization] - NODE 2: updating lastSentMessageTimestamp
13:05:03.645 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 2: Response processed after 39ms/1664ms.
13:05:03.646 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
13:05:03.646 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0B 00 13 02 04 31 04 01 00 25 EA 1A 
13:05:03.646 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 2: Sending REQUEST Message = 01 0B 00 13 02 04 31 04 01 00 25 EA 1A 
13:05:03.654 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
13:05:03.654 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
13:05:03.655 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
13:05:03.655 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
13:05:03.656 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
13:05:03.656 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: Sent Data successfully placed on stack.
13:05:03.670 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 EA 00 00 02 03 
13:05:03.671 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
13:05:03.671 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 EA 00 00 02 00 00 0D 
13:05:03.672 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 EA 00 00 02 00 00 0D 
13:05:03.672 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=EA 00 00 02 
13:05:03.672 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: SendData Request. CallBack ID = 234, Status = Transmission complete and ACK received(0)
13:05:03.672 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
13:05:03.673 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@269bc29c already registered
13:05:03.673 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=2, callback=234, payload=02 04 31 04 01 00 
13:05:03.673 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=EA 00 00 02 
13:05:03.674 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=234, expected=ApplicationCommandHandler, cancelled=false      MISMATCH
13:05:03.682 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 02 06 31 05 01 22 00 E8 0C 
13:05:03.682 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
13:05:03.683 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0C 00 04 00 02 06 31 05 01 22 00 E8 0C 
13:05:03.683 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0C 00 04 00 02 06 31 05 01 22 00 E8 0C 
13:05:03.684 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 06 31 05 01 22 00 E8 
13:05:03.684 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
13:05:03.684 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
13:05:03.684 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@269bc29c already registered
13:05:03.684 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class SENSOR_MULTILEVEL
13:05:03.685 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V8
13:05:03.685 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Multi Level REPORT received
13:05:03.685 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Type = Temperature(1), Scale = 0
13:05:03.685 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Value = 23.2
13:05:03.686 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
13:05:03.686 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=2, callback=234, payload=02 04 31 04 01 00 
13:05:03.686 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 06 31 05 01 22 00 E8 
13:05:03.686 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=234, expected=ApplicationCommandHandler, cancelled=false        transaction complete!
13:05:03.687 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
13:05:03.687 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
13:05:03.687 [DEBUG] [curityCommandClassWithInitialization] - NODE 2: updating lastSentMessageTimestamp
13:05:03.687 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 2: Response processed after 40ms/1664ms.
13:05:03.687 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
13:05:03.688 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0B 00 13 02 04 31 04 19 00 25 EB 03 
13:05:03.688 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 2: Sending REQUEST Message = 01 0B 00 13 02 04 31 04 19 00 25 EB 03 
13:05:03.696 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
13:05:03.696 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
13:05:03.697 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
13:05:03.697 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
13:05:03.697 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
13:05:03.698 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: Sent Data successfully placed on stack.
13:05:03.712 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 EB 00 00 03 03 
13:05:03.713 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
13:05:03.713 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 EB 00 00 03 00 00 0D 
13:05:03.713 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 EB 00 00 03 00 00 0D 
13:05:03.714 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=EB 00 00 03 
13:05:03.714 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: SendData Request. CallBack ID = 235, Status = Transmission complete and ACK received(0)
13:05:03.714 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
13:05:03.715 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@269bc29c already registered
13:05:03.715 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=2, callback=235, payload=02 04 31 04 19 00 
13:05:03.715 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=EB 00 00 03 
13:05:03.715 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=235, expected=ApplicationCommandHandler, cancelled=false      MISMATCH

13:05:46.604 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
13:05:46.604 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@269bc29c already registered
13:05:46.605 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class SENSOR_MULTILEVEL
13:05:46.605 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V8
13:05:46.605 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Multi Level REPORT received
13:05:46.606 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Type = Luminance(3), Scale = 1
13:05:46.606 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Value = 13
13:05:46.606 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
13:05:46.607 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=2, callback=240, payload=02 02 84 08 
13:05:46.608 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 06 31 05 03 0A 00 0D 
13:05:46.608 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=240, expected=SendData, cancelled=false      MISMATCH

but still the motion alarm is not sent - even as it is detected (sensor flashing) - and the values for temperature and battery are still empty.

sihui · June 5, 2017, 11:27am

Load your debug log into the Zwave log viewer:
http://www.cd-jackson.com/index.php/openhab/zwave-log-viewer
it’s much easier to read:

Actually it looks fine, data is coming in.

Verify you have the correct channels linked to your items:

Number	FibEye1_Battery	"Motion Sensor: [%d %%]"	<battery>	(gBattery,gInfluxdb) {channel="zwave:device:158b44ebf65:node3:battery-level"}
Switch	FibEye1_Motion_S	"Motion Hallway up [%s]" <motion> (gRestore) {channel="zwave:device:158b44ebf65:node3:sensor_binary"}

ohmicha · June 5, 2017, 11:46am

OK thank you, great tool!
I removed all my items and recreated them, then I woke up device again as you described. So now at least values for all sensors are shown and the motion alert is fired. I will observe if they are updated as expected.

chimera · July 11, 2017, 5:40am

I have the same problems as others have had in this post. I’ve followed the same steps, but cannot get events logging for motion. I had to remove from PaperUI, remove from ZWave stick, then include again for it to show up correctly. If I edit the thing in PaperUI, then change say, parameter 1 to 30, then click to Save, it says at the bottom right of the GUI:

"Thing updated"
and then 1 second later:
“HTTP: 500 - Internal Server Error”

and in the openhab.log I get:

2017-07-11 17:26:46.905 [ERROR] [ome.io.rest.core.thing.ThingResource] - Exception during HTTP PUT request for update config at ‘things/zwave:device:fbcf2efa:node13/config’ for thing ‘zwave:device:fbcf2efa:node13’: For input string: “org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@55f01b”

I’ve been going around in circles with this for ages and am now at a loss on what to do next. I don’t think I need to exclude/include again, as it picks it up with all the parameters fine in PaperUI.

chris · July 11, 2017, 6:31am

I would strongly recommend not to use PaperUI for configuring ZWave - it does a number of strange things and doesn’t handle some constructs properly.

Dim · July 11, 2017, 6:34am

I can confirm…
I always use HABmin to modify my Z-Wave nodes (things) configuration parameters…
PaperUI almost always gives me troubles (I have the same device: FGMS001)

chimera · July 11, 2017, 10:04am

Thanks, and totally agree… if I could get HABMin to load. It just sits there saying “Loading…” and never does.

chris · July 11, 2017, 10:05am

Check the console log in the browser debugger to find out what’s happening then…

chimera · July 11, 2017, 10:07am

Just got a response in another thread, “delete browser cache” - instead I tried Firefox instead of Chrome, and it goes STRAIGHT in no issues! Here I was looking into the deep dark depths of configuration problems… gah! Thanks Chris!

chimera · July 11, 2017, 10:04pm

I now have it to a stage where I can get alarm, tamper, temperature and LUX recording event changes in events.log file. In HABMin, Configuration/Things/FGMS001 Motion Sensor/Description, I can see these show “Alarm” (on the right side) against the channels if I pickup or “tamper with” the sensor (and they show “Ok” under normal use)

I can also see items related to the binary sensor that I created.

I have the .items file populated with the following entries:

// Sensor
Switch          masterWardrobeAlarm             "Alarm [%s]"                         <fire>                             { channel="zwave:device:fbcf2efa:node14:alarm_motion" }
Switch          masterWardrobeTamper            "Tamper [%s]"                        <tamper>                           { channel="zwave:device:fbcf2efa:node14:alarm_tamper" }
Switch          masterWardrobeSensor            "Movement [%s]"                      <sensor>                           { channel="zwave:device:fbcf2efa:node14:sensor_binary" }
Number          masterWardrobeLUX               "LUX [%.2f Lux]"                     <sun>                              { channel="zwave:device:fbcf2efa:node14:sensor_luminance" }
Number          masterWardrobeBattery           "Battery [%d %%]"                    <energy>                           { channel="zwave:device:fbcf2efa:node14:battery-level" }
Number          masterWardrobeTemp              "Temperature [%.1f C]"               <temperature>                      { channel="zwave:device:fbcf2efa:node14:sensor_temperature" }

I cannot get the sensor to provide any feedback on movement events.

I have spent 4 days trying to get this working and am at a complete loss as to why the channels appear to be properly linked to the items, but they do not respond.

Any ideas at all would be appreciated.

EDIT: I DID have it reporting LUX, after I clicked refresh items in HABmin, it now only responds to tamper and alarm. But I get this in the logs:

2017-07-12 10:43:43.320 [ItemCommandEvent ] - Item ‘masterWardrobeLUX’ received command REFRESH
2017-07-12 10:43:43.325 [ItemCommandEvent ] - Item ‘masterWardrobeSensor’ received command REFRESH
2017-07-12 10:43:43.423 [ItemCommandEvent ] - Item ‘masterWardrobeAlarm’ received command REFRESH
2017-07-12 10:43:43.448 [ItemCommandEvent ] - Item ‘masterWardrobeTemp’ received command REFRESH
2017-07-12 10:43:43.513 [ItemCommandEvent ] - Item ‘masterWardrobeTamper’ received command REFRESH
2017-07-12 10:43:43.555 [ItemCommandEvent ] - Item ‘masterWardrobeBattery’ received command REFRESH

Attached is the zwave node.xml file
node14.xml (22.2 KB)

Additionally, if I triple click the device it wakes up the device and I will get some feedback on LUX and temp. But then it goes back to sleep and I get nothing after that (LUX and temp won’t report changes)

2017-07-12 10:50:16.500 [ItemStateChangedEvent ] - masterWardrobeLUX changed from 23 to 36
2017-07-12 10:50:16.680 [ItemStateChangedEvent ] - masterWardrobeTemp changed from 19.9 to 19.8
2017-07-12 10:50:19.499 [ItemStateChangedEvent ] - masterWardrobeLUX changed from 36 to 283
2017-07-12 10:50:27.666 [ItemStateChangedEvent ] - Date changed from 2017-07-12T10:49:27.534+1200 to 2017-07-12T10:50:27.534+1200
2017-07-12 10:50:33.865 [ItemStateChangedEvent ] - masterWardrobeLUX changed from 283 to 3

And this is what I see in HABmin. Binary Sensor always says triggered no matter what.

Moving my hand in front of the sensor, the alarm motion gets triggered - not the binary sensor. Therefore would this most likely indicate an issue on the OpenHAB side??? If so, what?

chimera · July 12, 2017, 12:18am

Hmmm, when I declared my items, I never really revisited them when troubleshooting this… I’ve been looking at sensor binary all this time and trying to get events triggered on this.

I’ve just looked now and noticed the “alarm_motion” event, whereas others above do not seem to declare that and rely on sensor binary for movement. I’ve changed my items to the following, and will just use “masterWardrobeSensor” for ON/OFF events to trigger the wardrobe lights. I’ve removed sensor binary mapping to an item completely.

Switch masterWardrobeTamper “Tamper [%s]” { channel=“zwave:device:fbcf2efa:node14:alarm_tamper” }
Switch masterWardrobeSensor “Movement [%s]” { channel=“zwave:device:fbcf2efa:node14:alarm_motion” }
Number masterWardrobeLUX “LUX [%.2f Lux]” { channel=“zwave:device:fbcf2efa:node14:sensor_luminance” }
Number masterWardrobeBattery “Battery [%d %%]” { channel=“zwave:device:fbcf2efa:node14:battery-level” }
Number masterWardrobeTemp “Temperature [%.1f C]” { channel=“zwave:device:fbcf2efa:node14:sensor_temperature” }

Dim · July 12, 2017, 4:11am

In firmware version 2.8 of the FGMS001 (node2.xml) I don’t have this channel (sensor_binary). It seems that this exists only in version >3.2

Anyway, I use the alarm_motion channel to get movement events and it works fine.
I personally, use a Number item and then define my rule as:

ZWave.items:

/* Fibaro Sensors */
Number	FibEye01_Movement	"FE01 Movement: [%s]"			<present>		(gZWave)	{channel="zwave:device:ZW090C:node2:alarm_motion"}
Number	FibEye01_Temp		"FE01 Temperature: [%.2f °C]"	<temperature>	(gZWave)	{channel="zwave:device:ZW090C:node2:sensor_temperature"}
Number	FibEye01_Lux		"FE01 Lux: [%.2f Lux]"			<sun>			(gZWave)	{channel="zwave:device:ZW090C:node2:sensor_luminance"}
Number	FibEye01_Bat		"FE01 Battery [%d %%]"			<battery>		(gZWave)	{channel="zwave:device:ZW090C:node2:battery-level"}
Number	FibEye01_Alarm		"FE01 Alarm: [%s]"				<fire>			(gZWave)	{channel="zwave:device:ZW090C:node2:alarm_tamper"}

example rule:

var	Timer	FE01_Timer = null
val	Integer	FE01_TimeOut = 5

rule "FE01_ON" // FibEye01 motion detection turns ON Staircase LEDs when dark
when
	Item FibEye01_Movement changed from 0 to 1
then
	if (FibEye01_Lux.state < 80 ) {
		if (FE01_Timer != null) {
			WDim01_Dim.sendCommand(100)
			logInfo("FE01","FE01 Timer rescheduled for " + FE01_TimeOut + " minutes")
			FE01_Timer.reschedule(now.plusMinutes(FE01_TimeOut))
		} else {
			logInfo("FE01", "FE01 Motion Detected! Turn ON Staircase LEDs")
			WDim01_Dim.sendCommand(100)
			logInfo("FE01","FE01 Timer created with " + FE01_TimeOut + " minutes")
			FE01_Timer = createTimer(now.plusMinutes(FE01_TimeOut))
			[|
				if (FibEye01_Movement.state ==  1) {
					logInfo("FE01","FE01 Timer triggered, but rescheduled again for " + FE01_TimeOut + " minutes")
					FE01_Timer.reschedule(now.plusMinutes(FE01_TimeOut))
				} else {
					logInfo("FE01", "FE01 No Motion Detected! Turn OFF Staircase LEDs")
					WDim01_Dim.sendCommand(0)
					FE01_Timer = null
				}
			]
		}
	}
end

Of course, you can use a Switch type for alarm_motion and then use changed from OFF to ON

chimera · July 12, 2017, 4:23am

Thanks, yeah I just setup this similar - in my case its simply a sensor in the wardrobe that switches on the lights… because I’m too lazy to reach 0.5m away and flick a switch…

I did my rule similar, although used switches and did separate rules. It uses the configuration parameter 6 (“motion detection - alarm cancellation delay”) which I set to 40 (seconds) - which is when it automatically switches back to OFF triggering the 2nd rule, which simply turns off the light (don’t like timers had issues with them, it doesn’t give me the reschedule option you have but eh, its only a wardrobe)

//
// Wardrobe SENSOR - activation
//

rule "Master Wardrobe Movement activated"
when
    	Item masterWardrobeSensor changed from OFF to ON
then
	if (swSystemBootUp.state == OFF) {
		if (masterWardrobeLight.state == OFF) 	{
			if (masterWardrobeLUX.state <= 100) {
				logInfo("wardrobe sensor", "Turning Wardrobe Light ON")
				sendCommand(masterWardrobeLight, ON)
			}
			else {
				logInfo("wardrobe sensor", "Not turning on, sufficient light detected")
			}
		}
		else {
			logInfo("wardrobe sensor", "Not turning on, wardrobe light already on")
		}
	}
	else {
		logInfo("wardrobe sensor", "Wardrobe sensor got triggered, doing nothing because booting up")
	}
end


//
// Wardrobe SENSOR - deactivation
//

rule "Master Wardrobe Movement deactivated - after 30 seconds"
when
    	Item masterWardrobeSensor changed from ON to OFF
then
	if (swSystemBootUp.state == OFF) {
		sendCommand(masterWardrobeLight, OFF)
	}
end