FIBARO FGK101 Door Opening Sensor, failing to set contact type Topic is solved

[BakSeeDaa]

One of my FIBARO System FGK101 Door Opening Sensors stopped working, it reset itself to factory defaults. After that I couldn't set Type of input to "NO" (Normally Open) so I bought a new one. I've spent 4-5 hours of work trying to solve this simple thing but with no success.

The problem persists. I have 5 of these and one of them is set to "NO" (Normally Open) since a long time ago.

How am i supposed to set Type of input to "NO" (Normally Open) ???

I've tried to set the new value in both OpenZWave Control Panel and in the Domoticz Node Management. It always revert to the default value (NC). After setting the value I awaken the device by pressing the small button once. (Tamper switch on back of the device is always pushed).

Thanks in advance...

[bbqkees]

Did you try to exchange the battery?

[BakSeeDaa]

Did you try to exchange the battery?

It's a new device with a new battery.

[BakSeeDaa]

Just to inform, I can't seem to set any parameters like for example the Wake-up Interval.

I solved my problem by replacing the switch that I connected to the sensor to a "normally closed". Even though I can't change any configuration values, the factory default configuration is currently acceptable and works for me.

[BakSeeDaa]

Maybe someone else who also own a FGK-101 sensor is willing to try to set any configuration value. What happens if You set the Wake-up Interval for example? Is it persistent?

[LouiS22]

You can only change configuration parameters while the device is in inclusion mode (you have to press 3 times the button (the led will start blinking). You'll have 30 seconds to change the parameters)).

I usually solve this issue next to the computer: first I add the device, then set the proper values, then put the device into inclusion mode, and quicly hit the save button in domoticz. After doublechecking that the correct values are indeed set I put the sensor to its final resting place

[BakSeeDaa]

You can only change configuration parameters while the device is in inclusion mode (you have to press 3 times the button (the led will start blinking). You'll have 30 seconds to change the parameters)).

I usually solve this issue next to the computer: first I add the device, then set the proper values, then put the device into inclusion mode, and quicly hit the save button in domoticz. After doublechecking that the correct values are indeed set I put the sensor to its final resting place

Thanks @LouiS22 for this valuable information. I wasn't aware of that. Where did You learn that? Is that documented somewhere?

I appreciate your kind help!!!

[LouiS22]

You can only change configuration parameters while the device is in inclusion mode (you have to press 3 times the button (the led will start blinking). You'll have 30 seconds to change the parameters)).

I usually solve this issue next to the computer: first I add the device, then set the proper values, then put the device into inclusion mode, and quicly hit the save button in domoticz. After doublechecking that the correct values are indeed set I put the sensor to its final resting place

Thanks @LouiS22 for this valuable information. I wasn't aware of that. Where did You learn that? Is that documented somewhere?

I appreciate your kind help!!!

Sure, i think it's in the manual If not, then I read it probably here. Anyway, I'm glad that you can solve your issue!

[BakSeeDaa]

Sure, i think it's in the manual If not, then I read it probably here. Anyway, I'm glad that you can solve your issue!

Trying to figure out if I failed to read the manual but I can't find that information in the OPERATING MANUAL DOOR / WINDOW SENSOR FGK - 101 - 107 v2.1 - v2.3. Never mind. I'm happy that there is a solution. Thanks!

[LouiS22]

Sure, i think it's in the manual If not, then I read it probably here. Anyway, I'm glad that you can solve your issue!

Trying to figure out if I failed to read the manual but I can't find that information in the OPERATING MANUAL DOOR / WINDOW SENSOR FGK - 101 - 107 v2.1 - v2.3. Never mind. I'm happy that there is a solution. Thanks!

Hm, then I read it somewhere (probably here, in another topic)