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.
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.
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.
Done. You need to hit the “Request approval” button next time 
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
No:
Usually once a week, mostly at weekends.
1 Like
@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
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!
2 Likes
No, it is still there: I applied the bitmask again and I applied an advanced tag to the parameter without a bitmask (you can change this parameter after you’ve set the advanced mode in HABmin) :
Although we normally don’t add parameters which are not in the manual I approved this
Please (!) report back if the parameter works on this device or not.
Merging make take a while as Chris is on vacation.
I have set a reminder in my calender to otherwise remove this parameter in four weeks.
Thx.
I tested out two values this morning on my LZW30-SN switch and they worked (Red blinking and Green Blinking)
I believe he is away for 2 weeks without a working VPN.
1 Like
I’ve just installed two of inovellis new dimmer switches which just became available a few days ago.
I see someone has just added the dimmer to the database 12 hours ago, but I assume we also have to wait for Chris to be able to use these, is that right?
That is correct. The database is part of the binding. Chris is away on vacation until late next week. I would guess he will export the database at the end of next week.
After the build system picks up the changes you will then need to upgrade the binding to the snapshot version. Finally you need to delete and rediscover the Things.
No, the device is available since 20190930 in the database:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1118
and has been merged into the binding on 20191003:
https://github.com/openhab/org.openhab.binding.zwave/blob/master/src/main/resources/ESH-INF/thing/inovelli/lzw30_0_0.xml
1 Like
In that case they need to manually update their binding preferably using the script.
1 Like
Thanks for the reply guys.
This is a new v2 edition of the dimmer, just released this week. It’s a completely different model: LZW31-SN
I’ll wait for Chris to update the binding. just wanted to confirm. Thanks!
Please post your xml & a pdf of the manual. There are people other than Chris that can update the database but, AFAIK, only Chris can export it to OpenHAB.
This thread is about the LZW30, though.
The LZW31 is available in the database, but has not yet made it into the binding:
Next time please open a new thread.
1 Like
Sorry for the confusion. Will open a new thread next time, thanks!
1 Like