Detecting 'tamper' alarm with Devolo MT02648 Door/Window Contact

Tags: #<Tag:0x00007fc8efa11bb0>

I’m using a zwave Devolo MT02648 Door/Window Contact and openHAB 2.5.10 and I’m trying to work out how to detect the Tamper alarm function of this sensor. It’s this device:

It’s a door/window sensor with a magnet… moving the magnet away from or towards the sensor causes an event and I’ve got that updating a channel like this:

2020-12-14 10:55:25.870 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 12: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2020-12-14 10:55:25.872 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 12: SECURITY NOT required on COMMAND_CLASS_SENSOR_BINARY
2020-12-14 10:55:25.874 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 12: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
2020-12-14 10:55:25.876 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Processing Sensor Type 10
2020-12-14 10:55:25.878 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Sensor Type is DOORWINDOW
2020-12-14 10:55:25.880 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 12: Sensor Binary report, type=Door/Window, value=255
2020-12-14 10:55:25.882 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2020-12-14 10:55:25.884 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=255
2020-12-14 10:55:25.887 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:fd0cc7d1:node12:sensor_door to OPEN [OpenClosedType]

ie, zwave:device:fd0cc7d1:node12:sensor gets set to OPEN or CLOSED when the magnet moved.

There is also a tamper switch on the back of the device. When that opens I get this:

2020-12-14 11:01:45.281 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 12: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2020-12-14 11:01:45.283 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 12: SECURITY NOT required on COMMAND_CLASS_SENSOR_BINARY
2020-12-14 11:01:45.285 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 12: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
2020-12-14 11:01:45.286 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Processing Sensor Type 8
2020-12-14 11:01:45.288 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Sensor Type is TAMPER
2020-12-14 11:01:45.290 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 12: Sensor Binary report, type=Tamper, value=255
2020-12-14 11:01:45.291 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2020-12-14 11:01:45.293 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=255
2020-12-14 11:01:45.295 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: Updating channel state zwave:device:fd0cc7d1:node12:sensor_door to OPEN [OpenClosedType]

So I’m getting the same event when the door opens as I do when the tamper switch is opened… but in the openhab.log I can see that these are slightly different as one has “Sensor Type is DOORWINDOW” and the other has “Sensor Type is TAMPER”.

In both cases I get an event “zwave_device_fd0cc7d1_node12_sensor_door changed from CLOSED to OPEN”. How can I identify which Sensor Type has caused the event in my rule?

(There’s also an Alarm channel, but I’m not sure what causes the device to generate an Alarm. Not this, as far as I can see.)

I’ll update the binding definitions - it should solve this in a few days.

Chris,

That’s excellent. Thanks very much.

1 Like

Thank me after it works :slight_smile:

Seriously though - I’ll do a database update later so this should be in the system tomorrow. You’ll need to delete and add the device back again (no need to exclude) - this just allows OH to pick up the new definitions. Let me know if it works ok or if it requires further tweeks.

1 Like