Geekzone: technology news, blogs, forums
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.

617 posts

Ultimate Geek
+1 received by user: 66

Lifetime subscriber

Topic # 223468 1-Oct-2017 10:25
Send private message

I have problems with Fibaro FGK10x window sensors added to my VeraEdge controller.


I bought sensors and a controller in New Zealand (921.42MHz) just a few days ago.


1. Fibaro sensor with firmware V3.2 and dated 1/12/2016, installs as an I/O Device. The reed switch and external contacts do not appear to work. The LED does not operate when the reed switch is operated. Tamper is ok and operates the LED.


2. Two Fibaro sensors with firmware V2.5 and dated 17/12/2015, install as motions sensors. The reed switch, external contacts and tamper work ok. However, when setting up a Scene in VeraEdge, motion detection is the only detection option. This is no good for window open or closed state indication. I need an option that shows when the reed switch is open or closed.


I also have some Aeotec window sensors and switches. These all install correctly in the controller and allow correct operation when setting up Scenes.


I have aluminium doors, windows and frames so I am planning on using an external reed switch wired into the Fibaro sensors so that the sensor can be mounted well away from the aluminium to ensure good Z-Wave RF transmission.


My VeraEdge controller has firmware 1.7.3014.


When pairing all sensors I made sure all powered Z-Wave devices were turned off (except for the controller) and that the pairing link distance was only about 600mm.


I have done a lot of Googling to find help without success.


Anyone know how to solve these issues?


Can the firmware in the Fibaro FGK10x be upgraded or changed in some way?


I have tried the Fibaro sensor reset operation and have not seen any improvement. However, the reset process is a bit hit and miss to be sure it has happened.


Is there a better option for selecting a sensor, other than the FGK101 from the list provided in the VeraEdge?


Can sensor parameters be changed in the config for the installed sensor as shown in the VeraEdge? Which parameters to change to fix the problems?


I am also contacting various support...




Create new topic

617 posts

Ultimate Geek
+1 received by user: 66

Lifetime subscriber

  Reply # 1875775 1-Oct-2017 23:24
Send private message

It seems that the VeraEdge Controller does not correctly recognise and configure the Fibaro Door/Window sensors.


With the help of Active Automation support I have been able to change the sensor parameters as below.


VeraEdge controller installs the Fibaro sensors as shown below.


FibaroFGK101#1 I/O Device (Firmware V3.2)
Device Type urn:schemas-micasaverde-com:device:GenericIO:1
Device File D_GenericIO1.xml
Device Json D_GenericIO1.json


FibaroFGK101#2 Motion Device (Firmware V2.5)
Device Type urn:schemas-micasaverde-com:device:MotionSensor:1
Device File D_MotionSensor1.xml
Device Json D_MotionSensor1.json


Device Type urn:schemas-micasaverde-com:device:DoorSensor:1
Device File D_DoorSensor1.xml
Device Json D_DoorSensor1.json


Fibaro Advanced Parameters were changed to the Aeotec parameters.
The Fibaro sensors now operate as a Door/Window sensor.




Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:

Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:

Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:

Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.

Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.