Fibaro FGBS-001 universal binary sensor with UI7 !!

That’s because this is 7.11, not 7.12. 7.12 was scheduled beginning of October according to MCV.

where did you get that information?

What information? Read this thread and you know I think few posts up.

I feel dumb, sorry did not read.
I thought there was a roadmap where we could look this up.

No prob. With MCV we all feel this way some times (lots of times for me)

Hi,

If anyone needs this device working until the 7.12 release, please send us a ticket and we’ll assist you with it. You’ll need to have 7.11 software version installed on your Vera unit.

Thanks.

George i replied on case 123136 its open for weeks. Please assist me i have 7.11.

[quote=“George, post:26, topic:187417”]Hi,

If anyone needs this device working until the 7.12 release, please send us a ticket and we’ll assist you with it. You’ll need to have 7.11 software version installed on your Vera unit.

Thanks.[/quote]

I’ve just send an email (Case #129054) requesting assistance for this. Would be great if it can be resolved as it’s about the only thing I care about in my setup…

Support fixed mine :smiley:

But then I hit “Configure Node right now” and it reconfigured itself back to being broken >:(

So appears that support now have a solution, it’s just not “me” proof yet!

Cheers

Rob

Support has also fixed mine. Won’t hit the ‘configure node’ button now though :smiley:

support dint fix mine yet :frowning:

Aaargh, I’ve now discovered my sensor acts in a reverse way, so I’m trying to change parameter 3 on the Master device, but your remark about the ‘configure node’ prevents me from updating it! Wish they could just roll out a fix the proper way :confused:

Quinten, same here… Support “did something to my system”… but I just sent a reply on the ticket mail:

I have major problems with these “binairy sensors”. Please help me solve this.

I have only 2 binairy sensors in the room (CV ruimte).

  1. The device “M2 Motion Sensor 1DB” is tripped alway and “untripped” if the device is tripped. I have used parameter 3 and 4 to set the sensor to NO (normally open) and thus to trip when closed. (Wireless Smart Home and Home Automation | FIBARO). PLease, why is it reverse tripping? UPDATE: this device is gone now. I excluded and included the sensor and it is now showing as “M2 BinSensor” up with 4 generic devices. It should show up with 4 temeprature deivces and 2 motion sensors.

  2. I have added a new binairy sensor… doesnt work (M Universal Sensor). Also need to be NO (Normally open).

  3. Why for G-sake do I have SO MANY sensors. Lots of them are “nothing”. The show “NA” in settings. UPDATE: there are now all gone after I excluded (like in point 1).

  4. M1 Motion Sensor 1 and M1 Motion Sensor 2 are working fine and as desired… they trip when “closed”. That is strange though, because the configuration setting is default and thus NC (Normally close). But stil it trips if i CLOSE is. (so it is normally open.

PLease assist!!! And again… in UI5 IT WORKED PERFECT!!!

As you can see I am very frustrated with this. Because it is an essential piece of configuration for my vera and it always worked perfect on UI5.

Let’s hope Vera can give this top priority and make true their claim “we support all zwave devices”.

Hi!

Does anyone have a Fibaro FGBS-001 function with Ui7? Can they please post their configuration settings?

I have one wired with 4 temp sensors and with 2 binary NC contacts. The inputs are not correct anymore, when i’am making a new scene and i’am going to select them as a trigger I get this option : “Whenever XXXXXXX detects motion whether is armed or disarmed” it should be " Whenever XXXXXX is armed and detects motion"

Frode

We are waiting 7.12

Asked micasaverde… thet promised 1st week of October. But i think it has to do with the rotation of the earth that their office is still in september :stuck_out_tongue:

There’s 3 hours of my life I wont get back !!! *facepalm

Any news where this is at??? was planning to use it at a clients tomorrow… guess not now.

According to mcv it should work after they have support on the unit. But no succes till today. Still waiting for 7.12 relaese which was promised 1st week of october…

I sent a ticket to support and they added a fix to both of my controllers, so now the inputs work.

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