Handling zwave notifications - Need Help

FRamos · January 28, 2017, 9:14pm

Hello, to all the members of the community. I need your help.
First of all let me congratulate all the contributors, especially @Kai and @Chris, for the openHAB2 and zwave projects, which for the moment I am most interested in.

I have known these projects for about two months and since then I have set up a “test lab” with some devices that I have removed from a myDLinkHome installation which, although working well, does not offer me the control and integration with others that I need.

In the “test lab” I have installed a Z-Stick Gen5, a DCH-Z110 door sensor, a DCH-Z120 PIR and a DCH-Z510 siren.
I have already used several installations - SNAPSHOT, Manual and openHABianPi, as well as various configurations, with PaperUI or with HABmin, but I can not go beyond the question I bring you here:

Both sensors (door and PIR) identify 5 channels each, but sensor_door and sensor_binary channels are never used. What are they used for?
Both sensors operate the ALARM channel, which in case the door sensor processes the respective notifications (22 - door open and 23 - door closed), but the PIR does not process the notification despite receiving motion detection (8 - Motion Detection). This is my problem for which I thank you for your help.

node1.xml (1.3 KB)
node2.xml (9.6 KB)
node3.xml (14.8 KB)
node4.xml (14.5 KB)

I am currently using an openHABianPi installation, in which I already ran the openHAB2 STABLE.
Send the zwave node files together for the 4 devices, as well as the generated startup and event logs.

Time	Node	Entry
19:57:20.473		
Binding started. Version 2.0.0
19:57:25.718	4	
COMMAND RECEIVED zwave:device:tst:node4:sensor_binary REFRESH
19:57:25.720	4	
COMMAND RECEIVED zwave:device:tst:node4:sensor_luminance REFRESH
19:57:25.722	4	
COMMAND RECEIVED zwave:device:tst:node4:sensor_temperature REFRESH
19:57:25.722	3	
COMMAND RECEIVED zwave:device:tst:node3:sensor_door REFRESH
19:57:25.725	4	
COMMAND RECEIVED zwave:device:tst:node4:alarm_general REFRESH
19:57:25.727	3	
COMMAND RECEIVED zwave:device:tst:node3:sensor_luminance REFRESH
19:57:25.729	4	
COMMAND RECEIVED zwave:device:tst:node4:battery-level REFRESH
19:57:25.730	3	
COMMAND RECEIVED zwave:device:tst:node3:sensor_temperature REFRESH
19:57:25.733	3	
COMMAND RECEIVED zwave:device:tst:node3:alarm_general REFRESH
19:57:25.736	3	
COMMAND RECEIVED zwave:device:tst:node3:battery-level REFRESH
19:57:25.742	2	
COMMAND RECEIVED zwave:device:tst:node2:switch_binary REFRESH
19:57:25.745	2	
COMMAND RECEIVED zwave:device:tst:node2:notification_send REFRESH
19:57:28.727		
TX REQ GetVersion
19:57:28.754		
RX RES GetVersion
19:57:28.827		
TX REQ MemoryGetId
19:57:28.834		
RX RES MemoryGetId MemoryGetId: HomeID E5E17A69 ControllerID NODE 1
19:57:28.851		
TX REQ SerialApiGetCapabilities
19:57:28.864		
RX RES SerialApiGetCapabilities Controller Info 0086:0001:005A
19:57:28.950		
TX REQ SerialApiSetTimeouts FRAME=1500s BYTE=150ms
19:57:28.956		
RX RES SerialApiSetTimeouts FRAME=1500s BYTE=150ms
19:57:28.974		
TX REQ GetSucNodeId
19:57:28.980		
RX RES GetSucNodeId SUC ID: NOT SET
19:57:28.997		
TX REQ SerialApiGetInitData
19:57:29.096		
RX RES SerialApiGetInitData Found 4 nodes 
19:57:29.168		
TX REQ GetControllerCapabilities
19:57:29.173		
RX RES GetControllerCapabilities
19:57:29.681	1	
Stage advanced to PROTOINFO
19:57:29.692	1	
TX REQ IdentifyNode
19:57:29.698	1	
RX RES IdentifyNode STATIC_CONTROLLER PC_CONTROLLER LISTENING FLIRS250 FLIRS1000 ROUTING BEAMING
19:57:29.726	3	
Stage advanced to PROTOINFO
19:57:29.761	2	
Stage advanced to PROTOINFO
19:57:29.772	4	
Stage advanced to PROTOINFO
19:57:29.781	1	
Stage advanced to PROTOINFO
19:57:29.788	1	
Stage advanced to INIT_NEIGHBORS
19:57:29.810	1	
TX REQ IdentifyNode
19:57:29.818	1	
RX RES IdentifyNode STATIC_CONTROLLER PC_CONTROLLER LISTENING FLIRS250 FLIRS1000 ROUTING BEAMING
19:57:29.856	3	
TX REQ IdentifyNode
19:57:29.862	3	
RX RES IdentifyNode ROUTING_SLAVE NOTIFICATION_SENSOR LISTENING FLIRS250 FLIRS1000 ROUTING BEAMING
19:57:29.904	3	
Stage advanced to INIT_NEIGHBORS
19:57:29.916	4	
TX REQ IdentifyNode
19:57:29.921	4	
RX RES IdentifyNode ROUTING_SLAVE NOTIFICATION_SENSOR LISTENING FLIRS250 FLIRS1000 ROUTING BEAMING
19:57:29.984	4	
Stage advanced to INIT_NEIGHBORS
19:57:29.994	2	
TX REQ IdentifyNode
19:57:30.001	2	
RX RES IdentifyNode ROUTING_SLAVE SIREN_SWITCH_BINARY LISTENING FLIRS250 FLIRS1000 ROUTING BEAMING
19:57:30.035	2	
Stage advanced to INIT_NEIGHBORS
19:57:30.042	1	
TX REQ GetRoutingInfo
19:57:30.050	1	
RX RES GetRoutingInfo Found 0 neighbours
19:57:30.089	1	
Stage advanced to FAILED_CHECK
19:57:30.170	3	
TX REQ GetRoutingInfo
19:57:30.177	3	
RX RES GetRoutingInfo Found 0 neighbours
19:57:30.206	3	
Stage advanced to FAILED_CHECK
19:57:30.217	4	
TX REQ GetRoutingInfo
19:57:30.224	4	
RX RES GetRoutingInfo Found 1 neighbours 
19:57:30.255	4	
Stage advanced to FAILED_CHECK
19:57:30.265	2	
TX REQ GetRoutingInfo
19:57:30.272	2	
RX RES GetRoutingInfo Found 1 neighbours 
19:57:30.305	2	
Stage advanced to FAILED_CHECK
19:57:30.315	3	
TX REQ IsFailedNodeID Check if NODE 3 is failed
19:57:30.319	3	
RX RES IsFailedNodeID NODE 3 is marked as HEALTHY by controller.
19:57:30.345	3	
Stage advanced to WAIT
19:57:30.356	4	
TX REQ IsFailedNodeID Check if NODE 4 is failed
19:57:30.361	4	
RX RES IsFailedNodeID NODE 4 is marked as HEALTHY by controller.
19:57:30.386	4	
Stage advanced to WAIT
19:57:30.423	2	
TX REQ IsFailedNodeID Check if NODE 2 is failed
19:57:30.428	2	
RX RES IsFailedNodeID NODE 2 is marked as HEALTHY by controller.
19:57:30.441	2	
Stage advanced to WAIT
19:57:30.445	2	
Stage advanced to PING
19:57:30.455	2	
TX REQ SendData 2 NO_OPERATION  ACK AUTO_ROUTE EXPLORE
19:57:30.466	2	
RX RES SendData 2 ACCEPTED BY CONTROLLER
19:57:31.904	2	
RX REQ SendData 2 ACK RECEIVED from device in 1449ms
19:57:32.089	4	
Stage advanced to PROTOINFO
19:57:32.136	3	
Stage advanced to PROTOINFO
19:57:35.458	2	
Sending data abort
19:57:35.458		
TX REQ SendDataAbort
19:57:35.478	2	
Message retry (0 attempts remaining)
19:57:35.481	4	
TX REQ IdentifyNode
19:57:35.487	4	
RX RES IdentifyNode ROUTING_SLAVE NOTIFICATION_SENSOR LISTENING FLIRS250 FLIRS1000 ROUTING BEAMING
19:57:35.497	4	
Stage advanced to INIT_NEIGHBORS
19:57:35.504	3	
TX REQ IdentifyNode
19:57:35.510	3	
RX RES IdentifyNode ROUTING_SLAVE NOTIFICATION_SENSOR LISTENING FLIRS250 FLIRS1000 ROUTING BEAMING
19:57:35.522	3	
Stage advanced to INIT_NEIGHBORS
19:57:35.528	4	
TX REQ GetRoutingInfo
19:57:35.538	4	
RX RES GetRoutingInfo Found 1 neighbours 
19:57:35.550	4	
Stage advanced to FAILED_CHECK
19:57:35.553	3	
TX REQ GetRoutingInfo
19:57:35.560	3	
RX RES GetRoutingInfo Found 0 neighbours
19:57:35.591	3	
Stage advanced to FAILED_CHECK
19:57:35.594	4	
TX REQ IsFailedNodeID Check if NODE 4 is failed
19:57:35.600	4	
RX RES IsFailedNodeID NODE 4 is marked as HEALTHY by controller.
19:57:35.606	4	
Stage advanced to WAIT
19:57:35.609	3	
TX REQ IsFailedNodeID Check if NODE 3 is failed
19:57:35.614	3	
RX RES IsFailedNodeID NODE 3 is marked as HEALTHY by controller.
19:57:35.622	3	
Stage advanced to WAIT

20:03:14.043 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 24 00 04 00 03 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 16 00 05 31 05 03 01 01 06 31 05 01 0A 00 3A 0F 
20:03:14.046 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_tst_serial_sof changed from 58 to 59
20:03:14.049 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
20:03:14.052 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 24 00 04 00 03 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 16 00 05 31 05 03 01 01 06 31 05 01 0A 00 3A 0F 
20:03:14.054 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 24 00 04 00 03 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 16 00 05 31 05 03 01 01 06 31 05 01 0A 00 3A 0F 
20:03:14.057 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 03 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 16 00 05 31 05 03 01 01 06 31 05 01 0A 00 3A 
20:03:14.058 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 3: Application Command Request (INITIALIZING:PING)
20:03:14.058 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 3: Node is ALIVE. Init stage is PING.
20:03:14.059 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveNodeStatusEvent
20:03:14.059 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Node Status event during initialisation - Node is ALIVE
20:03:14.059 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Node advancer - PING: queue length(0), free to send(true)
20:03:14.060 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Node advancer: loop - PING try 1: stageAdvanced(false)
20:03:14.060 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Node advancer: PING - send NoOperation
20:03:14.060 [DEBUG] [ndclass.ZWaveNoOperationCommandClass] - NODE 3: Creating new message for command No Operation
20:03:14.061 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Node advancer - queued packet. Queue length is 1
20:03:14.063 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 3: Putting message SendData in wakeup queue.
20:03:14.063 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveNodeStatusEvent
20:03:14.064 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Setting ONLINE
20:03:14.066 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 3: Node Status event - Node is ALIVE
20:03:14.066 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 3: Incoming command class MULTI_CMD
20:03:14.067 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Received Multi-Command Request
20:03:14.067 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:tst:node3' changed from ONLINE: Node initialising: WAIT to ONLINE
20:03:14.068 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Incoming command class BATTERY
20:03:14.069 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Calling handleApplicationCommandRequest.
20:03:14.069 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 3: Received Battery Request
20:03:14.070 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 3: Battery report value = 100
20:03:14.071 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
20:03:14.072 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: CC event during initialisation stage IDLE
20:03:14.072 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
20:03:14.073 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
20:03:14.074 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Updating channel state zwave:device:tst:node3:battery-level to 100 [DecimalType]
20:03:14.076 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Incoming command class ALARM
20:03:14.076 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Calling handleApplicationCommandRequest.
20:03:14.076 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 3: Received ALARM command V4
20:03:14.077 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 3: Process NOTIFICATION_REPORT V4
20:03:14.077 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 3: NOTIFICATION report - 0 = 0, event=22, status=255
20:03:14.077 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 3: Alarm Type = ACCESS_CONTROL (0)
20:03:14.078 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
20:03:14.078 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveAlarmValueEvent
20:03:14.078 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
20:03:14.079 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_tst_node3_battery_level changed from NULL to 100
20:03:14.079 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
20:03:14.080 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 22, type OnOffType
20:03:14.081 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Updating channel state zwave:device:tst:node3:alarm_general to ON [OnOffType]
20:03:14.082 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Incoming command class SENSOR_MULTILEVEL
20:03:14.083 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Calling handleApplicationCommandRequest.
20:03:14.084 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V5
20:03:14.084 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Sensor Multi Level REPORT received
20:03:14.086 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Sensor Type = Luminance(3), Scale = 0
20:03:14.086 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_tst_node3_alarm_general changed from NULL to ON
20:03:14.087 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Sensor Value = 1
20:03:14.088 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
20:03:14.088 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
20:03:14.089 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 1
20:03:14.091 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Updating channel state zwave:device:tst:node3:sensor_luminance to 1 [DecimalType]
20:03:14.092 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Incoming command class SENSOR_MULTILEVEL
20:03:14.093 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Calling handleApplicationCommandRequest.
20:03:14.093 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V5
20:03:14.094 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Sensor Multi Level REPORT received
20:03:14.094 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Sensor Type = Temperature(1), Scale = 1
20:03:14.095 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Sensor Value = 58
20:03:14.095 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
20:03:14.096 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_tst_node3_sensor_luminance changed from NULL to 1
20:03:14.096 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
20:03:14.096 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 58
20:03:14.098 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 3: Sensor is reporting scale 1, requiring conversion to 0. Value is now 58.
20:03:14.102 [DEBUG] [converter.ZWaveCommandClassConverter] - Converted temperature from 58F to 14.4C
20:03:14.103 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Updating channel state zwave:device:tst:node3:sensor_temperature to 14.4 [DecimalType]
20:03:14.105 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Transaction not completed: node address inconsistent.  lastSent=2, incoming=255
20:03:14.108 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_tst_node3_sensor_temperature changed from NULL to 14.4
20:03:15.315 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 24 00 04 00 03 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 17 00 05 31 05 03 01 01 06 31 05 01 0A 00 3A 0E 
20:03:15.317 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_tst_serial_sof changed from 59 to 60
20:03:15.323 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
20:03:15.325 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 24 00 04 00 03 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 17 00 05 31 05 03 01 01 06 31 05 01 0A 00 3A 0E 
20:03:15.327 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 24 00 04 00 03 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 17 00 05 31 05 03 01 01 06 31 05 01 0A 00 3A 0E 
20:03:15.328 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 03 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 06 17 00 05 31 05 03 01 01 06 31 05 01 0A 00 3A 
20:03:15.329 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 3: Application Command Request (ALIVE:DETAILS)
20:03:15.329 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 3: Incoming command class MULTI_CMD
20:03:15.329 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Received Multi-Command Request
20:03:15.330 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Incoming command class BATTERY
20:03:15.330 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Calling handleApplicationCommandRequest.
20:03:15.330 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 3: Received Battery Request
20:03:15.330 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 3: Battery report value = 100
20:03:15.330 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
20:03:15.330 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
20:03:15.331 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
20:03:15.331 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Updating channel state zwave:device:tst:node3:battery-level to 100 [DecimalType]
20:03:15.333 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Incoming command class ALARM
20:03:15.333 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Calling handleApplicationCommandRequest.
20:03:15.333 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 3: Received ALARM command V4
20:03:15.333 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 3: Process NOTIFICATION_REPORT V4
20:03:15.333 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 3: NOTIFICATION report - 0 = 0, event=23, status=255
20:03:15.334 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 3: Alarm Type = ACCESS_CONTROL (0)
20:03:15.334 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
20:03:15.334 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveAlarmValueEvent
20:03:15.334 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
20:03:15.335 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
20:03:15.335 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 23, type OnOffType
20:03:15.336 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Updating channel state zwave:device:tst:node3:alarm_general to ON [OnOffType]
20:03:15.337 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Incoming command class SENSOR_MULTILEVEL
20:03:15.337 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Calling handleApplicationCommandRequest.
20:03:15.337 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V5
20:03:15.338 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Sensor Multi Level REPORT received
20:03:15.338 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Sensor Type = Luminance(3), Scale = 0
20:03:15.341 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Sensor Value = 1
20:03:15.341 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
20:03:15.341 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
20:03:15.341 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 1
20:03:15.342 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Updating channel state zwave:device:tst:node3:sensor_luminance to 1 [DecimalType]
20:03:15.343 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Incoming command class SENSOR_MULTILEVEL
20:03:15.343 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 3: Calling handleApplicationCommandRequest.
20:03:15.343 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V5
20:03:15.343 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Sensor Multi Level REPORT received
20:03:15.344 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Sensor Type = Temperature(1), Scale = 1
20:03:15.344 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 3: Sensor Value = 58
20:03:15.344 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
20:03:15.344 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
20:03:15.344 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 58
20:03:15.345 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 3: Sensor is reporting scale 1, requiring conversion to 0. Value is now 58.
20:03:15.345 [DEBUG] [converter.ZWaveCommandClassConverter] - Converted temperature from 58F to 14.4C
20:03:15.345 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: Updating channel state zwave:device:tst:node3:sensor_temperature to 14.4 [DecimalType]
20:03:15.346 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Transaction not completed: node address inconsistent.  lastSent=2, incoming=255
20:03:25.956 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_tst_serial_sof changed from 60 to 61
20:03:25.957 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 24 00 04 00 04 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 07 08 00 05 31 05 03 01 01 06 31 05 01 22 00 9B 9E 
20:03:25.978 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
20:03:25.981 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 24 00 04 00 04 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 07 08 00 05 31 05 03 01 01 06 31 05 01 22 00 9B 9E 
20:03:25.984 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 24 00 04 00 04 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 07 08 00 05 31 05 03 01 01 06 31 05 01 22 00 9B 9E 
20:03:25.987 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 04 1E 8F 01 04 03 80 03 64 09 71 05 00 00 00 FF 07 08 00 05 31 05 03 01 01 06 31 05 01 22 00 9B 
20:03:25.988 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 4: Application Command Request (INITIALIZING:PING)
20:03:25.988 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Node is ALIVE. Init stage is PING.
20:03:25.988 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveNodeStatusEvent
20:03:25.989 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 4: Node Status event during initialisation - Node is ALIVE
20:03:25.989 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 4: Node advancer - PING: queue length(0), free to send(true)
20:03:25.989 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 4: Node advancer: loop - PING try 1: stageAdvanced(false)
20:03:25.990 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 4: Node advancer: PING - send NoOperation
20:03:25.990 [DEBUG] [ndclass.ZWaveNoOperationCommandClass] - NODE 4: Creating new message for command No Operation
20:03:25.991 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 4: Node advancer - queued packet. Queue length is 1
20:03:25.991 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 4: Putting message SendData in wakeup queue.
20:03:25.992 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveNodeStatusEvent
20:03:25.992 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Setting ONLINE
20:03:25.994 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 4: Node Status event - Node is ALIVE
20:03:25.994 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 4: Incoming command class MULTI_CMD
20:03:25.995 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 4: Received Multi-Command Request
20:03:25.995 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 4: Incoming command class BATTERY
20:03:25.995 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 4: Calling handleApplicationCommandRequest.
20:03:25.996 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:tst:node4' changed from ONLINE: Node initialising: WAIT to ONLINE
20:03:25.996 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 4: Received Battery Request
20:03:25.996 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 4: Battery report value = 100
20:03:25.996 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
20:03:25.996 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 4: CC event during initialisation stage IDLE
20:03:25.997 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
20:03:25.997 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
20:03:25.998 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Updating channel state zwave:device:tst:node4:battery-level to 100 [DecimalType]
20:03:26.000 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 4: Incoming command class ALARM
20:03:26.001 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 4: Calling handleApplicationCommandRequest.
20:03:26.001 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 4: Received ALARM command V4
20:03:26.001 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 4: Process NOTIFICATION_REPORT V4
20:03:26.002 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 4: NOTIFICATION report - 0 = 0, event=8, status=255
20:03:26.002 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 4: Alarm Type = BURGLAR (0)
20:03:26.002 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
20:03:26.003 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveAlarmValueEvent
20:03:26.003 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
20:03:26.004 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
20:03:26.004 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_tst_node4_battery_level changed from NULL to 100
20:03:26.004 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 4: Incoming command class SENSOR_MULTILEVEL
20:03:26.005 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 4: Calling handleApplicationCommandRequest.
20:03:26.005 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 4: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V5
20:03:26.005 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 4: Sensor Multi Level REPORT received
20:03:26.006 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 4: Sensor Type = Luminance(3), Scale = 0
20:03:26.006 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 4: Sensor Value = 1
20:03:26.007 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
20:03:26.007 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
20:03:26.007 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 1
20:03:26.008 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Updating channel state zwave:device:tst:node4:sensor_luminance to 1 [DecimalType]
20:03:26.010 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 4: Incoming command class SENSOR_MULTILEVEL
20:03:26.010 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 4: Calling handleApplicationCommandRequest.
20:03:26.011 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 4: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V5
20:03:26.011 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 4: Sensor Multi Level REPORT received
20:03:26.011 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 4: Sensor Type = Temperature(1), Scale = 0
20:03:26.012 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 4: Sensor Value = 15.5
20:03:26.012 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
20:03:26.013 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
20:03:26.013 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 15.5
20:03:26.013 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_tst_node4_sensor_luminance changed from NULL to 1
20:03:26.014 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 4: Sensor is reporting scale 0, requiring conversion to 0. Value is now 15.5.
20:03:26.014 [DEBUG] [converter.ZWaveCommandClassConverter] - Converted temperature from 15.5C to 15.5C
20:03:26.015 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Updating channel state zwave:device:tst:node4:sensor_temperature to 15.5 [DecimalType]
20:03:26.016 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Transaction not completed: node address inconsistent.  lastSent=2, incoming=255
20:03:26.021 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_tst_node4_sensor_temperature changed from NULL to 15.5

Still for curiosity, I would like to hear your opinion about the fact that in the HABmin, the Controller does not show any attributes and the Zwave Network Viewer view does not display all connections between devices. (See pictures)

chris · January 30, 2017, 5:07pm

For the notifications, probably the database needs to be updated to filter the events. I looked at the database for the DCH-Z110 and the door sensor uses the binary sensor class - not the notification so this will also need to be changed in the database.

Regarding the network view - this is not reliable in the current version since the neighbours are not updated. The development branch fixes this so it will be available in future.

FRamos · January 30, 2017, 8:18pm

Thanks @chris
I will follow any database updates

sihui · January 30, 2017, 8:19pm

Original post was changed/deleted, my comment is obsolete …

FRamos · January 30, 2017, 8:21pm

I´m very sorry @sihui , I’ve asked for comments without seeing @Chris reply

FRamos · January 30, 2017, 9:57pm

@Chris - but the DCH-Z110 is working “well”. At least is handling the NOTIFICATION_REPORT V4, with event=23, updating the correct node channel.

My problem is with DCH-Z120 that produces a NOTIFICATION_REPORT V4, with event=8 (motion detected). It handles the notification, but stops on the ZWaveAlarmConverter with the message “Alarm converter processing NOTIFICATION”.

I’ve take a look at the source files, on the ZWaveAlarmConverter.java and found the conversion for event=23 (Door CLOSED) as for event=22 (Door OPEN), but not for other events/DataTypes. I believe this can be solved on this file (ZWaveAlarmConverter.java). Don’t you?

chris · January 30, 2017, 10:06pm

I don’t see why the converter needs updating? It is already capable of filtering events.

I think the database needs to be updated for this device so that it filters the events. You need to add the correct notification type, and the correct event filter. So, I think type=BURGLAR, event=8 should work.

Additionally the channel type should be changed to alarm_motion instead of alarm_general.

The same sort of updates probably need to be done to the Z110 as well - even if it is working “well”. For starters the channel type is wrong - it should be sensor_door… Filters don’t really mater for the door sensor since it is handled a little differently in the converter.

FRamos · January 31, 2017, 9:11am

@Chris, please feel free to ask me some help on testing with this devices (DCH-Z110 and DCH-Z120)

chris · January 31, 2017, 9:48am

I think the database needs to be updated first - as per my comment above. Do you have a login for the database to make the changes? If so, it would be good if you can update?

FRamos · January 31, 2017, 12:35pm

Do not know!
Should?

chris · January 31, 2017, 12:39pm

Did you sign up for an account on the database site? You need to do this then email me for access - sorry I can’t remember if you did or not as I get many such requests every day.

FRamos · January 31, 2017, 1:35pm

OK. Thanks @chris
Registed
Awaiting for activation

chris · January 31, 2017, 5:32pm

Done ;).

FRamos · February 1, 2017, 7:36pm

Thanks @chris
I’m going to do some tests.
As soon I get conclusions (if any) I will share it here.

chris · February 1, 2017, 7:50pm

I will look to update the database to add the filter.

chris · February 1, 2017, 9:23pm

I’v updated the alarm_motion on the Z120

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/308

Youll need to delete the current thing and add it again.

FRamos · February 4, 2017, 5:35pm

@chris, I tried load this new Z120 device configuration, but without success. Certainly my fault.
Mean while i’ve been following your new topic ‘Z-Wave refactoring and testing… and SECURITY’ and have already installed this new Binding.
So, I will stop this topic now and will proceed on the new one.
Many thanks for all the support

FRamos · February 7, 2017, 8:03pm

Advised by @chris I´m back to this topic, since the issue on the DCH-Z120 PIR remains.

I’m now using (bundle:list):

168 | Active    |  90 | 2.1.0.201702032321    | openHAB Core
169 | Active    |  80 | 2.1.0.201702032321    | openHAB Karaf Integration
172 | Active    |  80 | 2.1.0.201702032321    | openHAB Dashboard UI
177 | Active    |  80 | 2.4.5                 | Jackson-annotations
178 | Active    |  80 | 2.4.5                 | Jackson-core
179 | Active    |  80 | 2.4.5                 | jackson-databind
180 | Active    |  80 | 2.0.0                 | json-path
182 | Active    |  80 | 2.1.1                 | json-smart
185 | Active    |  75 | 0.9.0.201702010824    | Eclipse SmartHome JSonPath Transformation Service
192 | Active    |  80 | 2.1.0.201702032321    | openHAB 1.x Compatibility Layer
196 | Active    |  80 | 2.1.0.201702032321    | ZWave Binding

my devices DCH-Z110 (Node5) and DCH-Z120 (Node6) have this configuration:

node5.xml (13.2 KB)

node6.xml (13.3 KB)

and gives this results when detects a door open (Node5), or a motion (Node6):

//dchz110 door opened
22:13:07.039 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 5: Incoming command class ALARM
22:13:07.041 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 5: Calling handleApplicationCommandRequest.
22:13:07.043 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 5: Received ALARM command V4
22:13:07.046 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 5: Process NOTIFICATION_REPORT V4
22:13:07.050 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 5: NOTIFICATION report - 0 = 0, event=22, status=255
22:13:07.053 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 5: Alarm Type = ACCESS_CONTROL (0)
22:13:07.055 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
22:13:07.057 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveAlarmValueEvent
22:13:07.058 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
22:13:07.061 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
22:13:07.062 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 22, type OnOffType
22:13:07.063 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating channel state zwave:device:frs:node5:alarm_general to ON [OnOffType]


//dchz120 motion detected
20:14:51.142 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 6: Incoming command class ALARM
20:14:51.143 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 6: Calling handleApplicationCommandRequest.
20:14:51.146 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 6: Received ALARM command V4
20:14:51.149 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 6: Process NOTIFICATION_REPORT V4
20:14:51.151 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 6: NOTIFICATION report - 0 = 0, event=8, status=255
20:14:51.153 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 6: Alarm Type = BURGLAR (0)
20:14:51.155 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
20:14:51.158 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Got an event from Z-Wave network: ZWaveAlarmValueEvent
20:14:51.161 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
20:14:51.165 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION

My interpretation for the fact DCH-Z120 (Node6) can’t handle the “Alarm converter processing NOTIFICATION” is because:

I’ve read CC_ALARM (0x71) is deprecated. CC_NOTIFICATION (0x71) is the successor.

CC_NOTIFICATION_REPORT_V4 (0x05) uses notification type

NOTIFICATION_REPORT_ACCESS_CONTROL_V4 (0x06) with events “Window/Door is open” (0x16) and “Window/Door is closed” (0x17)
and NOTIFICATION_REPORT_HOME_SECURITY_V4 (0x07) with events “Tampering, Product covering removed” (0x03), “Motion detection” (0x07) and “Motion detection Unknown Location” (0x08)

Instead, the deprecated CC_ALARM (0x71) uses alarm type

ALARM_REPORT_ACCESS_CONTROL_V4 (0x06) with events “Window/Door is open” (0x16) and “Window/Door is closed” (0x17)
and ALARM_REPORT_BURGLAR_V4 (0x07), but doesn’t support event (0x08), then it fails for the motion event

My conclusion is that DCH-Z120 should uses CC_NOTIFICATION (0x71) (instead of CC_ALARM)
[CC_NOTIFICATION_REPORT_V4 (0x05) with NOTIFICATION_REPORT_ACCESS_CONTROL_V4 (0x06) and NOTIFICATION_REPORT_HOME_SECURITY_V4 (0x07)]

Despite DCH-Z110 being working it should also be configured with the same CC_NOTIFICATION (0x71)

Reinforcing this, the ‘D-Link-DCH-Z110_120-manual’ never refers CC_ALARM, but mentions:
COMMAND_CLASS_NOTIFICATION_V4,
Notification Type: Home Security (0x07)
Event: Motion Detection, Unknown Location (0x08)
Notification Type: Access Control (0x06)
Event: Door/Window is open (0x16)
Door/Window is closed (0x17)

So, lets adapt the DB in order to replace CC_ALARM by CC_NOTIFICATION_V4 and replace alarmType_BURGLAR by alarmType_HOME_SECURITY for event 3 on both DCH-Z110 and DCH-Z120 and events 7 and 8 on DCH-Z120.

Do you agree?

FRamos · February 9, 2017, 2:00pm

I’ve changed configuration for the two devices, to Sensor Binary Report instead of the previous Notification Report.
This makes me to have both devices working, now with channels sensor_door and sensor_binary instead of using the alarm channels.

This new configuration (Parameter 7, Bit4 = 1) permits the plain use of this devices, but I steel think my last suggestion should be implemented for those who would prefer use the Notification Report type.

chris · February 10, 2017, 8:46am

You’ll note that both of these are the same - 0x71.

The binding uses the appropriate type depending on the version. NOTIFICATION is the same as ALARM - as I mentioned above, they are both the same command class - just the version changes.

As above - they are the same, and the binding does process your notifications correctly I think.

We can’t have both types in the database since they are the same. It doesn’t matter what we call it - ALARM, NOTIFICATION, ALARM_NOTIFICATION, or anything else - this is simply a human readable name. What matters is the class number (0x71). ZWave ensures backward comparability with these classes.

Again, this is just a name - it doesn’t matter to the operation of the protocol. For historical reasons the binding uses names that aren’t 100% consistent with the standard since the standard was only released recently, but it’s only the human readable name - it still processes the data exactly the same.

As I’ve said a earlier in this thread, this is configured in the database. Simply setting the filter in the configuration will make the binding react to the correct events - so long as you are using a recent snapshot of the binding and not the released version.

The following configuration is used for the door open event -:

type=ACCESS_CONTROL, event=22

The following configuration is used for the motion event -:

type=BURGLAR, event=8

Note that the event could also be 7 - depending on the device.

The following configuration is used for the tamper event -:

type=BURGLAR, event=3

Note that the event could also be 4 - depending on the device.

I hope this helps explain this further. I’ve added some of this to the database already but I would strongly urge you to try and do it yourself. I know you said you weren’t confident to change the database, but you clearly have an understanding of things here, and you at least should be able to copy from other entries in the database, or just copy in what I’ve said earlier in post 7 of this thread.

If you’re really stuck, then let me know and I’ll do the changes, but it would be really appreciated if you can try yourself - with around 420 devices in the database, it would be a full time job for me to keep up with everyones requests (which is why I wrote the online database editor - to make it easier for people than having to edit XML files and manage this in Git).

Thanks.
Chris