zwave-js: HS-WX300 Switch/Dimmer Parameter 3 seems to not work correctly

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?

Unknown

What do you observe?

Parameter 3, which controls the bottom LED operation, doesn’t seem to work correctly. Here is what happens on my HS-WX300 that is setup as a switch

on when load is on load is off == LED 1 is on load is on == All 7 LEDs are on on when load is off load is off == All 7 LEDs are off load is on == All 7 LEDs are on

What did you expect to happen?

on when load is on load is off == LED 1 is off load is on == LED 1 is on on when load is off load is off == LED 1 is on load is on == LED 1 is off

Steps to reproduce the behavior:

  1. Go to config parameter 3 and set it to desired setting, make sure config parameter 13 is disabled and all LEDs are switched to off.
  2. Click on/off the switch either manually or remotely
  3. Look at LED 1

Device information

Manufacturer: Homeseer Model name: HS-WX300 Node ID in your network: 120

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: node-zwave-js branch: zwavejs2mqtt branch:

zwavejs2mqtt: 6.2.0 zwave-js: 8.9.1

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

2022-01-05 23:13:51.445 INFO ZWAVE-SERVER: ZwaveJS server listening on port 3000

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 17 (7 by maintainers)

Most upvoted comments

exclusion, factory reset, and inclusion fixed the issue. Thanks !!!

@rrauenza I’m fine updating our config files to match the actual device behavior.

Thank you for your last comment. I used it in my communications with HS. I seem to have gotten some traction.

From Homeseer:

It looks like this is an error in documentation as parameter 3 explicitly says both that it will control the bottom LED and that it will control all of them. I will reach out to our engineers about this so we can get the doc updated and perhaps get a feature request in that allows for both options.