Z-Wave Fibaro Universal Sensor

🧰 Built-In Apps and Drivers Built-in Drivers
1

trying to get some response from my Z-Wave Fibaro Universal Sensor FIB_FGBS-001
Newly included, it detected it was a "Z-Wave Fibaro Universal Sensor" and the panel appeared.
i see "child 1" and "child 2" ( the two inputs)
In order to configure the device, do i need to assign parameters or use the interface that is provided?
Not having any luck seeing the change of input state on either of the two inputs (within the HE interface) though it is reporting the correct temperature.

i have a PIR switching the input. How should i assign the switch-type and device-type?

apologies for the newbie dumb questions.

2

Is this the old model, with just inputs and you can't control the outputs.

3

It's the "Z-Wave Fibaro Universal Sensor FIB_FGBS-001"
has two inputs and one output plus the temperature sensor input.

Would it be wise to assume that what functions were available on my 'old' vera system are accessible in the HE environment ?

4

found a bit more info in the forums suggesting that you configure the input types as "momentary button" this did work once or twice but not reliably every time.
Anyone able to add to this please?
thanks

5

getting closer...
Seeing the event (input activated) being recognised in the logs but also with some errors.
Is this a broken driver or can someone help resolve the issue please?

[dev:65](http://192.168.x.x/logs#pastdev65)2022-08-26 22:10:29.848 [error](http://192.168.x.x/device/edit/65)org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: fibaroBinarySensor.componentRelease() is applicable for argument types: (com.hubitat.app.DeviceWrapper, java.math.BigDecimal) values: [Outside PIR button child 1, 1] (method componentRelease)

[dev:65](http://192.168.x.x/logs#pastdev65)2022-08-26 22:10:26.206 [error](http://192.168.x.x/device/edit/65)org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: fibaroBinarySensor.componentHold() is applicable for argument types: (com.hubitat.app.DeviceWrapper, java.math.BigDecimal) values: [Outside PIR button child 1, 1] (method componentHold)

[dev:66](http://192.168.x.x/logs#pastdev66)2022-08-26 22:10:13.030 [info](http://192.168.x.x/device/edit/66)Fibaro Universal Binary Sensor temperature child 1 temperature is 19.31°C

button showing as held (input being made)
[dev:136](http://192.168.x.x/logs#pastdev136)2022-08-26 22:09:50.059 [info](http://192.168.1.3/device/edit/136)Outside PIR button child 1 button 1 was held

6

This has been replaced by the FGBS-222. It looks like it may be the FGBS-101 in a case. I don't know if any of the features are different, but all the i/o are the same. I am trying to get my new 222 sorted out and have found a lot of help by searching in the forum for FGBS-222. Looking there may work for you.

7

thanks tried that driver but still get the same errors

[dev:193](http://192.168.x.x/logs?device=4#pastdev193)2022-08-27 09:13:59.933 [error](http://192.168.x.x/device/edit/193)org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_boblehest_Fibaro_FGBS_222_Smart_Implant_609.componentHold() is applicable for argument types: (com.hubitat.app.DeviceWrapper, java.math.BigDecimal) values: [Garage_PIR button child 1, 1] (method componentHold)

getting the device held shown in the logs but not executing any actions

8

If that's the case this device only works with the C-5 and below. I believe the driver was removed from the C-7?

Unless @bcopeland has changed the driver to my suggestion on using the button events, that's how I have it working. Then you have to now pole the temperature probes which is not ideal.

9

I gave up with my old fibaro, it was useless.

I may be wrong but it seemed to be a case of buy a new version or expect to have issues. Afaik.

10

sounds like i can expect similar issues with some of my other "older" z-wave devices.
Shame, as i got the impression that the HE could be the solution for a straight swap.

Is it a case that a proper driver is needed or that the HE operating system is not fully compatible with older z-wave items?

11

I'll leave it for people more knowledgeable that me to answer completely, but I believe that unless there's an official driver then devices can have issues.

Personally, for whatever reasons, I've had issues with fibaro over 2 seperate systems. For that reason - I don't rate them.

Others will doubtlessly have another opinion.

12

may i ask, what do you use as a reliable alternative?
Looking for a small and simple single-channel input on/off module.
thanks

13

Wifi.

Nodemcu/konnected.

Search my posts.

/ off topic

14

It's because they are so old they didn't follow the standard fully. So when the new 700 series z-wave chip came out silicon labs tightened up on what works with their chip. Subsequently any device which doesn't abide by their standard would work. In this case it was how the input was triggered and how the temperature reported, however they also could reported "scene" events at the same time as the binary report. That part is to standard and so I was able to use that.

The temperature was the next problem and only way to get that working was to refresh it, so less than ideal. I have removed all but 3 of mine.

1 Like
15

I already replaced FGBS-101 2 years ago in my Vera Plus net (at that time makeshift with a qubino device). It had slowed down the connection of some other devices in the net. Now after migration to C7 I use FGBS-222.

16

@kunpet How do you get on with the FGBS-222 ?
Does it play nicely with HE ?

It appears to be a repackaged version of the original Fibaro Universal Sensor

17

I use the device as double contact sensor and it works fine (with the standard driver). It's a Gen7 device with much better z-wave qualities than the old (and additional output features I don't use)