LZW31-SN Not updating LED after zwave command to do so

Sorting Category
1

I have an LZW31 controlling 2 smart bulbs. I wanted constant power to the smart bulbs so I disabled Local Control. Following the documentation here for ST, I first set Node Protection to “No Operation Possible” before realizing that no operation local or remote would be possible and subsequently set to “Protection by Sequence” which gives me what I want.

I had expected that “No Operation Possible” would render the scene control to still work, but it did not.

So with “Protection by Sequence”, the behavior is what I wanted: scene control…button press sends command to HA and HA controls the attached Zigbee lights.

The problem now is that with the switch proving constant power to the smart bulbs, the LED on the front panel is at constant ON…even when the lights are off. I tried to remedy the situation by adding to my ON and OFF automation, a command to change the brightness of the LED. It didn’t work. I tried writing to parameter 16 a color change; but yet again, no change.

I then changed the protection to “Unprotected” thinking it had something to do with that. But, still, change to the status LED do nothing. Even if I go to the Zwave Integration and manually set Node Configuration Options. To check that I wasn’t doing anything wrong, I sent status to a different LZW31 and it was doing what it is supposed to do; just not on the smart switch I want it to.

Any thoughts?

2

So I started playing with another LZW31 and messed it up too…and made it worse. The switch mentioned in my previous post now won’t take any commands. I could send a command to power off the switch’s load. The only thing it does now is send the scene commands for presses of the paddle.

I did capture a Zwave log trying to send a command to increase the light intensity when OFF. Note the ERROR at the bottom of the log. Something isn’t happy.

================

2020-06-02 21:38:00.377 Info, Node014, Value::Set - COMMAND_CLASS_CONFIGURATION - LED Strip Intensity (When OFF) - 15 - 1 - 100%
2020-06-02 21:38:00.377 Info, Node014, Configuration::Set - Parameter=15, Value=10 Size=1
2020-06-02 21:38:00.377 Detail, Node014, Queuing (Send) ConfigurationCmd_Set (Node=14): 0x01, 0x0c, 0x00, 0x13, 0x0e, 0x05, 0x70, 0x04, 0x0f, 0x01, 0x0a, 0x25, 0x6f, 0xd1
2020-06-02 21:38:00.377 Detail, Node014, Queuing (Send) ConfigurationCmd_Get (Node=14): 0x01, 0x0a, 0x00, 0x13, 0x0e, 0x03, 0x70, 0x05, 0x0f, 0x25, 0x70, 0xc4
2020-06-02 21:38:00.378 Detail,
2020-06-02 21:38:00.378 Info, Node014, Sending (Send) message (Callback ID=0x6f, Expected Reply=0x13) - ConfigurationCmd_Set (Node=14): 0x01, 0x0c, 0x00, 0x13, 0x0e, 0x05, 0x70, 0x04, 0x0f, 0x01, 0x0a, 0x25, 0x6f, 0xd1
2020-06-02 21:38:00.384 Detail, Node014, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-06-02 21:38:00.384 Detail, Node014, ZW_SEND_DATA delivered to Z-Wave stack
2020-06-02 21:38:00.437 Detail, Node014, Received: 0x01, 0x05, 0x00, 0x13, 0x6f, 0x00, 0x86
2020-06-02 21:38:00.437 Detail, Node014, ZW_SEND_DATA Request with callback ID 0x6f received (expected 0x6f)
2020-06-02 21:38:00.437 Info, Node014, Request RTT 59 Average Request RTT 68
2020-06-02 21:38:00.438 Detail, Expected callbackId was received
2020-06-02 21:38:00.438 Detail, Expected reply was received
2020-06-02 21:38:00.438 Detail, Message transaction complete
2020-06-02 21:38:00.438 Detail,
2020-06-02 21:38:00.438 Detail, Node014, Removing current messageA
2020-06-02 21:38:00.438 Detail,
2020-06-02 21:38:00.438 Info, Node014, Sending (Send) message (Callback ID=0x70, Expected Reply=0x04) - ConfigurationCmd_Get (Node=14): 0x01, 0x0a, 0x00, 0x13, 0x0e, 0x03, 0x70, 0x05, 0x0f, 0x25, 0x70, 0xc4
2020-06-02 21:38:00.444 Detail, Node014, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-06-02 21:38:00.444 Detail, Node014, ZW_SEND_DATA delivered to Z-Wave stack
2020-06-02 21:38:00.523 Detail, Node014, Received: 0x01, 0x05, 0x00, 0x13, 0x70, 0x00, 0x99
2020-06-02 21:38:00.524 Detail, Node014, ZW_SEND_DATA Request with callback ID 0x70 received (expected 0x70)
2020-06-02 21:38:00.524 Info, Node014, Request RTT 85 Average Request RTT 76
2020-06-02 21:38:00.524 Detail, Expected callbackId was received
2020-06-02 21:38:00.609 Detail, Node014, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x0e, 0x03, 0x22, 0x02, 0x00, 0xdf
2020-06-02 21:38:00.609 Detail,
2020-06-02 21:38:00.610 Info, Node014, Response RTT 171 Average Response RTT 655
2020-06-02 21:38:10.439 Error, Node014, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-06-02 21:38:10.439 Detail, Node014, Removing current message
2020-06-02 21:38:10.439 Detail, Node014, Notification: Notification - TimeOutA

3

The only thing I could do to recover was to remove the node and add it again after factory resetting the switch.

I suppose the only way around this is to disconnect the load wire from the switch and tie it to the “Line”. It seems this is the suggestion elsewhere. The only thing I didn’t expect was the switch to end up in-operative.

4

The current firmware does not have the ability to reflect dimmed state of smart bulbs. It can only reflect the state of the switch dimmer itself.

It does sound like (per other threads) this featureset might be being worked on:

Edit: It is also NOT recommended to dim the switch level on a smart bulb, but you can send the level of the bar through a command. I use ST so in Webcore I send setColor HSL (Hue, Saturation (no effect), Level)

5

Thanks. I disabled local control so there shouldn’t be an issue with the smart bulbs. And they are working fine. In fact the switch still sends scenes to the HA controller for automation processing.

But by trying to change the LED intensity manually through the HA controller (automation or Zwave command) I eventually caused the LZW31-SN to stop accepting zwave commands. I accomplished this on 2 separate switches I was experimenting on. I cleaned them both up through factory reset.

But in the end, I want to have control of the LED on the front panel and I do not want it on all the time. So I’ll be just pigtailing the load to the line and using the LZW31-SN as a controller. I would lose the power monitoring feature that seems nice but wasn’t the intent of the purchase.

I guess through this thread I was hoping to find out:

  1. Is there a simpler way to get the LZW31-SN to start responding again without factory reset.
  2. Is the front panel LED really locked out when local controls are disabled. Seems odd.

Thanks.

6
  1. Did you pull the front breaker thingy (I forget the name) to soft reset the switch?
  2. By sending a command to the switch uising setColor HSL command in ST, the level can be modified. I see that this is HA sub though, so I don’t have an answer as this was only recently added into the device handler for ST, it was not a feature at release.
7

Thanks for the tip. I didn’t try the “front breaker”. I didn’t think that would soft-reset the switch. I’ll give it a try.

As for the command to change the color, I used raw zwave commands from the zwave integration. I sent similar commands to another switch just to ensure the expectations were correct. When local controls are disabled, there is no control of the LED…at least with my LZW31-SN. I’ve read that in other places on this site. However, I’d be glad to be wrong. My current plan is to disconnect the load from the switch and tie it to the line.

Thanks for your help.

8

I’ve just screwed up two of my switches in the same way and pulling the air gap switch does not work to clear this problem.

9

Hello,

Could you start from the beginning and tell us what you have done specifically? The more details you provide the better we can help you.

10

Sorry. Was just posting that for posterity. I’ve been playing with the node_protection setting in Home Assistant and made 2 of my switches non-operable via zwave commands. Found another thread in the meantime which seems to suggest that this is a combination of a bug in older(?) switch firmwares when it is sent an outdated zwave protocol on the Home Assistant side. My current problem is not having a Windows PC to update the switches but that’s not a problem for this forum.