Fibaro FGBS-001 universal binary sensor with UI7 !!

Community Playground General Discussions
41

[quote=“slajgaj”]Frode!

You written: now inputs work…
What to do the Micasa support for you?
Maybe some device setting parameter?
Please share your answer or setting parameters[/quote]
If you update to last beta it works:D

Inviato dal mio LG-D802 utilizzando Tapatalk

42

I see the beta release , but i can not seeing in the user guides modify this Universal device.

http://support.getvera.com/customer/en/portal/articles/2172118-beta-software-update-▾-ui7-▾-version-7-0-12-1-7-707-1-7-1509-▾-october-23-2015

43

It works on beta

44

I’ve updated to the last beta, but not seeing much in the way of an improvement on the Fibaro binary sensor… More testing is required (it’s on my garage door, so unless I need to be inside, it won’t be used) this weekend…

45

Send a ticket to support and they will add a temporary fix to your unit, the fix is suppose to be in the release this month.
I didn’t see any new configurations settings on the fibaro but it did work for me.

46

But that’s the thing, they did the temporary fix, which did fix it for oh, about a week, and then stopped working again… Also not sure if the temporary fix interferes with the new beta?

47

Strange, have u tried to restore a backup from that time?

48

No I haven’t. And to be honest, I’m more of the type ‘onwards and upwards’ than going back again. But it’s a valid suggestion, thanks

49

I had the same trouble with the sensor.
Had contact with customer support and they changed somthing in my vera edge firmware1.7.1419, now its working!

Im pretty new to vera so i dont know what they did.

This is what he said:

I?ve added this variable and service on the child devices:

urn:micasaverde-com:serviceId:ZWaveDevice1
variable: BasicSetCapabilities
value: 00=T0,FF=U0

Hope it helps for you guys

Greetz

50

It’s not working for me unfortunately. Mine stopped working completely, so I took it out of the Zwave network, reset it and re-associated it again. It shows up as 1 motion sensor, and 1 generic io (the temperature sensor). I’ve fixed the generic io device by changing the .xml and .json file to D_TemperatureSensor1, but the two child motion sensor devices are nowhere to be seen. The master device does not seem to react to status change, so at a loss how I can ‘unhide’ the child motion sensors…

51

Quinten I have that exact same issue for 1 of the 3 binairy aensors in my ui7…

52

Great, or rather, that’s comforting to know that I’m not alone in this… Here’s hoping on the next Beta being better…

53

Snap i’m also having the problem.

54

Including lots of phantom devices created randomly…

55

Hi All - I’ve been reading this thread with interest because I too had lots of problems with this device. I only recently bought a Vera Edge so am using the latest version of the firmware. I am using the device connected to 2 DS18B20 temperature sensors and nothing else. I initially got a temperature reading but no updates, then I tried to Exclude and re-Include the device, and couldn’t and then I finally managed to re-include the device but ended up with, apparently, ghost devices. After a few weeks of exchanging emails with the retailer and with Vera support the solution, at least for me, turned out to be nothing more than an error in the wiring. I had crimped boot lace ferrules to the very fine gauge wires from the Fib device and hadn’t done a very good job with the power cable so that, apparently, the power supply to the device was intermittent. Once I corrected this, excluded and re-included the device it showed up in Vera as 1 Universal Sensor (shown as a motion sensor for some reason), 2 Universal Temperature sensors and 2 binary input sensors and the device now correctly polls the 2 temperature sensors. I didn’t change the name of anything or make any other config changes. I still have some ‘ghost’ devices (although I think these have come about from my earlier issues) and I still would like to ‘flush’ these out but in all other respects the device worked ‘out of the box’. I am not suggesting that this is the answer to anyone else’s problem but posted this to illustrate the feasibility of getting this working with the current version of the firmware and in case it does help anyone else.

56

Latest firmware and it works (although I think I had to swap the NC/NO setting over, but it’s so long since it worked it may have always been like that)
Had to unpair and re-pair mind.

It doesn’t seem to be listed as a fix in release notes either

Rob

57

I’ve just fallen off my chair in shock after loading the latest firmware release :o It seems we finally have a fix!

58

Saw your message on the other thread, robw… gives me hope for tonight :smiley:

59

Well, I’m still no further. Sensor excluded and re-included but it only shows the ‘master’ device along with the temperature sensor, but not the 2 inputs. If I go to http://<vera’s ip address>:3480/data_request?id=user_data&output_format=xml, I can see device id’s 63 (the master device), 64 (e1), 65 (e2) and 66 (temperature sensor), but e1 and e2 are completely empty

60

Same here problems persist…