How to Set Parameter 6 on HomeSeer HS-WS200+ switches?

Configuration Z-Wave
1

I have a number of HomeSeer HS-WS200+ Z-Wave switches in my house and would like to set parameter 6 to a value of “1” to disable central scene. This effectively makes switching instant as it removes the delay since the switch doesn’t have to wait for multiple taps.

This parameter is only available in the most recent firmware version for this switch. Because of this (I’m assuming), Z-Wave JS does not support changing this parameter. I even tried using the developer tools to do it–it simply doesn’t recognize that parameter.

So… two questions:

  1. Is it possible to set this parameter within Home Assistant?
  2. If not, is it possible to set this parameter otherwise? I.e., is there an application I can run (Windows preferred, but could manage Linux) where I could access the Z-Wave controller to manually set this variable?
2

Go to Open your Home Assistant instance and show your service developer tools.

Use the zwave_js.invoke_cc_api service to manually call the Driver CC API to set config parameters.

service: zwave_js.invoke_cc_api
data:
  command_class: '112'
  method_name: set
  parameters:
    - 6
    - 1
    - 1

The first item in the parameter list is the parameter number, the second is the value to set, and the third is the size of the parameter (1-byte).

You can copy and paste that YAML code into the Services YAML mode, then switch to UI mode and select your device.

Consider submitting a Bug Report to request that the new parameter be added (or even better, submit a PR to implement it) for the benefit of the community. Z-Wave JS has the ability to present config parameters based on firmware versions.

zwavejs2mqtt also provides the ability to perform this same task in an easier manner via its control panel UI.

3

That is perfect–thanks so much. I never would have figured that out on my own. I was able to update around 13 devices within seconds.

I also submitted a bug report to see if we can get it added to Z-Wave JS for future use. Thanks again for your help.

4

I have a similar problem with my HomeSeer HS-FLS100+. All of the parameters 5 and above are not available. I compared the Z-Wave JS Device Database with the manufacturer’s documentation The former has 4 parameters and the latter has 8.

I tried the technique here

action: zwave_js.invoke_cc_api
data:
  device_id:
    - 213e0ef9a083aa3d505bce43c954274c
  command_class: "112"
  method_name: set
  parameters:
    - 6
    - 1
    - 1

and got the error

Failed to perform the action zwave_js.invoke_cc_api. Endpoint(node_id=6, index=0) - FailedZWaveCommand: zwave_error: Z-Wave error 322 - options is not a ConfigurationCCAPISetOptions (ZW0322)

command class 0x70 (112)
parameter 6
size of data 1
data 1

What is the encantation to set this parameter?

5 
action: zwave_js.invoke_cc_api
data:
  device_id:
    - 213e0ef9a083aa3d505bce43c954274c
  command_class: "112"
  method_name: set
  parameters:
    - parameter: 6
      value: 1
      valueSize: 1
      valueFormat: 1    # Unsigned

If you don’t need to automate it, just use the device configuration UI.

image
image1612×385 22.8 KB

6

Thanks!

The YAML did not report an error.

Alas, the UI responded with:

zwave_error: Z-Wave error 322 - options is not a ConfigurationCCAPISetOptions (ZW0322)

7

I see the same thing, both with Get and Set. Although I don’t see the errors in the UI, just the Z-Wave JS UI logs. Guess it’s a bug.

Update: UI works fine for me in 2025.1.1, was not working in 2024.12.5.

8

I updated HA core to 2025.1.1 and I didn’t get any errors.

But, when I performed the incantations you described; they had no effect, the actions remained as if the setting were default. I tried many variations: Visual Editor vs YAML, three different valueSize, five different valueFormat (one of the 5 valueFormat was none)

Previously I had this sensor on a Z-Wave network sourced by a Universal Devices ISY994i controller. I was able to set the parameter with that controller.

I also have a Z-Wave Plus Floodlight Sensor HomeSeer HS-FLS100-G2 and HA has all of the parameters for it. For completeness sake, I tested changing parameter 5 on this device using all the techniques described here and the results were what one would expect from reading the manual for it.

This may be a bug?

Thanks for your consideration

OSD

9

UPDATE:

My claim that I had this working with the ISY994i got me thinking and concerned that I made an unfounded claim or that the Z-Wave Plus Floodlight Sensor HomeSeer HS-FLS100+ had gone bad. So I excluded the device from the HA Z-Wave network and included it the ISY994i Z-Wave network.

This showed the same problem. (One reason I moved the Z-Wave devices from the ISY994i to HA was that Z-Wave didn’t always work well enough.) After more trial and error I was able to get the device to work how I wanted: Light switch working independently from the motion sensor. I did this by setting

  • Lux Sensor Threshold. parameter 2 to the minimum. (HA indicates 0, HomeSeer docs say 10)
  • Load Control Mode parameter 5 to Load controlled by Z-Wave Only (0)
  • Load Control Sensor Mode parameter 6 to Load controlled by Lux Only (1)

In conclusion, I have every reason to believe that there is no bug in HA in regards to this matter.

(Sorry for the long winded response. It’s just that I don’t like no responses nor responses that just say “I got it fixed” with no explanation of how.)

Thanks for all the help here.

OSD

1 Like