Fibaro multisensor FGMS-001 does not work on latest zwave snapshot

S2w · October 9, 2018, 8:59pm

Platform information:
- Hardware: _Raspberry PI
- OS: raspbian
- Java Runtime Environment: which java platform is used and what version
- openHAB version:openHAB 2.4.0 Milestone Build

I have upgraded to the latest milestone build (2.4 M4) on my raspberrypi loaded with raspbian. Previous to this my 2 x Fibaro FGMS-001 were working correctly. Now I get nothing back from either of them.

I have followed the instructions for the new zwave binding by removing all zwave components and re-adding them back. Some of my z-wave devices do work but the 2 x FGMS-001 do not work at all. I have tried waking them up,leaving for several days etc but no luck

I have a zwave.log file but not sure how to post it… I have added the first few lines here in the event it helps

09-Oct-2018 21:38:46.949 [DEBUG] [org.openhab.binding.zwave                         ] - BundleEvent STOPPING - org.openhab.binding.zwave
09-Oct-2018 21:38:46.953 [DEBUG] [org.openhab.binding.zwave                         ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.core.ConfigDescriptionProvider, org.eclipse.smarthome.config.core.ConfigOptionProvider}={service.id=230, service.bundleid=224, service.scope=bundle, component.name=org.openhab.binding.zwave.internal.ZWaveConfigProvider, component.id=25} - org.openhab.binding.zwave
09-Oct-2018 21:38:46.962 [DEBUG] [org.openhab.binding.zwave                         ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.core.events.EventFactory}={service.id=177, service.bundleid=224, service.scope=bundle, component.name=org.openhab.binding.zwave.event.BindingEventFactory, component.id=26} - org.openhab.binding.zwave
09-Oct-2018 21:38:46.968 [DEBUG] [org.openhab.binding.zwave                         ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.discovery.usbserial.UsbSerialDiscoveryParticipant}={service.id=133, service.bundleid=224, service.scope=bundle, component.name=org.openhab.binding.zwave.discovery.ZWaveUsbSerialDiscoveryParticipant, component.id=27} - org.openhab.binding.zwave
09-Oct-2018 21:38:46.973 [DEBUG] [org.openhab.binding.zwave                         ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.core.thing.binding.ThingHandlerFactory}={service.id=134, service.bundleid=224, service.scope=bundle, component.name=org.openhab.binding.zwave.internal.ZWaveHandlerFactory, component.id=28} - org.openhab.binding.zwave
09-Oct-2018 21:38:46.979 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Handler disposed. Unregistering listener.
09-Oct-2018 21:38:46.992 [TRACE] [ternal.protocol.initialization.ZWaveNodeSerializer] - Initializing ZWaveNodeSerializer.
09-Oct-2018 21:38:47.042 [TRACE] [ternal.protocol.initialization.ZWaveNodeSerializer] - Initialized ZWaveNodeSerializer.
09-Oct-2018 21:38:47.044 [DEBUG] [ternal.protocol.initialization.ZWaveNodeSerializer] - NODE 2: Serialise aborted as static stages not complete
09-Oct-2018 21:38:47.050 [DEBUG] [org.openhab.binding.zwave                         ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=321, service.bundleid=224, service.scope=singleton} - org.openhab.binding.zwave
09-Oct-2018 21:38:47.059 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 5: Handler disposed. Unregistering listener.
09-Oct-2018 21:38:47.066 [TRACE] [ternal.protocol.initialization.ZWaveNodeSerializer] - Initializing ZWaveNodeSerializer.
09-Oct-2018 21:38:47.100 [TRACE] [ternal.protocol.initialization.ZWaveNodeSerializer] - Initialized ZWaveNodeSerializer.
09-Oct-2018 21:38:47.102 [DEBUG] [ternal.protocol.initialization.ZWaveNodeSerializer] - NODE 5: Serializing to file /var/lib/openhab2/zwave/network_e2c3f7c4__node_5.xml
09-Oct-2018 21:38:47.148 [DEBUG] [org.openhab.binding.zwave                         ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=320, service.bundleid=224, service.scope=singleton} - org.openhab.binding.zwave
09-Oct-2018 21:38:47.155 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 4: Handler disposed. Unregistering listener.
09-Oct-2018 21:38:47.163 [TRACE] [ternal.protocol.initialization.ZWaveNodeSerializer] - Initializing ZWaveNodeSerializer.
09-Oct-2018 21:38:47.190 [TRACE] [ternal.protocol.initialization.ZWaveNodeSerializer] - Initialized ZWaveNodeSerializer.
09-Oct-2018 21:38:47.191 [DEBUG] [ternal.protocol.initialization.ZWaveNodeSerializer] - NODE 4: Serialise aborted as static stages not complete
09-Oct-2018 21:38:47.197 [DEBUG] [org.openhab.binding.zwave                         ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=319, service.bundleid=224, service.scope=singleton} - org.openhab.binding.zwave
09-Oct-2018 21:38:47.202 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 3: Handler disposed. Unregistering listener.
09-Oct-2018 21:38:47.211 [TRACE] [ternal.protocol.initialization.ZWaveNodeSerializer] - Initializing ZWaveNodeSerializer.
09-Oct-2018 21:38:47.237 [TRACE] [ternal.protocol.initialization.ZWaveNodeSerializer] - Initialized ZWaveNodeSerializer.
09-Oct-2018 21:38:47.238 [DEBUG] [ternal.protocol.initialization.ZWaveNodeSerializer] - NODE 3: Serialise aborted as static stages not complete
09-Oct-2018 21:38:47.244 [DEBUG] [org.openhab.binding.zwave                         ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=323, service.bundleid=224, service.scope=singleton} - org.openhab.binding.zwave
09-Oct-2018 21:38:47.287 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Stopped ZWave thread: Receive
09-Oct-2018 21:38:50.298 [INFO ] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - Stopped ZWave serial handler
09-Oct-2018 21:38:50.301 [DEBUG] [nhab.binding.zwave.discovery.ZWaveDiscoveryService] - ZWave discovery: Deactivate zwave:serial_zstick:512
09-Oct-2018 21:38:50.307 [DEBUG] [org.openhab.binding.zwave                         ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=322, service.bundleid=224, service.scope=singleton} - org.openhab.binding.zwave
09-Oct-2018 21:38:50.310 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - Interrupted taking message from recvQueue
java.lang.InterruptedException: null
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2014) ~[?:?]
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2048) ~[?:?]
	at java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403) ~[?:?]
	at org.openhab.binding.zwave.internal.protocol.ZWaveTransactionManager$ZWaveReceiveThread.run(ZWaveTransactionManager.java:426) [224:org.openhab.binding.zwave:2.4.0.M4]
09-Oct-2018 21:38:50.361 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
09-Oct-2018 21:38:50.363 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
09-Oct-2018 21:38:50.366 [TRACE] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 2: listening == false, frequentlyListening == false, awake == false
09-Oct-2018 21:38:50.367 [TRACE] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 2: Node not awake!
09-Oct-2018 21:38:50.370 [TRACE] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 4: listening == false, frequentlyListening == false, awake == false
09-Oct-2018 21:38:50.371 [TRACE] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 4: Node not awake!
09-Oct-2018 21:38:50.374 [TRACE] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 3: listening == false, frequentlyListening == false, awake == false
09-Oct-2018 21:38:50.375 [TRACE] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 3: Node not awake!
09-Oct-2018 21:38:50.378 [TRACE] [ng.zwave.internal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage nothing
09-Oct-2018 21:38:51.112 [DEBUG] [org.openhab.binding.zwave.internal.ZWaveActivator ] - ZWave ```

3DJupp · October 14, 2018, 10:51pm

I also noticed, that there were some differences. Since i had to readd one of the sensors, I can understand the trouble with the inclusion.
My sensors are back in the ZWave Network, but a Motion dectetion will only be shown in the sitemap.
Related rules won’t be executed anymore.

witti · October 27, 2018, 4:03pm

I am not on the snapshot… I just did a fresh install of openhabian and all internal updates.
A brand new FGMS-001 is only detected as “unknown” device like that in Paper UI:

Z-Wave Node 2 (010F:0801:1002:3.3)

Everything matches to the info in the zipped json-Database, except the 3.2 version there is 3.3 for me - it should not matter, but it seems to…
Maybe because there are two FGMS-001-Entries in the DB it must fall back to include the version - so for everyone having neither a very old or the 3.2 version, it will fail?
If so it should be reported as a bug.

Unfortunately, there seems to be no possibility to select a device manually, at least not in the GUI – and in command line I am still googling how to do that… So that is the real bug (or missing feature), to suggest “close” matches from the DB in case there is no “full” match… I also checked out if in the habmin UI I had such a selection, but unfortunately not…

chris · October 27, 2018, 4:08pm

Please update to the latest snapshot and it will work.

witti · October 27, 2018, 4:15pm

Good Idea…

I will give that a try…

Update: On 2.4.0 Snapshot 4, The sensor is detected but no usable data arrives. (Some data has been seen in the log files, but that never propagated to any UI I tried).
I will have to dig deeper with a more native approach i.e. setting up arch linux secondary pi, skip all that fancy GUI stuff and try to get a more native service scripted…

witti · October 28, 2018, 9:55pm

Today the sensor was one of the view surviving things in Paper UI and posted a value that was either sensible or just the static with my -4 degC offset deducted. Will have to wait for the room to be cooled down tomorrow.
But I seem to be getting there…

Bernd_R · November 29, 2018, 8:21pm

I habe exactly the same issue, did switching on 2.4.0 Snapshot 4 solve the problem @witti?