Flat face down (on a TO92 can package) is the way mine is mounted also and I believe that is the proper orientation for connecting the device. If you are mounting the DS18B20 within the body of the sensor then it can be tricky getting it to fit: the first couple of attempts I found that one of the leads had not entered the terminal block correctly and so was not correctly trapped when tightened - maybe a loose connection could cause problems with the operation of the Fibaro.
@Gommasch: I agree about the multiple presses and the bottom tamper. I had to mount it on a small wooden block to keep the bottom tamper closed while having to exclude/include it when trying to get the temp sensor to work.
I shortened the leads to about a cm and bend them to fit nicely in the openings.
I saw that is was tricky but am 100% sure the connection was made correctly.
I also got the thing incuded by keeping the button underneath pressed and then hit the inner button repeatingly.
Do you guys see the different motion sensors change when the lower button isn pressed or the magnet is remover (one icon for the bottom swich and the other for the magnet)?
When I got it included, the magned switched both icons to tripped… is that correct?
I dont see the motion sensors change when either tamper (bottom & internal) is activated or closed. Only when the reed switch or IN is activated and typically both together (depending on whether the normally open or closed mode is selected as I posted earlier).
I’m hoping that both of them changing together is due to the current default configuration on Vera (V2, 1.5.408) and this can be rectifed on a future release. The documentation and marketing info from Fibaro suggests they should be fully independant. I checked their forum when I first tried the device to see if HC2 users were reporting them as independant or linked but there didn’t appear to be any relevant postings.
I also saw a review of this sensor and it seems to be hardware-tecvhnically ompossible to have both the reed switch and the IN seperately activated.
As soon as you use the IN, the magnet is to be removed (so dont use it as a doorbell and door sensor (which was a super sollution).
Im not 100% sure (was a preliminary review… from France…) because I see this as a design f#ckup forwhich I regard Fibaro as too smart…
What I do know is that Micasaverde is behind in their software…
Time will tell Im afraid…
I am waiting to use the “scene activate” option for this device , for the moment this device is useless to me. if i keep it , will it perhaps work in the future?, or will this device be as it is now and will I need a newer version? If there is a high probablity i will need a newer version , I will send it back …and wait… so dissapointing :-s
Well, the software is changable (is says in the flyer) and I think micasaverde should first update their part befor I can actually judge the sensor itself…
Till then, I agree with you…
I’m in research to get one of this units for my doors and windows and think that the issue with vera may be because you didn’t update the software trough the wirless internet netwok at home or didn’t set the home center 2 in the learn mode pushing the service button 3 times. Any ways i’ll be following this important post for more details and progress by other users.
Ehhh no, I didnt put the home center 2 in learn mode since this is the MICASAVERDE forum so guess what controller we have…
Anyways, I received a Zipabox this weekend as well and this controller fully supports the sensor, including temp.
Including was still by pushing the inner button while holding the external button as well.
@DRuw
I’m interested to see if with the Zipabox (or HC2) if the two sensors (reed switch & IN contact) are still linked or whether they can detect status change independently of each other? Please post your findings.
I would expect that the two tamper switches are probably connected in series so one has to be kept closed while the other is used for inclusion.
Will check soon, I need to reset and change it with a couple of wires.
I found that the switch on the back doesnt do anything when connected tot the Zipabox.
I think this is a software thingy which is not included yet in the Zipabox since the unit itsef does blink when I push it.
I’ve trying to configure this s**t for 6 hours now >:( Including this device is not problem at all, just press ±button on my Vera lite and then hold sensor and magnet near Vera (remember to keep cover on) and press once backside tmp-button and then three times. Inclusion done, then little waiting and device is configuring it self and 3 devices are added to dashboard.
But the main problem is that I am trying to use this device 3-in-1 mode (temp/door/binary input). Temperature is working fine and reed sensor. But when trying to get binary input work, it changes the status of reed sensor?
Am I correct that this piece of art is only 2-in-1 device? Temp and reed or Temp and Binary Input, not all? ???
well, it has the functions but you cant use it simultaniously.
sorry for the late reply but in the zipabox its the same thing with the external connection. Probably hardware of the fibaro unit…
I have been in contact with MCV,concerning the "scene activation"option , which is not working.
Their replies:
I just want to let you know that we are aware of this issue and we are still working on it and as soon as I will have an update from the development team I will let you know.
We should release the new firmware in the next several weeks. You will see on the user interface when the new version is available so you can do the update and if you want to check the fixes and features that we added you should go to this page: http://wiki.micasaverde.com/index.php/Release_Notes
Wait and see.
BUT, I sas just playing a bit with my setup again and got the fibaro 3in1 device out of the box again , but it doesn’t seem to be working anymore?!?!? :-\
I activate the device by removing the little magnet, pressing the tamper switch, the blue light does come on, and when I poll the device, the vera interface on my computer says the correct says,but without the poll , nothing happened. A few weeks ago when I got the device , when I tested it , everytime there was a change, I saw it on my computerscreen immediately.
I just removed the device and included it again , I got now 3 devices again , including the “_generic IO”, “Motion sensor” and the “real device” But still the same, a change in status does not show up without doing a “poll”. Battery level is 77% a stress test shows results of about 300ms and all pings ok.
What’s wrong? the device has just been laying in a box nothing happened with it ?!?!
Is it currently not possible to kick off a Vera scene using this device at all?[/quote]
No, The scene activation does not work on this device, although in the manual is says , it is possible to activate scenes. :-s
BUT , I wanted to play arround again with this device a little :
it doesn't seem to be working anymore?!?!? :-\
I activate the device by removing the little magnet, pressing the tamper switch, the blue light does come on, and when I poll the device, the vera interface on my computer says the correct says,but without the poll , nothing happened. A few weeks ago when I got the device , when I tested it , everytime there was a change, I saw it on my computerscreen immediately.
I just removed the device and included it again , I got now 3 devices again , including the “_generic IO”, “Motion sensor” and the “real device” But still the same, a change in status does not show up without doing a “poll”. Battery level is 77% a stress test shows results of about 300ms and all pings ok.
What’s wrong? the device has just been laying in a box nothing happened with it ?!?!
Is it currently not possible to kick off a Vera scene using this device at all?[/quote]
Not via the way explained in the manual, where you need to change parameters and use LUUP code to activate a scene. According the email I recieved MCV worked on it and might work with the future update.
But I just got it to work with a workarround, I created a scene, based on a trigger from this sensor, this activated the scene I want to activate . ( used it as a doorbell to play a doorbell sound).
Previously I reported a problem that the device didn’t work anymore, but resetting it did the trick.
Activating a scene in Vera and using the scene activation feature of the device are 2 different things. (Or can be.) I had expected the standard [tt]An armed sensor is tripped[/tt] trigger to work (assuming this device is handled like a motion sensor in Vera).
Me too, and that was very dissapointing, but using a trigger in a scene does what i want now as well… although it took me a while I am now happy that I can activate a scene with this device.
Great! That’s exactly what I intended with my question if it wasn’t working at all. Glad it does work.
Background:
I think typically/traditionally sensors like this report to Vera by telling her their state is 1 or 0 (representing on or off, tripped or untripped, etc.). Vera provides a trigger based on changes in those states (and adds the arm/bypass facility). This trigger kicks off a Vera scene. This appears to be the default mode for the Fibaro as well. (That’s why parameter 14 is not 1).
Z-Wave also has the notion of scenes, providing Z-Wave scene commands. Both your controllers and devices (dimmers/switches) need to support these commands, for this to work. Not many do.
However, some devices have appeared (keyfob, remote, your Fibaro) that use (some of the) scene commands to specifically communicate to a gateway (such as Vera) the state of one or more buttons. If Vera has knowledge of these devices, she can properly decode these commands and provide triggers off of them, which can then be used to trigger Vera scenes.
Parameter 14 appears to switch your Fibaro to that mode. I had assumed you were looking for the additional capabilities that this mode would offer: hold, release, double click and triple click detection. You can now do a lot more with a single button (or input). As said, I think that is going to require specific knowledge of this device in Vera, as every manufacturer may (mis?)use the scene commands differently.
It would probably be good if there were some sort of Z-Wave push button command class…