Fibaro FGBS001 Universal Binary Sensor not working in openHAB2

[sihui]

@chris

but in the upcoming version of the binding

What happened to the database?
Errors all over the place:

[chris (Chris Jackson)]

@sihui

What happened to the database?

I added an extra check to make sure that manufacturer data is set before I export since I had a new manufacturer which wasn’t properly configured… Unfortunately, in the summary list, this information isn’t available so it shows errors (at the moment). I’ll sort this out - it’s not real though and ‘only’ shows up on this page - not the device pages (unless the data is really not set).

[sihui]

@chris

it’s not real though

Fortunately …

[chris (Chris Jackson)]

I’ve removed this check for now - once I work out how to manage it in the device list I’ll add it back… All the checks are managed centrally, but in this list I don’t load all data as it’s not needed (although I might see if it slows things down as it might ensure better consistency)…

Cheers
Chris

[alberto.vincenzi (Alberto V.)]

I’m trying to migrate to OH2 but I’m facing some problems with the Fibaro Universal Sensor: I can configure that as a contact but once I try to see it on the sitemap, nothing appear. I only see the label without the value.

On my sitemap it is configured as “Text” and in item configuration, I’m using a mapping.

In habmin->things, I see the value “Triggered” and “Untriggered”.

[dan12345 (Dan)]

I found it wouldn’t work correctly as a contact, but works fine as a Switch. Since then has been 100% reliable (it’s on a doorbell, so triggered multiple times/day).

All configurations at defaults. Items file as follows:

Switch Doorbell  "Doorbell sensor" { channel="zwave:device:51e2ba40:node228:sensor_binary1" }

[alberto.vincenzi (Alberto V.)]

But this is not correct because the fibaro input isn’t a switch but contact instead, so I should use “text” like in openhab1.

[chris (Chris Jackson)]

@alberto.vincenzi

But this is not correct because the fibaro input isn’t a switch but contact instead

Why?

Is it a Contact (Open/Closed), or is it a Switch (On/Off), or something else - your view is it’s a contact but if the binding is using a switch, then you will need to use the same type.

[alberto.vincenzi (Alberto V.)]

The binding see it as a contact but if I configure the item as text in the sitemap, I’m not able to see the value.

[sihui]

Add a [%s] to your items label definition, either through PaperUI or if your are using a text file:

Switch FibUniSens1_1 "Motion [%s]" <motion> {channel="zwave:device:158b44ebf65:node23:sensor_binary1"}

[sihui]

@alberto.vincenzi

The binding see it as a contact

Overlooked that statement: that is wrong.
If you bind an item to one of the binary_sensor channels (in HABmin click on the plus sign) it comes up as default with a switch … and you should not change the default as the item might not work then …

[alberto.vincenzi (Alberto V.)]

OK, I configured that as a switch and I get ON and OFF correctly.
I have 2 problems:

• The switch is updated only on page refresh
• The [%s] in the label doesn’t work

Frankly speaking, I don’t like to use that as a switch because any user can change the value of the item and this don’t make sense: a device like this should be a contact and not a switch.

[sihui]

@alberto.vincenzi

a device like this should be a contact and not a switch.

Have a look at this wonderful thread:

ON/OFF vs OPEN/CLOSE & Contact item - Cannot get it to work

I have a few door contacts, and while one of them works, the others don’t. They are all defined as ‘Contact’ in the item file, but the one working reports OPEN/CLOSED on change while the non-working reports ON/OFF. I have read that a contact does not accept anything but OPEN/CLOSED, so I added a map file to do this; (door.map) OFF=CLOSED ON=OPEN NULL=Unknown … and then I changed the item into; Contact GF_Corridor_Door_Garage "Garagedörr [MAP(door.map):%s]" (GF_Corridor) …

[sihui]

@alberto.vincenzi

The [%s] in the label doesn’t work

At which GUI?
I use my above item definition and it is showing in all sitemaps (Basic and Classic and Android App):

Sitemap:
Text item=FibUniSens1_1

[alberto.vincenzi (Alberto V.)]

Thanks sihui!
I solved that. The problem now is that the text value isn’t updated. I have to refresh (F5) the page to see the changes.
This seems to be more related to basicui because the classic works fine.

[randomname872634]

Thank you for starting this thread. I experienced the same problem with this sensor, but managed to get it working with the help from this thread. I can confirm it’s working now with the zwave 2.0 binding from 2.0.0.b5.

[dkw04058]

I have a FGBS-001 with a 1-Wire temperature sensor connected to Openhab2 using z-wave binding 2.2.0.201712022337.

Openhab reports the temperature with a value in the range of 170 at room temperature. When I connect additional sensor both read the same value in the range of 170. (Additional Sensor added as per Fibaro instructions.)

The log console shows the following "NODE 10: Received a multi instance encapsulation with a destination endpoint = 3. " for each temperature update.

Solved*

The DS18b20 Temperature sensors were set 9 bit resolution, they need to be set to 12 bit resolution. To change the resolution I followed the guide here. It uses an Arduino to write the resolution to 12 bit in the eeprom.

Darren