name:Bulk set partial configuration parameters for a Z-Wave device (Advanced).
description:Allow for bulk setting partial parameters. Useful when multiple partial parameters have to be set at the same time.
target:
entity:
integration:zwave_js
fields:
parameter:
name:Parameter
description:The id of the configuration parameter you want to configure.
example:9
required:true
selector:
text:
value:
name:Value
description:The new value(s) to set for this configuration parameter. Can either be a raw integer value to represent the bulk change or a mapping where the key is the bitmask (either in hex or integer form) and the value is the new value you want to set for that partial parameter.
description:Allow for changing any value that Z-Wave JS recognizes on a Z-Wave device. This service has minimal validation so only use this service if you know what you are doing.
target:
entity:
integration:zwave_js
fields:
command_class:
name:Command Class
description:The ID of the command class for the value.
example:117
required:true
selector:
text:
endpoint:
name:Endpoint
description:The endpoint for the value.
example:1
required:false
selector:
text:
property:
name:Property
description:The ID of the property for the value.
example:currentValue
required:true
selector:
text:
property_key:
name:Property Key
description:The ID of the property key for the value
description:Whether or not to wait for a response from the node. If not included in the payload, the integration will decide whether to wait or not. If set to `true`, note that the service call can take a while if setting a value on an asleep battery device.
name:Set a value on multiple Z-Wave devices via multicast (Advanced)
description:Allow for changing any value that Z-Wave JS recognizes on multiple Z-Wave devices using multicast, so all devices receive the message simultaneously. This service has minimal validation so only use this service if you know what you are doing.
description:Forces Z-Wave JS to try to reach a node. This can be used to update the status of the node in Z-Wave JS when you think it doesn't accurately reflect reality, e.g. reviving a failed/dead node or marking the node as asleep.
name:Invoke a Command Class API on a node (Advanced)
description:Allows for calling a Command Class API on a node. Some Command Classes can't be fully controlled via the `set_value` service and require direct calls to the Command Class API.
target:
entity:
integration:zwave_js
fields:
command_class:
name:Command Class
description:The ID of the command class that you want to issue a command to.
example:132
required:true
selector:
text:
endpoint:
name:Endpoint
description:The endpoint to call the API on. If an endpoint is specified, that endpoint will be targeted for all nodes associated with the target areas, devices, and/or entities. If an endpoint is not specified, the root endpoint (0) will be targeted for nodes associated with target areas and devices, and the endpoint for the primary value of each entity will be targeted.
example:1
required:false
selector:
text:
method_name:
name:Method Name
description:The name of the API method to call. Refer to the Z-Wave JS Command Class API documentation (https://zwave-js.github.io/node-zwave-js/#/api/CCs/index) for available methods.
example:setInterval
required:true
selector:
text:
parameters:
name:Parameters
description:A list of parameters to pass to the API method. Refer to the Z-Wave JS Command Class API documentation (https://zwave-js.github.io/node-zwave-js/#/api/CCs/index) for parameters.