Best practice for updating z-wave device config options from an automation

Configuration Z-Wave
1

I have a scene controller z-wave device that has status LEDs and I want to update them based on the states of other devices. The LEDs are controlled by configuration parameters, so I’ve found 2 different ways to change their status (set_config_parameter on the device or zwave_js.bulk_set_partial_config_parameters on the entity). I wondered if one or the other is considered best practice, or if there are any performance implications or other things I should be aware of?

I find the set_config_parameter approach to be easier via the GUI automation editor.

For reference, here are examples of the generated YAML for the 2 approaches:

alias: led update based on bulk_set_partial_config_parameters
description: ""
trigger:
  - platform: state
    entity_id:
      - switch.patio_lights
    to: "off"
condition: []
action:
  - service: zwave_js.bulk_set_partial_config_parameters
    data:
      parameter: "2"
      value: 3
    target:
      entity_id: switch.scene_controller
mode: single

alias: led update based on set_config_parameter
description: ""
trigger:
  - platform: device
    type: turned_off
    device_id: ef...95
    entity_id: switch.z_wave_plus_700_series_on_off_switch_2
    domain: switch
condition: []
action:
  - device_id: 28...68
    domain: zwave_js
    type: set_config_parameter
    parameter: 3
    bitmask: null
    subtype: 3 (LED Indicator (Button 2))
    value: 3
mode: single
2

bulk_set_partial_config_parameters is used for partial parameters, which use bitmasks (multiple settings in one parameter). There’s no reason to use it for a non-partial (bitmask) value.