I have major issues with this sensor. When it is near the Vera, it works quite well. But when it is put in its final position, it is unreachable, even when the nearest repeater is just 1,5 meters away…
Jaap
Quite the same problem here JaapvanEkris. I have another one working fine but it’s closer from the Vera (3 m) and one further (6 m, upstairs). The second one was not transmitting at all so I installed an Everspring plug 2 m from it. Now it’s working but not properly.
I don’t know the cause. Maybe I have to play with polling periode… ???
Hi,
I bought 1 of this sensor to try.
The door detection and temperature measurement works fine. The procedure to do the association with the VERA was a bit difficult, I did it several time to see the 3 devices.
Unfortunately it seems that the DI input cannot be used at the same time that the door magnet. They are linked, so you can use or the DI input OR the door magnet…
but this sensor is a good choice anyway !!
Hi,
I also have trouble with getting the temperature displayed.
I have connected according to user manual. But in vera it comes up as 3 devices, none of them showing the temperature.
Anyone know what to do?
regards
Same for me. Temperature sensor device should be connected with the pins in reverse order! 
I have 4 sensors. At the moment I’m able to associate 2 of them. I keep trying with the 2 others… :-[
Just in case it help someone, I’ve found that instead of just click fast 3 times for inclusion, I needed to click fast near 10 times to do the inclusion. In fact I just keeped clicking the tmp button until my vera3 flashes. It worked fine for 2 devices that were problematic to include.
I found out that including the device pressing 3x the button does nothing. I tried it 2 times, both times it worked immediately with: pressing the tamper switch and at the same time pressing the other switch 6!! times.
For me the 2 motion sensors also work together, it is a bit vague how it works , maybe to do with the tamper switch?
I want to use this device as a scene activator , but have difficulties with th e LUUP code, Parameter 14 is configured , but no clue about what to do with the LUUP code :-s if anyone who is interested to use this device as a scene activator can you take a look at this thread:
[url=http://forum.micasaverde.com/index.php/topic,13343.msg99555.html#msg99555]http://forum.micasaverde.com/index.php/topic,13343.msg99555.html#msg99555[/url]
Cor
Same for me. Temperature sensor device should be connected with the pins in reverse order!
I have 4 sensors. At the moment I’m able to associate 2 of them. I keep trying with the 2 others… :-[[/quote]
Does this mean you should switch the ground and power supply to the sensor?
I use an external sensor. http://www.smarthus.info/product_info.php?products_id=2986
I tried to switch around the cables, but then no light came on when I put in the battery, so I assumed that this was wrong.
So I never tried to include it again.
I have been able to include it as a standard magnet switch.
Can someone please confirm witch pins they switch?
power & ground?
And can someone also please confirm if I need a new firmware to get the temperature sensor working?
I am currently running 1.5.459.
thanks!
Just wanted to tell my experience here as well:
it didnt do anything at first… including works by pressing both inner and outer button.
The temperature measurement doesnt work both installed as mentioned in the manual as or rotated 180deg (did anyone solve this?)
Im using vera fw 1.5.459 but its not really working correctly I think. It shows “polling node” spontaniously and once every some time the light keeps blinking (still works though).
Also sometimes I see “Waiting for wakeup to configure device” while nothing changed in the setttings…
I just dont get it really…
Any news on how you guys get them to work?
Just got one of these today and have to say I am somewhat disappointed. While the size and styling is ok the functionality is not (yet) as expected.
As reported by others previously, Including the device required multiple quick presses rather than the 3 that are normally sufficient for other devices. It also took ages to configure, read back configuration parameters and accept new ones.
The DS18B20 works when connected as shown in the datasheet but it does not seem to be as flexible in the reporting as the datasheet suggests. Parameter 12 suggests it can do it every time the temp varies by say 0.5’C but it just seems to report at the wakeup interval. This may be due to the report being sent for a device in Association group 3. I suspect the battery life will be considerably shorter than the estimated 2 years with the temp sensor attached. As with the Fibaro Universal Sensor you have to paste the device file ‘D_TemperatureSensor1.xml’ into the Generic IO child device to get the temperature to display.
The data sheet implies that the magnetic switch and the potential free input channel work independently but as observed by others above they are essentially configured as two parallel inputs: if the IN channel is set to ‘Normally Closed’ then both In and the magnetic contact must be opened to detect a change. If set to ‘Normally Opened’ then either closing is detected. As a result both sensor widgets change state more or less together which seems rather pointless. I had anticipated the two detector channels would allow the Fibaro to act as a combined front door and door bell push sensor but this does not appear to be practical.
Maybe some of these issues can be sorted out with a specific configuration file for this device but this seems a long way off with MCV’s current apparent focus on Enterprise MiOS customisations. 
@ Frasier:do you have any idea how to use the “scene activation” with this device. A luup code has to be used, but I have no idea how to implement this.
Thanks,
Cor
I only have a single icon on vera with this thing and as soon as I connect the temp sensor, the unit itself stops flashing.
Strange as well is when I put the magnet near it and remove it a couple of times, the led starts blinking mutiple times.
No idea what it meand (the unis still works and sends its status to vera) but directly after this, the unit doesnt flash its led when status changes (although still reporting to vera).
I will remove and reinclude the device later today and see if that works…
Druw, same thing here, I have given up.
Use lots of presses to include/exclude - a simple triple click is not enough. Keep the bottom tamper switch pressed like if it was already mounted on the wall and then use the inner include button to manage it - seems like it gives better results.
The users manual is wrong about connecting the DS18B20 to the FGK, You need to connect like this (see images):
http://www.etotal.eu/product_info.php?products_id=251&language=en
That diagram you linked to is WRONG. I have checked the physical connections on the device and TP(VDQ) and GND terminals are as shown in the V2.1 version of the data sheet; i.e. the GND terminal is beside the IN terminal on the reed switch side of the device. I can measure 3.6V across these two terminals with the correct polarity.
Unless Fibaro have shipped two different versions which seems unlikely…
You are probably right but this setup is actually the only way it works for me. Setting it up the way the manual describes locks up my device. This way everything runs like it is supposed to.
This is weird… I can only put the sensor in sucht a way (flat part down) otherwise the device locks up…
For the guys who got this thing to work, what does vera show?
2x motion sensor and 1 temp or do you have to make manual adjustments as well?
As far as I can tell, the guys running Fibaro homecenters or Zipaboxes do not have the problem so I actually also blame it (partially) on the Vera fw…
Remember in the Generic_IO device (which is the temperature sensor) under Advanced to paste D_TemperatureSensor1.xml into the field device_file, and that’s it.
I got that one time and then after a day or two (I didnt got the temp reading so gave up and forgot to remove the unit) my vera gave errors.
suddenly all my fibaro and duwi switches got messed up and were not controllable anymore.
I had to reinstall a backup which solved it…
I will try probably this afternoon again… it shall work dammit;)