Motion sensor light configuration using BASIC_SET in Habmin

I have a motion sensor that I have linked to a light in Habmin using the target nodes receiving BASIC_SET command. The basic set value is 1, the re-trigger value is 30 and duration is 60. I’m assuming those values are in minutes. If I trigger the motion sensor, the light turns on but only remains on for approximately 10 seconds. I’ve changed the duration value to the maximum and in still only stays on for 10 seconds. Am I approaching the configuration incorrectly or missing a step?

Also, I’m not sure why the pending message remains, it goes away if I restart the openhab2 service but the issue remains

The “pending…” means the message is queued but has not been sent to the device yet. When you restart OH, the queue is destroyed (because it’s memory based).

In order for the new config to be applied, you need to wake up the device, which will trigger the zwave binding to send the queued message(s) to the device. The wake up method is different from device to device, but it normally involves a button press (or multiple button presses) on the device. The device manual should indicate how you manually wake it up.

If you don’t manually wake it up, most battery-powered devices wake up on their own every few hours, at which point the queued messages will be sent (unless you restart OH before the device wakes up).

Thanks, that makes sense. I’ve woken up the sensor, still says pending, but I’ll keep playing with it and see if I can get the settings to stick.

Am I correct in understanding the re-trigger setting to be the minutes before triggering another motion event? If so, it would make sense to have the re-trigger less than the on-off duration.

I’m not sure which sensor you’re using, so I’m not sure about your device. For the motion sensors I have (Aeon ZW100 and Fibaro FGMS001), the reset time is in seconds.

I have an Everspring HSP02. I cannot get my configuration to apply. The on-off duration doesn’t say pending anymore but hasn’t changed the actual behavior. The retrigger interval still says pending. Is there a way to force a configuration with command line or some other method?

If you can put the zwave binding into debug mode, you should see some activity for that node when you manually wake up the device.

I took a look at the manual. It says the retrigger time is in seconds.

Having skimmed the manual, it doesn’t look like there’s a way to manually wake up the device, other than when it detects motion. So… If there’s a command queued to change the retrigger time, it should be sent to the device when the device detects motion.

I also see the default wakeup interval is 1 day, which is a pretty long time to wait for the device to wake up…

The detector stays in sleep status for the majority of time in order to conserve
battery life. However, it can be woken up by either triggers of movement or
by setting WAKE_UP_INTERVAL_SET command via Z-Wave Controller.
After the unit wakes up, it will send Wakeup Notification Command to the node
ID that requires to be reported. The minimum and maximum wakeup interval is
60 seconds and 194 days respectively. Allowable interval among each wakeup
interval is 1 second, such as 60, 61, 62 ….
Note: The default value is 1 day, which implies that the detector awakes and
sends the Wakeup Notification Command to the set node every day. 

I have the paper manual, I can wake it up by opening it and clicking the button. I can see in habmin that the last wake time is changing accordingly. It’s just not taking the settings. I’ll put it in debug and see if I can get anymore information.

Once you get a debug log, go to @chris’s log viewer. It’ll show what’s happening much more clearly than reading the log file. After you import the log file, filter by the node number of the HSP02 device and it’ll show just the transactions for that device.

Here’s my log excerpt when trying to apply changes to the motion sensor (node2).
My process was:

  1. Change re-trigger and on-off duration without saving
  2. Wake up motion sensor
  3. Click save.

Sometimes pending disappears from one of the settings but neither ever actually change

2017-05-24 21:19:08.362 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 00 02 02 84 07 70 
    2017-05-24 21:19:08.364 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
    2017-05-24 21:19:08.364 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 04 00 02 02 84 07 70 
    2017-05-24 21:19:08.364 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 08 00 04 00 02 02 84 07 70 
    2017-05-24 21:19:08.364 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 02 84 07 
    2017-05-24 21:19:08.364 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
    2017-05-24 21:19:08.364 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
    2017-05-24 21:19:08.364 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@40f6d798 already registered
    2017-05-24 21:19:08.364 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class WAKE_UP
    2017-05-24 21:19:08.364 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Received Wake Up Request
    2017-05-24 21:19:08.364 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Received WAKE_UP_NOTIFICATION
    2017-05-24 21:19:08.364 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Is awake with 0 messages in the wake-up queue.
    2017-05-24 21:19:08.364 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
    2017-05-24 21:19:08.365 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveWakeUpEvent
    2017-05-24 21:19:08.365 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 255: Transaction not completed: node address inconsistent.  lastSent=255, incoming=255
    2017-05-24 21:19:09.061 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Configuration update received
    2017-05-24 21:19:09.067 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Configuration update config_6_1 to 200
    2017-05-24 21:19:09.067 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 2: Creating new message for application command CONFIGURATIONCMD_SET
    2017-05-24 21:19:09.068 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
    2017-05-24 21:19:09.068 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0C 00 13 02 05 70 04 06 01 C8 25 55 2C 
    2017-05-24 21:19:09.068 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 2: Sending REQUEST Message = 01 0C 00 13 02 05 70 04 06 01 C8 25 55 2C 
    2017-05-24 21:19:09.068 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 0. Queue={}
    2017-05-24 21:19:09.068 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 2: Creating new message for application command CONFIGURATIONCMD_GET
    2017-05-24 21:19:09.069 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
    2017-05-24 21:19:09.088 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
    2017-05-24 21:19:09.090 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
    2017-05-24 21:19:09.090 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
    2017-05-24 21:19:09.090 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
    2017-05-24 21:19:09.090 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
    2017-05-24 21:19:09.090 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: Sent Data successfully placed on stack.
    2017-05-24 21:19:09.104 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 05 00 13 55 00 BC 
    2017-05-24 21:19:09.107 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
    2017-05-24 21:19:09.107 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 13 55 00 00 00 BE 
    2017-05-24 21:19:09.107 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 13 55 00 00 00 BE 
    2017-05-24 21:19:09.107 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=55 00 
    2017-05-24 21:19:09.107 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: SendData Request. CallBack ID = 85, Status = Transmission complete and ACK received(0)
    2017-05-24 21:19:09.107 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
    2017-05-24 21:19:09.107 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@40f6d798 already registered
    2017-05-24 21:19:09.107 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Config, dest=2, callback=85, payload=02 05 70 04 06 01 C8 
    2017-05-24 21:19:09.107 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=55 00 
    2017-05-24 21:19:09.107 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=85, expected=SendData, cancelled=false        transaction complete!
    2017-05-24 21:19:09.107 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
    2017-05-24 21:19:09.107 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
    2017-05-24 21:19:09.108 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 2: Response processed after 36ms/3563ms.
    2017-05-24 21:19:09.108 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
    2017-05-24 21:19:09.108 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 02 03 70 05 06 25 56 E7 
    2017-05-24 21:19:09.108 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 2: Sending REQUEST Message = 01 0A 00 13 02 03 70 05 06 25 56 E7 
    2017-05-24 21:19:09.120 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
    2017-05-24 21:19:09.124 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
    2017-05-24 21:19:09.124 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
    2017-05-24 21:19:09.124 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
    2017-05-24 21:19:09.124 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
    2017-05-24 21:19:09.124 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: Sent Data successfully placed on stack.
    2017-05-24 21:19:09.172 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 05 00 13 56 00 BF 
    2017-05-24 21:19:09.174 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
    2017-05-24 21:19:09.174 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 13 56 00 00 00 BD 
    2017-05-24 21:19:09.174 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 13 56 00 00 00 BD 
    2017-05-24 21:19:09.174 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=56 00 
    2017-05-24 21:19:09.174 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: SendData Request. CallBack ID = 86, Status = Transmission complete and ACK received(0)
    2017-05-24 21:19:09.174 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
    2017-05-24 21:19:09.175 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@40f6d798 already registered
    2017-05-24 21:19:09.175 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Config, dest=2, callback=86, payload=02 03 70 05 06 
    2017-05-24 21:19:09.175 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=56 00 
    2017-05-24 21:19:09.175 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=86, expected=ApplicationCommandHandler, cancelled=false      MISMATCH
    2017-05-24 21:19:09.636 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0B 00 04 00 02 05 70 06 06 01 0F 89 
    2017-05-24 21:19:09.638 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
    2017-05-24 21:19:09.638 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0B 00 04 00 02 05 70 06 06 01 0F 89 
    2017-05-24 21:19:09.638 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0B 00 04 00 02 05 70 06 06 01 0F 89 
    2017-05-24 21:19:09.638 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 05 70 06 06 01 0F 
    2017-05-24 21:19:09.638 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
    2017-05-24 21:19:09.638 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
    2017-05-24 21:19:09.638 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@40f6d798 already registered
    2017-05-24 21:19:09.638 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class CONFIGURATION
    2017-05-24 21:19:09.638 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 2: Received Configuration Request
    2017-05-24 21:19:09.638 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 2: Node configuration report, parameter = 6, value = 15, size = 1
    2017-05-24 21:19:09.638 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveConfigurationParameterEvent
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveConfigurationParameterEvent
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = CONFIGURATION, value = org.openhab.binding.zwave.internal.protocol.ZWaveConfigurationParameter@106bbbe2
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Update CONFIGURATION 6/1 to 15
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Config about to update 37 parameters...
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@224daf43
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@71689ccc
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@46a4fc54
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@3b45bec6
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@3554a220
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@19f3b7ac
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_1
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_2
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@2961c173
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing action_reinit
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing wakeup_node
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@51b30bd7
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@1bcb0854
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@5e93ce49
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@67a88e2e
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@4db00ef0
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@17ad4305
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@318553cf
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@14b18725
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing action_failed
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@1b15df5d
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing wakeup_interval
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing action_remove
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing binding_pollperiod
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing action_heal
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_1_1
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_1_1 len=3
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_1_1 - id = '1'
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_2_1
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_2_1 len=3
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_2_1 - id = '2'
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@22aa1cbf
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@2c8a54a2
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@3849a39d
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@27922f65
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@65a6cf0b
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_3_1
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_3_1 len=3
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_3_1 - id = '3'
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_4_1
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_4_1 len=3
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_4_1 - id = '4'
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_5_1
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_5_1 len=3
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_5_1 - id = '5'
    2017-05-24 21:19:09.638 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_6_1
    2017-05-24 21:19:09.639 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_6_1 len=3
    2017-05-24 21:19:09.639 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_6_1 - id = '6'
    2017-05-24 21:19:09.639 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing config_6_1 - size = '1'
    2017-05-24 21:19:09.639 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Sub-parameter config_6_1 is 0000000F
    2017-05-24 21:19:09.639 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Pre-processing  0000000F>>FFFFFFFF
    2017-05-24 21:19:09.639 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Post-processing 0000000F>>FFFFFFFF
    2017-05-24 21:19:09.639 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Sub-parameter setting config_6_1 is 0000000F [15]
    2017-05-24 21:19:09.639 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@2fe130f3
    2017-05-24 21:19:09.639 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Config, dest=2, callback=86, payload=02 03 70 05 06 
    2017-05-24 21:19:09.639 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 05 70 06 06 01 0F 
    2017-05-24 21:19:09.639 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=86, expected=ApplicationCommandHandler, cancelled=false        transaction complete!
    2017-05-24 21:19:09.639 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
    2017-05-24 21:19:09.639 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
    2017-05-24 21:19:09.639 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 2: Response processed after 530ms/3563ms.
    2017-05-24 21:19:10.639 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: No more messages, go back to sleep
    2017-05-24 21:19:10.639 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
    2017-05-24 21:19:10.639 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
    2017-05-24 21:19:10.639 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
    2017-05-24 21:19:10.639 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 02 02 84 08 25 57 1B 
    2017-05-24 21:19:10.639 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 2: Sending REQUEST Message = 01 09 00 13 02 02 84 08 25 57 1B 
    2017-05-24 21:19:10.657 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
    2017-05-24 21:19:10.659 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
    2017-05-24 21:19:10.659 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
    2017-05-24 21:19:10.659 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
    2017-05-24 21:19:10.659 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
    2017-05-24 21:19:10.659 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: Sent Data successfully placed on stack.
    2017-05-24 21:19:10.677 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 05 00 13 57 00 BE 
    2017-05-24 21:19:10.681 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
    2017-05-24 21:19:10.681 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 13 57 00 00 00 BC 
    2017-05-24 21:19:10.681 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 13 57 00 00 00 BC 
    2017-05-24 21:19:10.681 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=57 00 
    2017-05-24 21:19:10.681 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: SendData Request. CallBack ID = 87, Status = Transmission complete and ACK received(0)
    2017-05-24 21:19:10.681 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
    2017-05-24 21:19:10.681 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@40f6d798 already registered
    2017-05-24 21:19:10.681 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=2, callback=87, payload=02 02 84 08 
    2017-05-24 21:19:10.681 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=57 00 
    2017-05-24 21:19:10.681 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=87, expected=SendData, cancelled=false        transaction complete!
    2017-05-24 21:19:10.681 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
    2017-05-24 21:19:10.681 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Went to sleep
    2017-05-24 21:19:10.681 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Is sleeping
    2017-05-24 21:19:10.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
    2017-05-24 21:19:10.681 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 2: Response processed after 40ms/3563ms.
    2017-05-24 21:19:16.890 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 00 02 02 84 07 70 
    2017-05-24 21:19:16.894 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
    2017-05-24 21:19:16.894 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 04 00 02 02 84 07 70 
    2017-05-24 21:19:16.894 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 08 00 04 00 02 02 84 07 70 
    2017-05-24 21:19:16.894 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 02 84 07 
    2017-05-24 21:19:16.894 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
    2017-05-24 21:19:16.894 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
    2017-05-24 21:19:16.894 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@40f6d798 already registered
    2017-05-24 21:19:16.894 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class WAKE_UP
    2017-05-24 21:19:16.894 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Received Wake Up Request
    2017-05-24 21:19:16.894 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Received WAKE_UP_NOTIFICATION
    2017-05-24 21:19:16.894 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Is awake with 0 messages in the wake-up queue.
    2017-05-24 21:19:16.894 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
    2017-05-24 21:19:16.894 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveWakeUpEvent
    2017-05-24 21:19:16.894 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=2, callback=87, payload=02 02 84 08 
    2017-05-24 21:19:16.894 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 02 84 07 
    2017-05-24 21:19:16.894 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=87, expected=SendData, cancelled=true      MISMATCH
    2017-05-24 21:19:17.894 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: No more messages, go back to sleep
    2017-05-24 21:19:17.894 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
    2017-05-24 21:19:17.894 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
    2017-05-24 21:19:17.894 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
    2017-05-24 21:19:17.894 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 02 02 84 08 25 58 14 
    2017-05-24 21:19:17.894 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 2: Sending REQUEST Message = 01 09 00 13 02 02 84 08 25 58 14 
    2017-05-24 21:19:17.915 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
    2017-05-24 21:19:17.916 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
    2017-05-24 21:19:17.916 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
    2017-05-24 21:19:17.916 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
    2017-05-24 21:19:17.916 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
    2017-05-24 21:19:17.916 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: Sent Data successfully placed on stack.
    2017-05-24 21:19:17.930 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 05 00 13 58 00 B1 
    2017-05-24 21:19:17.934 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
    2017-05-24 21:19:17.934 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 13 58 00 00 00 B3 
    2017-05-24 21:19:17.934 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 13 58 00 00 00 B3 
    2017-05-24 21:19:17.934 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=58 00 
    2017-05-24 21:19:17.934 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: SendData Request. CallBack ID = 88, Status = Transmission complete and ACK received(0)
    2017-05-24 21:19:17.934 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
    2017-05-24 21:19:17.934 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@40f6d798 already registered
    2017-05-24 21:19:17.934 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=2, callback=88, payload=02 02 84 08 
    2017-05-24 21:19:17.934 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=58 00 
    2017-05-24 21:19:17.934 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=88, expected=SendData, cancelled=false        transaction complete!
    2017-05-24 21:19:17.934 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
    2017-05-24 21:19:17.934 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Went to sleep
    2017-05-24 21:19:17.934 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Is sleeping
    2017-05-24 21:19:17.934 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
    2017-05-24 21:19:17.934 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 2: Response processed after 37ms/3563ms.

Just for info, normally detecting motion will not wake up a device…

From a quick look at your log, it looks like the system is working, but you need to read the manual, and maybe update the database.

The manual says the following -:

In the above log you tried to set the value to 0xc8 (ie 200) and this is greater then 127 so it was rejected.

I would try a value of 120 and see if that works. I suspect that the database should be updated to use a size of 2.

Yeah, I thought that was a little odd, too. But, it is what the manual says. :confused:

Interesting - it would be interesting to know if it’s true - it should be easy to tell from a log of a motion event. I’ve not seen a device that does that, but there’s a first for everything :wink:

I am able to wake it up with the tamper switch as stated in the manual I received with the sensor.
OpenHab2 now thinks the values are changed (no pending messages) however it’s still behaving the same. I’m going to exclude it and re-include it later tonight and start from scratch.

I’ve decided to send updates only to the controller and use rules with timers, but now I’m up against another odd issue. I have a switch set to the binary channel of the motion sensor

Switch Motion_MF_OF "Office Motion" <switch> {channel="zwave:device:6873f5c9:node19:sensor_binary"}

and a simple rule that logs

rule "Office Motion start"
when
        Item Motion_MF_OF received command ON
then
    logInfo("Lights", "motion in office detected")
end

The switch toggles with motion, but the rules only runs if I click the toggle in the sitemap. Do I use something other than “received command”. I assumed that the switch command status would be the same in either case

For my motion sensors, I typically use

        Item Motion_MF_OF changed to ON

or

        Item Motion_MF_OF changed from OFF to ON

Thanks, that works. I didn’t expect there would be a difference, but this feature could be helpful in determining how the switch was changed.