LR Multicast Not Functioning As Expected (ZVIDAR Z-CM-V01)

[alexschneider]

Checklist

• I have read and followed the above instructions

• 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 or the fix did not work.

Describe the issue

What is happening?
When sending a multicast command to raise/lower my shades they don't all raise or lower simultaneously.

What did you expect to happen instead?
All the shades raise/lower simultaneously

Steps to reproduce the behavior:
Send a multicast driver command commanding shades to raise/lower (I did so via homeassistant as shown):

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

Anything else we should know?

Software versions

Z-Wave JS UI:
zwave-js-ui: 9.14.6
zwave-js: 12.12.4
home id: 3806735750
home hex: 0xe2e62d86

Device information

I don't think it's device related but here's the info:

Manufacturer: ZVIDAR
Model name: Z-CM-V01
Node ID: 256-265

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

z-ui_current.log

[zwave-js-bot]

👋 Hey @alexschneider!

It looks like you attached a logfile, but its filename doesn't look like it a driver log that came from Z-Wave JS.

Please double-check that you uploaded the correct logfile. If you did, disregard this comment.

As a reminder, here's how to create one:

• Z-Wave JS UI
• Home Assistant Z-Wave Integration
• ioBroker.zwave2 Adapter

[alexschneider]

zwavejs_current.log
Take two for the file.

[AlCalzone]

Ok it does look like it mostly works, but the initial multicast frame is sent to the Z-Wave Classic broadcast node ID 0xff, not the Z-Wave LR broadcast node ID 0xfff.
Should be an easy fix, but you're dealing with frequently listening nodes (FLiRS), so I'm not sure this will work out of the box. At least there's some ongoing discussion in the Z-Wave alliance about ZWLR FLiRS and multicast.

[AlCalzone]

Escalated to an issue: #7016

[alexschneider]

I assume, if I was willing to add latency, that I could start by pinging all nodes prior to the multicast to wake them up. Will give that a try once the issue had been fixed.