Fibaro Door Window Sensor 2 (FGDW002) binary_sensor does not update

[Veldkornet]

Home Assistant release with the issue:
0.94.4

Last working Home Assistant release (if known):
N/A

Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io

Component/platform:
https://www.home-assistant.io/components/zwave/

Description of problem:
The binary sensor state of the Fibaro Door Window Sensor 2 (FGDW002 Door Opening Sensor 2) does not update when the "door" is opened and closed.

Currently, you are required to add a template such as the below, in order to create a new virtual sensor which uses the access_control sensor of the FGDW002 in order to update the state:

- platform: template
  sensors: 
    door:
      sensor_class: opening
      friendly_name: 'Door'
      value_template: >
          {{ is_state('sensor.DOOR_access_control', '22') if states('sensor.DOOR_access_control') in ['22','23'] else states('binary_sensor.door') }}

With the access_control being:

22 : Open
23 : Closed
254 : Deep sleep
255 : Case open

Additional information:
The primary binary_sensor of the device should update without the need of having to create a virtual sensor with templates. The V1 of the sensor (FGK10x Door Opening Sensor) works correctly and without any problems. It is expected that the FGDW002 should function in the same way.

Home Assistant Community Discussion

[stale]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Veldkornet]

Still an issue on 0.99.2 as far as I know.

[pulsar895]

Same issue on 0.99.3 on HassOS 2.12.

[mr-white83]

same issue on 0.100.2

[altomcat]

Still an issue on 0.101.3 [HassOS 2.12]

[vt220-100]

Still an issue on 0.102....Please fix

[JIOB]

Still an issue in 0.103

[ismarslomic]

Still an issue in 0.103.5

[bpannier]

Still an issue with 0.105.1

[probot-home-assistant]

Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with a integration (zwave) you are listed as a codeowner for? Thanks!

[stale]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Stromber03]

I have still this issue on HassOS 4.10 and hasio 0.110

[Veldkornet]

FYI, it seems to be okay with the new OpenZWave Beta