HA ZWave service for multicast set value needs to be updated to reflect the latest API changes in ZWave JS

[nmeachen]

The problem

AlCalzone indicates that changes to the ZWave multicast functionality to support S2 Security may have resulted in a need to update the HA zwave_js.multicast_set_value service to reflect those changes.

What version of Home Assistant Core has the issue?

2023.3.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Z-Wave JS

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[nmeachen]

Associated Z-Wave JS PR, #5475

[mbbush]

I think this will require changes in https://github.com/home-assistant-libs/zwave-js-server-python, either instead of or in addition to changes to core.

I opened https://github.com/home-assistant-libs/zwave-js-server-python/issues/608 to track this there

[raman325]

I'll leave this open so that no dupes are created but see my response in the linked issue

[nmeachen]

This should be addressed by https://github.com/zwave-js/zwave-js-server/issues/894.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[nmeachen]

Multi-cast now works with S2 devices,