Fibaro FGK-101 runs amok in OH 2.2

After my first FGK-101 finally workes at least as a door sensor (but without tamper alarm) under 2.2 I dared buying some more. The first new one could be included and configured without any problems to my Razberry and worked fine. So I glued it to its place, and tested it positive. Trying to include the second one, this stays a “unknown device” and (without jnowing if there is any dependency between these two problems) the second but last one started to run amok after an hour it was glued in place.

Since then I get log entries
"2018-01-08 18:57:57.097 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4c4871f0:node18’ has been updated." every three seconds and the device is using up its battery (now reduced to 70%). Restarting the device and my openHAB Raspberry did not change this behaviour.

Any ideas? I hate thinking about removing it again, as the gluepad will be destroyed and is quite hard to remove from the windowframe (had this trouble with the very first one I bought).

For the unknown device problem, Try to wake the device up as often if it is fully discovered.

Another question.
Do the devcies all have the same firmware version?

I run into a problem with Version 2.1. 2.5 and 3.2 are working well.

The new ones are 2.5, and the elder one is a 3.2. And as I was just looking for that I found out something interesting: The 2.5 device, that is running amok had a wakup interval of 1 second when I opened it again (so the log-entries seem to follow this). But whatever I enter there, no change is saved, although there is no error reported when I save them. I tried with the location, but this is also not saved.

To complete inclusion of the next device i cannot Count how many times I woke it up during the last days. This is not working.

Log while trying to save changes:
2018-01-08 19:21:00.330 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=wakeup_interval, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_3, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_2, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_1_2, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_2_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=wakeup_node, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_7_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_9_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_12_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_3_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_13_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_5_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_14_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]
2018-01-08 19:21:00.667 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4c4871f0:node18’ has been updated.
2018-01-08 19:21:00.676 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=group_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_3, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_2, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_1_2, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_2_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_7_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_9_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_12_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_3_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_13_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_5_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=config_14_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]
2018-01-08 19:21:00.789 [hingStatusInfoChangedEvent] - ‘zwave:device:4c4871f0:node18’ changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2018-01-08 19:21:00.808 [hingStatusInfoChangedEvent] - ‘zwave:device:4c4871f0:node18’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2018-01-08 19:21:00.976 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4c4871f0:node18’ has been updated.
2018-01-08 19:21:00.996 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=group_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_3, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_2, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]
2018-01-08 19:21:01.028 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4c4871f0:node18’ has been updated.
2018-01-08 19:21:01.375 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=group_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_2, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]
2018-01-08 19:21:01.382 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4c4871f0:node18’ has been updated.
2018-01-08 19:21:01.772 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=group_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]
2018-01-08 19:21:01.776 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4c4871f0:node18’ has been updated.
2018-01-08 19:21:02.541 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4c4871f0:node18’ has been updated.
2018-01-08 19:21:02.572 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=group_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]
2018-01-08 19:21:15.094 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4c4871f0:node18’ has been updated.
2018-01-08 19:21:17.528 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4c4871f0:node18’ has been updated.
2018-01-08 19:21:19.940 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4c4871f0:node18’ has been updated.
2018-01-08 19:21:22.371 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:4c4871f0:node18’ has been updated.

As I know there is no real acknowledge that the device got the update of the settings in teh log.

I just press the wakeup button (which is only the button on the back!) 3 times within 1sec and repeat this until I see an change.

Wow, this was crazy! I tried waking up by tipping 3 times (although I always thought, that this would start inclusion an 1 time would wake up). After the second time it worked. But after changing parameters like location and wakeup time (this device started with a crude 115… something) in paper-UI it also went amok the same way with a log entry every two seconds.

I then remenbered that the first device came with a parameter 7: Forced Level of Dimming group = -1 although this has to be 1 at least and that no parameters could be saved until this was set to 255 (the default). I tried to change it to -1 again, which did not work, but when changing it to 1 it worked and wakeup was also accepted now exactly one time! But at least the log entries stopped. So I tried the same with the second device, but it did not work with this device. Than I thought I could give it a try in HABmin. And, surprise, surprise: Changing the wakeup time in HABmin works! So there must be a Problem with paper-UI changing parameters.

keep in mind.

HABmin changed only the setting which are changed
paper-UI always send a full parameter set to the device

It is better to use HABmin to change a single parameter. Better to never use paper-UI for parameter settings

Thank you for advice. I thought that the time was over, when HABmin was absolutely necessary. But this problem here makes clear, that setting parameters with Paper UI does not work correctly (at least for this device).

But even with HABmin now I am stuck again. The first new device obviously got a pending parameter set from paper UI in the meantime, and started running amok again bevor getting a communication error after a battery warning. I just reconnected it, and corrected the wakeup-parameter through HABmin. Now it shows up as “not communication with controller” This might be a battery problem.

The second device now shows a behavior I knew from the very first door sensor unter OH 1.8. After removing the battery I can “open” the sensor exactly one time, and it stays open for ever. I never got a real solution to this, but by Chance found out that it was working some day after I had installed OH2 and was just playing with it on my desk.

I really would like to through all this Fibaro stuff away as the floodsensor does not work, too.

I checked the batterie replacement szenario too and for me it works as expected. I just have to open/close the door one time after batterie replacement to get the sensor into the right state and synchron with OH.

From my experiance fibaro are one of the best, only support is worse. I had some aeotec sensors and they do not really work.

I use a everspring water sensor and it work well.

Maybe we open here a new topic about experience of z-wave device. Which are is working any which one causes problems.

That would be a great idea! Especially with a list of parameters/values that are a must under OH 1/2 and with different versions of firmware of the devices to get it to work at all, and which parameters can be changed individually for what reason. A definiton of useful and approved"standard items" for the devices would be great too.

Unbelievable, after playing around with the last device again, and doing another reinitialize with HABmin, it now works (at least as a glass sensor, have not try tamper alarm) as it should.
After installing it at the window I thought it would be a good idea to check the first new glass sensor again (the one running amok) and found out that it does not work again, so I started a reinitialize for this one too, and saw that it stuck (compared to the other one). As it was already mounted to the window I took out the battery several time (had my notebook with running log in sight), and over several battery out/battery in it got more and more through the process ending with:
2018-01-12 16:28:04.758 [hingStatusInfoChangedEvent] - ‘zwave:device:4c4871f0:node18’ changed from ONLINE: Node initialising: RETURN_ROUTES to ONLINE: Node initialising: NEIGHBORS
2018-01-12 16:28:04.851 [hingStatusInfoChangedEvent] - ‘zwave:device:4c4871f0:node18’ changed from ONLINE: Node initialising: NEIGHBORS to ONLINE

Then it worked again. Hope it keeps running now!

But to be honest: This is no acceptable way to include a device to a home automation system.

I will now try the next sensor directly in HABmin without any attempts in PaperUI. Hope this works better.

OK, final reply: Following this procedure I could now include all new glass sensors: After including them with PaperUI I first did a reinitialize in HABmin. With the logviewer open I triggered the wake up several times. Although some wakeups just resulted in a “has been updated” log entry I did it again an again, until the log entry “changed from ONLINE: Node initialising: NEIGHBORS to ONLINE” appeared. At this stage the device is working and items can be linked and will work.

After this success I tried the same with the Fibaro water sensor, and it worked too. Now water is detected correctly.

So there must be a bigger bug in the inclusion and initializing of such devices within openHAB.

No, that is the normal procedure for battery operated devices: they must be waked up several times.

Yea, I know that a device may need some wakeups. But this was not working within OH2 here for the flood and the glass sensor. I could wake up as often as I wanted without a change. Only with the additional reinitialization in HABmin it works now.