Multicast commands from zwavejs2mqtt not working

Checklist:

• I am not using HomeAssistant. Or: a developer has told me to come here.
• I am not using ZWaveJS2MQTT. Or: a developer has told me to come here.
• I have checked the troubleshooting section and my problem is not described there.
• I have read the changelog and my problem was not mentioned there.

Describe the bug

Sending a multicast command to zwavejs2mqtt results in a timeout of the command and all communication with the nodes included in the command getting queued until the timeout occurs.

Device information

Which device(s) is/are affected (make/model)? Zooz Zen 22 and Nortek PD300Z-2 What are the node IDs? 4 and 5

Did you change anything?

• Yes: (please describe)
• No

Did this use to work before?

• Don’t know, this is a new device
• No, it never worked anywhere
• Yes, in: (specify application with versions)

How are you using node-zwave-js

• zwavejs2mqtt (latest) docker image
• zwavejs2mqtt (dev) docker image
• zwavejs2mqtt Manual Docker build
  • node-zwave-js branch:
  • zwavejs2mqtt branch:
• ioBroker.zwave2 adapter
• HomeAssistant version XYZ
• Pkg
• Manual Docker build
  • node-zwave-js branch:
  • zwavejs2mqtt branch:
• node-red-contrib-zwave-js
  • Module version (double click node):
• Manually built (as described in the docs)
• Other:

To Reproduce

Steps to reproduce the behavior:

1. Publish following data to zwave/_CLIENTS/ZWAVE_GATEWAY-zwavejs2mqtt/multicast/set

{ “nodes”: [ 4, 5 ], “commandClass”: 38, “property”: “targetValue”, “value”: 33 }

Additional context

I thought the issue might be related to the one node supporting SupervisionCC, and the other not, but I tried sending commands to two nodes that both do not support SupervisionCC and saw the exact same behavior. I did change the light states individually on the two nodes in the log file so that can be seen working.

Logfile: zwavejs_1.log

[AlCalzone]

The command is being sent and we get confirmation from the stick, so I’d say it’s very unlikely that zwave-js is messing up here.

[AlCalzone]

Fix is up at #2194