[quote=“Frasier, post:80, topic:187417”]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?[/quote]
My child devices are also resetted when I reconfigure the FGBS001. Very annoying! :S
The four DS18B20 sensors that are attached seems to work fine and get updated, but the two motion sensors doesn’t work under UI7. I have set variable 3 and 4 to 0 and “BasicSetCapabilities” to “00=U0,FF=T0” (the inputs are connected to a normal open relay). The inputs are not changed properly.
Regards to child devices resetting and changing I’d numbers etc. The same happened to my fibaro motion sensors fgms-001 v3.2.
Today I needed to change some of the parameters within the pir, I changed the value in the parameter and clicked save remotely from work
I got the usual wake device and then waiting for manufacturer, on the way home I thought I’d try the reload engine under Z-Wave settings and it went out and changed the parameters as requested without resetting child device id’s etc.
I decided to exclude and input both my FGBS-001. Now on including the devices are well imported in vera and after manually altering the xml and json files to show my temperature sensors all seems fine.
BUT on tipping the input of the sensor ZWAVE resets!
I do not get the tripped signal in vera (red mark) and I get the blue lines on page top stating it is resetting the zwave :-\
Update 25-4-2016: I just saw both universal sensors have both inputs permanently tripped.
[i]Indeed there is an already reported issue, where some z-wave devices get reconfigured and if they have child devices, they will fail at configuring these. This is already reported and while I?m not sure if there will be enough time to be included in this months release, it will be included in 7.15 release.
As a temporary solution, you can try to configure the master sensor device, and set ?Automatically configure? to no. But not sure if this will fix the issue in every scenario.[/i]
I was also having trouble with the 2 inputs not detecting anything, but this fixed my issue
[quote=“xgutterratx, post:61, topic:187417”]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.[/quote]
Hi My sensor is not logging anything either.
To understand adding the New SErvices, Do I Put in two new services one for normally closed and one for open or do I put both values into the box, presumably I dont include the bracketed bits?
Thanks
[quote=“PCL84, post:87, topic:187417”]I was also having trouble with the 2 inputs not detecting anything, but this fixed my issue
[quote=“xgutterratx, post:61, topic:187417”]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.[/quote][/quote]
I created another ticket to MCV and this was the answer:
The priority of the issues reported in our bug tracking system is set by the number of cases reported and the gravity of the issue. I have raised the priority of this issue but the final decision on when it will be handled is taken by the product management team, so I don?t know for sure when it will be resolved.
I have 3 of those as well , included 2 of them without a problem on a vera + ( 4 temp , and both inputs) and no issues.
Another one , which I allready had some issues with , but I thought it was due to bad contacts ( ouside doorbell and gate sensor) , when I included the fibaro, only the Temperature was working, no way to get the inputs working on the vera 3 (UI7, ) and vera plus (1.7.2138).
Another one was bought , and that one included without a problem and both inputs are working.
Can it have something to do with later versions of the sensor?
[quote=“Cor, post:93, topic:187417”]Oh that is wierd ,
I have 3 of those as well , included 2 of them without a problem on a vera + ( 4 temp , and both inputs) and no issues.
Another one , which I allready had some issues with , but I thought it was due to bad contacts ( ouside doorbell and gate sensor) , when I included the fibaro, only the Temperature was working, no way to get the inputs working on the vera 3 (UI7, ) and vera plus (1.7.2138).
Another one was bought , and that one included without a problem and both inputs are working.
Can it have something to do with later versions of the sensor?
Cor[/quote]
Cor, yes. If you start reading this thread from the beginning you’ll find confirmation.
Is there any update on the state of this? I’ve just been battling trying to configure this and then came across this thread.
Cheers,
AJ[/quote]
What’s your issues AJ? I have one that I bought in the last month and worked fine straight out of the box. Using it to monitor a microswitch on a door lock and to take the indoor temperature in the house using the DS18B20 Digital Thermometer. However it does show up as generic binary sensor by default and the two inputs as motion detectors and no matter what I have tried (I want to change them to door sensors using the D_DoorSensor1.xml/D_DoorSensor1.json) as soon as I try create a scene using the sensors as trigger they default back to motion detectors in the system. I’m running the latest Vera Plus UI7 firmware 1.7.2414.
I’m still having problems with both my FGBS-001
They are both supplied from stable 12V. One is acting as a bridge from my alarm system and the other is sniffing my doorbell.
They work perfect as hardware… The outputs of the device are controlled by the inputs. No problem there…
The problem is that the status of the inputs are not reported correct in my Vera+.
For a while they worked but now both of them are reporting (falsely) one input as beeing active.
I have this:
“00=U0,FF=T0 (for normal open)
00=T0,FF=U0 (for normal closed)”
But this didn’t help.
incorrect wiring… swapped pin 1 & 3 on ds18b20 and everything working perfectly