SOLVED - Problems using Inovelli Black Dimmer (LZW31) with scene control

Configuration
1

Hello all. I have a few Inovelli Red switches (see my other post in the hardware section) and wanted to add some more, but found out that the Red series is done and the new Blue series has extremely limited availability. I did some research and found out that the older Black series had a firmware update that allowed limited scene control (single tap up and down and 2x tap on the config button). I successfully updated the firmware on my switch to 1.57, but the scene control doesn’t seem to show up in the Zwave JS integration logs. All I get is the following when I tap the paddle up and then down:

2022-12-28T13:21:46.639Z DRIVER « [Node 013] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 99
2022-12-28T13:21:48.793Z DRIVER « [Node 013] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 0

This is in contrast to the Red switches, which give me this output on a paddle down:

2022-12-28T13:26:22.705Z DRIVER « [Node 010] [REQ] [ApplicationCommand]
└─[CentralSceneCCNotification]
sequence number: 17
key attribute: KeyPressed
scene number: 2
2022-12-28T13:26:22.715Z CNTRLR « [Node 010] received CentralScene notification {
“nodeId”: 10,
“ccId”: “Central Scene”,
“ccCommand”: “0x03”,
“payload”: “0x118002”
}
2022-12-28T13:26:24.793Z DRIVER » [Node 005] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 27
└─[SupervisionCCGet]
│ session id: 35
│ request updates: true
└─[MultilevelSwitchCCSet]
target value: 255
duration: default
2022-12-28T13:26:24.800Z DRIVER « [RES] [SendData]
was sent: true
2022-12-28T13:26:24.816Z DRIVER « [REQ] [SendData]
callback id: 27
transmit status: OK
2022-12-28T13:26:24.838Z DRIVER « [Node 005] [REQ] [ApplicationCommand]
└─[SupervisionCCReport]
session id: 35
more updates follow: false
status: Success
duration: 0s
2022-12-28T13:26:25.641Z DRIVER « [Node 010] [REQ] [ApplicationCommand]
└─[BasicCCReport]
current value: 99
2022-12-28T13:26:28.073Z CNTRLR [Node 005] Scheduled poll canceled because expected value was received
2022-12-28T13:26:28.075Z DRIVER « [Node 005] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 98
2022-12-28T13:26:30.464Z DRIVER « [Node 010] [REQ] [ApplicationCommand]
└─[MeterCCReport]
type: Electric
scale: W
rate type: Consumed
value: 5.2
time delta: 0 seconds
2022-12-28T13:26:32.736Z DRIVER « [Node 005] [REQ] [ApplicationCommand]
└─[MeterCCReport]
type: Electric
scale: W
rate type: Consumed
value: 5.2
time delta: 0 seconds

Home Assistant is still able to see if the switch is on or off, and I can set up triggers with turning the switch on and off, but actually having the ability to use the limited scenes that the newer firmware enables would be really nice. I assume the problem is in the Zwave JS plugin that Home Assistant uses not recognizing the scene commands, but I’m not sure. Has anyone run into this issue and found a solution?

Thanks

2

The odd thing is that Zwave JS seems to be aware of firmware > 1.47 as configuration options 50-52 are only available “if: firmwareVersion >= 1.47” and these latest firmware updates enabled scene control on these switches.

Is there some setting on the switch that I’m missing? For reference, this is the thread that confirms scene control was added in 1.52:

3

Success! It turns out that the 1.56 and 1.57 drivers that I tried do NOT support the scene control. You have to use the 1.52 beta driver here:

https://files.inovelli.com/firmware/LZW31/Beta/1.52/

Specifically, the LZW31_1.52.otz file which I was able to flash to the device using Home Assistant (go to the Zwave JS integration, click devices, select the device, and then use the drop down next to the configure button to “Update”). I was unable to update the bin file, just the otz, but the bin file seems to just be the LED driver so just ignore that - it doesn’t matter. I also updated the switch close in proximity to the RPi that I use for Home Assistant, which makes it go much faster.

Anyway, after the update, I now get this in the logs:

2022-12-28T16:02:03.629Z DRIVER « [Node 013] [REQ] [ApplicationCommand]
└─[CentralSceneCCNotification]
sequence number: 26
key attribute: KeyPressed
scene number: 2
2022-12-28T16:02:03.637Z CNTRLR « [Node 013] received CentralScene notification {
“nodeId”: 13,
“ccId”: “Central Scene”,
“ccCommand”: “0x03”,
“payload”: “0x1a8002”
}
2022-12-28T16:02:04.593Z DRIVER « [Node 013] [REQ] [ApplicationCommand]
└─[MultilevelSwitchCCReport]
current value: 99

I am going to make a blueprint specifically for this switch and will post it as soon as I get it working.

1 Like
4

Please see the following post for my Blueprint for the LZW31 switch:

5

Just wanted to thank you for following up on this thread all by lonesome. It was just what I was searching for!

6

I’m not sure what happened but I used to be able to control my bath fan using the config button. I set up an automation to toggle on/off on press using the blueprint and it worked great. Until today I noticed it not working. Not sure what happened but I have been try to troubleshoot for some time now.

When testing the automation—> Here is an error I’m seeing on the automation trace:

Executed: March 22, 2024 at 7:58:04 AM

Error: UndefinedError: ‘dict object’ has no attribute ‘event’

Also physical pressing the config button doesn’t appear to do anything. I check logbook and nothing. I know it used to.

I even tried just doing an automation using the scene 3

Central Scene action on Endpoint 0 Scene 003 As a trigger and nothing when physically hitting the button.

Any thoughts?