node-zwave-js: Incorrect parameter range for HomeSeer Floodlight Sensor HS-FLS100+

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? Unable to input parameter value of zero due to incorrect range in homeseer_template.json file. Current parameter min to max is 10 to 900, but actual parameter min-max is 0 to 255.

For HomeSeer HS-FLS100+, Lux_Trigger_Threshold, allowed values are 0, 30-200, 255. Value 0 will NOT activate floodlight. Value 30 represents 10 lux, Value 200 represents 900 lux. Value 255 will activate floodlight regardless of ambient light level

What do you observe? Zwave JS HomeSeer HS-FLS100+ parameter options

What did you expect to happen?

Per the manual (located at - https://products.z-wavealliance.org/ProductManual/File?folder=&filename=MarketCertificationFiles/2947/HS-FLS100-user-manual2b-A501112779R.pdf )

HomeSeer HS-FLS100+ Manual

Parameter file needs to be updated as follows:

"lux_trigger_threshold": {
	"label": "Light Level Threshold",
	"description": "Allowed values are 0, 30-200, 255. Value 0 will NOT activate floodlight. Value 30 represents 10 lux, Value 200 represents 900 lux. Value 255 will activate floodlight regardless of light level",
	"valueSize": 2,
	"minValue": 0,
	"maxValue": 255,
	"defaultValue": 50,
	"unsigned": true
},

Steps to reproduce the behavior:

  1. Go to ‘…’
  2. Click on ‘…’
  3. Scroll down to ‘…’
  4. See error

Device information

Manufacturer: HomeSeer Model name: HS-FLS100+ Node ID in your network:

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:

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

No Log file needed

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 1
  • Comments: 23 (6 by maintainers)

Most upvoted comments

@AlCalzone thanks! I was missing the templates folder and I was able to add the custom device config now. I didn’t see that mentioned here https://zwave-js.github.io/zwave-js-ui/#/device-support/custom-device-files

Adding the code to disable “Supervision with Configuration CC” as mentioned above works and I am now able to set the parameters without errors

I will open a PR to change the device config. Thanks again

PR created: https://github.com/zwave-js/node-zwave-js/pull/5663