Fibaro (3 in 1) Door/Window Sensor

Other Devices & Integrations Door Locks & Sensors
61

After numerous attempts to get this sensor working I seem to be at the end of my tether.
Finally I have it included, it seems to react to configuration and polling. A weird thing is that the system recognises it as a device from Aeon instead of Fibaro.
There just seems no way for me to get this sensor to fire a trigger.
I have put var 14"scene execution" to “1”, no difference.
The sensor reacts to the door opening and closing with a short blue flash on the sensor, making me believe at least something is working, but the “sensor tripped” trigger associated with the sensor never fires, so the scene cannot be executed.

I gather that some are able to get it to fire a trigger but I am curious how.
Any takers?

62

@ srvmam: it is allready meantioned a couple of times (in this thread) that the scene execution of this device is not working on MCV. It might be working with the new firmware which should come in the near future.

Better to resset the device, remove it completely from your vera and include it again (I had the same issue when I inserted parameter 14) , there shoud be 3 devices after configuration. To activate a scene you can do via: new scene>> trigger>> the device>> trigger when active (or not) > in the LUUP for that trigger insert a line to execute the scene you want. I got it working for a doorbell ( see the thread “making a doorbell” where i explained)

Cor

63

I fought with mine last night like everybody else >:(

Long story short, I was able to include the sensor to Vera but for me it it just 1 Motion Sensor (I don’t plan to use this sensor for anything other than detecting the door opening). I can configure it fine by pressing the TMP on the back 3 times (I believe it sends a NIF to Vera) and the configuration will proceed.

My problem is the sensor is always tripped. Moving the magnet to/from the sensor’s body has no effect on the LED or the sensor (nothing appears to happen). Maybe I have a dud? Is there something special you have to do to use the sensor without any additional sensors?

I’m at a lost, really thought this would be super simple. Thoughts and advice desperately welcome!

Update: It’s weird, but I can reset my sensor (2 quick flashes after inserting the battery) by simply holding both TMP buttons down (with the case off) and taking out the battery and putting it back in - no magnet necessary ??? Is it possible the reed switch is damaged?

mgb

64

@mgbowman

I have had exactly that problem too - and continue to do so, for most of my units. I have one successfully installed on a door and working fine (with the exception of still “waiting for wakeup to configure device”), but have been struggling with the rest.

Taking on board all the advice about including and configuring battery devices, I have several times reached the stage where the device works fine on the bench, but fails in this way once installed. Noting this, I’ve reproduced the problem by removing and re-installing the battery (which you HAVE to do to mount the device permanently with screws) - works OK before, doesn’t afterwards.

I’ve had the blue light flash when magnet is brought near or taken away. I’ve had it not flash. I’ve also had it stuck as not tripped, and gone through the belief that the reed switch was broken - only to get it going again later. I’ve included, removed, factory reset, pressed TMP once, twice, thrice, … said a few prayers, sworn, but so far refrained from hitting it with a hammer. I’ve upgraded to 622 public beta firmware, but that hasn’t helped. It sometimes looks as though everything is just fine, except there’s no Z-Wave transmission.

I just wish they worked as well as they look. I continue to search for a solution.

65

I just updated my vera3 to the beta 1.5.532 , this firmware recognises the fibaro sensor better and there is just the motion sensor and the temperature sensor , not the third motion sensor.

I was hoping that the option for scene activation would be more clear in this firmware, but it all looks the same, anyone has an idea what to do with “parameter14”

Thanks,
Cor

66

i recently purchased the FGK101, and have been mucking with it for ages like most of you. It took me a while to get in included. In the end i came across a youtube video that showed to hold down the back TMP switch, then press the internal tmp switch more than 3 times and the led will change from pulsing quickly, to slowly, which shows inclusion. This worked first time for me. Without the temp sensor, it comes up as one device in vera on 622 public beta, a motion sensor.

My biggest issue however, was that it would not detect the magnet. I was sure the unit was faulty. So to eliminate the whole unit and zwave communication as a possible fault, i hooked up a momentary switch to the IN connectors. when i push the button i can see the state switch from triggered, to not triggered. So this proves the unit is fine, the zwave communication is fine, but it must be the reed sensor. So i took a closer look.

I got out my multimeter, and as soon as 1 probe touched the side of the sensor closest to the battery, the led flashed and vera changed state, i removed the multimeter, and it changed back. so next, i put the magnet next to the module, no change again, touched it with the multimeter probe and bang, the state changed, this time however, the sensor didnt change back when i removed the probe, the magnet was holding it in place. i moved the magnet away and the state changed.

So either the magnet wasnt strong enough to close the switch, or the points were to far away inside of the sensor. but after giving it a helping hand the switch closed and stayed closed.

so i figured, the points in the switch are so small, i must be able to bring them closer. so with a real small screw driver, and a magnifying headband, i gave the right side of the switch a gentle push to attempt to slightly bend the wire that little bit closer so the magnet can do it on its own. And it worked.

Now its important that you dont push the wire too much, because if you do, the switch will be constantly closed and you cant even use it as a binary switch, so be real careful, you have been warned.

Do so at your own risk, but like i said, this worked for me.

Now whether installing it in the garage, and all that constant movement will revert the switch to the way it was is anyones guess, but for now, its working as intended.

I hope this helps someone. Report back your findings

Cheers

67

reading this topic makes me realize it aint all that straightforward as it looks.

first :

to save a lot of huzzle upgrade vera to firmware 1.5.622
when you have included the device allready to vera (with or without troubles) and later on attach a tempsensor, you will need to reset both the vera and the device.
since device removal is a bit not really ok working for some devices in vera in former firmware before 490 you have to do it by hand.
using the http://vera-ip:3480 delete device option.
normally it would delete after excluding device.
steps :
put device on table with battery lid off and magnet next to it.
full power exclude for 60 seconds and press tamperswitch 3x
it is now excluded as you can tell from the messages in the upper blue part of the vera UI5 (status window)
now wait for the vera to reload luup and remove the device. do not touch it in any other way nor pressing any button or whatsoever.
see it finished and reloaded and ready to do it stuff. to be safe just wait 5 minutes.
now remove power from the fibaro and attach the tempsensor dallas thingy. if you look on the little thingy you see a code which says its a dallas blabla.
there is a + located on the left of the 3 pin with a number next to it. great u found the packagingcode. this + is the GROUND or MIN. the middle one is the datapin and the right one is the + Vcc
now that we sort that out we can attach it. use a simple nailcutter to bend and cut it into place. or if you have one a telephone-pliers
check the thing if all is seated well and attached. now put power on it. wait for a half minute.
go to vera dashboard and do full power inclusion. (DO NOT USE BATTERY-OPERATION as it foks up the multi-device, this is made for single parent devices and will screw up your z-wave)
so while you press ok for the 60 secs full power inclusion, go to the device which should be around 3 meters or 2 from the vera and press the tamper-switch 3 times in 1.5 secs. tap-tap-tap. anything else will not work. press the tamperswitch with ur nail so it will be totally pressed in and release. (again make sure the thing is on flat surface and no tamperswitches are touched or pressed and the magnet is on the side). you will see it added to vera. if not > wait 5 secs and triple press again. ok now u see it appear in the vera window. it says some lines like z-wave bla found. ok now that is ok, wait for 5 minutes and see the vera is reloaded and restarted and ready for action. now go to the device added. press wrench to open properties and keep your mouse on the config now.
get the fibaro and be ready to press it 3 times on the tamperswitch (with nothing else pressed, no battery lids etc you know by now i may hope).
now press in vera config node now and immediatly after press OK you press 3 times tamperswitch and wait. you see it configured. if not wait 2 minute and do it again. now that its configured we are going to add the device files for the tempsensors. after this is done and saved you have you vera ready for action again. now you may reboot the whole device :slight_smile:
in the meanwhile put the fibaro where you want it and go to vera dashboard z-wave stuff and do a z-wave network heal. after this make a backup of it !

Do not use battery powered inclusion for multi-devices. use full power inclusion with the device around 3 meters from the vera.

68

[quote=“Cor, post:65, topic:173593”]I just updated my vera3 to the beta 1.5.532 , this firmware recognises the fibaro sensor better and there is just the motion sensor and the temperature sensor , not the third motion sensor.

I was hoping that the option for scene activation would be more clear in this firmware, but it all looks the same, anyone has an idea what to do with “parameter14”

Thanks,
Cor[/quote]
setting this would make the sensor a momentary switch. you can make a scene and add trigger to look for the code for the scene variable in the device. but i think only first scene work.
this is supposed to be added in 622 firmware, didnt test yet. idea is to trigger the scene when the not armed device is triggered. i.e. everytime you hold the magnet against the doorsensor it would alter state thus functioning as a pushbutton scene switch

make scene… press ON on the device you want to turn on. go to triggers and add trigger for motion-sensor not armed but is triggered (a sensor is tripped, device is tripped)
in a way this is nice coz you can set it to armed device and thus so control the button-activation. i.e. put it to disarm would disable the scene trigger :slight_smile:

69

It is a bit of a wierd device ::slight_smile:

Trigering a scene was allready possible with the previous firmware, I used a notification, which triggered a scene (for doorbell purposes) , but as I understoond with that parameter 14 stuff , you can do more as 1 scene, a double click etc does another scene for exeample…

I have another question , which I posted in another thread, since that thread is more specific for manual routing… but I will post it here as well… maybe it is just a fibaro 3in1 thing :-X

[quote=“Cor”]I am trying to give a fibaro 3in1 sensor a manuel routing ( see attachment) , I will try to use this as a scene trigger device, ( to open my garagedoor), This manuel routing since I want to try to use it in my car to open the garagedoor. (The ultimate goal is to have to of these devices together in 1 case to operate on 2 different mesh-networks).

But it doesn’t want to configure, it keeps on saying “waiting for device to wake up”, I left it about a day next to the vera3, and today half of the day near the device of the manuel routing… it somehow cannot connect …

It was included after the beta firmware update and worked fine! , the problem started with the manual routing…

Any ideas?

Thanks,
Cor[/quote]

70

yes you can use 3 scene per input indeed and this should now function in 622 firmware but did not test it yet as i have a lot of other stuff to do.
it cannot have 2 mesh networks. it is inclusioned in 1 so it cannot be in another.
it seems the device got put in group 3 and attached the z-wave which returns via scenecontroller , i.e. it should now do scene stuff.
the device can be woken up by opening the battery lid and press the tamperswitch 3x after you press configure now on vera

71

[quote=“Da_JoJo, post:70, topic:173593”]yes you can use 3 scene per input indeed and this should now function in 622 firmware but did not test it yet as i have a lot of other stuff to do.
it seems the device got put in group 3 and attached the z-wave which returns via scenecontroller , i.e. it should now do scene stuff.[/quote]
Would be great when you have tested it and you can show how you did it :smiley:

I know, the idea is to have 2!! of these sensors in one little case , pressing a button will activate both ! sensors , the one which has network coverage will activate the scene , the other one does basically nothing.

The wake up intervall is set at 1800sec , shouldn?t it wake up automatically?

Thanks,
Cor

72

Just tried to wake up the device as you told, but no luck. Vera keeps on saying “waiting for wake up of the device” when I click “stress test” it does it’s thing , 200ms and 7 out 10 okay, direct and indirect. Thereafter again “waiting for wake up of the device”.
it looks like it doesn’t like the manual routing :-/

More ideas :-\

Cor

73

Hi,
I set up this device on the current public firmware. No problem.
I updated to the latest beta (622) because of another sensor. Broke things with the Fibaro 3 in 1 and I couldn’t exclude the device (and so start again).
Only difference : for the public firmware, the sensor was lying flat on a table with the underside tmp switch pressed. When I attempted excluding the device, it was stuck on the door frame and I assumed the switch was pressed. When I removed/reinserted the battery for the xxxth time, I heard a small click and realised that without the sensor cover, the battery was not pushed as far down and the tmp switch was not pressed. I put the vera lite in exclusion mode, pushed the battery with one hand and triple-clicked with the other and… hurray, it worked !
Exclusion worked so I tried inclusion using the same technique. It took one attempt only (clicking the tmp switch from time to time during configuration, reloading of UI, final configuration).

So my advice : make sure the underside swith is activated when you triple click the top one (and apparently sometimes you need more than 3 clicks).

And for those with temp sensor issues : if you connect it incorrectly, the blue led will NOT switch on. If you connect it correctly, the blue led should be on when you insert the battery.

Hope this helps !

74

i guess setting the right parameter will do and then a reconfigure. and have 622 firmware otherwise it surely dont work. after that it suppose to work like a regular scene-controller remote. 1,2,3 taps give 3 different output on the parameter for scene. read parameter and according to that activate scene. way 1 = look for scenecontroller stuff… way 2 = make a scene with luup wich reads parameter for which scene. triggered by sensor 1 or 2. and according to parameter value start activate the 1,2 or 3 scene.

I know, the idea is to have 2!! of these sensors in one little case , pressing a button will activate both ! sensors , the one which has network coverage will activate the scene , the other one does basically nothing.
this really does not make sense to me... :) connecting 2 sensors you can just attach both ground to eachother and connect both inputs together while using the same powersupply.
The wake up intervall is set at 1800sec , shouldn?t it wake up automatically?
yes it should. i have wake interval on 1800 and poll interval on 1080 and device works immediatly when triggered.
Thanks, Cor
welcome
75
I know, the idea is to have 2!! of these sensors in one little case , pressing a button will activate both ! sensors , the one which has network coverage will activate the scene , the other one does basically nothing.
this really does not make sense to me... :) connecting 2 sensors you can just attach both ground to eachother and connect both inputs together while using the same powersupply. the one which has network coverage will activate the scene , the other one does basically nothing.
the one which has network coverage will activate the scene , the other one does basically nothing.
That?s exact the idea how to connect them. This is for my car , when i want to open the gate and garagedoor , they are both on different vera?s . When I arrive I need to open the gate , and will have only network with the vera at the gate , when I want to leave and I am in my garage, I will have only network acces with my vera at home. By activating both fibaro sensors at the same time I hope that at least one will have connection and will activate the right scene.

Hope it makes sense now …although I am still unluky with the manual routing, the device does not want to configure now :-\

Cor

76

So if you remove the manual routing, the device configures fine (again)?
(Also: as said on the other thread, I think only the first manual route is being used (but this isn’t the cause of the issue you’re seeing)).

Is the association for group 3 correct?

Regarding parameter 14, I would leave it at 0. I think the device would need to be treated as a scene controller and a mapping must be added to Vera, to allow support for the ‘scene activation’ feature.

77

My temp sensor arrived today, so i excluded the doorsensor from vera, installed temp sensor, included doorsensor into vera.
3 devices showing, changed generic_IO to tempsensor. All good so far.

Mounted the sensor for the garage.

all working and reporting quickly. One issue I have is that the temperature in celsius is definitely higher than it really is.

it showed 28 degree about an hour ago, now it shows 26, so it is changing, but its more like 18 degrees outside, no more than 20.

Anyone know why its reporting higher than it should be?

78

Anyone have a clue as the above is still happening, its probably 24 degreees celcius outside, temp sensor showing 28 degrees.

its not in direct sunlight, but the only thing i can think of is maybe because its at the top of a roller door near the gap, as the sun hits the roller door, it heats up the inside of the garage, and the air comes out near the top where the sensor is.

but this wouldnt explain why its few degrees over at 4 or 5am.

79

The dallas temperature sensors need air flow around it. Put it in a location where the airflow is restricted and they will not give decent temperatures back. It also needs to be shielded from direct sunlight. I suspect you’ve answered your own question just now :slight_smile:

80

well its got airflow, the sensor is mounted on the outside of the unit, not inside. so that already has more airflow than most. its not in direct sunlight, its under the easement of the house.

thanks for the info. i might take it down, and see if its any more accurate just sitting on a bench inside. i can compare it to my heater thermostat. I might take a pic tomorrow, post it up.

cheers