VES-ZW-WAL-009 has problems with Zwave.JS and Home Assistant, according to Vesternet Support.

[MOROHEUZ]

Describe the issue you are experiencing

"I have been trying to integrate the VES-ZW-WAL-009 from Vesternet for some time. The Vesternet support is doing a good job and they suggested that excluding and including the device multiple times could help.

In the end, the scenes from the switch are not displayed.

After further discussion with the support, it is a known problem between ZwaveJS and HomeAssistant.

I am writing down the wording here:

"We have had a few other reports of this in the last few days and it seems to be some issue between Z-Wave JS and Home Assistant where the triggers aren't being created. The other people reported that Excluding and Including the device several times appeared to resolve the problem.

I have added a note to our development team to investigate this further in due course, in case there's something amiss with the device configuration within Z-Wave JS."

However, I cannot find anything about this anywhere, so I have to assume that nothing has been reported here.

The switch, however, works smoothly under SmartThings, so the support must be right."

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Z-Wave JS

What is the version of the add-on?

1.15.11

Steps to reproduce the issue

1. Include The VES-ZW-WAL-009
2. Click Automation
3. only Battery Status are available.
4. no Central Scene action on Endpoint 0 are Possible. ...

System Health information

nothing

Anything in the Supervisor logs that might be useful for us?

no Error for this Device

Anything in the add-on logs that might be useful for us?

NO Error for This Device

Additional information

Perhaps the topic is already known. As I said, I have not found anything about it. Maybe Vesternet does not communicate through this channel.

[home-assistant[bot]]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `zwave_js` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zwave_js` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

zwave_js documentation zwave_js source _{^{(message by IssueLinks)}}

[MartinHjelmare]

Please download diagnostics of your Z-Wave device and attach it as a text file here by dragging and dropping the file in a comment.

The diagnostics tool is available by clicking the three dots menu of the Z-Wave device in the device page in the Home Assistant GUI.

The device diagnostics will help us troubleshoot your device.

Thanks!

[MOROHEUZ]

zwave_js-b2a7c664ad9c153fa63380f1463877bd-Wall Controller - 8 Button-57ea1674eb3b5a9b808ec89cb4637504.json.txt

I hope this files helps

[MartinHjelmare]

Looking at the diagnostics dump of the device, there's no central scene command class value that has property scene. The only central scene command class value in the that dump has property slowRefresh.

Either the device isn't interviewed properly or the device software is broken somehow if a central scene with scene property is expected for this device.

I'd try re-interviewing the device. If that doesn't solve it, capture a driver debug log from the interview and also from an inclusion and attach to this issue.

https://www.home-assistant.io/integrations/zwave_js/#how-to-access-the-z-wave-logs

[MOROHEUZ]

zwave_js.log

I have added the JS debug log.

would be a real pity if it would not work. according to support information, they currently often have the problem, apparently only with Zwave - JS.

I will test this again with Smartthings and an Edge driver.

a second Zwave network I will not build because of a switch.

Subsequent modification

When testing with Smartthings, all buttons work and the battery status is also ok.

The problem is definitely not with the switch itself. (Hardware)

[MOROHEUZ]

I have found a workaround.

but shouldn't it work automatically if I select "Secure if possible?"

I can live with it. I use the button with this setting.

No idea if you can change that. I will tell the manufacturer so that he can possibly inform his other customers.

[AlCalzone]

@MOROHEUZ The device responds with an invalid version when asked with version of Security 2 it supports:

2023-09-22T08:51:00.246Z CNTRLR » [Node 060]   querying the CC version for Security 2...
2023-09-22T08:51:00.255Z DRIVER » [Node 060] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      215
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 111
                                    │ security class:  S2_Unauthenticated
                                    └─[VersionCCCommandClassGet]
                                        CC: Security 2
...
2023-09-22T08:51:00.308Z DRIVER « [Node 060] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -87 dBm
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 23
                                    │ security class:  S2_Unauthenticated
                                    └─[VersionCCCommandClassReport]
                                        CC:      Security 2
                                        version: 0
2023-09-22T08:51:00.309Z CNTRLR   [Node 060]   does NOT support CC Security 2 (0x9f)

This causes Z-Wave JS to stop using S2 for communication although the device is included using S2.

The version: 0 is a bug in the device, but we shouldn't use this information to deduce that the device doesn't support the CC.