Has anybody managed to get this to work correctly. I have added, deleted it to the network several times. I have noticed that it will not read the binary input no matter what I do. It reads the temperature and tamper alerts but nothing else. I also notice there is no history to any of the settings events unlike other fibaro sensors I have. Any feedback would be very much welcome. I have looked at other threads with people having similar issues and there is no conclusive answer to this question…
Thanks
OK so I have ascertained that the newer versions of Fibaro sensor have firmware 3.2 and above use a slightly different protocol than the earlier ones…so does this mean the code on Home Assistant has to be modified before it can handle the binary inputs or are they just never going to work ! Also the lack of history turned out to be a corrupt database. Deleted it and restarted and that is ok now…
Did you use Add Node Secure to pair it? If not then that would explain your problems. From their product page:
FIBARO Flood Sensor with firmware 3.2 or higher is a Security Enabled Z-Wave Plus product and a Security Enabled Z-Wave Controller must be used in order to fully utilize the product.
If you didn’t exclude it, ensure you’ve set a network key, and add it using Add Node Secure. Don’t use any button on your Z-Wave stick, don’t use OZWCP.
If you did use Add Node Secure read on.
If the newer firmware isn’t supported by OpenZWave then see here for how you can work with the OpenZWave developers to address that.
Looking at the config list, there’s already 2 versions supported, the latter of which (this one), looks to be a match for the Fibaro manual.
Hi Tinkerer
Thanks for the information
I did add it via Add Node Secure within HassIO…and the network key has been set. It is recognised but the binary condition
binary_sensor.fibaro_system_fgfs101_zwave_flood_sensor_sensor
is not recognised in a flood condition.
Check the configuration of the device, few will enable the Binary reports by default.
I’ve read and re-read the pdf…But can’t seem to find anything that enables by default…the sensor beeps in a flood condition and that can be switched off from Home Assistant but that is about the only one that I could see that would cause a problem not set correctly, unless there are other hidden attributes I am unaware of…
Have you looked in the Configuration section of the Z-Wave control panel? Manuals are often out of sync with the updates to device firmware.
Yes I have…It reflects the contents of the manual…
Unfortunately in that case it sounds like the device doesn’t actually support Binary reports fully.
If you can identify which sensor. node reports on the flood conditions, you can create a template binary sensor to use that.
I’m not quite sure how they work…I know the output from
sensor.fibaro_system_fgfs101_zwave_flood_sensor_flood
reads 2 when it is in flood condition…and when it isn’t it, it’s 0
But not sure how that translates to the ‘template binary sensor’
Like this:
binary_sensor:
- platform: template
sensors:
flood:
device_class: moisture
friendly_name: 'Flood sensor'
value_template: >-
{%- if is_state("sensor.fibaro_system_fgfs101_zwave_flood_sensor_flood", "2") -%}
on
{%- else -%}
off
{%- endif -%}I am really grateful for all your help Tinkerer…I have entered the code as written above into configuration.yaml.
the sensor is listed as a binary sensor
binary_sensor.flood
But it only report OFF and does not trigger when the the contacts are soaked. The
sensor.fibaro_system_fgfs101_zwave_flood_sensor_flood
goes from 0 to 2 though when wet…all very confusing
Check the sensor name in the template is correct.
You should also be able to use
binary_sensor:
- platform: template
sensors:
flood:
device_class: moisture
friendly_name: 'Flood sensor'
value_template: >-
{%- if states("sensor.fibaro_system_fgfs101_zwave_flood_sensor_flood") > 0 -%}
on
{%- else -%}
off
{%- endif -%}Ok I’ve checked all syntax and the sensor name, I have also tried your last suggestion above and still no trigger…
Hmmmm, try true instead of on and false instead of off. That’s the only thing I can think of.
1 Like
Brilliant you’re a star…Thank you so much for your help Tinkerer…works a treat now !!
Has anyone figured out what the General sensor shows?
I am struggling with the same senario. I am on Hassio 0.59.2.
I was hoping this would work in my configuration.yaml-file, but it does not:
alert:
water_sensor1:
name: Vannlekasje
done_message: Vannleksje alarm slått av
entity_id: binary_sensor.fib_flood_sensor1_sensor
state: 'on'
repeat: 30
can_acknowledge: True
skip_first: False
notifiers:
- ios_Tomahawk_iphone_6
Looking in “Developer Tools -> States”, I have:
zwave._fib_flood_sensor1
binary_sensor.fib_flood_sensor1_sensor
sensor.fib_flood_sensor1_alarm_level
sensor.fib_flood_sensor1_alarm_type
sensor.fib_flood_sensor1_burglar
sensor.fib_flood_sensor1_flood
sensor.fib_flood_sensor1_flood_2
sensor.fib_flood_sensor1_general
sensor.fib_flood_sensor1_sourcenodeid
sensor.fib_flood_sensor1_temperature
Do I rely have to program set up “binary_sensor:
platform: template” as described above to get this to work?
If so, please describe where which file “binary_sensor:” goes, and other relevant code/files.
Since I am not å developer/programmer I find this platform quite difficult to work with.
Does binary_sensor.fib_flood_sensor1_sensor show on if the sensor comes into contact with water?
Do either of sensor.fib_flood_sensor1_flood or sensor.fib_flood_sensor1_flood_2 change state when the sensor comes into contact with water?
Thanks for replying!
My log after triggering the sensor with water says:
2017-12-19 11:54:52.985 Info, Node006, Received Alarm report: type=5, level=0, sensorSrcID=0, type:Flood event:0, status=255
2017-12-19 11:54:52.985 Detail, Node006, Refreshed Value: old value=5, new value=5, type=byte
2017-12-19 11:54:52.985 Detail, Node006, Changes to this value are not verified
2017-12-19 11:54:52.985 Detail, Node006, Refreshed Value: old value=2, new value=0, type=byte
2017-12-19 11:54:52.985 Detail, Node006, Changes to this value are not verified
2017-12-19 11:54:52.986 Detail, Node006, Refreshed Value: old value=0, new value=0, type=byte
2017-12-19 11:54:52.986 Detail, Node006, Changes to this value are not verified
2017-12-19 11:54:52.986 Detail, Node006, Refreshed Value: old value=2, new value=0, type=byte
2017-12-19 11:54:52.986 Detail, Node006, Changes to this value are not verified
2017-12-19 11:54:52.986 Detail, Node006, Notification: ValueChanged
2017-12-19 11:54:52.999 Detail, Node006, Notification: ValueChanged
2017-12-19 11:54:53.011 Detail, Node006, Notification: ValueChanged
2017-12-19 11:54:53.023 Detail, Node006, Notification: ValueChanged
Andt the “Developer Tools - States” shows:
No, the sensor states does not change from “0”.