New Inovelli Z-Wave On-Off switches (LZW30), Z-Wave integration with Openhab

bdm · September 23, 2019, 4:00am

Hello all,
I have recently received my order of the new inovelli z-wave on-off switches. I know getting something at the front end (pre-order) usually means compatibility challenges.

I reached out to them about a month ago about trying to ensure we get the information needed to use these switches in OpenHab. The response from Eric was:

[...] We have been working on integrations with various hubs. We should have full support from SmartThings, Hubitat, Homeseer, Fibaro, and some others upon launch. Most other hubs should support basic functionality with our devices as they use common z-wave command classes.

We are also working on the config files for open-z-wave which should cover several of the open source z-wave projects out there such has Home Assistant. I believe OpenHAB uses open-z-wave or something close so the conversion shouldn't be that difficult. That support should be available upon launch or shortly after.

When trying to add the device in openhab it states the device is not in the database.

What I’m wondering is if these config files automatically come from open-z-wave to openhab, if there’s somewhere I can get them and put together a database addition to help with this, or if I need to sit back and be patient.

I think the device ID is: 031E:0004:0001:1.11
Product page: https://inovelli.com/shop/smart-light-switches/zwave-smart-switches-gen2/pre-order-z-wave-on-off-switch-base-model/#hardware
(Of note, they specifically list openhab as compatible)

Thanks
Ben

sihui · September 23, 2019, 4:47am

You need to add that device to the database:

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide

openHAB has nothing to do with openzwave. The device needs to be in the openHAB Zwave database which is merged into the binding jar file.
To always have the latest device support you need to switch to the latest zwave snapshot binding.
Download the zwave snapshot binding and drop it into your addons folder after you uninstalled the current binding version through PaperUI or HABmin.

Bruce_Osborne · September 23, 2019, 9:33am

I know some other systems use ooenzwave. I used one of those systems and can assure you tge IH binding is superior. Our developer is a dedicated European Soace engineer. Early on he offered to collaborate and share with ooenzwave but they did not want that.

bdm · September 24, 2019, 1:55am

Thanks.
It looks like getting the latest zwave snapshot requires at the very least removing the previous zwave binding and reinstalling another one. Potentially the 2.5 snapshot binding won’t work in a stable way on a 2.4 installation, from some threads. Alternately, there is 5iver’s script to manually install the binding. His instructions were meant to adress a 2.3 -> 2.4 audience, where there were substantial changes in zwave, and suggested deleting and re-discovering all the items. My network is getting a bit large, and this represents an onerous task.
Is it really necessary?

Also, @sihui, your post seems to suggest (contrary to others) that the old binding doesn’t have to be removed before putting the snapshot binding into the addons folder. Is this the case? Can anyone out there attest to if the 2.5 snapshot binding works on a stable 2.4 installation?

I had been hoping it would be as simple as updating a database file.
I do have this tall stack of switches waiting to be installed, but I don’t really like moving to unstable builds (given my limited time to fix things I’ve broken).

Cheers,
Ben

Andrew_Rowe · September 24, 2019, 2:58am

I think it is just your zwave things that need deleted and recreated. your items will still be there

sihui · September 24, 2019, 5:18am

Of course not, you can’t have two zwave bindings running at the same time.

Yes, it does, but you may have to install the xstream dependency and the serial transport driver. Go through the manual steps from the script, it’s all there.

It’s even simpler, you just need to update a binding from an old version to a newer version.

Bruce_Osborne · September 24, 2019, 8:54am

That is also the case moving from 2.4 to a 2.5 version. The Things keep the same IDs so nothing gets broken.

bdm · September 25, 2019, 11:38pm

Interesting. It seems my imprecise language may have confused myself a bit. Items, defined in files, can stay as they are, it seems.
Z-wave binding needs to be deleted.
The individual Z-wave things - some people seem to say they need to be deleted. If they are deleted, but not excluded/rediscovered, does the underlying ID stay the same (used in my items files)? If this is the case, then it is much less onerous than I was thinking. I didn’t want to go around to all the z-wave switches/devices with my RPi on battery, excluding and re-discovering the things, then having to update all my items files.

Thanks

Bruce_Osborne · September 25, 2019, 11:42pm

The Things just need to be deleted & rediscovered, NOT excluded from the Z-Wave network.
They keep the same thingids but the new binding rediscovers them. Since the thingids are the same, the Item files do not need to be changed.

bdm · September 29, 2019, 8:09pm

OK, thanks.
I am now using an up-to-date 2.5 snapshot zwave module, and it didn’t hurt as much as I thought it would.

I’ve now signed up on Chris’ Cd-Jackson zwave database, have access, and have read a wide variety of threads explaining the process.
I have my xml file from /var/lib/openhab2/zwave (openhabian setup)
When I try to add a device and paste in the xml code, I get an ‘error parsing xml’ message, and the device doesn’t update.

Looking at the xml code, I’m exactly pasting it in from the openhab-created file, which is:

<node>
  <homeId>0xc3b69503</homeId>
  <nodeId>24</nodeId>
  <version>4</version>
  <manufacturer>0x31e</manufacturer>
  <deviceId>0x1</deviceId>
  <deviceType>0x4</deviceType>
  <listening>true</listening>
  <frequentlyListening>false</frequentlyListening>
  <routing>true</routing>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>
  <sleepDelay>1000</sleepDelay>
  <nodeInformationFrame>
    <commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
    <commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
    <commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
    <commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
    <commandClass>COMMAND_CLASS_TRANSPORT_SERVICE</commandClass>
    <commandClass>COMMAND_CLASS_VERSION</commandClass>
    <commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
    <commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
    <commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
    <commandClass>COMMAND_CLASS_SUPERVISION</commandClass>
    <commandClass>COMMAND_CLASS_SECURITY</commandClass>
    <commandClass>COMMAND_CLASS_SECURITY_2</commandClass>
    <commandClass>COMMAND_CLASS_SWITCH_BINARY</commandClass>
    <commandClass>COMMAND_CLASS_PROTECTION</commandClass>
    <commandClass>COMMAND_CLASS_APPLICATION_STATUS</commandClass>
    <commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>
  </nodeInformationFrame>
  <associationGroups class="concurrent-hash-map">
    <entry>
      <int>1</int>
      <associationGroup>
        <index>1</index>
        <maxNodes>0</maxNodes>
        <name>Lifeline</name>
        <profile1>0x0</profile1>
        <profile2>0x1</profile2>
        <commands>
          <commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
          <commandClass>COMMAND_CLASS_SWITCH_BINARY</commandClass>
          <commandClass>COMMAND_CLASS_PROTECTION</commandClass>
        </commands>
        <associations>
          <associationMember>
            <node>1</node>
          </associationMember>
        </associations>
      </associationGroup>
    </entry>
    <entry>
      <int>2</int>
      <associationGroup>
        <index>2</index>
        <maxNodes>0</maxNodes>
        <name>On/Off Control</name>
        <profile1>0x20</profile1>
        <profile2>0x1</profile2>
        <commands>
          <commandClass>COMMAND_CLASS_BASIC</commandClass>
        </commands>
        <associations/>
      </associationGroup>
    </entry>
  </associationGroups>
  <endpoints class="concurrent-hash-map">
    <entry>
      <int>0</int>
      <endPoint>
        <deviceClass>
          <basicDeviceClass>BASIC_TYPE_ROUTING_SLAVE</basicDeviceClass>
          <genericDeviceClass>GENERIC_TYPE_SWITCH_BINARY</genericDeviceClass>
          <specificDeviceClass>SPECIFIC_TYPE_POWER_SWITCH_BINARY</specificDeviceClass>
        </deviceClass>
        <endpointId>0</endpointId>
        <secureCommandClasses/>
        <supportedCommandClasses class="concurrent-hash-map">
          <entry>
            <commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>
            <COMMAND__CLASS__FIRMWARE__UPDATE__MD>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>4</versionSupported>
            </COMMAND__CLASS__FIRMWARE__UPDATE__MD>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
            <COMMAND__CLASS__DEVICE__RESET__LOCALLY>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
            </COMMAND__CLASS__DEVICE__RESET__LOCALLY>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
            <COMMAND__CLASS__MANUFACTURER__SPECIFIC>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <initSerialNumber>false</initSerialNumber>
              <deviceManufacturer>798</deviceManufacturer>
              <deviceType>4</deviceType>
              <deviceId>1</deviceId>
            </COMMAND__CLASS__MANUFACTURER__SPECIFIC>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_VERSION</commandClass>
            <COMMAND__CLASS__VERSION>
              <version>2</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <libraryType>LIB_SLAVE_ENHANCED</libraryType>
              <protocolVersion>6.4</protocolVersion>
              <applicationVersion>1.11</applicationVersion>
              <hardwareVersion>1</hardwareVersion>
            </COMMAND__CLASS__VERSION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
            <COMMAND__CLASS__ZWAVEPLUS__INFO>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <zwPlusVersion>1</zwPlusVersion>
              <zwPlusRole>ROLE_TYPE_SLAVE_ALWAYS_ON</zwPlusRole>
              <zwPlusNodeType>NODE_TYPE_ZWAVEPLUS_NODE</zwPlusNodeType>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__ZWAVEPLUS__INFO>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_APPLICATION_STATUS</commandClass>
            <COMMAND__CLASS__APPLICATION__STATUS>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
            </COMMAND__CLASS__APPLICATION__STATUS>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
            <COMMAND__CLASS__POWERLEVEL>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
              <powerLevel>0</powerLevel>
              <powerTimeout>0</powerTimeout>
            </COMMAND__CLASS__POWERLEVEL>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_BASIC</commandClass>
            <COMMAND__CLASS__BASIC>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__BASIC>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
            <COMMAND__CLASS__ASSOCIATION>
              <version>2</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <maxGroups>2</maxGroups>
            </COMMAND__CLASS__ASSOCIATION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
            <COMMAND__CLASS__CONFIGURATION>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
              <configParameters/>
            </COMMAND__CLASS__CONFIGURATION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_SWITCH_BINARY</commandClass>
            <COMMAND__CLASS__SWITCH__BINARY>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__SWITCH__BINARY>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_SECURITY</commandClass>
            <COMMAND__CLASS__SECURITY>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
            </COMMAND__CLASS__SECURITY>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_PROTECTION</commandClass>
            <COMMAND__CLASS__PROTECTION>
              <version>2</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <localModes/>
              <rfModes/>
            </COMMAND__CLASS__PROTECTION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_NO_OPERATION</commandClass>
            <COMMAND__CLASS__NO__OPERATION>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
            </COMMAND__CLASS__NO__OPERATION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
            <COMMAND__CLASS__ASSOCIATION__GRP__INFO>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
              <autoSubscribeGroups>
                <int>1</int>
              </autoSubscribeGroups>
            </COMMAND__CLASS__ASSOCIATION__GRP__INFO>
          </entry>
        </supportedCommandClasses>
      </endPoint>
    </entry>
  </endpoints>
  <nodeNeighbors>
    <int>1</int>
    <int>6</int>
    <int>9</int>
    <int>12</int>
    <int>20</int>
  </nodeNeighbors>
  <lastReceived>2019-09-28 22:18:58.891 UTC</lastReceived>

Looking superficially at it, there seems to be a missing , to correspond with the opening , but this is the way openhab made it. Is this the problem? Am I using the wrong XML file?
Looking at other threads, this ( /var/lib/openhab2/zwave ) seems to be the place others go for their files, and I do see an xml file for each zwave node.

Thanks for indulging my clumsy steps!

Bruce_Osborne · September 29, 2019, 8:25pm

You can try adding the missing </node> line. I have seen times where the beginning and ending node lines are missing.

bdm · September 29, 2019, 8:54pm

Putting at the very end gives me this error:

1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '95,1,1,2603)' at line 3

And when I look at the other xml files for correctly functioning nodes, I don’t see the closing .

Interestingly enough, when I look at the database devices list, LZW30 (The device in question) is now listed. I suppose either someone else put it in, or despite the error messages one of these attempts worked.

I’ll keep working on trying to configure this device up, then.

Bruce_Osborne · September 29, 2019, 9:01pm

LZW30-SN has been in the database (with warning errors) since 9/21 but is for a different specific device. Perhaps a different region.
The database reference is 0002:0001 Yours is 0004:0001. IF they are indeed the same model functionally your device could be added to that database entry.

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1113

bdm · September 29, 2019, 10:37pm

That’s correct - it’s a different device.
It’s for the same region
LZW30 is the base model
LZW30-SN is their ‘red line’, which includes scenes and notifications (and an energy monitor). There were some inconsistencies with the data on the open-z-wave alliance website and the inovelli manual for parameter 1 reflecting a dimmer rather than binary switch (I’ve emailed them about this), and I went with what is in the manual/ the database’s LZW30-SN settings as it made more sense.

Separately, I think the LZW30-SN entries for the endpoints/command classes are incorrect, as it doesn’t have any of them ‘secure’. These switches both support S2 security. https://products.z-wavealliance.org/products/3452
I’ve asked inovelli about these settings, as I can’t seem to make sense of which options to check for which command classes.

Now (I think that) I’m waiting for this device that I’ve created to be approved and built into the database, so that I can update and test it.

Bruce_Osborne · September 29, 2019, 10:49pm

The manual trumps zwave alliance, usually unless the manual is proven wrong. I ran into that with one of my cheap Chinese devices. Fortunately, our database was correct.

The database pulls that information from the xml file generated by OH.

sihui · September 30, 2019, 8:17am

Done. You need to hit the “Request approval” button next time

bdm · October 1, 2019, 5:24am

Thanks. I will look for this and do it next time.

It looks like the new device should be in the database, and I used 5iver’s script again today.
That was a bit of an adventure: Zigbee and Z-Wave manual install script
I imagine when I thought I had updated my zwave binding previously I was actually unsuccessful. Anyway, I’m fairly sure I’m using an up-to-date snapshot currently.
Deleting and re-adding the z-wave node seems to still have the device not recognized.
Looking at the database entry notes at the bottom, I thought this device should be in the snapshot I downloaded. https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1118
When I download the snapshot jar to my laptop, whoever, and open the archive, in the inovelli directory I only see the LZW30-SN device, not the LZW30 device.

Looking at the timestamps:
Approved on 2019-09-30 09:17:17, and last exported on 2019-09-30 09:17:19.
Seeing it was exported doesn’t necessarily mean it’s already included in the snapshot file, I assume then.
Is there a more efficient manner to test new devices being entered into the database? How often is the database being updated into the snapshot?

Thanks

sihui · October 1, 2019, 5:44am

No:

Usually once a week, mostly at weekends.

Python · November 1, 2019, 1:17am

@bdm can you explain the “LED Strip Effect” channel and an example command i can send to it to understand a correct value that uses all 4 bytes to control Color/Brightness/Duration/Effect

bdm · November 1, 2019, 5:27am

Hi @Python,
The LED Strip Effect currently seems to be partially implemented in the LZW30-SN (red/fancy) model, but not the basic LZW30 one I set up. I’m not entirely sure that the basic LZW30 switch supports it - it is variably documented - which is why I hadn’t put it in there.

I had emailed Eric at Inovelli about this channel, and he sent me a spreadsheet to calculate the value to be sent for any given effect. I still don’t know if it is just on the LZW30-SN, or if it also is on the basic LZW30 switch.

I am not sure if I can attach a spreadheet document here, so I’ll describe it instead, and you should be able to re-create it fairly easily.

B2: a text entry box. You could type in Red, Orange, Green, Blue, Pink, Yellow, Cyan
B3: =IF(B2=“Red”,1,IF(B2=“Orange”,21,IF(B2=“Green”,85,IF(B2=“Blue”,170,IF(B2=“Pink”,234,IF(B2=“Yellow”,42,IF(B2=“Cyan”,127,0)))))))
C2: text (number) entry box. I think the values are 1-10
C3: =C2 * 256
D2: Text entry for durations. Options are: 1-10 Seconds, 20, 30, 40, 50, 60 Seconds, 2-4 Minutes, Indefinitely
D3: =IF(D2=“1 Second”,1,IF(D2=“2 Seconds”,2,IF(D2=“3 Seconds”,3,IF(D2=“4 Seconds”,4,IF(D2=“5 Seconds”,5,IF(D2=“6 Seconds”,6,IF(D2=“7 Seconds”,7,IF(D2=“8 Seconds”,8,IF(D2=“9 Seconds”,9,IF(D2=“10 Seconds”,10,IF(D2=“20 Seconds”,20,IF(D2=“30 Seconds”,30,IF(D2=“40 Seconds”,40,IF(D2=“50 Seconds”,50,IF(D2=“60 Seconds”,60,IF(D2=“2 Minutes”,120,IF(D2=“3 Minutes”,180,IF(D2=“4 Minutes”,240,IF(D2=“Indefinitely”,255,0))))))))))))))))))) * 65536
E2: Text entry. Options are Slow Blink, Fast Blink, Strobe, Pulse, Solid
E3: =IF(E2=“Slow Blink”,3,IF(E2=“Fast Blink”,2,IF(E2=“Strobe”,2,IF(E2=“Pulse”,4,IF(E2=“Solid”,1,0))))) * 16777216

H1: Config Value (label)
I1: =SUM(B3:E3)

========
So, I1 displays the sum of all B3-E3, and the switch will then decode this to display the desired effect.
The color value is the color wheel value /128
The duration value is the number of seconds * 65536

Of note, the notification style seems to have some typos in it. There are two options with a value of ‘2’. I imagine one should read either zero or 5… I’m unable to test this currently.

The reason I didn’t code this into the z-wave database as I couldn’t decide how to go about it. If looking to have a more robust system that can’t be broken, I think we’d be limited to manually calculating each of the desired combinations, and entering them individually. Ugh. Perhaps one of the z-wave database gurus could chime in on if there is a way to programatically do this by simply choosing colours/durations/effect names/ etc, similar to what the spreadsheet would have you do.

The other option, potentially easier and leaving more freedom for the end user, is to simply pass on the number. The end user decides how to configure this, and the light switch tries to decode it, with openhab simply passing the value on.

==
Quickly creating some options from a spreadsheet, all at level 5:

52299009	Red Slow Blink 30 sec
35521793	Red Fast Blink 30 sec
35521793	Red Strobe 30 sec
69076225	Red Pulse 30 sec
18744577	Red Solid 30 sec
52299029	Orange Slow Blink 30 sec
35521813	Orange Fast Blink 30 sec
35521813	Orange Strobe 30 sec
69076245	Orange Pulse 30 sec
18744597	Orange Solid 30 sec
52299093	Green Slow Blink 30 sec
35521877	Green Fast Blink 30 sec
35521877	Green Strobe 30 sec
69076309	Green Pulse 30 sec
18744661	Green Solid 30 sec
52299178	Blue Slow Blink 30 sec
35521962	Blue Fast Blink 30 sec
35521962	Blue Strobe 30 sec
69076394	Blue Pulse 30 sec
18744746	Blue Solid 30 sec
52299242	Pink Slow Blink 30 sec
35522026	Pink Fast Blink 30 sec
35522026	Pink Strobe 30 sec
69076458	Pink Pulse 30 sec
18744810	Pink Solid 30 sec
52299050	Yellow Slow Blink 30 sec
35521834	Yellow Fast Blink 30 sec
35521834	Yellow Strobe 30 sec
69076266	Yellow Pulse 30 sec
18744618	Yellow Solid 30 sec
52299135	Cyan Slow Blink 30 sec
35521919	Cyan Fast Blink 30 sec
35521919	Cyan Strobe 30 sec
69076351	Cyan Pulse 30 sec
18744703	Cyan Solid 30 sec

Or all at level 10:

52300289	Red Slow Blink 30 sec
35523073	Red Fast Blink 30 sec
35523073	Red Strobe 30 sec
69077505	Red Pulse 30 sec
18745857	Red Solid 30 sec
52300309	Orange Slow Blink 30 sec
35523093	Orange Fast Blink 30 sec
35523093	Orange Strobe 30 sec
69077525	Orange Pulse 30 sec
18745877	Orange Solid 30 sec
52300373	Green Slow Blink 30 sec
35523157	Green Fast Blink 30 sec
35523157	Green Strobe 30 sec
69077589	Green Pulse 30 sec
18745941	Green Solid 30 sec
52300458	Blue Slow Blink 30 sec
35523242	Blue Fast Blink 30 sec
35523242	Blue Strobe 30 sec
69077674	Blue Pulse 30 sec
18746026	Blue Solid 30 sec
52300522	Pink Slow Blink 30 sec
35523306	Pink Fast Blink 30 sec
35523306	Pink Strobe 30 sec
69077738	Pink Pulse 30 sec
18746090	Pink Solid 30 sec
52300330	Yellow Slow Blink 30 sec
35523114	Yellow Fast Blink 30 sec
35523114	Yellow Strobe 30 sec
69077546	Yellow Pulse 30 sec
18745898	Yellow Solid 30 sec
52300415	Cyan Slow Blink 30 sec
35523199	Cyan Fast Blink 30 sec
35523199	Cyan Strobe 30 sec
69077631	Cyan Pulse 30 sec
18745983	Cyan Solid 30 sec

I just added the necessary parameter 8 to the zwave database entry for the LZW30 which would be needed to support this. Once the database has been updated (?this weekend), then if you update your zwave snapshot, you could give it a try. If, on the other hand, you have the LZW30-SN scenes+notification fancy switch, you may be able to try it right away - although you would probably need to manually go into the zwave archive file and modify the device file to remove the bitmask on parameter 8… It appears as that parameter wasn’t working on the LZW30-SN, @sihui had locked it off.

Hope this helps!