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?