Fibaro Door Sensor (FGDW-002) Does not work in Openhab 2.5

I am running Openhab 2.5 on a linux machine.
I wanted to connect some door/window sensors. I got me a fibaro systems door/window sensor 2 (FGDW-002).

As most of the functionality works (temperature, battery levels, tampering), the door sensor itself does not work. I have created a “contact” item that is connected with the nodes door sensor channel:

Contact entry_door "Door Entry [%s]" <door> { channel="zwave:device:controller:node4:sensor_door" }

While my ZWave PIR sensors work and trigger updates to their items, the door contact does not trigger any update whatsoever.

if I am checking the ZWave logs (in this case from opening the door) I see the command being sent from the sensor:

17:54:25.470 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0B 00 04 08 04 03 20 01 63 CA 00 77 
17:54:25.473 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=8, payload=08 04 03 20 01 63 CA 00 
17:54:25.477 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=8, payload=08 04 03 20 01 63 CA 00 
17:54:25.479 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - lastTransaction null
17:54:25.480 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 4: Application Command Request (ALIVE:REQUEST_NIF)
17:54:25.481 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 4: Incoming command class COMMAND_CLASS_BASIC, endpoint 0
17:54:25.483 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported
17:54:25.485 [DEBUG] [otocol.commandclass.ZWaveCommandClass] - NODE 4: Received COMMAND_CLASS_BASIC V0 BASIC_SET
17:54:25.486 [DEBUG] [l.commandclass.ZWaveBasicCommandClass] - NODE 4: Basic report, value = 99
17:54:25.487 [DEBUG] [ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0B 00 04 00 04 03 20 01 63 DB 00 6E 
17:54:25.487 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
17:54:25.489 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_BASIC, value = 99
17:54:25.489 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 03 20 01 63 DB 00 
17:54:25.491 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 4: Commands processed 1.
17:54:25.492 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 4: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@35c4bed6.
17:54:25.493 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
17:54:25.494 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
17:54:25.494 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 03 20 01 63 DB 00 
17:54:25.495 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - lastTransaction null
17:54:25.496 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 4: Application Command Request (ALIVE:REQUEST_NIF)
17:54:25.497 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 4: Incoming command class COMMAND_CLASS_BASIC, endpoint 0
17:54:25.497 [DEBUG] [ing.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported
17:54:25.498 [DEBUG] [otocol.commandclass.ZWaveCommandClass] - NODE 4: Received COMMAND_CLASS_BASIC V0 BASIC_SET
17:54:25.499 [DEBUG] [l.commandclass.ZWaveBasicCommandClass] - NODE 4: Basic report, value = 99
17:54:25.499 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
17:54:25.500 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_BASIC, value = 99
17:54:25.501 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 4: Commands processed 1.
17:54:25.502 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - NODE 4: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@7fcb0a65.
17:54:25.502 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
17:54:25.503 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
17:54:25.504 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
17:54:25.504 [DEBUG] [rnal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

my sensor is configured in the following way:

  • 1: closed when near
  • 2: open/close indication on
  • 2: wakeup indication off
  • 2: tamper indication off
  • 3: tried any of these values. currently at “none as secure”
  • 11: switch after open and close
  • 12: 99
  • 13: 0
  • 14: 0
  • 15: 0

Associations:

  • 1: Lifeline: Controller
  • 2: on/off: Controller
  • 3: tamper: none

properties:

I tried reboots of the system, removing the sensor, repowering the sensor… nothing worked.

Ah, forgot to mention:

  • I have found multiple threads in this forum adressing similar issues. most of them were solved by “updating” the binding or openhab. However, I am on the most recent versions, I could find.

The device seems to be sending BASIC messages which the binding probably isn’t processing. I suspect that there is a setting in the device that will change this, or maybe you have incorrect association groups configured (although these should be configured automatically).

The binding will likely be looking for the ALARM messages rather than the BASIC messages.

Try removing that association:

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

Group 2: On/Off

is assigned to the device status - Hall effect sensor (sends Basic Set command frames) is assigned to the device status - Hall effect sensor (sends Basic Set command frames).

As the tamper switch did work, I just soldered a contact switch to the tamper switch and used that one.