Driver does not seem to allow multicast for Start and Stop Level Commands - Intentional?

[martinrasm]

Hi all,

I was trying to set up multicast from Home Assistant, using the zwavejs integration towards zwavejs2mqtt.
Specifically for some blind controllers. Using the binary switch command (turn it on and off) worked and it would go all open/all closed. Also the multilevel switch command to set individual levels (0-99) work.

What does not work is to get the blinds to stop while they are already moving. There are a few additional commands on the multilevel switch to go "Up" and "Down" (on/off). Setting either of these to false in the zwavejs2mqtt UI does seem to stop the blinds.

But trying to set the same via the multicast set value command (via Home Assistant's zwavejs integration) will fail. The error seems to originate from the driver.
Here is a stack trace from the zwavejs2mqtt log console:
2021-07-20 02:12:14.043 ERROR ZWAVE-SERVER: Z-Wave error The node of a virtual endpoint cannot be accessed this way! ZWaveError: The node of a virtual endpoint cannot be accessed this way! at VirtualNode.getNodeUnsafe (/usr/src/app/node_modules/zwave-js/src/lib/node/VirtualEndpoint.ts:203:9) at MultilevelSwitchCCAPI.stopLevelChange (/usr/src/app/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:250:30) at Proxy.MultilevelSwitchCCAPI.<computed> (/usr/src/app/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:420:16) at VirtualNode.setValue (/usr/src/app/node_modules/zwave-js/src/lib/node/VirtualNode.ts:47:14) at Function.handle (/usr/src/app/node_modules/@zwave-js/server/dist/lib/multicast_group/message_handler.js:12:51) at Object.multicast_group (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:38:112) at Client.receiveMessage (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:91:99) at WebSocket.<anonymous> (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:44:45) at WebSocket.emit (node:events:394:28) at WebSocket.emit (node:domain:470:12)

A person wiser than me pointed out the following and suggested I come here and ask if this is an intentional limitation. (Seems like a bug, right?)

It seems The driver code does not allow multicast for the Start and Stop Level Commands. Either this is not supported by the z-wave specification (which would surprise me) or it’s a bug/unimplemented functionality.

More information can be found in a thread in the Home Assistant forum where this was originally discussed.

[AlCalzone]

Already fixed in 8.x:
https://github.com/zwave-js/node-zwave-js/releases/tag/v8.0.1

Edit: it is not

[martinrasm]

Wonderful! So, I did try the new version (as it is now part of zwavejs2mqtt v5.3.0)

Setting Up/Down to false via home assistant & multicast now works! Awesome! Exactly what I needed so I'm happy.

However, while testing, I noticed that setting true still does not work. Is this a bug or by design? Contrary to the "false" (i.e. stop) you can still achieve the same effect by setting the binary switch or the multilevel switch to a suitable value, so I guess it's not a showstopper, really.

2021-07-20 19:17:15.510 ERROR ZWAVE-SERVER: Z-Wave error The node of a virtual endpoint cannot be accessed this way!
ZWaveError: The node of a virtual endpoint cannot be accessed this way!
at VirtualNode.getNodeUnsafe (/usr/src/app/node_modules/zwave-js/src/lib/node/VirtualEndpoint.ts:235:9)
at Proxy.MultilevelSwitchCCAPI.<computed> (/usr/src/app/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:419:7)
at VirtualNode.setValue (/usr/src/app/node_modules/zwave-js/src/lib/node/VirtualNode.ts:51:14)
at Function.handle (/usr/src/app/node_modules/@zwave-js/server/dist/lib/multicast_group/message_handler.js:12:51)
at Object.multicast_group (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:38:112)
at Client.receiveMessage (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:91:99)
at WebSocket.<anonymous> (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:44:45)
at WebSocket.emit (node:events:394:28)
at WebSocket.emit (node:domain:470:12)
at Receiver.receiverOnMessage (/usr/src/app/node_modules/ws/lib/websocket.js:835:20)

[AlCalzone]

Oh, I totally missed that you were using setValue. The fix I did was for the specific API methods.

[AlCalzone]

==> #3062