Fibaro Door Sensor V2

ViperRNMC · September 18, 2017, 11:56am

here also after update unknown and not working

frelev · September 18, 2017, 7:57pm

I´ve spent some time trying to get this sensor to work without luck.

If anyone got this up and running please specify what you have in your zwcfg_XXX.xml, manufacturer_specific.xml and if you are using fgdw2.xml

I can see the temperature and other sensors but binary_sensor is alway off and wont change

Thanks

ghayoz · October 1, 2017, 5:41pm

Same for me. At the end I reinstall from zero all my Home assistant but this is worst! All my sensor (including old one which was working before) are not recognize…
I’ll retry other install, I have the feeling that some open z-wave or python z-wave are not updated or compatible.

Tinkerer · October 1, 2017, 8:39pm

What version of Home Assistant did you install, and how did you install it (HassIO, Hassbian, AIO, other)?

What is your Z-Wave controller?

The FGDW2 was added to OpenZWave 5 months ago, and is available in 0.54 of Home Assistant. If you’re having problems with other devices too though, I’d suggest that a fresh thread for your specific problems is a good idea.

krmzn · October 2, 2017, 7:07am

I don’t see Open z-wave being mentioned anywhere in the latest change log, but I surely hope it is true
I will try to unpair and repair my FGDW2 devices to see if they appear as expected.

ghayoz · October 2, 2017, 7:14am

Hello,
I have follow this procedure :

I have a Aeotec ZW090 Z-Stick Gen5 EU.
Accordons to you what is the best way to install HA with Zwave?

This morning after many reboot and a night of discovery, senses are named :
FGK10x Door Opening Sensor --> old recognize as before, I have to check if it works when I open the door.
FGDW002 Door Opening Sensor 2 --> named but no reaction when I move the sensor (temperature is ok)
second FGDW002 Door Opening Sensor 2 --> not named and manufacturer_name is not displayed…

Disappointed

Tinkerer · October 2, 2017, 6:28pm

It happens automatically as long as you’re running a recent version. What version did you install?

How did you include the devices? Did you use the Z-Wave control panel built into HA (the correct way), or the OZW control panel, or the button on the stick (a way that’ll cause issues)?

ghayoz · October 3, 2017, 9:39pm

I instal the last version available 0.54.0.
Ok, how can I reset my Z-wave and try again. I have click on “remove node” in HA control panel but I still see the device in list (after having restart HA services).
Thanks for your help.

Tinkerer · October 3, 2017, 9:41pm

You have to put the device into exclusion mode immediately after you select Remove Node for it to be removed. The manual for the device will tell you how to do that.

ghayoz · October 4, 2017, 11:39am

Hello Tinkerer,
Thanks for your message. I have exactly made your procedure. Click on “Remove Node” and click 3 times on my Z-Wace device, but he remained in the list…

Tinkerer · October 4, 2017, 12:59pm

Did you then restart HA?

While it’ll be removed, the entity may remain visible until you restart.

ghayoz · October 4, 2017, 1:28pm

yes I restarted HA by the commande : “sudo systemctl restart home-assistant.service” and finally my raspberry totally…

ViperRNMC · October 4, 2017, 2:21pm

Hi, i removed and insert the sensor again and the name is fine, but de binary sensor won’t switch. Maybe this ozw log will help.

2017-10-04 16:16:25.411 Info, Node029, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:23, status=255
2017-10-04 16:16:25.411 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:25.411 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:25.411 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:25.411 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:25.411 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:25.411 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:25.411 Detail, Node029, Refreshed Value: old value=22, new value=23, type=byte
2017-10-04 16:16:25.411 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:25.411 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:25.414 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:25.416 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:25.418 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:25.509 Detail, Node029,   Received: 0x01, 0x0f, 0x00, 0x04, 0x00, 0x1d, 0x09, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x16, 0x00, 0x7b
2017-10-04 16:16:25.509 Detail, 
2017-10-04 16:16:25.509 Info, Node029, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:22, status=255
2017-10-04 16:16:25.509 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:25.509 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:25.509 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:25.509 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:25.509 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:25.509 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:25.509 Detail, Node029, Refreshed Value: old value=23, new value=22, type=byte
2017-10-04 16:16:25.510 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:25.510 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:25.512 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:25.514 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:25.516 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:28.355 Detail, Node029,   Received: 0x01, 0x0f, 0x00, 0x04, 0x00, 0x1d, 0x09, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x17, 0x00, 0x7a
2017-10-04 16:16:28.355 Detail, 
2017-10-04 16:16:28.355 Info, Node029, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:23, status=255
2017-10-04 16:16:28.355 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:28.355 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:28.355 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:28.355 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:28.355 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:28.355 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:28.355 Detail, Node029, Refreshed Value: old value=22, new value=23, type=byte
2017-10-04 16:16:28.355 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:28.355 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:28.357 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:28.360 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:28.362 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:28.654 Detail, Node029,   Received: 0x01, 0x0f, 0x00, 0x04, 0x00, 0x1d, 0x09, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x06, 0x16, 0x00, 0x7b
2017-10-04 16:16:28.654 Detail, 
2017-10-04 16:16:28.654 Info, Node029, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Access Control event:22, status=255
2017-10-04 16:16:28.654 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:28.654 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:28.654 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:28.654 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:28.654 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:28.654 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:28.654 Detail, Node029, Refreshed Value: old value=23, new value=22, type=byte
2017-10-04 16:16:28.654 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:28.654 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:28.656 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:28.659 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:28.661 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:37.222 Detail, Node029,   Received: 0x01, 0x0f, 0x00, 0x04, 0x00, 0x1d, 0x09, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x07, 0x00, 0x00, 0x6c
2017-10-04 16:16:37.223 Detail, 
2017-10-04 16:16:37.223 Info, Node029, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Burglar event:0, status=255
2017-10-04 16:16:37.223 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:37.223 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:37.223 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:37.223 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:37.223 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:37.223 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:37.223 Detail, Node029, Refreshed Value: old value=3, new value=0, type=byte
2017-10-04 16:16:37.223 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:37.223 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:37.226 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:37.228 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:37.230 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:38.683 Detail, Node029,   Received: 0x01, 0x0f, 0x00, 0x04, 0x00, 0x1d, 0x09, 0x71, 0x05, 0x00, 0x00, 0x00, 0xff, 0x07, 0x03, 0x00, 0x6f
2017-10-04 16:16:38.683 Detail, 
2017-10-04 16:16:38.683 Info, Node029, Received Alarm report: type=0, level=0, sensorSrcID=0, type:Burglar event:3, status=255
2017-10-04 16:16:38.683 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:38.683 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:38.683 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:38.683 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:38.683 Detail, Node029, Refreshed Value: old value=0, new value=0, type=byte
2017-10-04 16:16:38.683 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:38.683 Detail, Node029, Refreshed Value: old value=0, new value=3, type=byte
2017-10-04 16:16:38.683 Detail, Node029, Changes to this value are not verified
2017-10-04 16:16:38.683 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:38.686 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:38.688 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:38.690 Detail, Node029, Notification: ValueChanged
2017-10-04 16:16:44.317 Detail, Node006,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x06, 0x06, 0x31, 0x05, 0x04, 0x22, 0x00, 0x06, 0xe3
2017-10-04 16:16:44.317 Detail,

Tinkerer · October 4, 2017, 5:30pm

The Fibaro Door Sensor v2 (FGDW-002) doesn’t list Binary Sensor in the supported command classes, which is why you’re not finding a binary sensor node.

You’ll need to use a binary_template sensor. If it has an access_control entity, then the following should work:

- platform: template
  sensors: 
    door:
      sensor_class: opening
      friendly_name: 'Door'
      value_template: >- 
        {%- if is_state("sensor.DOOR_access_control", "22") -%}
        open
        {%- else -%}
        closed
        {%- endif -%}

ViperRNMC · October 4, 2017, 6:35pm

thanks, this works

ghayoz · October 4, 2017, 8:39pm

Hi,
thanks for your message. It start to help me!
I try to copy/past your custom code in sensor section but I get this error message:
2017-10-04 22:32:11 ERROR (MainThread) [homeassistant.config] Invalid config for [sensor.template]: [sensor_class] is an invalid option for [sensor.template]. Check: sensor.template->sensors->door->sensor_class. (See ?, line ?). Please check the docs at https://home-assistant.io/components/sensor.template/

In my sensor section I have other sensor working fine.

ViperRNMC · October 5, 2017, 6:09am

must be device class, if have this binary sensor

binary_sensor:
- platform: template
  sensors:
    sensor_schuur:
      device_class: opening
      friendly_name: Schuurdeur
      value_template: >
        {{ states.sensor.sensor_schuur_access_control.state != '23' }}

Luckymoep · December 28, 2017, 6:36pm

thx, this is working for me!

klaasnicolaas · February 13, 2018, 6:16pm

This code works fine here too, Thnx!
Edit: unfortunately the sensor appeared but when the door was opened nothing happened (now solved)

Have improved the code a little bit. Sometimes the value changed to 254, which caused me an “open” status

This is the code that I used:

binary_sensor:
- platform: template
sensors:
sensor_voordeur:
device_class: door
friendly_name: Voordeur
value_template: >
{{ states.sensor.fibaro_system_fgdw002_door_opening_sensor_2_access_control.state < ‘23’ }}

northhacks · July 19, 2018, 10:12am

If I try your Code @klaasnicolaas my Doors are all closed.

My config is working fine but the value 254 is a problem for it.

platform: template
sensors:
buero_tuer:
device_class: door
friendly_name: ‘Büro Tür’
value_template: >-
{{ states.fibaro_system_fgdw002_door_opening_sensor_2_access_control.state != ‘23’ }}

Does anyone has an idea?

Thanks