Hi,
I’ve connected the sensor with my Vera 3 UI7. If i’m connecting the GND with IN1 or 2 nothing is happening (I want to use it as a doorbell switch). I can’t use the “device option” on Vera (N/A).
Does anybody have an idea?
regards
I heard it’s a UI7 bug. I have one that used to work in UI7 but stopped 2 firmware updates ago.
The newest update doesn’t list this problem as fixed ;/
I’ll need to try it during the weekend, but I won’t get my hopes up. Shame, really.
i have the same problem. No solution yet
I have the same problem.
All fgbs owners have the same problem :-\
Wtf??? It not work in 7.0.9 too
I was so hoping to see it fixed in this revision. My system has been useless for over 3 months now 
- I use a lot of these devices to interface to sensors.
Come on Vera Support, GET YOUR ACT TOGETHER !!!.. the time for jumping ship to a Fibaro controller is fast approaching for this user.
I received this email from Support. Unfortunately no indication of when we can expect a fix.
This issue has been forwarded to our development team which is currently working on it.
We are doing our best to solve the issue but for the moment I don?t have an ETA.
In the meanwhile you can keep an eye on our release notes :
http://support.getvera.com/customer/portal/topics/666697-release-notes/articles
The name of the bug is :
( Customer issue ) Fibaro Universal sensor FGBS321 is not getting tripped or untripped
[quote=“Andrew, post:9, topic:187417”]I received this email from Support. Unfortunately no indication of when we can expect a fix.
This issue has been forwarded to our development team which is currently working on it.
We are doing our best to solve the issue but for the moment I don?t have an ETA.
In the meanwhile you can keep an eye on our release notes :
http://support.getvera.com/customer/portal/topics/666697-release-notes/articles
The name of the bug is :
( Customer issue ) Fibaro Universal sensor FGBS321 is not getting tripped or untripped[/quote]
Very disappointing, OpenHab is looking better every day
Same here?.
Hoping against hope, I checked the recent update to see if this was fixed.
Sadly - not yet.
I wonder if they will ever get round to it…
I’ve been trying to get the binary inputs of one of these sensors working on a veralite with UI7 for the past few hours. Wish I had of found this thread before wasting my time.
I can confirm the same problem. I have a Vera Edge with fw 1.7.1320.
The interesting thing is that (I think) you can see the sensor generate log events when tripping using the following:
tail -f LuaUPnP.log | grep “4275 class 0x60” in the directory /var/log/cmh
where 4275 is my device ID.
Example output, note the last data byte (0x0 → 0xff):
24 08/15/15 11:14:26.341 ZWaveNode::HandlePollUpdate node 7 device 4275 class 0x60 command 0xd m_iFrameID 1225/9222096 data 0x1 0x1 0x30 0x3 0x0 (##0##) <0x7765e520>
24 08/15/15 11:14:26.410 ZWaveNode::HandlePollUpdate node 7 device 4275 class 0x60 command 0xd m_iFrameID 1226/10512384 data 0x2 0x2 0x20 0x1 0xff (## ##) <0x7765e520>
It worked fine for 2 years on my Lite… now on edge with UI7.
I was trying and trying, configured NO (Normally Open) with a paperclip but no “motion”…
Then I found this thread…
MCV:
Hello and thank you for contacting Vera Support.
Please know that we are aware of this issue and our development team is working on fixing it. Once the fix will be available it will be included in a future firmware update for your Vera controller. Unfortunately our development team could not give me an ETA on this.
Thank you for your patience and understanding.
MCV:
I have checked with our development team and it seems that the fix for the this device will be included in the 7.12 version, that should be released at the beginning of October.
Just updated to 7.11 and no joy - then found this post - fingers crossed - it’s about time…
crossed? twist em around. they didn’t say 2015 or 2016 
meanwhile it still doesn’t work in firmware 1.7.1419. Does any know if there’s a workaround?