Question to zwave device IS140-2 PIR sensor with relay

Tags: #<Tag:0x00007fc20939cad8>

I have just installed the PIR-sensor “IS140-2 PIR sensor with relay” with my OH2.3 and zwave installation. Looks good - and works.

However, it seems that I dont get ON/OFF / Open/Close announcements when motion happens ?
The light turns on/off on the attached floodlight - when it is dark - but I would like to use it as an “all day motion warning” sensor as well.

Can anyone share their config for this thing ?

From the database it looks like the alarm_burglar channel with a Switch item type should do it.

https://www.openhab.org/addons/bindings/zwave/thing.html?manufacturer=steinel&file=is1402_0_0.html

Edit: I remember some database changes on this device about 2 month ago, so you may need to switch to the latest zwave snapshot or development version of the zwave binding …

Ah - OK. Used Chris log-viewer after waving my hands in front of the PIR - and noticed that it is indeed the “alarm_burglar1” which reports motion. What surprised me is, that it simply sends an “OFF” report when motion occurs - and never an “ON”. Doesn’t sound logical - but hey :wink:

I have written a small piece of .rules to handle it in my setup, so that the system can react on it.

Thanks !

For anyone else looking for a non-battery driven zwave PIR sensor - this one is quite neat !

One more question:
In config parameter #9 you can supposedly control how the device controls its relay. The manual describes “slave mode”, “stupid mode” etc.

What I want to do is, to ALWAYS report motion - but ONLY switch the relay/light when the relay is asked (by OpenHab) to do so. The idea is to always monitor when motion occurs - and then only turn on light when the sun is down or I otherwise want to. Also, I can then have OH control how long the lights should be on etc.

I believe this can be achieved by setting parameter #9 to “slave mode”:

Slave mode (bit 0 =1):
 - only if included in Z-Wave network
 - useful for controlling via third-party sensor
 - lamp/relay is directly controlled via Z-Wave, internal sensors are not used
for controlling it
  • and I can see in Habmin that the configured (default) value of parameter# 9 is “2” in my setup - but how to figure out what value this should be set to - since the parameter is a bitfield ?

Any help would be much appreciated - expecially if someone is already using the device as I intend to…?

I have updated the database to simply enable/disable each bit.
You need to wait for the next zwave binding update, then delete the thing and readd it.
If it does not work just shout :sunglasses:

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

Side note: In a ‘burglar alarm’ context, it is common for no-problem status to be represented by CLOSED contacts (equivalent to switch ON) , and the alarm state to be represented as OPEN contacts (equivalent to switch OFF).
It’s a historical legacy from wired alarms, so that cutting a wire (causing OPEN circuit) rings the alarm.

Failure to report “I’m idle again” later seems to be a peculiarity of some zwave designers, don’t know why, perhaps to reduce traffic.
Easily dealt with in Openhab by using the expire binding to autoupdate your Item to it’s rest state after some time similar to the sensors retriggering interval.

1 Like

Could you configure this successfully? I am struggling with my new IS140-2 as it only reports the state of the relay switch and the luminance values correctly to OH. The AlarmBurglarMotion channel is updated with OFF-values, BUT MUCH TOO LATE! It indeed is only updated after the motion sensor has stopped to detect motion.
Example: Motion is detected at 11:00:00. The RelaySwitch channel is immediately updated to ON. No updates at all for AlarmBurglarMotion. No more motion and at 11:00:10 the sensor swichtes off the light. The RelaySwitch channel is immediately updated to OFF. And also the AlarmBurglarMotion channel is now updated to OFF. But with this delay it is useless if you want to use the motion signal to fire other rules immediately.
Did you manage to have a better setup?

I meanwhile did some analysis with debug loggin in my test environment. It seems that the sensor is sending an alarm notification, but the binding is not updating the channel.
Here is a debug log (node 2):

2018-10-03 12:52:56.350 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 02 0A 60 0D 02 01 31 05 03 0A 06 CA 7C 
2018-10-03 12:52:56.352 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0A 60 0D 02 01 31 05 03 0A 06 CA 
2018-10-03 12:52:56.353 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0A 60 0D 02 01 31 05 03 0A 06 CA 
2018-10-03 12:52:56.353 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-03 12:52:56.354 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2018-10-03 12:52:56.354 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-10-03 12:52:56.355 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2018-10-03 12:52:56.355 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 2
2018-10-03 12:52:56.355 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-10-03 12:52:56.356 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_SENSOR_MULTILEVEL V4 SENSOR_MULTILEVEL_REPORT
2018-10-03 12:52:56.356 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Type = Luminance(3), Scale = 1
2018-10-03 12:52:56.357 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Value = 1738
2018-10-03 12:52:56.357 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2018-10-03 12:52:56.358 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 2, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 1738
2018-10-03 12:52:56.358 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:ZWTE:node2:sensor_luminance2 to 1738 % [QuantityType]
2018-10-03 12:52:56.359 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2018-10-03 12:52:56.360 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@696633c.
2018-10-03 12:52:56.361 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:52:56.362 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:52:56.366 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-03 12:52:56.367 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-03 12:52:56.731 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 13 00 04 00 02 0D 60 0D 01 01 71 05 00 00 00 FF 07 08 00 0E 
2018-10-03 12:52:56.732 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0D 60 0D 01 01 71 05 00 00 00 FF 07 08 00 
2018-10-03 12:52:56.734 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0D 60 0D 01 01 71 05 00 00 00 FF 07 08 00 
2018-10-03 12:52:56.735 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-03 12:52:56.735 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2018-10-03 12:52:56.736 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-10-03 12:52:56.737 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2018-10-03 12:52:56.737 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_ALARM, endpoint 1
2018-10-03 12:52:56.738 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-10-03 12:52:56.738 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2018-10-03 12:52:56.739 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
2018-10-03 12:52:56.740 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = BURGLAR (0)
2018-10-03 12:52:56.740 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-10-03 12:52:56.741 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_ALARM, value = 255
2018-10-03 12:52:56.742 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter processing NOTIFICATION
2018-10-03 12:52:56.743 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter NOTIFICATION event is 8, type OnOffType
2018-10-03 12:52:56.743 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2018-10-03 12:52:56.744 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@298babdf.
2018-10-03 12:52:56.745 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:52:56.746 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:52:56.746 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-03 12:52:56.747 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-03 12:52:56.750 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 02 0A 60 0D 02 01 31 05 03 0A 03 50 E3 
2018-10-03 12:52:56.752 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0A 60 0D 02 01 31 05 03 0A 03 50 
2018-10-03 12:52:56.753 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0A 60 0D 02 01 31 05 03 0A 03 50 
2018-10-03 12:52:56.753 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-03 12:52:56.754 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2018-10-03 12:52:56.755 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-10-03 12:52:56.755 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2018-10-03 12:52:56.756 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 2
2018-10-03 12:52:56.756 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-10-03 12:52:56.757 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_SENSOR_MULTILEVEL V4 SENSOR_MULTILEVEL_REPORT
2018-10-03 12:52:56.758 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Type = Luminance(3), Scale = 1
2018-10-03 12:52:56.758 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Value = 848
2018-10-03 12:52:56.759 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2018-10-03 12:52:56.760 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 2, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 848
2018-10-03 12:52:56.761 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:ZWTE:node2:sensor_luminance2 to 848 % [QuantityType]
2018-10-03 12:52:56.762 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2018-10-03 12:52:56.764 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@f43e7f5.
2018-10-03 12:52:56.765 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:52:56.766 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:52:56.767 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-03 12:52:56.767 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-03 12:52:56.770 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 02 07 60 0D 03 01 25 03 FF 45 
2018-10-03 12:52:56.772 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 07 60 0D 03 01 25 03 FF 
2018-10-03 12:52:56.772 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 07 60 0D 03 01 25 03 FF 
2018-10-03 12:52:56.773 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-03 12:52:56.774 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2018-10-03 12:52:56.775 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-10-03 12:52:56.776 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2018-10-03 12:52:56.777 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_SWITCH_BINARY, endpoint 3
2018-10-03 12:52:56.779 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-10-03 12:52:56.780 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_SWITCH_BINARY V1 SWITCH_BINARY_REPORT
2018-10-03 12:52:56.780 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 2: Switch Binary report, value = 255
2018-10-03 12:52:56.781 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-10-03 12:52:56.782 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 3, command class = COMMAND_CLASS_SWITCH_BINARY, value = 255
2018-10-03 12:52:56.783 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:ZWTE:node2:switch_binary3 to ON [OnOffType]
2018-10-03 12:52:56.784 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2018-10-03 12:52:56.784 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@438c5f1b.
2018-10-03 12:52:56.785 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:52:56.785 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:52:56.786 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-03 12:52:56.786 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-03 12:52:56.791 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 13 00 04 00 02 0D 60 0D 01 01 71 05 00 00 00 FF 07 08 00 0E 
2018-10-03 12:52:56.792 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0D 60 0D 01 01 71 05 00 00 00 FF 07 08 00 
2018-10-03 12:52:56.792 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0D 60 0D 01 01 71 05 00 00 00 FF 07 08 00 
2018-10-03 12:52:56.792 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-03 12:52:56.793 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2018-10-03 12:52:56.793 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-10-03 12:52:56.793 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2018-10-03 12:52:56.794 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_ALARM, endpoint 1
2018-10-03 12:52:56.794 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-10-03 12:52:56.794 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2018-10-03 12:52:56.794 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
2018-10-03 12:52:56.795 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = BURGLAR (0)
2018-10-03 12:52:56.795 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-10-03 12:52:56.796 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_ALARM, value = 255
2018-10-03 12:52:56.796 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter processing NOTIFICATION
2018-10-03 12:52:56.796 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter NOTIFICATION event is 8, type OnOffType
2018-10-03 12:52:56.797 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2018-10-03 12:52:56.797 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@76365bd5.
2018-10-03 12:52:56.797 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:52:56.798 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:52:56.798 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-03 12:52:56.798 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-03 12:53:03.881 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 14 00 04 00 02 0E 60 0D 01 01 71 05 00 00 00 FF 07 00 01 08 0B 
2018-10-03 12:53:03.882 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0E 60 0D 01 01 71 05 00 00 00 FF 07 00 01 08 
2018-10-03 12:53:03.882 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0E 60 0D 01 01 71 05 00 00 00 FF 07 00 01 08 
2018-10-03 12:53:03.883 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-03 12:53:03.883 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2018-10-03 12:53:03.884 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-10-03 12:53:03.884 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2018-10-03 12:53:03.885 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_ALARM, endpoint 1
2018-10-03 12:53:03.886 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-10-03 12:53:03.886 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2018-10-03 12:53:03.886 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 0 = 0, event=0, status=255, plen=1
2018-10-03 12:53:03.887 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = BURGLAR (0)
2018-10-03 12:53:03.888 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-10-03 12:53:03.888 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_ALARM, value = 255
2018-10-03 12:53:03.888 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter processing NOTIFICATION
2018-10-03 12:53:03.889 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter NOTIFICATION event is 0, type OnOffType
2018-10-03 12:53:03.890 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:ZWTE:node2:alarm_burglar1 to OFF [OnOffType]
2018-10-03 12:53:03.890 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2018-10-03 12:53:03.891 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@217d39f.
2018-10-03 12:53:03.892 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:53:03.893 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:53:03.894 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-03 12:53:03.896 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-03 12:53:03.902 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 14 00 04 00 02 0E 60 0D 01 01 71 05 00 00 00 FF 07 00 01 08 0B 
2018-10-03 12:53:03.903 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0E 60 0D 01 01 71 05 00 00 00 FF 07 00 01 08 
2018-10-03 12:53:03.904 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 0E 60 0D 01 01 71 05 00 00 00 FF 07 00 01 08 
2018-10-03 12:53:03.905 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-03 12:53:03.905 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2018-10-03 12:53:03.905 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-10-03 12:53:03.906 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2018-10-03 12:53:03.907 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_ALARM, endpoint 1
2018-10-03 12:53:03.907 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-10-03 12:53:03.908 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2018-10-03 12:53:03.908 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 0 = 0, event=0, status=255, plen=1
2018-10-03 12:53:03.909 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = BURGLAR (0)
2018-10-03 12:53:03.910 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-10-03 12:53:03.910 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 1, command class = COMMAND_CLASS_ALARM, value = 255
2018-10-03 12:53:03.912 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter processing NOTIFICATION
2018-10-03 12:53:03.912 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Alarm converter NOTIFICATION event is 0, type OnOffType
2018-10-03 12:53:03.913 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:ZWTE:node2:alarm_burglar1 to OFF [OnOffType]
2018-10-03 12:53:03.913 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2018-10-03 12:53:03.914 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@127bf067.
2018-10-03 12:53:03.915 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:53:03.916 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:53:03.919 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-03 12:53:03.920 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-03 12:53:08.894 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 02 07 60 0D 03 01 25 03 00 BA 
2018-10-03 12:53:08.894 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 07 60 0D 03 01 25 03 00 
2018-10-03 12:53:08.894 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 07 60 0D 03 01 25 03 00 
2018-10-03 12:53:08.895 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-03 12:53:08.895 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2018-10-03 12:53:08.895 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-10-03 12:53:08.895 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2018-10-03 12:53:08.895 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_SWITCH_BINARY, endpoint 3
2018-10-03 12:53:08.896 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-10-03 12:53:08.896 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_SWITCH_BINARY V1 SWITCH_BINARY_REPORT
2018-10-03 12:53:08.896 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 2: Switch Binary report, value = 0
2018-10-03 12:53:08.896 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-10-03 12:53:08.896 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 3, command class = COMMAND_CLASS_SWITCH_BINARY, value = 0
2018-10-03 12:53:08.896 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:ZWTE:node2:switch_binary3 to OFF [OnOffType]
2018-10-03 12:53:08.897 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2018-10-03 12:53:08.897 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@332e11b4.
2018-10-03 12:53:08.897 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:53:08.898 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:53:08.898 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-03 12:53:08.898 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-10-03 12:53:08.944 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 02 07 60 0D 03 01 25 03 00 BA 
2018-10-03 12:53:08.944 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 07 60 0D 03 01 25 03 00 
2018-10-03 12:53:08.944 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=2, callback=0, payload=00 02 07 60 0D 03 01 25 03 00 
2018-10-03 12:53:08.945 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-10-03 12:53:08.945 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2018-10-03 12:53:08.945 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-10-03 12:53:08.945 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Decapsulating COMMAND_CLASS_MULTI_CHANNEL
2018-10-03 12:53:08.945 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_SWITCH_BINARY, endpoint 3
2018-10-03 12:53:08.946 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-10-03 12:53:08.946 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_SWITCH_BINARY V1 SWITCH_BINARY_REPORT
2018-10-03 12:53:08.946 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 2: Switch Binary report, value = 0
2018-10-03 12:53:08.946 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-10-03 12:53:08.946 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 3, command class = COMMAND_CLASS_SWITCH_BINARY, value = 0
2018-10-03 12:53:08.946 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:ZWTE:node2:switch_binary3 to OFF [OnOffType]
2018-10-03 12:53:08.947 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Commands processed 1.
2018-10-03 12:53:08.947 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@77021cf7.
2018-10-03 12:53:08.947 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:53:08.947 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-10-03 12:53:08.947 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-10-03 12:53:08.948 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

The motion was triggered and the binding receives an Incoming command class COMMAND_CLASS_ALARM, endpoint 1 at 12:52:56.737. However the binding does NOT update the channel.
When the sensor reports the end of motion it sends again the Incoming command class COMMAND_CLASS_ALARM, endpoint 1 at 12:53:03.885. This time the binding does update the channel alarm_burglar1 at 12:53:03.890.
@chris: Could you have a look at this please? Thank you!

I have updated the database to change the channel type to alarm_motion - this should make it report now, but note that you’ll have to update channels.

This will probably flow into the binding tomorrow night.

Thank you very much for the quick solution! I will test it on the weekend then and report back.

1 Like

Thank you very much @chris ! I just tested it with the 1381 Snapshot and Z-Wave Binding 20181006 and it now works like a charm with the new MotionAlarm channel. Perfect! Thank you for all the great work and support!

1 Like

@vossivossi Could you please share your .items and the config from Habmin/PaperUI of the device ?

I also use the latest snapshot - but am really struggling to get something usable out of the device; either it doesnt report at all, or seem to kind of loop motion messages at a fast pace - all depending on settings. I just cant get it set up right with all the options and combinations :wink:

I just want it to report motion, luminance and to be able to control the switch - preferably only from OH.

I just tested it in a test environment where I created the items quickly with PaperUI, so I do not have the device yet in my item files. So the item for the Motion Alarm is defined as a Switch bound to Channel alarm_motion1:
grafik

The config looks as follows:


And these are the Associations:

Hope that helps.

very strange; following your settings, it does work :wink: - I need to look a bit further into this to fully understand… Am checking performance for a few hours before I call this one “solved”…

So, after testing a bit, I can confirm that motion and luminescens works - and is reported to OH correctly. However, I cannot trigger the relay in the box - neither through “switch_binary” nor through “switch_binary3”. They are reported received correctly - but no click/no switch happens…

Any ideas/suggestions ?

Another strange thing that may be coupled to the described issue; when I try to set “Controller” in association group “Root” it is “saved” - but if I update the page, the group is still empty / blank.
How can this be ? In other words, I cannot seem to store anything in the “Root” group…

Ok, I have to admit that my primary interest was to use the device as a motion sensor for outdoor use powered by wire on 230V. So I only tested motion and lux reports. I did not check the relay switch.

I am not sure but it sounds as if the Z-Wave device database might be incorrect for the device. But I am just speculating, maybe @chris can tell more.

@chris what is your estimate here ? - any ideas where to look for this issue in logs etc. ?
As mentioned the issue is, that the relay in the device now never get switched / cannot be switched by triggering the channels. It worked well in an earlier version of the binding - but now now (latest snapshot). Am not sure how to look for what has changed from i.e. 2.3 to the latest snapshot - but perhaps you can guide me in the right direction to investigate ?

Would be nice to finally get this otherwise very nice device working - there are not that many 230V driven switch + PIR combos out there…

You should get a debug log so we can see what is happening.

There are a huge number of changes - the binding is nearly (not quite) a rewrite in many parts.

Thanks @chris - my logfile is here: https://ufile.io/3is87
Node = 11 - fast forward to around 19:23 where I first switch the switch_binary channel ON and then OFF - and a few seconds later, I switch the switch_binary3 channel ON and then OFF.
The latter results in switch_binary being switched automatically for some reason (follows b_binary3 both on and off)…

In the log - and with your viewer - I see a lot of “application busy” - and other weird stuff. Can you make sense of it to figure out why the switching doesnt seem to have effect on the relay ?

Luminance and motion works well alone… and as said; the relay part did work in an earlier version of the binding…

I’m not sure why the device is reporting it’s busy. Not many devices do this, and it’s hard to understand why a light would tell you it’s too busy to turn on - it’s the only thing it has to do :wink:

The device however is reporting that it’s busy, and the binding should try again later, which it does a few seconds later. Unfortunately I don’t know why it’s busy…

I’m assuming that endpoint 2 is correct?

The only other thing I can think of is to ask the manufacturer what would cause this report to be sent - the ZWave docs don’t provide any information, and all the binding can do is to retry…