I had been having problems getting the inputs to work, this is the fix for that.
I added a variable to the child device of the Fibaro universal sensor on the Vera controller.
To do this, go to the input in question by clicking on its greater than sign in the Devices tab → Advanced → Variables and check if you have the ?BasicSetCapabilities? variable. If so, please edit it with the values below. If the variable isn?t there, create it by going to New Service and enter the following:
New service:
urn:micasaverde-com:serviceId:ZWaveDevice1
New variable:
BasicSetCapabilities
New value:
00=U0,FF=T0 (for normal open)
00=T0,FF=U0 (for normal closed)
When you have these pieces of information entered, click on Add, then on Reload Engine. You should expect the sensor to be reconfigured.
I tried that last time but it made f all difference for me. My 2 inputs are not even showing in UI7, so until that is fixed, there is no point in messing with the capabilities for the master device.
Hi,
I bought a Foscam F19803EP Outdoor camera and later found that it couldn’t send motion requests to Vera, which was a pain to say the least.
Anyway, thinking out of the box, my solution was to use one of the Fibaro universal sensors and a Foscam FN3104H NVR. I setup the NVR to send a signal to its external alarm output when the camera detected motion.
I’m pleased to say that, after totally reseting all of the parameters Vera defaulted to (some of which were way out) to that recommended by Fibaro, I’ve actually got it to work.
So when my camera detects motion a light switches on!!! Sorted.
Maybe not as complicated a use as others but still useful for future reference.
Quinten, according to John from Micasaverde there are “old” and “new” versions of the fibaro universal sensors. I have both as well. They worked very well with UI5 for more than 1.5 years. Now with UI7 I also have one of them not showing the 2 inputs. MCV did a lot of remote support sessions. One with temporary result one with none the oth with more than 15 (!) Ghost devices… etc. In the end I deleted both universal sensors and added them. Since it works…
According to MCV in the February update (7.13) this ghost device bug should be resolved.
Regarding the support of the universal sensor I don’t know…
Hi
I’m very new with z-wave and vera. I have VeraEdge and UI7. I’ve got sensor version v.2.1 - v.2.3 (according to manual).
I tried to pair sensor several times to vera. After several tries I had success. Next I want to experiment with temperature sensors and deleted the device from the vera. Then my troubles had started. I was struggling with pairing device several times, resseting sensor, reloading engine, resseting chip etc. Sometimes it worked, sometimes it can’t pair.
Now I have no troubles unpairing the device and adding it again (it gets new node and device ids). The trick I found is that - it wasn’t mentioned in fibaro manual - to unpair device the same way you pair it: 3 times press on B switch.
The funny thing is with temperature sensor output on UI7 dashboard (when you add one or remove it, you need to unpair and pair again sensor). I’m using breadboard for tests. When I eventually connect temperature sensors to fibaro binary sensor it shows 168.00 C.
So it’s rather hot on my desk ;D
Does anyone has working temperature sensors?
Pleased to report that since my 19th Nov post, the devices continue to work without issues using the latest firmware on my ‘Edge’. A few weeks ago I added 4 more devices to integrate my alarm system PIR’s etc and now using this data from the room PIR’s to mix into the lighting control logic.
I had an opportunity to speak face to face with Fibaro at the CES trade show a few weeks ago. I asked them whether they had any plans to make a device with more I/O’s ( I had to add 4 inside my alarm control panel which although works, seems a little wasteful…and expensive!)- an 8 input device would be very useful! Unfortunately they have no such device on their development road-map .
Hi gpaciorek, yes, I have one of these units connected to 4 temp sensors working ok. They are connected using twisted pair CAT5 cable. The cable is about 10m long.
Vera support is still working on mine. The two inputs have now appeared as working devices, but after an exclude/include they stopped working again. Getting close now…
Hi Andrew
Do you have correct temperature displayed on UI for these sensors?
Is there any trick to differentiate temp sensors? I was thinking about configuration 2 in one place and others in another? I mean sth. like the closest one to the fibaro sensor (with the shortest wires) gets number one or should I try to warm each one to check the temperature to match them?
Hi gpaciorek,
Yes, the correct temperature is displayed to one decimal place with default settings. I have the device located in one room monitoring the temperature in that room and also 3 other rooms. I wire to the other sensors using one CAT5 cable. Try and keep your cable as far away from other cables and possible sources of interference. If you have the furthest sensor quite a long distance away, don’t use multiple cables to each sensor as this increases the capacitance by a considerable amount and will limit your maximum distance. Chain from each one if you can, i.e. wire to the nearest one first, then on to the next nearest and so on. The sensor datasheet provides guidance for maximum cable length.
You can identify which sensor is which by the way you suggest - just warm them with your fingers and see which one rises. If you allocate the sensors to different rooms, you need to set ‘ChildrenSameRoom’ to ‘0’ in the Variables page. If you don’t set this you will find that although they can initially be allocated to different rooms to start with, they will automatically jump back to being in the same ‘parent’ room at some point.
I am still having issues with the universal sensor… It works for a day or two and then totally stops working.
My setup is to have the universal sensor connected to the existing security motion sensors, so I can use it in my scenes for motion detection. After 2 weeks, am tired of including and excluding the devices, adding the child services, does not work straight off the box…
Mine appears to be fixed now (after 3 months of ongoing support by MCV!), although I have noticed an increase in false detections. Am now monitoring false vs true and see if I can find out if there is some sort of pattern.
Dont think MCV is working on this… Mine is still giving false readings, and there seem to be no rhyme or reason for them. It does detect the open/close scenario for me correctly, so all I need to do is add some logic that a ‘open’ can only follow a ‘close’ and vice versa. That way my multiple ‘closed’ ‘closed’ ‘closed’ events will be ignored
I’m just using the two inputs on the Fibaro without any temperature sensing and also seem to be getting random false triggers on UI7 (Vera Edge). If I execute the “Configure node right now” command it does seem to improve things for a while but this also resets the two input child devices (reverts to default names, deletes any notifications, etc.). The parent device seems unchanged but its a pain having to set-up names and notifications again. I have other FGBS001’s running under UI5 and re-configuring the node does not reset their names.
Are others also seeing the child devices reset if re-configured?
.
: