[SOLVED] Vision Door/Windows sensor zd2102 open/close and tamper are not triggered to different events

Hi chris,

now I’ve done the debug for this device. Hopefully you can see the problem.

Device:
Node 6: Vision ZD2102
Type/ID: 2001:0106
Firmware Version: 5.1

items:
Contact DoorSensor03 “Sensor 3 [MAP(de.map):%s]” {channel=“zwave:device:15a7a49f3a6:node6:sensor_door”}
Switch DoorSensor03_Sabotage “Sensor 3 Tamper [%s]” {channel=“zwave:device:15a7a49f3a6:node6:alarm_burglar”}

This device has a door/open contact, a tamper contact and a enternal switch (binary contact) if parameter 1 is set.
In the documentation of Vision ZD2102:

The ZD2102 sensor equipped with tamper switch. If the cover of sensor is removed, the door sensor will send an alarm report (type:01, level:11) to the Z-Wave

External Switch: If your window needs two sensors for fully monitoring. You could use an external switch to connect with the ZD2102 for extending detection. The ZD2102 has 2 normally closed contact terminals. These can be used for additional external switch wired contacts. The external switch will send an alarm report (type:01,level:11) by opening the window/door.
For me this means, the external switch acts as tamper switch in this case too. Which means, I can seperate door/open (sensor_door event) from external switch open (alarm_burglar event). But I cannot seperate tamper alarm from external switch open/close, because both will be alarm_burglar event.

My problem is, that the two events comes in parallel and not as expected. See my discovery.

What I’ve done:

Starting with:

  1. door/window contact closed, tamper contact closed, binary contact closed
    
  2. 2017-05-28 10:59:11.826
    door/window contact changed to open

event log:
DoorSensor03_Sabotage changed from OFF to ON
DoorSensor03 changed from CLOSED to OPEN
wrong, only DoorSensor03 should change status not DoorSensor03_Sabotage

  1. 2017-05-28 11:00:41.593
    door/window contact open to closed
    DoorSensor03_Sabotage changed from ON to OFF
    DoorSensor03 changed from OPEN to CLOSED
    wrong, only DoorSensor03 should change status not DoorSensor03_Sabotage

  2. 2017-05-28 11:01:38.687
    tamper changed from close to open
    DoorSensor03_Sabotage changed from OFF to ON
    correct only DoorSensor03_Sabotage

  3. 2017-05-28 11:02:26.969
    tamper changed from open to close
    DoorSensor03_Sabotage changed from ON to OFF
    correct only DoorSensor03_Sabotage

  4. 2017-05-28 11:03:46.739
    binary contact changed from close to open
    DoorSensor03_Sabotage changed from OFF to ON
    DoorSensor03 changed from CLOSED to OPEN
    wrong, as written in the documentation, the external binary contact works similar to tamper contact. which means for me, if this contact goes to open the same event tamper was send from device, but this is not correct interpreted here, again both events are reported

  5. 2017-05-28 11:04:46.419
    binary contact changed from open to close
    DoorSensor03_Sabotage changed from ON to OFF
    DoorSensor03 changed from OPEN to CLOSED
    wrong, as written in the documentation, the external binary contact works similar to tamper contact. which means for me, if this contact goes to close the same event tamper was send from device, but this is not correct interpreted here, again both events are reported

I attached the full openhab.log (renamed from .log to .xml because of upload restrictions), the commented log (renamed from .txt to .xml because of upload restrictions) and the device XML-file

Hopefully you can work on it and find the problem.

node6.xml (8.7 KB)
openhab.xml (55.2 KB)
commented log.xml (57.3 KB)

If I should test something, just send me a post here