Inovelli Red/Black Series on/off or dimmer switch scene/action support LZW31 LZW30 LZW31-SN LZW30-SN

Blueprints Exchange
, ,
1

There are several for Inovelli this should cover all the options in one blueprint. Note things like config button scenes only work on the models that support that (per firmware logs). For black series dimmers you need a very specific version. This is laid out with fairly dynamic variables so adapting to other switches or the upcoming 2 in 1 should be pretty straightforward.

1 Like
3

Does anyone know how to adapt the blueprint to accept a list of switches to activate the exact same scene? That way, you don’t have to create duplicate automations for different switches. For example, you can open the garage door with say, 3 taps on the switch…but if you want 5 switches in your house to be able to do that, you need 5 duplicate automations each for a different device.

4

Add multiple: true in the device selector.

5

I have several LZW31 (Inovelli Black) dimmers. I’m trying to use this Blueprint to create triggers for simple up/down or Config button clicks.

I installed the Blueprint, I can create an automation and select my desired LZW31 devices as trigger device.

But the triggers never fire.

Some of my switches run Inovelli firmware 1.48, and some have the latest 1.57 firmware. Neither of the switches work with this blueprint.

I just removed and re-installed the Blueprint to make sure I have the latest version. But still no luck.

Any idea what I can do?

6

Hopefully this helps others… After spending quite a bit of time trying to figure out how to have multipress work at all, I found that it’s very straightforward, no blueprint needed.

Just create an automation, selecting the device, the trigger (scene 001 is button donw, 002 is button up, and 003 is the config button), and the value (dropdown list is easy to understand).

image
image656Ă—941 31.1 KB

1 Like
7

I’m trying to make the Config button work on a Black Series dimmer for quite a while now. Did some more testing today. First I had to find the right Firmware version, it turns out only version 1.52 actually shows the 3 “Central Scene” triggers shown above.
Then I created some test automations using each of those 3 scenes as triggers. Unfortunately none of the triggers ever fired.
Turning on Logging for Z-Wave, I found following log entry when I clicked my “Config” button:

2024-10-01T23:39:13.209Z SERIAL « 0x01110004003d096c011c055b033c8003be00f3                            (19 bytes)
2024-10-01T23:39:13.213Z SERIAL » [ACK]                                                                   (0x06)
2024-10-01T23:39:13.216Z CNTRLR   [Node 061] command was received at a lower security level than expected - disc
                                  arding it...
2024-10-01T23:39:13.219Z DRIVER « [Node 061] [REQ] [ApplicationCommand]                              [discarded]
                                  └─[SupervisionCCGet]
                                    │ session id:      28
                                    │ request updates: false
                                    └─[CentralSceneCCNotification]
                                        sequence number: 60
                                        key attribute:   KeyPressed
                                        scene number:    3

It looks like the Z-wave server discarded the command, as it didn’t send this command with the same security level as other commands.

Is there any way to change this in some z-wave config file to make it work with HA?