Instant Notifications All Switches Using Multicast on HA

Lighting General Discussion
29

Below is a quick guide to help anyone else who stumbles across this post.

  1. In zwavejs2mqtt, under store tab create a config under the root store folder
  2. Create the following files under the config folder, pasting the latest JSON from the associated link
    a. lzw30-sn.json (config json)
    b. lzw31-sn.json (config json)

It should look like this:

image
image1251×860 54 KB

Now we need to update the config files to give the ability to multicast the param with a single value:

For the on/off switch:

  1. Open the lzw30-sn.json created before
  2. Scroll to the bottom and after the JSON entry for 8[0x7f000000] add:
    "8": {
        "label": "Bulk set Param 8",
        "valueSize": 4,
        "minValue": 0,
        "maxValue": 100600575,
        "defaultValue": 0,
    }
  1. Save the changes

For the dimmer switch:

  1. Open the lzw31-sn.json created before
  2. Scroll towards the end of the file and after the JSON entry for 16[0x7f000000] add:
     "16": {
        "label": "Bulk set Param 16",
	    "valueSize": 4,
        "minValue": 0,
        "maxValue": 100600575,
        "defaultValue": 0,
     },
  1. Save the changes

Re-start zwavejs2mqtt and re-interview the nodes, and if it worked for the on/off switches you’ll see:

image
image1131×307 9.54 KB

And for dimmers it’ll be:

image
image1123×288 7.47 KB

Now you can use the multi-cast call to change notifications:

On/Off:

action:
  - service: zwave_js.multicast_set_value
    target:
      entity_id:
        - switch.garage_lights
        - switch.pantry_lights
    data:
      command_class: '112'
      property: '8'
      value: 16712960

Dimmer:

action:
  - service: zwave_js.multicast_set_value
    target:
      entity_id:
        - light.deck_lights_dimmer
        - light.front_lights_dimmer
        - light.garage_entryway_dimmer
    data:
      command_class: '112'
      property: '16'
      value: 16712960

As @firstof9 mentioned, zwavejs2mqtt will now be using your customized JSON config file for those devices and you’ll no longer get automatic updates for, so you’ll want to keep an eye on if these configs are changed in future. Hopefully there will be a longer-term fix that avoids the need for this workaround but for now it does the trick.

Really appreciate the help from all the folks involved!

6 Likes