FGMS001 not recognised

The device is not recognized. Sometimes after a while it is recognized but then suddenly it is not recognized anymore and OH2 reports online and offline and not recognized.

OH2 Version: 2.2.0.201710280843
Zwave Binding: 2.2.0.201710280843

Device name: Fibargroup FGMS0001
Device version: 3.2

Link to http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/328
An XML is not being generated for the device.

2017-10-29 12:46:59.139 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Checking zwave:qubino_zmnhdd_00_000
2017-10-29 12:46:59.147 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-10-29 12:46:59.153 [home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:03f9975a:node10' has been added.
2017-10-29 12:46:59.152 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:03f9975a:node10' to inbox.
2017-10-29 12:47:18.923 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 10: Device already known.

This indicates that the binding has not been able to communicate with the device. It probably means that you haven’t woken up the device (potentially required a few times) to allow this communication to take place.

There will be a button in the device to do this - maybe you have to click it quickly three times or something to wake it up - the manual should tell you how to do this.

Thanks Chris!

I got it working by letting it rest for an hour or so after I pushed the wake-up button. It finally works.

My problems are not resolved. After a reboot, due to an upgrade of OpenHAB to the latest snapshot, the following is shown in the log. And the device is listed as offline. It is a FGMS001. I find this behaviour strange as my other battery operated zwave smoke detector (FGSD002) starts and is active right from the start.

Actually looking to the FGSD002 it says Status: ONLINE Node initialising: WAIT. Which I rather understand as I think it waits for the device to wake-up before a timeout.

Can anyone help?

2017-10-30 14:05:44.580 [hingStatusInfoChangedEvent] - 'zwave:device:03f9975a:node10' changed from ONLINE to UNINITIALIZED
2017-10-30 14:05:44.632 [ERROR] [ome.core.thing.internal.ThingManager] - Exception occurred while disposing handler of thing 'zwave:device:03f9975a:node10': java.lang.NullPointerException
2017-10-30 14:05:44.710 [hingStatusInfoChangedEvent] - 'zwave:device:03f9975a:node10' changed from ONLINE to UNINITIALIZED (HANDLER_MISSING_ERROR)
2017-10-30 14:05:49.829 [temChannelLinkRemovedEvent] - Link 'zwave_device_03f9975a_node10_alarm_tamper => zwave:device:03f9975a:node10:alarm_tamper' has been removed.
2017-10-30 14:05:49.959 [temChannelLinkRemovedEvent] - Link 'zwave_device_03f9975a_node10_sensor_binary => zwave:device:03f9975a:node10:sensor_binary' has been removed.
2017-10-30 14:07:48.501 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_03f9975a_node10_battery_level-zwave:device:03f9975a:node10:battery-level' has been added.
2017-10-30 14:07:48.663 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_03f9975a_node10_alarm_tamper-zwave:device:03f9975a:node10:alarm_tamper' has been added.
2017-10-30 14:07:48.697 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_03f9975a_node10_sensor_seismicintensity-zwave:device:03f9975a:node10:sensor_seismicintensity' has been added.
2017-10-30 14:07:48.870 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_03f9975a_node10_sensor_temperature-zwave:device:03f9975a:node10:sensor_temperature' has been added.
2017-10-30 14:07:48.914 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_03f9975a_node10_sensor_binary-zwave:device:03f9975a:node10:sensor_binary' has been added.
2017-10-30 14:07:48.995 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_03f9975a_node10_alarm_motion-zwave:device:03f9975a:node10:alarm_motion' has been added.
2017-10-30 14:07:49.073 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_03f9975a_node10_sensor_luminance-zwave:device:03f9975a:node10:sensor_luminance' has been added.
2017-10-30 14:07:49.236 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_03f9975a_node10_alarm_general-zwave:device:03f9975a:node10:alarm_general' has been added.
2017-10-30 14:08:54.832 [vent.ItemStateChangedEvent] - zwave_device_03f9975a_node10_battery_level changed from NULL to 100
2017-10-30 14:08:54.895 [vent.ItemStateChangedEvent] - zwave_device_03f9975a_node10_alarm_tamper changed from NULL to OFF
2017-10-30 14:08:54.902 [vent.ItemStateChangedEvent] - zwave_device_03f9975a_node10_sensor_seismicintensity changed from NULL to 0
2017-10-30 14:08:54.956 [vent.ItemStateChangedEvent] - zwave_device_03f9975a_node10_sensor_temperature changed from NULL to 21.3
2017-10-30 14:08:54.967 [vent.ItemStateChangedEvent] - zwave_device_03f9975a_node10_sensor_binary changed from NULL to OFF
2017-10-30 14:08:54.986 [vent.ItemStateChangedEvent] - zwave_device_03f9975a_node10_alarm_motion changed from NULL to OFF
2017-10-30 14:08:55.004 [vent.ItemStateChangedEvent] - zwave_device_03f9975a_node10_sensor_luminance changed from NULL to 33
2017-10-30 14:08:55.064 [vent.ItemStateChangedEvent] - zwave_device_03f9975a_node10_alarm_general changed from NULL to OFF
2017-10-30 14:09:08.190 [hingStatusInfoChangedEvent] - 'zwave:device:03f9975a:node10' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)
2017-10-30 14:09:09.029 [hingStatusInfoChangedEvent] - 'zwave:device:03f9975a:node10' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING
2017-10-30 14:09:09.033 [hingStatusInfoChangedEvent] - 'zwave:device:03f9975a:node10' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2017-10-30 14:09:17.889 [hingStatusInfoChangedEvent] - 'zwave:device:03f9975a:node10' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to OFFLINE: Node not found in Z-Wave network

This item still is not working. I think it does not configure itself in the correct way.

See the image below what it thinks its properties are. The zwave_class_basic and zwave_class_generic are not_known. This cannot be correct. How can I change that?

I swicthed to HabMin for managing Z-Wave devices. The motion sensor is now shown correctly and sends data and reports.