Open foxxcomm opened 1 month ago
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!
(message by CodeOwnersMention)
zwave_js documentation zwave_js source (message by IssueLinks)
As of today, node-zwave-js
does not support creating mixed LR and non-LR (mesh) multicast groups. If it would, the call would internally be translated into two singlecasts anyways, since LR and mesh are two different protocols.
If it would, the call would internally be translated into two singlecasts anyways, since LR and mesh are two different protocols.
@AlCalzone - Thank You for your continuing great work on Z-Wave JS! Agree with you when there is only 2x in the group. For larger groups of switches however, it would make sense to support someday if possible. Suggest adding a section in the documentation on current LR restrictions/quirks (No beaming, Mixed Multicast) and any others not well known.
The problem
Calling zwave_js.multicast_set_value to turn on or off a light group fails when the group contains a Z-Wave 800 LR dimmer switch. In the example provided, the light group contains 1x Inovelli VZW31-SN included as a Z-Wave 800 Long Range node and 1x Inovelli VZW31-SN included as a normal Z-Wave mesh node. Both dimmer switches are included in the same Z-Wave network. If the light group is modified to contain 2x Inovelli VZW31-SN dimmers included as normal Z-Wave mesh nodes, the service call works fine.
What version of Home Assistant Core has the issue?
2024.7.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Z-Wave
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zwave_js/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
Z-Wave integration is connected to latest version of Z-Wave JS UI (v9.16.3) running on a separate server via web socket:
Driver version: 13.0.2 Server version: 1.37.0 Home ID: nnnnnnnnnn Server URL: ws://10.24.11.9:3000