HS-WX300 switch mode S2 broken

[pdobrien3]

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

• [X] I have checked the troubleshooting section and my problem is not described there.

• [X] I have read the changelog and my problem was not mentioned there.

Describe the bug

What causes the bug? When including the HS-WX300 while in switch mode, it appears to successfully include but then you cannot control the device. If included with no encryption, it works fine. Also, apparently when included with S2 in dimmer mode, the device works fine

What do you observe?

https://community.home-assistant.io/t/homeseer-hs-wx300-in-switch-mode/362425

What did you expect to happen?

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-WX300 Node ID in your network:

How are you using node-zwave-js?

• [X] 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.3.0 zwave-js: 8.10.1 home id: 3479161084 home hex: 0xcf5fc8fc

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

Log files are in the Home Assistant Forum post

[pdobrien3]

Hoping to pass along this issue to Homeseer for their response

[AlCalzone]

@pdobrien3 did you ever hear anything back from Homeseer?

[pdobrien3]

Yes, here was their response:

While I have not heard back about parameter 3, I do have more information about S2 security. That functionality was tested using independent Z-Wave certification tools as well as HS4 and we are unable to recreate the issue. There are only reports of this issue occurring in Home Assistant systems and I believe our engineers intend to post their detailed findings on the Home Assistant forum.

[AlCalzone]

There are only reports of this issue occurring in Home Assistant systems

Might be because there are no other open source drivers doing S2, but let me know when they do. That linked thread hasn't seen any activity in months, wonder when they are going to post their findings.

[pdobrien3]

I pretty much threw my hands up. Mostly because I do not have the knowledge to argue with them. They basically say S2 is a function of the software and not the device. I have the same issue with the 100s, they also can not be included with S2 even though they claim they support it.

[AlCalzone]

AFAIK S2 on end devices is actually implemented in the Z-Wave SDK, so it ideally they would be right. But on the other hand there are other devices from some manufacturers which also seem to have sporadic issues with S0 and S2 while devices from other manufacturers don't have these issues at all...

Go figure 🤷🏻‍♂️

[pdobrien3]

Wouldn’t it be awesome if they saw the benefit of looking at the zwavejs code and providing an opinion.

[AlCalzone]

It would, but I don't have high hopes seeing how they handled the obviously broken Supervision CC implementation in their 200 series (paraphrased: "Throw the 200 series devices out and buy the 300 series")