home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.11k stars 29.79k forks source link

Calling the zwave_js.multicast_set_value service with a light group containing a Z-Wave LR Dimmer switch fails #122817

Open foxxcomm opened 1 month ago

foxxcomm commented 1 month ago

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

service: zwave_js.multicast_set_value
target:
  entity_id: >-
    {{ expand(state_attr('light.testgroup',
    'entity_id')) | map(attribute='entity_id')| list }}
data:
  endpoint: "0"
  command_class: "38"
  property: targetValue
  value: 99

Anything in the logs that might be useful for us?

Logger: homeassistant.helpers.script.websocket_api_script
Source: helpers/script.py:2002
First occurred: 14:41:55 (1 occurrences)
Last logged: 14:41:55
websocket_api script: Error executing script. Error for call_service at pos 1: Unable to set value via multicast

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

home-assistant[bot] commented 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!

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. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


zwave_js documentation zwave_js source (message by IssueLinks)

AlCalzone commented 1 month ago

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.

foxxcomm commented 1 month ago

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.