Fgdw-002 handler_missing_error

Has anyone got the fgdw-002 window/door sensor from fibaro working with OH2 ?

When i add it, it failes every time, and results in “Handler_missing_error”. Heres the output from the log:

2017-07-02 14:31:52.772 [InboxAddedEvent ] - Discovery Result with UID ‘zwave:device:0377035b:node3’ has been added.
2017-07-02 14:31:52.777 [BindingEvent ] - org.openhab.binding.zwave.event.BindingEvent@af2adc
2017-07-02 14:31:56.952 [InboxRemovedEvent ] - Discovery Result with UID ‘zwave:device:0377035b:node2’ has been removed.
2017-07-02 14:32:00.404 [InboxRemovedEvent ] - Discovery Result with UID ‘zwave:device:0377035b:node3’ has been removed.
2017-07-02 14:32:00.410 [ThingAddedEvent ] - Thing ‘zwave:device:0377035b:node3’ has been added.
2017-07-02 14:32:00.462 [hingStatusInfoChangedEvent] - ‘zwave:device:0377035b:node3’ changed from UNINITIALIZED to INITIALIZING
2017-07-02 14:32:00.482 [hingStatusInfoChangedEvent] - ‘zwave:device:0377035b:node3’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2017-07-02 14:32:00.492 [hingStatusInfoChangedEvent] - ‘zwave:device:0377035b:node3’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
==> /var/log/openhab2/openhab.log <==
2017-07-02 14:32:05.463 [WARN ] [ome.core.thing.internal.ThingManager] - Initializing handler for thing ‘zwave:device:0377035b:node3’ takes more than 5000ms.
==> /var/log/openhab2/events.log <==
2017-07-02 14:32:05.483 [ThingUpdatedEvent ] - Thing ‘zwave:device:0377035b:node3’ has been updated.
2017-07-02 14:32:05.489 [ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
==> /var/log/openhab2/openhab.log <==
2017-07-02 14:32:12.672 [WARN ] [l.serialmessage.SendDataMessageClass] - NODE 3: Already processed another send data request for this callback Id, ignoring.
==> /var/log/openhab2/events.log <==
2017-07-02 14:32:13.692 [ThingUpdatedEvent ] - Thing ‘zwave:device:0377035b:node3’ has been updated.
2017-07-02 14:32:13.692 [ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2017-07-02 14:32:14.511 [ThingUpdatedEvent ] - Thing ‘zwave:device:0377035b:node3’ has been updated.
2017-07-02 14:32:14.515 [ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2017-07-02 14:32:14.565 [ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2017-07-02 14:32:14.577 [ThingUpdatedEvent ] - Thing ‘zwave:device:0377035b:node3’ has been updated.
2017-07-02 14:32:14.629 [ThingUpdatedEvent ] - Thing ‘zwave:device:0377035b:node3’ has been updated.
2017-07-02 14:32:14.633 [ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2017-07-02 14:32:14.711 [ThingUpdatedEvent ] - Thing ‘zwave:device:0377035b:node3’ has been updated.
2017-07-02 14:32:14.713 [ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2017-07-02 14:32:14.799 [ThingUpdatedEvent ] - Thing ‘zwave:device:0377035b:node3’ has been updated.
2017-07-02 14:32:14.804 [ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2017-07-02 14:32:15.655 [ThingUpdatedEvent ] - Thing ‘zwave:device:0377035b:node3’ has been updated.
2017-07-02 14:32:15.656 [ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2017-07-02 14:32:16.340 [ThingUpdatedEvent ] - Thing ‘zwave:device:0377035b:node3’ has been updated.
2017-07-02 14:32:16.347 [ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2017-07-02 14:32:16.367 [hingStatusInfoChangedEvent] - ‘zwave:device:0377035b:node3’ changed from ONLINE to UNINITIALIZED
2017-07-02 14:32:16.516 [hingStatusInfoChangedEvent] - ‘zwave:device:0377035b:node3’ changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2017-07-02 14:32:16.628 [hingStatusInfoChangedEvent] - ‘zwave:device:0377035b:node3’ changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2017-07-02 14:32:16.633 [hingStatusInfoChangedEvent] - ‘zwave:device:0377035b:node3’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2017-07-02 14:32:16.640 [hingStatusInfoChangedEvent] - ‘zwave:device:0377035b:node3’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2017-07-02 14:32:19.965 [BindingEvent ] - org.openhab.binding.zwave.event.BindingEvent@68d7b9
==> /var/log/openhab2/openhab.log <==
2017-07-02 14:32:21.630 [WARN ] [ome.core.thing.internal.ThingManager] - Initializing handler for thing ‘zwave:device:0377035b:node3’ takes more than 5000ms.
==> /var/log/openhab2/events.log <==
2017-07-02 14:32:21.647 [ThingUpdatedEvent ] - Thing ‘zwave:device:0377035b:node3’ has been updated.
2017-07-02 14:32:21.672 [hingStatusInfoChangedEvent] - ‘zwave:device:0377035b:node3’ changed from ONLINE to UNINITIALIZED
==> /var/log/openhab2/openhab.log <==
2017-07-02 14:32:26.792 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occurred while calling thing handler factory 'org.openhab.binding.zwave.internal.ZWaveHandlerFactory@1e7195’
java.util.concurrent.TimeoutException
at java.util.concurrent.FutureTask.get(FutureTask.java:205)[:1.8.0_121]
at org.eclipse.smarthome.core.common.SafeMethodCaller.callAsynchronous(SafeMethodCaller.java:194)[98:org.eclipse.smarthome.core:0.9.0.b5]
at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:83)[98:org.eclipse.smarthome.core:0.9.0.b5]
at org.eclipse.smarthome.core.common.SafeMethodCaller.call(SafeMethodCaller.java:67)[98:org.eclipse.smarthome.core:0.9.0.b5]
at org.eclipse.smarthome.core.thing.internal.ThingManager.doUnregisterHandler(ThingManager.java:795)[105:org.eclipse.smarthome.core.thing:0.9.0.b5]
at org.eclipse.smarthome.core.thing.internal.ThingManager.unregisterHandler(ThingManager.java:785)[105:org.eclipse.smarthome.core.thing:0.9.0.b5]
at org.eclipse.smarthome.core.thing.internal.ThingManager.unregisterAndDisposeHandler(ThingManager.java:866)[105:org.eclipse.smarthome.core.thing:0.9.0.b5]
at org.eclipse.smarthome.core.thing.internal.ThingManager.access$17(ThingManager.java:860)[105:org.eclipse.smarthome.core.thing:0.9.0.b5]
at org.eclipse.smarthome.core.thing.internal.ThingManager$3.run(ThingManager.java:289)[105:org.eclipse.smarthome.core.thing:0.9.0.b5]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_121]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_121]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_121]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_121]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]
==> /var/log/openhab2/events.log <==
2017-07-02 14:33:00.041 [ItemChannelLinkAddedEvent ] - Link ‘Node3_DoorSensor-zwave:device:0377035b:node3:sensor_binary’ has been added.
==> /var/log/openhab2/openhab.log <==
2017-07-02 14:33:26.895 [ERROR] [ome.core.thing.internal.ThingManager] - Thing type migration failed for zwave:device:0377035b:node3. The handler deregistration did not complete within 60,000ms.
==> /var/log/openhab2/events.log <==
2017-07-02 14:33:26.997 [hingStatusInfoChangedEvent] - ‘zwave:device:0377035b:node3’ changed from UNINITIALIZED to INITIALIZING
2017-07-02 14:33:27.004 [hingStatusInfoChangedEvent] - ‘zwave:device:0377035b:node3’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2017-07-02 14:33:27.027 [hingStatusInfoChangedEvent] - ‘zwave:device:0377035b:node3’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2017-07-02 14:33:27.032 [hingStatusInfoChangedEvent] - ‘zwave:device:0377035b:node3’ changed from ONLINE to UNINITIALIZED (HANDLER_MISSING_ERROR)
2017-07-02 14:33:27.034 [ThingUpdatedEvent ] - Thing ‘zwave:device:0377035b:node3’ has been updated.

Hi,
I’m facing the exact same issue with the fibaro smoke detector (version 2 firmware 3.3).
I also have a motion sensor from fibaro (firmware 3.2) who works like a charm.

OK, I found the solution by removing things and installing them again thanks to this :
https://community.openhab.org/t/fgms-001-unable-to-identify-again/23109