I’ve been using openhab with Z-WAVE for quite some time now but I have a real big problem with my Fibaro FGMS001 sensor. It’s connected and fully recognized.
And there comes the “but”…
I can read the temperature, battery level and luminance. But there are no transmissions/events for the tamper and motion alarm!
I have tried every fix I’ve found on the internet, but nothing works.
excluded / included it several times
waited for weeks / woke it up several times for the initialisation process to be completed
resetted the controller (!) and the sensor several times.
changed the parameter 8 to “always active” and 12 to “Basic ON and Basic OFF”
This is one of the ways I’ve tried to access it:
String Movement_Gang “Movement: [%s]” { channel=“zwave:device:c61532e6:node9:alarm_motion” }
But as I mentioned before: there is nothing in the openhab.log and events.log. I really don’t know what to do other than buying another Fibaro sensor for testing.
Does anyone have any suggestion for me how to proceed?
First thing is, you cannot actively “read” neither values such as the temperature nor alarms. FMGS, if configured correctly, will send them.
First, enable zwave debugging (log:set debug org.openhab.binding.zwave) in Karaf console and look for zwave messages from that node ID of your FGMS to ensure it’s sending them if triggered.
Next, you must properly map that to a Switch type item in your .items file (you used “String”, change that to “Switch”. Rest of the line is ok, assuming you’re using zwave2 binding and not OH1 binding any more).
Your log is fine, it shows OH to poll the device but no messages to originate from the device.
You need to wake it up (push the button three times) or wait until it wakes up (I think every 2 hours by default).
So messages are received.
Do you also see (ALARM or other) messages arrive when you trigger the motion and/or tamper sensor ?
Have you switched from String to Switch as mentioned in my first post ?
Yes, messages are received (temperature, luminance).
Today I found something new in the logs… (I’ve let my child play in front of the motion sensor)
2018-08-15 11:20:53.696 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Command received zwave:device:c61532e6:node9:alarm_motion --> ON
2018-08-15 11:20:53.713 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 9: No event found with name 'eventON'
2018-08-15 11:20:53.718 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: No messages returned from converter
2018-08-15 11:20:54.859 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Command received zwave:device:c61532e6:node9:alarm_motion --> OFF
2018-08-15 11:20:54.936 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 9: No event found with name 'eventOFF'
2018-08-15 11:20:54.938 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: No messages returned from converter
Hmm, don’t know, but sounds the binding could not properly map the message it received.
Possibly an issue with the database used for mapping. It’s hardcoded into the binding.
I suggest you upgrade OH to the latest version (snapshot).
It’s strange… I’m currently using OH 2.2, I should really upgrade to 2.3. But I’ve had the same issue with 2.1 and before as well. As meationed earlier, I’ve had the problem for a very long time now. I’ve also just ordered a second FGMS001 now just to make sure it’s not a malfunction in the device itself.
Is there a way for a firmware upgrade for the FGMS001?
And I found the solution! It’s working now / both are working.
I think my fault was that I added the first FGMS with PaperUI. I added the second one with Habmin and it worked. So I excluded the first one, reset it to factory settings and included it with Habmin. That worked for me.
