Issue getting zwave.set_config_parameter to work

I am attempting to call the zwave.set_config_parameter service in an automation and I can’t seem to get it to fire, or show up in the OZW_Log. To troubleshoot, I’ve been trying to get the service call to work by calling it through the Services Developer Tool, with no luck either… I have been successful in changing the Zwave parameter on the node itself by using the Zwave Node Management Screen. This is the successful change of the parameter via the zwave management page.

2020-01-12 16:42:14.633 Info, Node010, Value::Set - COMMAND_CLASS_CONFIGURATION - LED Strip Intensity - 14 - 1 - 100%
2020-01-12 16:42:14.634 Info, Node010, Configuration::Set - Parameter=14, Value=10 Size=1
2020-01-12 16:42:14.635 Detail, Node010, Queuing (Send) ConfigurationCmd_Set (Node=10): 0x01, 0x0c, 0x00, 0x13, 0x0a, 0x05, 0x70, 0x04, 0x0e, 0x01, 0x0a, 0x25, 0xc3, 0x78
2020-01-12 16:42:14.635 Detail, Node010, Queuing (Send) ConfigurationCmd_Get (Node=10): 0x01, 0x0a, 0x00, 0x13, 0x0a, 0x03, 0x70, 0x05, 0x0e, 0x25, 0xc4, 0x75
2020-01-12 16:42:14.635 Detail,
2020-01-12 16:42:14.636 Info, Node010, Sending (Send) message (Callback ID=0xc3, Expected Reply=0x13) - ConfigurationCmd_Set (Node=10): 0x01, 0x0c, 0x00, 0x13, 0x0a, 0x05, 0x70, 0x04, 0x0e, 0x01, 0x0a, 0x25, 0xc3, 0x78
2020-01-12 16:42:14.644 Detail, Node010,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-01-12 16:42:14.645 Detail, Node010,   ZW_SEND_DATA delivered to Z-Wave stack
2020-01-12 16:42:14.796 Detail, Node010,   Received: 0x01, 0x05, 0x00, 0x13, 0xc3, 0x00, 0x2a
2020-01-12 16:42:14.797 Detail, Node010,   ZW_SEND_DATA Request with callback ID 0xc3 received (expected 0xc3)
2020-01-12 16:42:14.797 Info, Node010, Request RTT 161 Average Request RTT 166
2020-01-12 16:42:14.798 Detail,   Expected callbackId was received
2020-01-12 16:42:14.798 Detail,   Expected reply was received
2020-01-12 16:42:14.798 Detail,   Message transaction complete
2020-01-12 16:42:14.799 Detail,
2020-01-12 16:42:14.799 Detail, Node010, Removing current message
2020-01-12 16:42:14.799 Detail,
2020-01-12 16:42:14.799 Info, Node010, Sending (Send) message (Callback ID=0xc4, Expected Reply=0x04) - ConfigurationCmd_Get (Node=10): 0x01, 0x0a, 0x00, 0x13, 0x0a, 0x03, 0x70, 0x05, 0x0e, 0x25, 0xc4, 0x75
2020-01-12 16:42:14.806 Detail, Node010,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-01-12 16:42:14.807 Detail, Node010,   ZW_SEND_DATA delivered to Z-Wave stack
2020-01-12 16:42:14.975 Detail, Node010,   Received: 0x01, 0x05, 0x00, 0x13, 0xc4, 0x00, 0x2d
2020-01-12 16:42:14.976 Detail, Node010,   ZW_SEND_DATA Request with callback ID 0xc4 received (expected 0xc4)
2020-01-12 16:42:14.976 Info, Node010, Request RTT 176 Average Request RTT 171
2020-01-12 16:42:14.976 Detail,   Expected callbackId was received
2020-01-12 16:42:15.112 Detail, Node010,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x0a, 0x05, 0x70, 0x06, 0x0e, 0x01, 0x0a, 0x8c
2020-01-12 16:42:15.112 Detail,
2020-01-12 16:42:15.112 Info, Node010, Response RTT 313 Average Response RTT 311
2020-01-12 16:42:15.112 Detail, Node010, Refreshed Value: old value=0, new value=10, type=list
2020-01-12 16:42:15.112 Detail, Node010, Changes to this value are not verified
2020-01-12 16:42:15.112 Info, Node010, Received Configuration report: Parameter=14, Value=10
2020-01-12 16:42:15.112 Detail, Node010,   Expected reply and command class was received
2020-01-12 16:42:15.112 Detail, Node010,   Message transaction complete
2020-01-12 16:42:15.112 Detail,
2020-01-12 16:42:15.113 Detail, Node010, Removing current message
2020-01-12 16:42:15.113 Detail, Node010, Notification: ValueChanged

I have tried seeming every combination of formatting in the service data window and can’t even see anything show up in the logs. Ive also tried removing the optional size parameter which hasn’t made a difference.

node_id: 10
parameter: 14
value: 10
size: 1

I’ve also tried:

{
  "node_id": 10,
  "parameter": 14,
  "size": 1,
  "value": 10
}

I feel like if I can’t get it to work in the services UI page, it wont work as an automation action. What am I missing here? I’m on HA v0.103.6

What does your automation look like? Are you doing it via yaml or the UI?

As i mentioned in first post, I’ve tried various different formats for the data section to see if that was the problem, currently this is what I have set in my automation.

- id: '1578727093819'
  alias: Config Light
  description: Set Zwave alert trigger if any lights in the garage group are on.
  trigger:
  - event_data:
      node_id: 10
      scene_data: 8040
      scene_id: 2
    event_type: zwave.scene_activated
    platform: event
  condition: []
  action:
  - service: zwave.set_config_parameter
      data:
        node_id: 10
        parameter: 14
        value: 10
        size: 1

It looks ok, have you tried manually triggering the automation?

Manually triggering the automation does nothing, nothing shows up in the OZW log. But, I just got some help in Discord and sending this worked through the services, so I’m going to update the automation and hope that works.

node_id: 10
parameter: 14
value: "100%"

If anyones looking, here’s my completed working automation. I was unaware that modifying my OZW config to support this device (inovelli LZW31-SN-Dimmer) it would change the expected value from an int to a string. Here’s my working automation.

- id: '1578727093819'
  alias: Config Light
  description: Set Zwave alert trigger if any lights in the garage group are on.
  trigger:
#5 up in Bedroom
  - event_data:
      node_id: 10
      scene_data: 8040
      scene_id: 2
    event_type: zwave.scene_activated
    platform: event
  condition: []
  action:
  - service: zwave.set_config_parameter
    data:
      node_id: 10
      parameter: 14
      value: "100%"

(I also had an extra two spaces for the data block which was screwing things up… )

2 Likes

Good to know. I recently added the Inovelli stuff as well… I have set the led strip intensity via the control panel though. What I will say is that the notification automatons work as intended for me. Although there is no way to get feedback and determine what the config values are set at, which sucks.