node-zwave-js: FIBARO Walli Double Switch FGWDSEU-221: "Parameter 40" and "Parameter 41" cannot be set to ">8"

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within ZWaveJS2MQTT?

NO, my problem is NOT within ZWaveJS2MQTT

Checklist

Describe the bug

What causes the bug? It is not possible to set configuration parameter 40 and 41 of the FIBARO Walli Double Switch FGWDSEU-221 to a value in range 0…15. It is possible to set this parameter 40 and 41 in range 0…8, but that does not cover all capabilities.

What do you observe? In the manual of the device: https://manuals.fibaro.com/wp-content/uploads/2019/06/FGWDSEU-221-T-EN-v1.2-1.pdf Page 30 shows that values 1, 2, 4 and 8 can be added to each other, resulting in a value in range 0…15.

In the documentation Z-Wave JS Config DB Browser: https://devices.zwave-js.io/?jumpTo=0x010f:0x1b01:0x1000:0.0 Parameter 40 and 41 can only be 1, 2 ,4 and 8. This is wrong.

What did you expect to happen? To be able to set the parameter of the device.

Steps to reproduce the behavior:

  1. In Home Assistant preferences select the device,
  2. Enter Z-Wave Device Configuration,
  3. Try to set parameter 40 or 41 to a value > 8
  4. An error occurred. Must provide a value within the target range (Min: 0, Max: 8)

Device information

Manufacturer: Fibaro Model name: FGWDSEU-221 Node ID in your network: 14

How are you using node-zwave-js?

  • zwavejs2mqtt Docker image (latest)
  • zwavejs2mqtt Docker image (dev)
  • zwavejs2mqtt Docker manually built (please specify branches)
  • ioBroker.zwave2 adapter (please specify version)
  • HomeAssistant zwave_js integration (please specify version)
  • pkg
  • node-red-contrib-zwave-js (please specify version, double click node to find out)
  • Manually built from GitHub (please specify branch)
  • Other (please describe)

Which branches or versions?

version: 0.1.52

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

No, it never worked anywhere

If yes, where did it work?

No response

Attach Driver Logfile

The logfile is not needed.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 19 (12 by maintainers)

Most upvoted comments

I’m going to merge both files, the other one seems to be redundant and wasn’t cleaned up.